Beginner Guide to Construction Document Management

Situation

A 45-strong mechanical contractor in South London, about £18m turnover, mostly Cat A and Cat B office fit-out. They were on a £280k first-fix package for heating and chilled-water pipework on a £3.8m Cat B refurbishment. The programme was 16 weeks and ceilings had to close on floor two in week 6.

Files were “controlled” through email, a shared folder, and whatever was printed in the site office. No live drawing register existed on site.

What happened

Week 4, the architect issued revised coordination drawings. A chilled-water riser moved 600mm to clear a new structural beam. Rev P3 went out on a transmittal to the main contractor’s project manager. Rev P2 stayed pinned on the site office wall.

Five days followed where everyone did what they thought was right. Pipefitters installed 38 metres of chilled-water pipework to Rev P2. Brackets, fire-stop sleeves, and builder’s work holes all landed in the wrong line. Nobody checked a register because there wasn’t one, and the site team had no single place to confirm “this is the current drawing”.

Day six, a ceiling-void walkdown spotted the clash. Strip-out and re-install took eight working days. Labour cost £9,200. Wasted materials were £3,400. The bigger hit was the knock-on, drylining could not close the ceiling on floor two, so they ran six extra days of prelims at £1,100 a day and claimed £6,600 loss and expense. Total cost of one wrong revision was £19,200 on a £280k package.

The mechanical contractor tried to push the cost up the chain. The main contractor asked for one thing, the formal issue record showing when Rev P3 was sent to the mechanical site team. Nobody could produce it. All they had was an email thread and a photo of the old drawing on the wall.

The decision / the lesson

The fix was basic and it stuck because it was enforceable. They put one named document owner on the package and introduced three rules the next Monday.

• Register every issue. Each drawing goes on a register with drawing number, current revision, date received, and transmittal reference.
• Check before you start. The foreman checks the register before starting any new area, even if a drawing is pinned up.
• Kill superseded drawings fast. Old revisions come off the wall within 24 hours. The digital copy is clearly marked “SUPERSEDED” so nobody can open it and assume it’s current.

Those steps took about 20 minutes a week to maintain. They stopped “wrong-revision installs” because the team could prove what was current before labour hit the deck. They also cut the dead time spent hunting for drawings. Site staff typically lose about 30% of their week, roughly 12 hours, searching for or checking documents. That wasted time is where wrong revisions slip through.

Document management is storing and sharing project files, document control is the rules that make one approved version the only one anyone builds from.

Think of it like a cheque book. Storing the cheque stubs is management. Control is knowing who can sign, what value they’re allowed to sign for, and having a record you can prove later.

Document management

Storing, organising, and sharing project files so people can find them. It answers, “Where is the file?”

Document control

The rules, approval steps, and audit trail that govern a file from draft to archive. It answers, “Is this the right file to build from, and can I prove it?”

Common Data Environment (CDE)

The single controlled place where the project team stores and issues project information, so there is one agreed current version of each drawing, spec, RFI and record.

Audit trail

A time-stamped history of actions on a document, who uploaded it, changed it, approved it, issued it, and when.

Poor control turns into rework fast. On a £1.2m Cat B fit-out over 16 weeks, one wrong-revision install, like an electrician setting containment off an old reflected ceiling plan, regularly creates £15,000 to £25,000 of abortive work and re-sequencing, before you even start the argument about who pays.

Only build from documents in the Published state, because that’s the only label that proves the team has checked and approved what you’re about to install.

Think of it like a commercial kitchen. Prep food stays in the prep area, plated food sits on the pass waiting for the chef’s check, “service” food goes to customers, and yesterday’s batch goes into storage for traceability. Nobody serves food from prep, and nobody should build from a draft drawing.

Work in Progress (WIP)

Draft information still being developed by the author. Nobody outside that author team should build, order, or set out from it.

Shared

Issued for review and comment. The wider team can coordinate and mark up, but it is not approved for construction.

Published

Approved for construction use. This is the only state you treat as “the truth” for procurement, setting out, and installation.

Archived

Superseded or completed information kept as the record for audit, final account, and claims. Searchable, but never current.

A single “wrong-state” build can become a real money problem fast. A £40,000 M&E rework dispute is usually not about technical ability, it’s about proving what revision each party had on the day the work was done. If you can’t show when a drawing moved from Shared to Published, you end up paying for fixes you shouldn’t.

