Every rework story I've ever heard starts the same way: somebody built it right, off the wrong set. The drawing was superseded three weeks earlier, the current revision was sitting in an email nobody forwarded, and the crew found out when the inspector walked the corridor and the door swings were backward. Now you're demoing framing that passed rough-in, chasing a change order that should have been free, and explaining to the owner why the schedule just moved.
Document control is the boring discipline that quietly decides whether a job runs clean or bleeds money. It isn't glamorous. Nobody puts "kept everyone on the current set" on their resume. But get it wrong and it shows up as demolished work, blown inspections, and arguments over who owed whom what. This is a field problem as much as an office one, and field management software is only useful here if it does the unglamorous work of making sure the right paper reaches the right hands at the right time.
Why document control is really a field problem
The office usually knows what the current revision is. The trailer has the transmittal log, the architect's most recent issue, the RFI responses filed by number. The problem is the last hundred feet — the gap between what's official and what the guy with the drill actually pulls out of his truck.
Field crews are pragmatic. A foreman who has a printed E-2 taped to a stud is going to build off that E-2 until somebody physically stops him, because that's the drawing in front of him and he has production to hit. He isn't refreshing a portal between conduit runs. So the real question isn't "do we have good document management?" It's "when a drawing changes, how many hours pass before the person installing that scope is working off the new one?" If the answer is measured in days, you have a control problem no matter how tidy your server folders look.
That's why mobile access matters more than any other single feature. When the current set lives on the phone in every foreman's pocket, and the superseded sheets are visibly stamped VOID or simply gone, you close that last-hundred-feet gap. Paper in the truck is a snapshot from whenever it was printed. A drawing pulled fresh on a phone is current by definition.
Version control: one source of truth, everything else stamped dead
Most bad document control isn't caused by having no system. It's caused by having several. There's the FTP the architect uses, the shared drive the PM keeps, the folder the sub downloaded once in March, and the printouts in three trailers. Each is internally consistent and none agree with the others.
The fix is not more folders. It's a single authoritative set that everyone reads from, with old revisions handled ruthlessly:
- One current set, one place. If someone has to ask "is this the latest?" the system has already failed. Current should be obvious and superseded should be either removed from circulation or clearly overstamped.
- Revisions carry their reason. A drawing that changes should tell you what changed and why — ASI, bulletin, RFI response, addendum. "A2.1 Rev 3" means nothing. "A2.1 Rev 3 — clouded for ASI 14, corridor rated wall added" means a foreman can decide in ten seconds whether it touches his work this week.
- Old sets don't just disappear silently. You keep them for the record — you'll need them in a claim — but you get them out of the working view so nobody builds off them by accident.
The trap to avoid is treating every issue as a full reprint of the whole set. When the architect reissues 40 sheets and only 6 actually changed, and you push all 40 as "new," crews stop reading revision clouds because everything looks new. Highlight what actually moved. Attention is finite; spend it on the sheets that changed.
Submittals and RFIs are schedule constraints, not filing
Here's where document control stops being clerical and starts driving the calendar. A submittal that isn't approved is a wall you can't close. An RFI that's still open is a decision the field is waiting on. Treating these as documents to be stored — instead of constraints to be cleared — is how jobs quietly fall behind while everyone insists they're on track.
Tie your document workflow to your look-ahead. In practice that means when you build a weekly work plan or a rolling look-ahead, every activity gets screened against its paperwork:
- Is the submittal approved? Not submitted — approved, or approved-as-noted with the noted items resolved. Long-lead items especially: if the light fixtures have a 10-week lead and the submittal is still in review at week 4, the ceiling grid date on your schedule is fiction.
- Are the governing RFIs answered? An activity sitting on top of an open RFI is a constraint wearing a costume. It looks ready. It isn't.
- Is the crew building off the drawing the answer landed on? An RFI response that clarifies a detail is worthless if the field never sees it. Link the response to the activity and the sheet it affects.
This is exactly the discipline the Last Planner approach calls "making work ready" — you don't put an activity on the weekly plan until its constraints, paperwork included, are cleared. A look-ahead tool like LookAheadWall earns its keep here when the schedule and the document status live in the same view, so the person planning next week's work is looking at approval status and open RFIs while they commit crews, not finding out on Monday that the material was never released. Software doesn't clear the constraint for you. It just makes the unready work impossible to ignore.
Markup from the field is documentation, if you capture it
Some of the most valuable information on a job never makes it into any system: the foreman's redline where the beam is two inches off the plan, the note that the underground actually ran along the north wall, the photo of the condition before it got covered. This is as-built data, and it's usually trapped on a crumpled sheet in a gang box or a photo buried in someone's camera roll.
The point of field markup tools isn't that they're neat. It's that a redline made on a phone, at the wall, at the moment the deviation is discovered, is tied to the sheet, the location, and the date automatically. Six months later when the owner asks where the buried conduit runs, you have an answer instead of an argument. Push those markups back to the whole team so the PM sees the field condition and the next trade doesn't repeat the mistake. A markup nobody else can see is just a doodle.
Access and audit trail: know who had what, and when
Role-based access sounds like an IT nicety until you're in a dispute. Then it's everything. When a sub claims they never got the revised structural, "the transmittal log shows it was issued March 12 and their PM opened it March 13" ends the conversation. An audit trail — who received a document, who opened it, when the current revision went out — is cheap insurance against the arguments that eat your margin at closeout.
Keep the controls sane. Subs need current construction documents and their own contract scope, not the owner's confidential agreements or the buyout numbers. Give people exactly what their role needs, log the distributions, and you protect both the sensitive stuff and yourself.
A practical baseline that actually holds
You don't need a fifty-page document control plan to fix most of this. You need a handful of habits that don't slip:
- One current set everyone works from, reachable on a phone in the field, with superseded revisions pulled or clearly voided.
- Revisions that announce what changed — clouded, described, and flagged only on the sheets that actually moved.
- A distribution log with receipt tracking so "I never got it" is a checkable claim, not a stalemate.
- Submittals and RFIs screened against the look-ahead every single week, so paperwork constraints surface before crews are committed.
- Field markups and photos captured to the sheet as you go, not reconstructed from memory at closeout.
None of this is exotic. It's the difference between a superintendent who spends Monday morning confirming everyone's on the current set and one who spends Thursday afternoon figuring out why a rated wall got built without the rated door. The tools have gotten good enough that the current drawing, the open RFI, and this week's work plan can all sit in front of the same person at the same time. That's the whole game — put the right information next to the decision, in the field, before the work goes in. Do that consistently and document control stops being the thing that bites you and becomes the quiet reason your jobs run clean.