What is a master document register?
A master document register is the table that answers three questions for every controlled document: what document is this, which revision is valid today and what status is it in. It is the reference everyone checks before using a document.
The term is used in two contexts, and the difference matters:
- In a quality management system (QMS), the master list covers the organisation’s procedures, work instructions, forms and policies. The focus is knowing which version is in force and who approved it.
- In engineering, the master document register covers the drawings, specifications, datasheets, calculations and vendor documents of a project or facility. It tracks issues, revisions, client approvals and transmittals, and often doubles as the basis for measuring engineering progress.
You will also see it called the master document list (MDL), document register or, in Brazil, lista mestra de documentos (LMD). The register is a core piece of engineering document management and of the engineering document control process.
What is an MDR for?
- Knowing which revision is valid. Anyone using a drawing on site or in maintenance checks the register first.
- Planning engineering. The engineering register starts life with the planned documents and their planned issue dates.
- Measuring progress. Comparing planned and actual dates shows how many documents have been issued and approved.
- Managing vendors. It shows which vendor documents are missing, under review or rejected.
- Passing audits. It shows the auditor that documents are identified, revised, approved and available.
- Handing over. At the end, the register becomes the index of the documentation handed over to the asset owner.
How does the MDR relate to ISO 9001?
ISO 9001 is the requirements standard for quality management systems. In the 2015 edition, clause 7.5 covers “documented information” and sub-clause 7.5.3 covers its control. Guidance from ISO technical committee ISO/TC 176/SC2 explains that QMS documentation includes the documented information the standard requires plus whatever the organisation itself decides is necessary, and that all of it must be controlled in line with clause 7.5. The same guidance notes that documents can be in any medium: paper, electronic, photograph or master sample.
The standard does not require a register with that name. It requires control. The register is the most common way to show, in one table, that each document has a known identity, revision, approval and status.
On 16 September 2026 ISO published ISO 9001:2026, which replaces the 2015 edition. According to ISO, the new edition adopts the Harmonized Structure for management system standards and puts more weight on leadership, quality culture and risks and opportunities. Certified organisations should check clause numbering in the new edition when they update their procedures.
Engineering MDR versus QMS master list: what changes?
| Aspect | QMS master list | Engineering MDR |
|---|---|---|
| Documents | Procedures, instructions, forms, policies | Drawings, specifications, datasheets, calculations, vendor documents |
| Typical volume | Dozens to hundreds | Hundreds to tens of thousands per project |
| Who produces them | The organisation’s own departments | Disciplines, designers, EPCs and vendors |
| Revisions | Current version and approval date | Preliminary and issued revisions, with full history |
| Approval | Internal | Internal and by the client, with a return code |
| Link to delivery | Internal distribution | A transmittal for every send and every return |
| End use | QMS audit | Handover and operation of the asset |
In practice, an engineering MDR is a quality master list with many more columns and much more movement.
Which columns does an MDR need?
A well-built engineering register usually has four groups of columns:
- Identification: document number, title, discipline, document type, area or unit, vendor number where applicable. The number follows the project numbering system.
- Revision and status: current revision, revision date, status, which can be in progress, issued for approval, approved, approved with comments, rejected, cancelled or superseded.
- Planning: planned and actual date of each key issue, such as first issue and issue for construction.
- Traceability: last outgoing transmittal, return transmittal, return code, document owner.
Master document register template
| Number | Title | Disc. | Type | Rev. | Status | Planned issue | Actual issue | Outgoing transmittal | Return code | Return transmittal | Owner |
|---|---|---|---|---|---|---|---|---|---|---|---|
P123-U200-ME-DE-0012 | Pump house layout | ME | DE | B | Issued for approval | 10 Oct 2026 | 14 Oct 2026 | TR-P123-ABC-0047 | Pending | Designer ABC | |
P123-U200-ME-FD-0003 | Pump P-201 datasheet | ME | FD | 0 | Approved | 1 Sep 2026 | 5 Sep 2026 | TR-P123-ABC-0031 | Approved | TR-P123-OWN-0019 | Designer ABC |
P123-U200-EL-LI-0001 | Electrical load list | EL | LI | A | In progress | 30 Oct 2026 | Designer ABC | ||||
P123-U200-CV-DE-0004 | Pump P-201 foundation | CV | DE | 1 | Superseded by rev. 2 | 20 Aug 2026 | TR-P123-ABC-0025 | Approved with comments | TR-P123-OWN-0015 | Designer ABC |
Numbers, dates and transmittal references are fictitious. For a QMS, keep the identification, revision, status, approver and approval date columns, and replace the transmittal columns with “access location” or “distribution”.
Register statuses: a closed list
The status column only works with closed, defined values. A common engineering set:
| Status | Definition | Who sets it |
|---|---|---|
| Planned | In scope, not started | Planning |
| In progress | Being produced or internally revised | Designer |
| Issued for comment or approval | Sent to the client by transmittal | Document control |
| Approved | Returned without restrictions | Document control, from the return transmittal |
| Approved with comments | May proceed, with changes in the next revision | Document control |
| Rejected | Needs a new revision before use | Document control |
| Issued for construction | Final issue for site use | Document control |
| As built | Reflects what was installed | Document control |
| Superseded | A newer revision exists | Automatic, on the next issue |
| Cancelled | Out of scope; number never reused | Engineering management |
Names vary by client. What matters is that the list is the same for every discipline and vendor, and that each status change has a recorded source, normally a transmittal.
The MDR and engineering progress measurement
On many engineering contracts the register is also the basis for progress measurement. Each document gets a weight, and each issue milestone releases part of that weight: first issue, approval and final issue. Physical engineering progress is the sum of milestones achieved.
That has two practical consequences. First, the register must be complete from the start: a document added late shifts the measurement baseline. Second, actual dates must come from transmittals, not estimates, because measurement triggers payment. The weighting rules live in the contract; the register only applies them.
How to build an MDR step by step
- Start from scope. List every document the contract requires, by discipline and area.
- Number every row. Assign the number before the document exists. The sequence number is reserved.
- Define the possible statuses. A closed, defined list avoids variants like “appr.”, “OK” and “client approved”.
- Define who updates it. Document control updates the register from transmittals, not from conversations.
- Link the register to transmittals. Every send and every return updates revision, status and dates.
- Keep the history. Old revisions and cancelled documents change status; they are never deleted.
- Publish the daily version. People without system access need the updated register with its date.
Where do registers usually fail?
- Two registers. The designer’s spreadsheet and the owner’s disagree, and nobody knows which one is right.
- Late manual updates. Revision C is already on site but the register still shows B.
- Free-text statuses. Everyone writes status their own way and filters stop working.
- Vendor documents left out. These are exactly the documents missing at handover.
- Deleting superseded rows. The history disappears and audits cannot reconstruct what happened.
How should the register handle vendor documents?
Vendor documents are where most registers break down. Each equipment package can bring dozens of drawings, datasheets, manuals and test certificates, issued under the vendor’s own numbering and revision rules. Three practices keep them under control:
- Register them before they arrive. The purchase order lists the vendor documents required, and each one gets a row in the register with a planned date.
- Keep both identities. Record the project number and the vendor’s original number and revision in separate columns.
- Track them through transmittals. Each vendor submission and each return code updates the row, just like an internal document.
On projects for Brazilian owners, the register is usually called the LMD and the transmittal the GRD. The structure is the same; only the names change.
The register during asset operation
After construction, the register remains useful as the index of the asset’s documentation. In Brazil, for example, regulatory standard NR-13 requires each pressure vessel to have up-to-date documentation at the site where it is installed, including the manufacturer’s vessel record with the set of drawings and other data needed to monitor its service life, plus inspection reports and alteration or repair designs. Finding those documents quickly depends on a register that links each item of equipment to its documents. It is a frequent topic in fertilizers and chemicals.
When the register no longer fits in a spreadsheet, it should be generated by the EDMS. 29docs’ Greendocs implementation configures the register, transmittals and revision workflows in the system, and its independent consulting helps decide when and how to make that move.
Updated on .