A crew has forms set, steel on the ground, and a pour window closing. Then someone notices the structural plan calls for a footing dimension that does not match the architectural layout. That is where construction drawing discrepancy software earns its place. Not in a conference room. At the point where a bad call turns into rework, a delayed pour, or an RFI nobody wants to own.
The drawings never match perfectly. Architectural and structural sets are issued by different disciplines, revised at different times, and read by people under pressure. The question is not whether conflicts will show up. The question is whether the field finds them before concrete, framing, or finish work makes the mistake expensive.
What construction drawing discrepancy software should do
Good discrepancy software compares related drawing sets and identifies the places where the documents disagree. That sounds basic. In practice, it means more than putting two PDFs beside each other and asking a superintendent to stare at clouds of revision marks.
A field-ready system should identify a conflict, show the exact sheets involved, and point to the source information behind the finding. If an architectural dimension says one thing and a structural grid or footing callout says another, the user needs the sheet number, detail reference, revision information, and the specific conflicting text or geometry. “Potential issue detected” is not enough when the crew is waiting.
The software should also distinguish between a discrepancy and a decision. It can flag that a beam pocket is missing from one sheet, or that a header size changed between revisions. A qualified person still decides whether the issue is real, which document governs, and what work can proceed. That human check is not a weakness. It is how accountability stays where it belongs.
The conflicts that cost field teams time
The most damaging discrepancies are usually not dramatic. They are small mismatches that get buried in a stack of sheets until the work reaches that location. Common examples include conflicting dimensions between architectural and structural plans, grids that do not align, missing posts or footings, headers that appear in one set but not another, and revision dates that drift across the issued package.
A framing crew may find a bearing condition on the structural sheets that never made it into the architectural wall plan. A concrete crew may see a column location that is offset from the layout dimensions. An installer may be working from an old reflected ceiling plan while the latest structural revision has moved a brace or opening. Every one of these problems can become a field RFI. The difference is whether the RFI is raised before or after work is installed.
Why desktop review breaks down at the slab
Office-based drawing review has a place. Preconstruction teams need to study sets, coordinate scopes, and plan procurement. But active construction is not preconstruction. The foreman does not have an hour to open a laptop, sort through folders, compare revisions, and explain the conflict in office language while a crew stands by.
Field conditions are different. Phones are available. Signal may not be. Gloves are on. The crew may be looking at a grid line, a form edge, or a framed opening that has to be resolved now. Software designed around desktop markups and enterprise workflows often adds steps at exactly the wrong moment.
That is also where language matters. A discrepancy needs to be clear to the person setting the layout, not just to the person writing a coordination report. English-only systems can leave Spanish-speaking crews dependent on someone else to translate what the drawings already should have communicated. Clear, terminology-aware output in English and Spanish reduces that handoff and keeps the question tied to the actual work.
Offline capability matters for the same reason. A jobsite tool that only works with strong service is not really a jobsite tool. It is a desk tool that happened to get a mobile version.
A practical workflow for resolving drawing conflicts
The best workflow is short enough to use under pressure. It starts before the work begins, but it stays useful when a conflict appears in the middle of the day.
1. Compare the sets that govern the work
Start with the relevant architectural and structural sheets, not the entire plan package as one giant review exercise. Before layout, compare the foundation plan, floor plans, framing plans, sections, and details that affect the area being built. Before framing, focus on wall types, bearing callouts, headers, beam pockets, elevations, and structural details.
The goal is not to create a giant punch list. It is to catch the conflicts that change where material goes, how it is installed, or whether the next operation can proceed.
2. Verify the revision trail
A mismatch can be a true design conflict, or it can be a revision-control problem. Check issue dates, revision clouds, addenda, and sheet references before escalating. If one sheet has been updated and its companion sheet has not, the discrepancy may be evidence that the set was not coordinated.
This is where source citations matter. A usable finding should show more than “grid conflict.” It should identify that Architectural Sheet A2.1, Revision 4, places a wall on one location while Structural Sheet S1.2, Revision 3, establishes the support line elsewhere. That gives the superintendent something concrete to review and send forward.
3. Turn the finding into a usable RFI
A good RFI states the conflict without guessing at the answer. It identifies the location, cites both documents, explains the field impact, and asks for direction. It does not need paragraphs of defensive language.
For example: “At Grid C/4, Architectural A2.1 shows the exterior wall 6 inches east of the structural support line shown on S1.2. Footing layout is scheduled for tomorrow. Please confirm the governing location before concrete placement.”
That is specific. It gives the architect or engineer a clear question, tells them why timing matters, and creates a record of what the field saw. Software that drafts this from a detected conflict can save real time, but the foreman or superintendent should review it before it goes out.
4. Set a hold point when the answer affects installed work
Not every discrepancy stops the job. A note conflict that does not affect the current scope may be documented and handled later. But if the conflict changes a footing, bearing wall, embed, opening, elevation, or required clearance, define a hold point.
The crew needs to know exactly what can continue and what cannot. “Waiting on RFI” is too vague. “Do not place footing at C/4 until design confirms location; proceed with forms at C/3 through C/6” keeps work moving without gambling on the disputed area.
5. Close the loop in the field
When the response arrives, make sure the people doing the work receive the answer in a form they can use. Update the relevant sheets, communicate the direction during the huddle, and record the approved resolution against the original finding. A closed RFI sitting in an inbox does not prevent rework.
What to look for before adopting a tool
Construction drawing discrepancy software is not all the same. Some products are built for document control. Some are built for office takeoff. Some identify visual changes but leave the field team to interpret everything from scratch.
For active jobsite use, look for comparison across architectural and structural sets, findings tied to specific source sheets, mobile access, offline use, and an RFI workflow that starts from the detected conflict. The product should be fast enough that a foreman will actually pull it out during layout. It should also support the language used by the crew, not force every question through an office translator.
There are trade-offs. Automated detection can surface false positives, especially in dense details, scanned sheets, or drawings with unusual conventions. It may not understand design intent when a conflict is resolved by a note elsewhere in the set. That is why the right tool does not pretend to replace the superintendent, engineer, or architect. It reduces the page-flipping and gives those people a clearer issue to decide.
Pricing and access matter too. A small builder should not need enterprise procurement, a seat minimum, and a training project just to stop comparing drawings by hand. If the people building the work cannot access the tool, the tool is not solving the field problem.
Put the answer where the work happens
TrueStruct is built around that reality: compare the architectural and structural sets, identify the mismatch, cite the sheets, and draft the RFI while the issue is still in front of the crew. The final call remains with the qualified person. The wasted search does not.
The next time a dimension conflicts at a grid intersection, do not make the crew choose between waiting blindly and building on an assumption. Put the discrepancy, the source, and the question in their hands before the work gets covered up.