System documentation

How the system works

The journey a project takes through the platform, drawn and described: where a project code comes from, what happens to a case and in what order, how a figure reaches the Office and what it carries with it, and what happens when a system the Office depends on is down, has changed, or was never connected at all.

This is the technical companion to the user guide. The guide explains how to do your job on a screen; this explains how the work moves. Neither assumes you have read the other.

1The shape of the systemWhat the platform holds itself, what it reads from elsewhere, and what it publishes.2How a project reaches the platformWhere a project code comes from, and what happens when the register does not have one.3What happens to a caseReceipt, acceptance, assessment, decision — and where the statutory clock runs.4How records reach the OfficeThree routes, one path: interface, controlled file, or an officer reading a letter.5How a project’s progress is recordedFinancial movement, physical progress, and what happens when neither moves.6When something is not thereWhat the platform does when a source is down, changes shape, or sends something wrong.7Who may do whatHow roles are held, changed and taken away, and the two things an administrator cannot do.8What makes a decision hold up afterwardsWhy the file cannot be edited after the fact, and what a certificate proves.