The master document register controls what documents are expected, which revision and status are current, who owes the next action and what was formally transmitted. It is not just a file list; it is the reconciliation layer between document identity, review, issue and receipt.
The short answer
Create one register row per governed document identity, not per file copy. Record title, information kind, discipline, originator, responsible reviewer, planned and actual dates, current revision, purpose/status, review code and linked file. A transmittal freezes an explicit set of document revisions sent to named recipients for a stated purpose. Record issue time, channel, receipt and response; never update the historic transmittal when a new revision is issued. Reconcile overdue, rejected, superseded, missing and handover-required documents continuously.
- The MDR describes expected and current document state.
- A transmittal is an immutable record of a specific issue set.
- Revision and status mean different things and are both controlled.
- Receipt, review response and supersession remain traceable.
Decision guide
| Record | Primary purpose | Must not change after issue |
|---|---|---|
| MDR row | Current plan and state of one document identity | Historical revision events |
| Revision record | Content issue with status and file | Released binary and checksum |
| Transmittal | What was sent, why, when and to whom | Document/revision membership |
| Review response | Recipient decision and comments | Original response evidence |
A practical workflow
- 01
Define document scope, identity, metadata, statuses, review codes and owners.
- 02
Load the planned MDR and validate required documents, dates and dependencies.
- 03
Create, review and release controlled revisions with immutable files.
- 04
Issue an immutable transmittal and record secure receipt and response.
- 05
Reconcile status, overdue actions, supersession and final handover manifest.
Evidence and acceptance
Retain MDR versions, document IDs and metadata, originator and reviewer, planned/actual dates, current and prior revisions, issue purpose and status, review codes and comments, file checksums, transmittal number and immutable membership, recipients, timestamp, delivery and receipt, responses, resubmission links, supersession, exception log and handover reconciliation.
Common mistakes
- Creating a new MDR row for every revision.
- Editing a historic transmittal to point to a newer file.
- Using status and revision interchangeably.
- Marking sent without recipient and receipt evidence.
- Closing the project without reconciling the MDR and handover package.
Responsibility boundary
Primary sources
Technical claims and product boundaries were checked against these primary sources. Fact-checked
Frequently asked questions
Is an MDR a folder index?
No. It controls planned and actual state, responsibilities, dates, revisions and review outcomes for governed documents.
Can a transmittal contain links?
Links can deliver files, but the transmittal must preserve immutable identity, revision and membership even if links expire.
What happens after rejection?
The response remains immutable; a corrected revision is reviewed and issued through a linked new transmittal.
Does AutoNexit replace contractual document control?
It provides controlled records, while the project defines contractual authorities and acceptance.