Document register template: know which file is current

Define references and statuses first

Choose a reference pattern that is short enough to use and distinct enough to avoid collisions. It might combine project, originator, document type and sequence, but every segment should have a stated meaning. Do not encode details that change often, such as the current status, into the permanent reference. Record revision separately so the same document can move through review without becoming a new item each time.

Agree a small status vocabulary before loading the register. Draft, For review, Accepted and Superseded may suit one team; another may have contract-defined codes that must be used exactly. Write down what each status means, who can change it and whether it permits issue or use. “Accepted” should not accidentally imply technical, legal or commercial approval beyond the authority of the reviewer.

Update the register at the hand-off point

Name the event that triggers an update: receipt from a supplier, internal issue, return from review or publication to an approved area. Record the relevant date and a concise review or approval note. Keep the file location specific enough for an authorised colleague to follow, but do not place sensitive access details in a broadly shared register. The register points to the controlled file; it is not a substitute for the repository, permissions or backup arrangements.

Use one owner for register quality and make contributors responsible for supplying complete information. Review duplicate references, missing revisions, unclear statuses and links that no longer resolve. When a revision is superseded, preserve its history in the appropriate location and make the current revision obvious rather than overwriting the evidence silently.

Fictional worked example

In the fictional North Quay project, Mina receives revision P01 of a mobilisation plan on 8 September. She checks that reference NQ-FIC-PMO-PLN-001 is unique, records Mina as document owner, sets the status to For review and points to the working-file location. After review, an authorised approver returns comments, so the item remains P01 and the note records the next review date. When P02 is issued, Mina updates the current revision and moves P01 to the team’s superseded area under its retention rules.

Keeping reference, revision and status separate means the team can identify the document, distinguish its editions and understand whether the current file is ready for its intended use.

Adapt without creating a shadow system

Before adopting this CSV, check the project’s contract, information-management plan and approved technology. If a client already has a controlled register, improve that process rather than creating a competing spreadsheet. Add fields only when they support a real hand-off or control, such as originator, work package, confidentiality or retention category. Assign any retention period through the organisation’s policy and obligations, not a generic template.

Source note

This template draws on the information-management principles in clause 7.9 of GovS 002, a standard for government bodies. Your own project requirements determine the controls you need. APM also lists document control among PMO services.