Revision C on the wall, revision E in the inbox
The architect issued a revised ground floor plan on Thursday. The door into the plant room moved and a partition changed. The drawing went to your document controller, who uploaded it and emailed the issue sheet to the site manager. The site manager printed it and put it in the drawings rack. The drylining foreman still had revision C in his van, marked up with his own notes, and set out from that on Monday.
Nobody did anything wrong in their own terms. The new drawing was issued and filed. It just never reached the person who needed it, in a form they would notice.
Why old revisions survive
Drawing issue is designed to record that a drawing was sent. It is not designed to make sure the right person on site knows what changed. A transmittal lists sheet numbers and revision letters; it does not say that a door moved, and it does not tell the dryliner specifically.
- Issue sheets list revisions, not what actually changed.
- Printed copies spread across cabins, vans and site offices.
- Subcontractors download their own copies at different times.
- Nobody records which trades have seen a revision.
- Mark-ups on old prints feel more useful than a clean new sheet.
What building from old drawings costs
Rework is the obvious one: partitions taken down, services moved, openings re-formed. Then the argument about who pays, which depends on whether the subcontractor was properly told. Programme time is lost while it is sorted out. On a larger job, the time your document controller and site manager spend reconciling who has what is a hidden cost every week.
The drawing register we build
- Each drawing issue, whether from email or your document platform, is read and the register updated: sheet, revision, date, status such as for construction.
- The revision note on the drawing, and where it helps, a comparison with the previous revision, is used to summarise what changed in plain words for the site team to check.
- Each sheet is tagged to the trades and areas it affects, so the right subcontractors are told about the change, not everyone.
- Affected trades receive a short message: which sheet, what changed, and a link to the current revision. They acknowledge it with one tap.
- Site tablets and phones show only the current revision, with superseded ones clearly marked if opened.
- The site manager sees who has not acknowledged a change and can chase before work starts in that area.
- Printed sets can be listed by location, so old prints are replaced when a revision lands.
| What site needs to know | Traditional issue | Drawing register |
|---|---|---|
| Which sheets changed | Transmittal list | Listed per trade |
| What changed on them | Revision cloud, if noticed | Plain summary to check |
| Who needs to know | Everyone on the list | Tagged trades and areas |
| Have they seen it | Unknown | Acknowledgement recorded |
| Is this print current | Check the letter by hand | Current revision on the tablet |
Where you use a common data environment, it stays the master. We add the site-facing part that tells people what changed.
A site working from the same sheet
When a revision lands, the trades it affects know within the day, and they know what changed rather than just that something did. The site manager can see who has acknowledged and who has not. If a trade still builds from an old drawing, there is a clear record of when they were told. Document control stops being a filing job and starts protecting the programme.
Is this happening on your sites?
- Trades have been found working from old revisions.
- Printed drawings are spread across vans and cabins.
- Revision issues do not say what changed in plain words.
- You cannot say which subcontractors have seen a revision.
- Rework from old drawings turns into arguments about who pays.