An official issue is a drawing or spec you can prove was sent, received, and at what revision.

Think of it like posting a parcel. Dropping it in a postbox moves it, but you can’t prove it arrived. Tracked delivery with a signature is proof. A transmittal is the tracked-delivery receipt for construction documents.

Version

Any saved iteration of a file, including drafts and internal edits. Versions are working history, not a green light to build.

Revision (Rev)

A controlled, numbered change to a drawing or specification that has been checked and approved for issue, like Rev 02 to Rev 03. The revision tells site which update they are building from.

Transmittal

A formal issue sheet that records exactly what was sent, sheet by sheet, including document number, title, revision, date, sender, recipients, and a transmittal number. This is what makes an issue defensible later.

Drawing register

A live list of every drawing sheet on the job showing the current revision and status, plus the last transmittal it was issued under, so teams can check what is safe to build from.

One wrong drawing revision can wipe out a week’s margin. On a £1.2m fit-out, an MEP crew building ductwork to Rev 02 instead of Rev 03 can trigger a £12,000 to £15,000 rework weekend and lose a week on the programme, then turn into an argument nobody can win because nobody can prove who had what.

Build your first register

Setting: a £1.2m Cat-B office fit-out, JCT Design and Build, 16-week programme. It’s week 2, trades are on site, and you already have 62 live files scattered across email chains and shared folders. You need a starter register that tells the team what exists, what state it’s in, and what is safe to build from.

Mechanics, step by step

1. Create six buckets that match site work, then give each a Doc ID prefix. The prefix stops “ceiling plan final FINAL.pdf” becoming your control system. On this job, your week 2 snapshot looks like this.

   Bucket	What goes in it	Doc ID prefix	Week 2 count
   Drawings and specs	Drawings and specifications, the written requirements	DRG	18
   Submittals	Shop drawings and product data for approval	SUB	11
   RFIs	RFIs, Requests for Information, formal questions	RFI	6
   Change management	Variation records, changes that affect time or money	VAR	4
   Field records	Daily diaries, inspections, snagging logs, defect lists	FRM	19
   Closeout	Handover pack, O&Ms, warranties, as-builts	CLS	4

2. Build the register with ten columns, then never change them mid-job. Changing columns in week 9 breaks filtering, reporting, and audit trail.

   Column	Example value	Why it matters
   Doc ID	DRG-017	Every argument ends at one reference.
   Doc type	Drawing	Fast filtering by what the team needs.
   Title	Level 02 reflected ceiling plan	Search works for site staff, not just designers.
   Package	Ceilings	Maps to trade scope and procurement.
   ISO state	Published	Shows if it’s safe to build from.
   Rev	P03	Stops rework caused by silent drawing changes.
   Owner	Design Manager	One named person to chase.
   Due date	Wk 3 Mon	Stops approvals drifting into the critical path.
   Transmittal no.	T-005	Proof of what was issued, to whom, and when.
   Link	/Published/DRG/DRG-017_P03.pdf	Keeps the team off email attachments.

3. Enter live documents using the four-state model. Work in Progress is draft. Shared is issued for review. Published is approved for construction use. Archived is retained for history and claims.

   Doc ID	Bucket	ISO state	Rev	Transmittal	Build from it?
   DRG-017	Drawings and specs	Published	P03	T-005	Yes
   DRG-018	Drawings and specs	Shared	S01	T-006	No
   SUB-004	Submittals	Shared	S02	T-007	No, don’t order until approved
   RFI-003	RFIs	Shared	S01	T-008	No, answer outstanding
   VAR-002	Change management	Work in Progress	W01	N/A	No, not agreed

4. Issue one “official” transmittal, then archive the superseded revision the same day. Example: Transmittal T-005 includes 7 sheets, including DRG-017 Rev P03, and goes to 9 recipients (ceiling foreman, M&E supervisor, setting-out engineer included). DRG-017 Rev P02 moves to Archived within 30 minutes of issue so nobody prints it again on Friday afternoon.

Takeaway

The non-obvious bit is that “ISO state” and “Transmittal number” turn document control into a build/no-build decision. A ceiling gang installing off DRG-018 in Shared state can burn £4,860 of labour in a day, then you pay twice when it has to come down and go back up. Your register prevents that by making “Published under T-xxx” the only answer the site accepts.

