Construction document control without another subscription

Document control is a register, not a folder: every document has a number, a current revision, a status and a record of who it went to. If your firm already pays for Microsoft 365 with SharePoint, you can build a workable register there. When you need generated transmittals, outside reviewers and reports across projects, you need a purpose-built tool.

Field guide · Construction project managers · SharePoint · Published · Get the PDF

Long exposure of a room of plan tables at night: a clean outline of light fitted around a looping band, closed by a blue period

Why does document control keep slipping?

  • Email becomes the transmittal. Documents arrive and leave as attachments, so the inbox ends up as the only record of what was issued.
  • Folders hold files, not status. A folder can’t tell you that a drawing is superseded, under review or issued for construction.
  • Naming drifts. “A-101 Rev C final,” “A101_RevC (2)” and “A-101 C issued” are the same sheet.
  • Too many parties. The architect, consultants, subs and owner each have their own systems.
  • Nobody owns it. On smaller jobs, it is a slice of the project manager’s week, often done last thing on a Friday.

How do you set it up yourself in SharePoint?

  1. Write the numbering rule down first. For example: project number, discipline letter, sheet number, as in 2417-A-101. Put the rule, the status list and who approves what on one page.
  2. Create one document library per project. Keep the library for controlled documents only. Working files and photos go elsewhere.
  3. Add columns for what a folder can’t hold. Open the library, select + Add column to the right of the last column heading, pick the type, name it and select Save. Add a drop-down list for Status (for review, approved, issued for construction, superseded), one for Discipline, a text column for Revision and a date column for Date issued.
  4. Turn on versioning. Select the Settings gear, then Library settings, then Versioning settings. Microsoft lets you keep major versions only, or major and minor versions, where minor versions are drafts. You can also set who can see drafts, so the field sees only what’s been published.
  5. Require approval before anything is visible. On the same Versioning settings page, Microsoft offers “Require content approval for submitted items.” Use it so a document isn’t treated as issued until the person who approves it has done so.
  6. Use required check-out with care. The same page offers “Require documents to be checked out before they can be edited.” It stops two people overwriting each other, but Microsoft notes that people can’t work on a document at the same time while it’s on, and only users with Full Control or Design permissions can set it. Use it for drawings and the register, not for documents your team writes together.
  7. Save a view for the field. Filter the library to Status equals issued for construction and save it as a view. That link is the only one the field gets.
  8. Keep a transmittal log. A simple list with date, documents and revisions sent, sent to, method and acknowledged. It is the record you will want in a dispute.

Requests for information (RFIs) and submittals are a close cousin of this problem, with their own review cycles. See RFI and submittal tracking.

What are your options?

OptionGood whenWatch for
Do it yourselfA small internal team and a handful of live projectsIt works only as long as everyone follows the rule
Buy a toolYou want a standard method and outside parties will work inside itAnother subscription, access for outside parties, getting your records out at the end
Hire a freelancerYou have a clear method and want it set up properly onceAutomations tied to one person’s account, documentation, who maintains it
Bring in an outside team (Custom software)Outside parties need to upload and review, you want transmittals generated, or you want reports across projectsTime from a project manager during setup; agree on ownership in writing

FAQ

Is SharePoint enough for construction document control?

For a small team with a few live projects, often yes, if everyone follows one numbering rule and the library is set up as above. It struggles with outside parties, generated transmittals and reporting across projects.

Can we keep our shared drive and add a register on top?

Yes. Many firms keep files where they are and add a register that records number, revision, status and who received each issue. The register is what makes it document control.

Should we turn on required check-out?

Only where overwrites are a real risk. It prevents two people editing the same file, but it also blocks working on a document together, and forgotten check-outs hold up the team.

Does document control replace RFI and submittal tracking?

No. They overlap, because RFIs and submittals produce documents, but each has its own review cycle and deadlines. Many firms set up document control first because every other process depends on knowing the current revision.

Sources

Have one problem in mind?

Walk us through it on a free 30-minute call. Within two business days you get a one-page note on what we’d fix first, yours to keep.

Walk us through one problem