A foreman drawing audit guide is not paperwork for the trailer. It is the check you run before a crew lays out a wall from one sheet and a concrete crew pours embeds from another. When the drawings disagree, the field pays first: lost hours, ripped-out work, delayed inspections, and a superintendent explaining why the schedule just slipped.
The drawings never match perfectly. Architectural sheets may show an opening that structural has framed differently. A plan revision may reach one trade but not another. A grid line can shift between sheets without anyone noticing until layout is already on the slab. The job is not to pretend these conflicts do not exist. The job is to catch them while they are still cheap.
What a foreman drawing audit should accomplish
A drawing audit is a focused comparison of the sheets that control the work about to happen. It is not a full design review, and it does not replace the architect, engineer, or superintendent. A qualified person still makes the final call. But a good audit gives that person a clean, cited conflict instead of a vague field complaint.
For the foreman, the goal is simple: verify that the crew has one buildable direction before materials are cut, forms are set, or a pour begins. That means checking more than the sheet title. You need to compare dimensions, grids, elevations, section references, details, revision clouds, and notes that affect the immediate scope.
The best time to do this is tied to production, not a Friday afternoon document ritual. Audit before layout. Audit before a footing or slab pour. Audit before framing a level. Audit again when a new bulletin, ASI, or revised sheet lands. If the work changes, the drawing set needs another look.
Start with the work in front of the crew
Do not begin by trying to read every page in a 200-sheet set. Start with the next operation. If the crew is laying out interior bearing walls, pull the current architectural floor plan, structural framing plan, relevant wall sections, opening schedules, and details referenced at those locations.
Then ask a blunt question: do these sheets describe the same thing?
A common example is a structural plan calling for a beam pocket or post at a grid intersection while the architectural plan shows a clear opening or a wall that cannot accommodate it. Another is a dimension chain that places a wall six inches off the location implied by the grid. Neither problem gets better after studs are standing.
Keep the audit scope tight enough to finish before the crew needs an answer, but broad enough to include every sheet that governs the work. For a slab edge, that may mean civil, architectural, structural, and MEP sleeves. For a framed opening, it may mean plans, elevations, header schedules, structural details, and reflected ceiling requirements.
Verify the revision baseline first
A foreman cannot audit a mixed set. Before comparing geometry or dimensions, confirm which revision controls each discipline. Check issue dates, revision numbers, clouded changes, bulletins, and any addenda carried into the field set.
This sounds basic because it is basic. It is also where crews get burned. The architectural sheet may be Revision 4 while the structural sheet in the gang box is still Revision 2. The conflict may not be a design conflict at all. It may be revision drift.
Mark the baseline you are using. If there is uncertainty about whether a revised sheet supersedes a prior detail, do not assume. Raise it. A fast wrong answer is still wrong.
Use a repeatable foreman drawing audit guide
Field audits work when the sequence stays consistent. The crew should not have to reinvent the process under pressure. Run each work area through the same checks:
- Confirm sheet names, issue dates, revision numbers, and applicable bulletins.
- Match grid lines, levels, north arrows, and reference points across disciplines.
- Compare controlling dimensions, including overall dimensions and dimension strings.
- Follow every section, detail, and schedule reference that changes the work.
- Check notes for material, fastening, reinforcement, fire rating, clearance, and inspection requirements.
- Document any mismatch with the exact sheet, detail, grid, and conflicting callout.
The order matters. A dimension conflict is hard to diagnose if one sheet is rotated differently or uses a changed grid. A missing header may be explained by a structural detail that was never pulled. The audit is not just looking for red flags. It is tracing the direction back to its source.
Compare what gets built, not just what looks different
Not every visual difference is a field conflict. A structural plan may simplify an architectural finish condition because it is outside structural scope. An architectural elevation may show a door type while the framing plan only shows the rough opening. Those differences can be normal.
The question is whether the difference changes layout, material, sequence, connection, clearance, or inspection. If it does, it needs attention. If it does not, do not flood the design team with noise.
That is the trade-off. A foreman needs enough discipline to catch real discrepancies without turning every notation difference into an RFI. The best RFIs are specific, necessary, and issued before the crew has to guess.
Capture conflicts so someone can answer them
A useful field finding has three parts: the location, the conflict, and the requested decision. “Plans do not match” is not useful. “A5.1 Detail 3 shows a 3-foot-0-inch opening at Grid C/4, while S2.2 calls for a post and beam at the same location. Confirm framing configuration and required header or beam detail before wall layout” gives the architect and engineer something they can resolve.
Add photos when the existing condition matters, but do not use photos as a substitute for citations. The person answering needs to see the exact sheet references. Include the date and revision on both sides of the conflict. That protects the crew from being blamed for building from an outdated direction.
This is where field-first reconciliation tools can earn their keep. TrueStruct compares architectural and structural plan sets, identifies discrepancies, and attaches source citations to the finding. It can draft the RFI from that conflict, while the foreman or superintendent keeps final judgment. That is different from dumping another software task on the field. The point is fewer page flips and faster answers at the place the work is happening.
For bilingual crews, the message also has to be usable in the field. A clear English and Spanish description of the issue helps the lead communicate the hold point without turning a plan conflict into a language problem.
Make the audit part of the daily plan
The drawing audit should feed directly into the morning huddle, look-ahead plan, and material decisions. If a wall location is under RFI, the crew needs to know whether to hold that wall, shift to another area, or stage materials without installing them. Silence creates improvisation. Improvisation creates rework.
Foremen should also tell the superintendent what the conflict threatens. Does it affect a pour window? Does it block framing inspection? Will it change lead time for steel, connectors, or a custom door frame? A cited discrepancy becomes more valuable when the schedule impact is clear.
Keep a simple record of findings and dispositions. Over time, recurring problems become visible: late revisions, coordination gaps at certain grids, structural details that do not track architectural changes, or RFIs that sit too long. That record is not bureaucracy when it prevents the same miss on the next floor.
Know when to stop work
Not every discrepancy requires a full stop. If a nonstructural partition dimension varies slightly but the controlling grid and room layout resolve the intent, a superintendent may be able to direct the work under established project procedures. If a conflict affects structure, fire-rated assemblies, egress, embeds, penetrations, elevations, or inspections, the threshold is different.
When the crew lacks a buildable answer, stop the affected work. Protect the schedule by moving to work that is clear, not by burying a bad assumption in the building. A one-hour hold before a pour beats a three-day repair after the concrete hardens.
The foreman who catches a conflict is not slowing the job down. They are keeping the job from building its own problem. Before the next layout line gets snapped or the next truck backs up to the forms, make sure every controlling sheet is telling the crew the same story.