Construction & engineering
Construction and engineering document management
Construction document management is a revision-control problem: work built to a superseded drawing is the single most expensive documentation failure on a site. The requirements are unambiguous current-revision marking, ISO 19650 naming, submittal and RFI tracking, and as-built records retained through the defects liability period.
Why documents are difficult in construction & engineering
Construction document management is a revision-control problem before it is anything else. Work built to a superseded drawing is the single most expensive documentation failure available on a site, and it happens through an entirely mundane sequence: a revision is issued, someone is working from a printout, and nothing in the process makes the difference visible. Every other requirement on this page is secondary to marking the current revision unambiguously.
The second characteristic is that the project team is not the organisation. A project involves the client, the designer, several contractors and a chain of subcontractors, all producing documents that end up in one record. Permissions therefore have to work across organisational boundaries, and the handover pack at the end has to be coherent to someone who was not involved in producing it.
Regulatory pressure
Three pressures that shape the configuration
ISO 19650 information management
What it requires. A defined information delivery process with a common data environment, a mandated file naming convention, and status codes indicating suitability for use — work in progress, shared, published, archived.
What it means for a document system. Naming is a compliance matter, not a preference: the convention encodes project, originator, volume, level, type and number, and it is what makes a drawing identifiable across organisations. Status codes then determine whether a document may be built from, which is exactly the distinction a document management system enforces through approval state.
Building safety and golden thread duties
What it requires. For higher-risk buildings, information about the design and construction must be created, maintained and handed over in a form that is accurate, accessible and up to date throughout the building’s life — the "golden thread" introduced by the UK Building Safety Act 2022.
What it means for a document system. Retention extends to the life of the asset rather than the life of the project, and the handover has to be usable decades later by people with no project context. That makes export completeness and format longevity design requirements rather than afterthoughts.
Contractual notice and limitation periods
What it requires. Standard forms — NEC, JCT, FIDIC — impose short notice periods for compensation events and claims, and limitation statutes set outer limits on liability, commonly six years for a simple contract and twelve for a deed.
What it means for a document system. Correspondence is evidence with a deadline attached, so the date a notice was issued and received must be recorded rather than inferred. And because liability runs for years after practical completion, the project record has to outlive the project team.
Capability mapping
Five capabilities mapped to construction requirements
Unambiguous current revision
Versions accumulate rather than overwrite, the current revision is marked unambiguously, and superseded revisions remain retrievable but clearly labelled. Watermarking carries the status onto printed copies, which is where the superseded-drawing failure actually occurs.
Submittal and RFI approval chains
Submittals and requests for information are workflows with dates that matter contractually. Step history records who reviewed what and when, reminders make an overdue response visible, and the record supports a delay claim rather than complicating one.
Cross-organisation permissions
Project folders scope access to the project team across organisations, with preview-only permission for parties who need to read a drawing but should not retain and reissue it. External signing links handle sign-off without provisioning accounts for every subcontractor.
Physical location tracking for originals
Signed contracts, as-built markups and statutory certificates often exist as paper originals. Document locations record which box, in which store, and every move it has made — so an original can still be produced when a claim arrives six years after completion.
OCR over site-captured paperwork
Delivery notes, inspection sheets and permits arrive as photographs from a phone. OCR makes them searchable by reference or date, which is what turns site paperwork from an unindexed pile into evidence.
Taxonomy
A starting folder taxonomy
Project — design
- Drawings by discipline and revision
- Specifications
- Design risk assessments
- Models and federated model records
- Technical queries
Project — commercial
- Contract and appendices
- Variations and instructions
- Compensation events and claims
- Payment applications and certificates
- Programme and progress reports
Project — site
- Submittals and approvals
- Requests for information
- Inspection and test records
- Permits to work
- Delivery notes and material certificates
Health, safety and environment
- Construction phase plan
- Method statements and risk assessments
- Incident reports
- Statutory inspections
Handover and asset record
- As-built drawings
- Operation and maintenance manuals
- Warranties and guarantees
- Statutory certificates
- Golden thread information
The handover branch is not a copy of the project folders — it is a curated subset assembled for someone with no project context, retained for the life of the asset rather than the limitation period of the contract. Treating it as a separate structure from the outset avoids assembling it under pressure at practical completion.
Worked example
A worked workflow: drawing revision issue and receipt
Step 1: Upload with the naming convention
The revision is uploaded against the ISO 19650 naming fields — project, originator, volume, level, type, number, revision — enforced as mandatory metadata rather than typed into a filename.
Step 2: Review and set suitability
The design lead reviews and sets the status code. A document at work-in-progress or shared status cannot be presented as published, so it cannot be built from.
Step 3: Issue and record receipt
The published revision is issued to the distribution list. Receipt is recorded per recipient, which is what makes "they were told" a fact rather than an assertion in a later dispute.
Step 4: Supersede and watermark
The previous revision is marked superseded and watermarked accordingly on any subsequent download or print, so a printout carries its own status.
Retention
Retention expectations
| Record class | Commonly applied period | What starts the clock | Source |
|---|---|---|---|
| Contract and contractual correspondence | 12 years where executed as a deed; 6 years for a simple contract | Practical completion or final certificate | Limitation Act 1980 (UK) and equivalents |
| As-built drawings and O&M manuals | Life of the asset | Not applicable — retained while the asset exists | Golden thread duties; client asset management requirements |
| Health and safety records for the construction phase | Commonly 3 years, longer where exposure is involved | End of the project | CDM Regulations 2015 and occupational exposure rules |
| Occupational exposure records (asbestos, silica, noise) | 40 years | Date of the last exposure record | Control of Asbestos Regulations 2012; comparable exposure rules |
| Payment applications and certificates | 6–7 years | Final account settlement | Tax and audit requirements |
| Statutory certificates and warranties | Life of the asset, or the warranty term plus a margin | Handover or warranty expiry | Building control and warranty terms |
These periods are indicative and must be confirmed against the jurisdictions, contract forms and building classifications you work under before you rely on them. Limitation periods differ between deeds and simple contracts, exposure records carry very long periods, and higher-risk buildings carry additional duties. Nothing here is legal advice.
FAQ
Construction & engineering document management: common questions
Does DocumentMS replace a common data environment?
It can serve as one for document-based information, and it enforces the naming and status discipline ISO 19650 requires. It is not a model federation or clash detection tool, so on projects with significant BIM coordination it sits alongside a model environment rather than replacing it — holding the documents, revisions, approvals and the asset record.
How do you stop work proceeding from a superseded drawing?
Three mechanisms together: the current revision is marked unambiguously, a document below published status cannot be presented as issued for construction, and downloads of superseded revisions carry a watermark. The last one matters most in practice, because the failure almost always involves a printout.
Can subcontractors access documents without accounts?
For signature, yes — a secure link scoped to one document in one request. For ongoing drawing access they need an account, but preview-only permission lets them read without retaining and reissuing copies, which is the usual concern.
How does the golden thread requirement affect retention?
It extends retention from the limitation period of the contract to the life of the asset, and it changes the audience: the information has to be usable by someone with no project context decades later. That makes handover pack curation and export format longevity design decisions rather than closeout tasks.
What happens to the project record when the project team disperses?
This is the strongest argument for a controlled repository on a project. Permissions attach to the project rather than to individuals, so access survives people leaving; the naming convention makes documents identifiable without tribal knowledge; and the handover branch is already assembled rather than reconstructed from someone’s laptop.
Dernière revue: 2026-09-01. Compare all ten industry configurations.