A £1.2m Cat-B office fit-out in Leeds, JCT Design & Build, 16-week programme. Week 4, the architect issues a revised core layout and the M&E subcontractor updates a ceiling coordination drawing after RFI 014 clears a clash. Two supervisors both download “the latest”, but one prints an older PDF because the filenames don’t sort or search the same way.

Worked example: one rule, plus one exception

1. Start with one naming rule for most documents. Use: ProjectName_DocumentType_Title_Date. Keep the order fixed and split with underscores so sorting works the same for everyone.

   Example for the core layout: LeedsHQ_DRG_CoreLayout_20260601.pdf.

2. Add a revision tag only for “living” documents. Drawings and submittals change, so add _Rev01, _Rev02, etc. Don’t use “FINAL” or “NEW”. They are opinions, not control.

   Example for the ceiling coordination update: LeedsHQ_DRG_CeilingCoordination_20260610_Rev03.pdf.

3. Keep document type codes short and closed. If you allow people to invent codes, you lose the whole point. Pick a small set and stick to it.

Date-first naming, only for time-series

4. Flip to date-first only when you search by date. Daily diaries, permits, inspection logs, and site reports are time-series. You don’t search those by title. You search “what happened on 11 June”.

   Use: YYYYMMDD_ProjectName_DocumentType_Title. Example: 20260611_LeedsHQ_RPT_DailyLog.pdf.

5. Prove the rule works with a 20-second test. Ask the site manager to find the latest ceiling coordination drawing by searching “CeilingCoordination”. Ask the QS to find it by filtering “LeedsHQ” + “DRG”. Both should land on LeedsHQ_DRG_CeilingCoordination_20260610_Rev03.pdf first time.

Takeaway

Most teams think the date is what makes a file “latest”. Revision control is what makes it safe to build from. Date-first naming is not “better”. It only fits time-series records where the date is the primary way you search, like daily reports and permits. Everything else wants a fixed pattern that sorts and searches the same way for every person, every time.

Document control works when one agreed system tells every trade what is safe to build from, and proves who saw what and when. Below is a worked one-page plan you can copy and adapt for your next pre-start meeting.

One-page document control plan: worked example

Project: Acme HQ Fit-Out, £4.2m Cat B, 22 weeks
Document controller: Sarah Patel (single named owner)
CDE rule: ISO 19650 four-state model. No file lives outside this structure.

Folder map (mirror in your CDE exactly)

Trade subfolders: M&E, Partitions, Ceilings, Joinery, Façade, Structural, Architectural. DocType subfolders: DRG (drawings), SPEC, RFI, TRANSMITTAL, SCHEDULE, O&M, TEST-CERT.

Register fields (minimum set, non-negotiable)

Naming convention, enforced without exception: ProjectCode_DocType_Title_YYYYMMDD_Rev##.pdf

Transmittal rules (paste these into your project preliminaries)

1. Published documents are issued by formal transmittal only. No email attachments, no WhatsApp photos.
2. Every transmittal lists each document by Doc ID, title, revision number, and ISO state.
3. The recipient confirms receipt within 48 hours. No confirmation = chaser at 72 hours, escalation to PM at 96 hours.
4. Superseded drawings move to S4-Archived on the same day the new revision enters S3-Published. The transmittal notes which revision is replaced.

Permission matrix by ISO state

The rule that matters most: Published is read-only for everyone except the document controller. No exceptions.

Closeout timeline (dated milestones)

What to learn next

• RFI and variation traceability, because one RFI (Request for Information) can trigger a revised drawing and a variation. You need one chain you can price and defend.
• Field mark-ups and as-builts, because if site changes stay on paper and WhatsApp, you will rebuild the record from memory at handover.
• Closeout pack structure for FM users, because O&Ms filed by trade suit builders, but facilities teams search by asset and location. The wrong structure delays sign-off and final payment.

Most rework starts with the wrong revision, not bad workmanship. A plumber installing to Rev 02 when Rev 03 was issued two weeks earlier is a fast route to £15,000 of abortive work and an argument nobody wins. Run the plan inside your CDE and keep it boring and enforced. In Archdesk this is the CDE setup with role-based permissions, version history, and approval workflows, so Published files are locked and every transmittal is time-stamped for audit and claims.