Work a project's document register

What is being asked of somebody, what is in force, and what was replaced, for one project.

The register is arranged by what it wants from you. The review queue and the gaps come first, because those are what somebody has to act on. Then what is in force. Then what has been replaced.

Everything that adds to the register, meaning an upload, a recorded link or a noted gap, is a button that opens a form when you ask for it. The record itself is the first thing on the page rather than the third.

Filing from storage

Sync is the main action here, because it is how most of a register gets filled. It sits at the top right rather than in a caption. The dry run on the project sync page shows exactly what filing would do before anything is written.

Superseding a document

Replacing a document is an act on a row. You open the form against the document you clicked, and it already knows which one you meant. The superseded document stays in the register, marked as replaced, because the fact that it was once in force is part of the record.

What the register feeds

A filed document is read for what it requires. Those requirements land in the constraint register and, where they gate an event, in the obligations register.