The Master Deliverables Register — MDR in engineering shorthand — is the single most important document control tool on an EPC or infrastructure project. It is the project’s contractual map of all technical documentation that must be produced, reviewed, approved and delivered. When it works, it gives the project director, the client, and the document control team real-time visibility of where every deliverable stands. When it fails — when it is incomplete, inconsistently maintained, or simply abandoned mid-project — the consequences cascade into approval delays, handover rejection, and contractual disputes.

This article provides a field-oriented guide to MDR structure, setup, maintenance and close-out, drawing on the realities of managing large document volumes on complex, multi-discipline, multi-contractor engineering programmes.

What Is the MDR and Why Does It Matter?

The Master Deliverables Register is a controlled list of all documents that the project is required to produce. Each line item in the MDR represents one deliverable: a drawing, a calculation, a specification, a procedure, a report, or any other technical document that forms part of the contractual scope. The MDR tracks:

• What the document is (number, title, document type, discipline)
• Who produces it (originator, responsible engineer)
• Where it is in its lifecycle (current revision, current status)
• When it is due (planned issue date per project schedule)
• When it was actually issued (actual issue date)
• Whether it has been reviewed and what the response was
• Whether it is required for handover and at what status

On a large EPC project, the MDR can contain anywhere from 2,000 to 30,000 line items. Managing it correctly at that scale requires discipline, clear ownership, an EDMS integration, and a regular review cadence throughout the project lifecycle.

MDR Structure: The Mandatory Fields

The MDR’s structure must be defined at project kick-off. Once documents start being produced, retroactively adding or restructuring fields requires MDR rework that can take days. The following fields are mandatory on any well-structured MDR:

Setting Up the MDR: The First 8 Weeks

The MDR should be baselined within the first 8 weeks of project mobilisation. This timeline assumes that the project scope is defined and that the contractual deliverable list is available. In practice, the deliverable list is often not complete at project start, which means the MDR must be set up with the documents that are known and expanded as the scope is confirmed.

The MDR setup process involves the following steps:

• Document list extraction: Extract the initial deliverable list from the contract, the project scope definition, and any applicable client document schedule. This becomes the seed list for the MDR.
• Discipline review: Each discipline lead reviews the deliverable list for their discipline, adds missing documents, removes documents that are out of scope, and confirms planned issue dates against the engineering schedule.
• Numbering assignment: The document control team assigns document numbers to all confirmed MDR items following the DCP numbering convention.
• EDMS synchronisation: Where the EDMS supports MDR functionality (Aconex has a native register; SharePoint requires custom development), the MDR is loaded into the EDMS so that document status updates flow automatically.
• Baseline freeze: The MDR is formally baselined and issued as a controlled document. Subsequent additions and deletions are managed through a formal change process with client notification where required.

MDR Maintenance: The Discipline That Separates Good Projects from Bad

The MDR is only useful if it is kept current. This sounds obvious; it is consistently where projects fail. The most common maintenance failures are:

• Delayed status updates: A document is issued but the MDR is not updated for two weeks. The MDR status does not reflect the actual document status, making it useless for reporting.
• Revision mismatch: The EDMS holds revision C of a drawing; the MDR still shows revision B. This discrepancy is discovered during a handover audit and requires rework.
• Undocumented additions: New documents are produced and loaded into the EDMS without being added to the MDR. The MDR completeness percentage becomes meaningless because the denominator is wrong.
• Review response not captured: A transmittal response is received with disposition code C (resubmission required) but the MDR is not updated. Six months later, the handover audit finds the document has never been resubmitted.

To prevent these failures, the Lead Document Controller should conduct a weekly MDR review during active project phases. This review checks that all documents issued in the previous week have been correctly updated in the MDR, that all outstanding review responses have been chased, and that the MDR completeness metrics are accurate for the weekly project report.

The MDR as a Project Control Tool

A well-maintained MDR is not just a document list. It is a project controls instrument. The metrics that can be derived from a live, accurate MDR include:

• Document delivery performance: percentage of documents issued on or before their planned date, by discipline and overall
• Review response rate: percentage of outstanding transmittals with responses received within the agreed response period — a key client performance indicator
• IFC readiness: percentage of documents at Issued for Construction status, by discipline — directly linked to construction schedule readiness
• Handover completeness: percentage of handover-required documents at their required final status — the critical close-out metric
• Overdue deliverables: number and percentage of documents past their planned issue date, by discipline — used for schedule impact assessment and resource allocation

These metrics should be reported weekly to the Project Director and the client. They give early warning of schedule risk and allow the project team to take corrective action before delays compound.

MDR and Handover: The Close-Out Perspective

The MDR is the foundation of the handover package. At close-out, the handover completeness check is essentially a verification that every line item in the MDR that has the “Handover Required = Yes” flag is present in the EDMS at the required final status, and that the document is complete, legible, and in the specified format.

Projects that maintain the MDR rigorously throughout the project can conduct this check in a matter of days. Projects that have neglected the MDR face weeks or months of remediation work: identifying missing documents, checking EDMS records against the MDR, chasing outstanding review responses, and preparing gap analysis reports for the client.

The operator’s acceptance team will typically use the MDR as the baseline for their incoming documentation audit. If the MDR is incomplete or inaccurate, the acceptance audit will fail and the handover will be delayed. For large projects, a delayed handover can cost the contractor millions in delay damages and retention withheld.

TERADOK’s Document Control Consulting service includes MDR setup, maintenance governance, and close-out preparation. Our Final Documentation & Handover service manages the complete handover package preparation from MDR completeness check to client acceptance.

MDR vs. MIDP: Understanding the ISO 19650 Equivalence

For projects operating under ISO 19650, the Master Information Delivery Plan (MIDP) serves the same function as the MDR. The MIDP is the ISO 19650 term for the master schedule of all information deliverables, and it contains essentially the same information as a well-structured MDR: deliverable identifier, title, discipline, information container type, level of information need, responsible party, planned and actual delivery dates, and delivery status.

On ISO 19650-compliant projects, the MDR and the MIDP are equivalent. Project teams that are familiar with traditional MDR management will find the MIDP straightforward. The key difference is that the MIDP is formally part of the BIM Execution Plan (BEP) governance framework and must be structured in accordance with the standard’s requirements.

For more on ISO 19650 implementation, read our detailed guide: ISO 19650 Information Management: The Implementation Guide.

Frequently Asked Questions about the MDR