Document control
Drawing Revision Control on Construction Sites
Set up a drawing revision release process in a common data environment, check offline copies and keep superseded drawings away from workfaces.
The latest upload and the drawing the site is authorised to build from can be different files. A design team might issue a revised layout for coordination while the site is still working to the previous authorised revision. If the tablet syncs the new drawing over the old one without showing the intended use, the crew has to guess. Give the supervisor one reliable way to answer: which revision covers my work area, and am I allowed to build from it?
Make the work package the unit of issue
Start with a package identifier and a named owner. List the sheets, models and written instructions it depends on. For each item, record the identifier, revision, status or permitted use, issuer and date. Agree the project's terms for information states and revision codes in the information protocol. Avoid treating a vendor folder name or a green icon as confirmation that a sheet is authorised for construction.
After a new issue, compare the revised sheet with the previous authorised version. Tag the affected locations and identify changes to interfaces, purchase orders or work already installed. Ask the responsible technical lead to resolve conflicts between drawings before the affected work proceeds. Issue a brief sheet list to the supervisor and confirm the crew can open it on the device they use at the workface.
Worked example — an updated ceiling plan
A ceiling plan moves an access hatch in Zone C. The coordination issue includes a new ceiling plan and an unchanged service layout. Comparing drawings shows that the hatch no longer aligns with a valve. The package owner records an exception for Zone C, checks whether unaffected zones can proceed under the approved issue and asks the designers for a coordinated decision. Once issued, the revised sheets are checked on one tablet in offline mode and outdated prints are collected. Record the sheet numbers and acknowledgements so the site can reconstruct what happened.
Before releasing the package
- Check the revision and status of each dependency against the agreed issue register.
- Record who authorised the package, the effective date and any excluded locations.
- Notify crews and suppliers whose work, fabrication or delivery is affected.
- Test an offline device and check a printed copy. Record how you removed stale copies from use while preserving the archive.
Video walkthrough
Open the file comparison lesson. Compare the same sheet at two revisions and note which differences affect a live work area. Write a release note that states who needs to act and by when.
Watch: Compare files and review changes in Forma Data Management