A document review checklist isn't a formality — it's the difference between finding a contradiction while it's still a redline and finding it while a crew is standing in front of a wall that can't be built as drawn. Most owners never see a bid set closely enough to know which specific signs mean "not field-ready" versus "just how construction documents look." Here are seven concrete ones, the kind that show up on a set right before bid, each with what it actually turns into downstream if it goes uncaught.
None of these require drafting experience to spot once you know to look for them. What they require is reading the set as a whole — every discipline against every other discipline, not each sheet against itself — which is exactly the read a design team's own internal QA/QC process isn't scoped to do.
1. Detail callouts that point to nothing
Every plan sheet is full of small circled numbers pointing to a detail: "see 4/A-501." That detail is supposed to exist, on the sheet the callout names, showing exactly what the symbol claims it shows. On a set that isn't field-ready, some of those callouts point to a detail number that was renumbered, deleted, or never drawn in the first place.
This one is mechanical to check and easy to miss, because nothing about the callout itself looks wrong — it's a small circle with a number in it, identical in format to every other callout on the sheet. The only way to catch it is to actually trace every reference to its destination, which is tedious enough that it's one of the first things skipped under deadline pressure. In the field, a missing detail reference becomes an RFI the moment a foreman needs to build to it and can't find what it's supposed to show.
2. Dimensions that disagree across disciplines
A structural sheet places a column line at one dimension. The architectural sheet, working from an earlier version of the same grid, places a partition wall relative to a slightly different reading of that same line. Individually, each sheet is internally consistent — the dimension matches everything else on that sheet. The disagreement only exists in the gap between the two disciplines' drawings, checked against each other.
A dimension conflict between disciplines almost never gets caught by either discipline's own QA/QC, because each firm's internal review checks its own sheet against its own standards — not against a different firm's sheet. It only surfaces when someone reads both sets side by side on purpose, which is a cross-discipline check, not a QA/QC check.
3. Spec sections that contradict the drawn detail
The specifications and the drawings are supposed to say the same thing about the same assembly, described two different ways — one in prose, one in a section cut. On a set that isn't field-ready, a spec section calls for a clearance, a fire rating, or a material the drawn detail doesn't actually provide for. Neither document is "wrong" in isolation. The spec writer wrote a correct spec section against a general standard; the drafter drew a correct detail against the plan. They just don't agree with each other, and whichever one the subcontractor happens to price from determines whether the bid reflects what actually has to get built.
4. Notes still marked "by others," "TBD," or "coordinate in field" at issue-for-bid
A placeholder note is a normal, honest thing to see on a set at 50% design. It's a red flag on a set that's being issued for bid, because "coordinate in field" on a bid document means the coordination decision — and its cost — is being pushed onto whoever is holding the tools when the ambiguity gets discovered. A subcontractor pricing that scope either prices it high to cover the unknown, or prices it low and change-orders the difference once the field decision gets made. Either way, the number in the bid isn't the number the work actually costs.
5. The sheet index doesn't match what's actually in the set
The cover sheet lists every drawing that's supposed to be included. Counting the actual sheets against that index sounds too basic to be a real check, but on a large multi-discipline set — sometimes several hundred sheets across a dozen disciplines — a sheet gets dropped from the transmittal without the index being updated, or an index entry survives after its sheet was cut. A missing sheet that nobody notices until submittals or shop drawings is a scope gap discovered well past the point where catching it was free.
6. A bulletin or addendum revision-clouded on one sheet but not the sheets it affects
When a bulletin changes something — a wall location, a duct routing, a fixture count — every sheet touched by that change is supposed to carry a revision cloud and a matching revision number. What actually happens under deadline pressure is the sheet that triggered the bulletin gets updated and clouded, and a downstream sheet that references the same element doesn't. The result is a set where two sheets disagree about current information, and only one of them shows a revision history that explains why.
7. No documentation that a cross-discipline coordination pass happened at all
This is the red flag that sits underneath the other six: nothing in the transmittal package indicates anyone read the full set — every discipline against every other discipline — as a single coordinated document before it went out. A firm's QA/QC stamp confirms its own internal review happened. It says nothing about whether the mechanical set was checked against the structural set, or the specs against the details. As covered in what architect QC covers and where an owner-side review picks up, that gap isn't a failure of the architect's or engineer's process — it's simply outside what any single firm's internal QC is scoped to check. If nothing in the package answers "who checked this against everything else," the honest answer is usually nobody did.
What these seven have in common
Every one of these red flags shares the same structure: each individual document can be completely correct on its own terms, and the conflict only exists in the space between documents. That's exactly the space a firm's internal QA/QC process isn't built to check — as we've written about in more detail in why passing QA/QC doesn't mean a set is coordinated, coordination and QA/QC are two different checks run against two different standards, and a set can pass one while carrying real exposure on the other.
The other thing they share is timing. Every one of these is inexpensive to fix while the set is still in front of the design team and expensive to fix once it's in front of a crew. As covered in pre-bid vs. IFC review timing, the same conflict costs dramatically different amounts depending purely on when in the process it gets caught — not on how serious the conflict actually is.
Key takeaways
- A dangling detail callout, a mismatched dimension across disciplines, or a spec-vs-drawing contradiction can all exist on a set that passed every internal QA/QC check.
- "By others," "TBD," and "coordinate in field" notes at issue-for-bid push an unresolved cost decision onto whoever discovers it in the field.
- Sheet index mismatches and inconsistent revision clouding are mechanical, checkable items — easy to catch, easy to miss under deadline pressure.
- None of these get caught by a single discipline's own QC, because the conflict lives between documents, not within one.
- Every one of these is a redline before bid and a change order in the field — the conflict doesn't get cheaper by going uncaught, it just moves downstream.
None of these seven require a specialist to explain once you know to look for them. What they require is someone actually reading the full set — every sheet against every other sheet, the specs against the details, the index against the transmittal — before it goes out, rather than trusting that a QA/QC stamp already covered it.
Frequently Asked Questions
What's the fastest way to check if a bid set is field-ready?
Start with the mechanical items: does the sheet index match the actual sheet count, and does every detail callout point to a detail that exists on the sheet named. Those two checks alone surface a surprising share of the red flags on an unready set, and neither requires deep technical review — just someone willing to trace every reference by hand.
Does a QA/QC stamp mean the set has already been checked for these red flags?
Not fully. A QA/QC stamp confirms a discipline's own internal review happened against that firm's own standards. It doesn't confirm that discipline's sheets were checked against a different discipline's sheets, which is where most of these seven red flags actually live.
Are placeholder notes like "coordinate in field" always a problem?
Not at early design phases, where they're a normal part of an evolving set. They become a real red flag specifically at issue-for-bid, because a placeholder note on a bid document means a subcontractor is pricing around an unresolved decision instead of a defined scope.
Who's responsible for catching a spec-vs-drawing conflict before bid?
Often nobody specifically, unless someone is scoped to check the full set against itself. The spec writer and the drafter can each produce a document that's correct against its own standard, and the contradiction between the two only surfaces when someone reads both together on purpose — which is the same document review checklist this article walks through.
How much does it cost to fix one of these red flags before bid versus after?
It varies by conflict, but the pattern is consistent: caught before bid, most of these are a redline the design team turns around at little or no cost. Caught in the field, the same conflict typically comes with an RFI, a change order, and a schedule impact, because the fix now has to happen around work that's already in progress instead of on paper.