A drawing register tracks drawings and their revisions. A document register covers the wider controlled information set, which may include drawings, specifications, calculations, reports, schedules, manuals and certificates. A separate drawing register is useful when drawings have distinct issue, revision or site-distribution controls; otherwise drawings can be a filtered part of the master document register.
Every drawing is a document, but not every document is a drawing. That simple distinction explains most of the difference between the two registers.
What belongs in a drawing register?
A drawing register normally records drawing number, title, discipline, sheet or series, current revision, purpose of issue, issue date and the organisation responsible for the drawing. Site-facing registers may also record who received each revision and whether superseded hard copies were withdrawn.
What belongs in a document register?
A broader document register may include specifications, design calculations, reports, procedures, method statements, schedules, data sheets, manuals, certificates and correspondence records as well as drawings. It usually needs a document-type field so those populations can be filtered without being split into unrelated spreadsheets.
| Feature | Drawing register | Document register |
|---|---|---|
| Coverage | Drawings and sometimes models | All defined controlled document types |
| Key detail | Sheet, revision and issue status | Type, owner, workflow and status |
| Site use | Often central to current-for-construction control | Supports the wider project record |
| Relationship | May feed the MDR | May serve as the master index |
When a separate drawing register helps
- The project issues drawings far more frequently than other documents.
- Drawings use a specialist numbering or revision convention.
- Site teams need a simple current-drawing view.
- Printed copies must be distributed, recalled or stamped.
- The contract explicitly requires a drawing register.
Separation should not create two competing sources of truth. Define which register owns the current revision and how changes flow into the master record.
Avoid the duplicate-register trap
Problems appear when engineering maintains one drawing list, document control maintains another and the contractor keeps a third. Each may be internally tidy while disagreeing about the current revision.
Choose one authoritative source for document identity and current status. Create filtered views for different teams rather than uncontrolled copies wherever possible. If separate registers are required, reconcile their shared fields on a defined schedule.
Check the register against the files
A correct register does not prove that the issue folder contains every listed drawing. Before pricing, construction or handover, compare the selected register rows with the actual package. Investigate missing PDFs, duplicate document numbers, old revisions and files that are not listed.
When Deliverable Preflight helps
Export either register to CSV or XLSX and compare it with the assembled folder. Exact Filename mode suits packages with controlled complete filenames. Document Number in Filename mode helps when drawing filenames contain extra descriptive text.
Deliverable Preflight reports missing, unexpected and ambiguous files without renaming or moving the source package.
View Deliverable Preflight in Microsoft Store →Related guides
Continue with controlling superseded drawings or review filename and document-number matching.
Further reading
Questions people ask
What is the main difference between a drawing register and a document register?
A drawing register is limited to drawings, while a document register can cover the full controlled document population, including drawings, specifications, reports and certificates.
Can drawings stay in the master document register?
Yes. Many projects keep drawings in the MDR and create a filtered drawing view rather than maintaining a separate source of truth.
Who should own the current drawing revision?
The project procedure should name one authoritative system or role. Separate uncontrolled spreadsheets should not compete over the current revision.