Document QA Review: Finding What Is Missing From a Plan Set
Referenced drawings that were never issued. Schedules that do not match the calculations. Details called out but not drawn. Flikt.AI reads the whole set and reports the gaps.
Document QA review is checking a plan set for internal completeness and consistency — whether every drawing the set references actually exists in it, whether the schedules agree with the calculations and the plans, and whether callouts, details, and notes resolve to something real. Flikt.AI performs this across your 2D PDF set alongside cross-discipline conflict detection, and reports each gap with the sheet that raised it.
These are not design errors. They are issuance errors, and they behave differently: a coordination clash gets argued about, but a missing sheet just stops work. They also survive review reliably, because checking them is tedious, unglamorous, and nobody’s scope.
The gaps that stop a crew
Referenced but not issued. The set calls out a consultant drawing, sheet, or detail that is not in the package you sent to the field.
Sheet index mismatches. Sheets listed in the index that are absent from the set, or sheets in the set that never made the index.
Schedule vs. plan disagreement. Equipment, fixtures, doors, or openings that appear in a schedule and not on the drawings, or the reverse.
Missing supporting calculations. Loads, fixtures, or equipment added on the drawings without the calculation or structural design that has to back them.
Unresolved callouts. Detail marks and section cuts pointing at a detail number or sheet that does not exist in the set.
Spec vs. drawing mismatches. A product, rating, or assembly named in the specification that the drawings contradict, omit, or supersede.
Dimensional inconsistency. Dimensions that disagree between plan, section, and elevation, or strings that do not sum to the overall.
Missing required notes. Notes and callouts the rest of the set assumes are present on a sheet where they never appear.
What a document QA finding looks like
From a South Florida commercial retail set — five disciplines. The general contractor independently reviewed all five findings and confirmed every one as a legitimate coordination issue.
One of five findings on the set, totalling $233,000–$583,000 in flagged exposure. Read the A-Z Builds case study →
What this does not do
Worth knowing before you buy.
It does not judge design intent
Flikt reports that a reference does not resolve or a schedule disagrees with a plan. Whether the omission was deliberate — deferred scope, delegated design, a later package — is a call your team makes.
It is not a permit or code certification
Flikt flags where the drawings appear to conflict with a cited requirement so a human can look. It does not certify compliance, and it is not an authority-having-jurisdiction review.
It does not replace the design team
Reports are recommended as a supplement to professional review, not a replacement. The architect of record and engineer of record remain responsible for the design.
Documentation gaps are one of five finding types the review reports. See the other four, with real examples — and the projects where a document review does not help.
Three steps, same day
Upload the set
Your 2D PDFs, as issued. Include the specification if you have it — spec-versus-drawing checks need it.
Flikt reads all of it
Sheets are tagged, indexed, and checked for unresolved references, schedule gaps, and inconsistencies.
Fix it before issuing
A severity-ranked report — PDF, Excel, or a shareable portal link — so gaps close on paper, not in an RFI.
Frequently asked
What is document QA review in construction?
It is the check that a plan set is internally complete and consistent before it goes out — that every referenced drawing exists, that schedules agree with plans and calculations, that callouts resolve, and that the specification and the drawings say the same thing. It is distinct from design review, which asks whether the design is right; document QA asks whether the set is whole.
How is this different from cross-discipline conflict detection?
Conflict detection finds two disciplines contradicting each other. Document QA finds something absent — a sheet, a detail, a calculation, a schedule row. Flikt runs both on the same upload, because in practice they show up together and a reviewer wants one list. See conflict detection →
Do I need to upload the specification too?
Not required, but it materially helps. Without a spec, Flikt still checks the drawings against each other, the schedules, and the sheet index. With it, spec-versus-drawing mismatches come into range. Multiple specification files are supported on a single upload.
How long does it take, and what does it cost?
Same-day turnaround on a typical set. A report for a set up to 30 sheets is $129 for PDF and Excel, or $169 in the interactive portal with RFI generation and revision comparison; larger sets are priced in bands by sheet count. See pricing.
Flikt.AI reports are recommended as a supplement to professional review, not a replacement. The architect of record and engineer of record remain responsible for the design.
Find the gaps before the field does
Upload a set and get a severity-ranked report the same day.