An inspector walks a corridor on level three and finds a cluster of pipe penetrations through a rated wall with gaps around the sleeves. She writes it up: "Firestopping incomplete at corridor wall, per code. Contractor to correct."
Two days later the superintendent pushes back. Which code section? The penetrations were going to be sealed with a listed system that is not installed yet. The wall type on the drawings may not even be rated at that location. Now the finding sits in limbo while the inspector, the PM and the contractor trade emails about what "per code" meant.
The observation was right. The reference was not there. And without it, a valid finding became an argument.
Why the reference matters as much as the observation
A finding has two jobs. It has to describe what is wrong, and it has to show why it is wrong according to something the contractor agreed to build to. The second part is what makes a finding enforceable.
When the reference is missing, vague or wrong, a few predictable things happen:
- The finding gets disputed. "Per code" or "per spec" invites the obvious question: which one? The contractor is within reason to ask.
- The item gets re-inspected. The inspector goes back to confirm what they saw, now with the documents in hand, and writes it up again.
- Closure slows down. A contractor cannot propose a corrective action against a requirement nobody named. The item ages on the open list.
- The record weakens. If the issue ever becomes part of a claim, a finding that never cited a requirement is much harder to stand behind.
- Credibility erodes. A pattern of loose references teaches the field team that findings are negotiable.
None of this is about effort. Inspectors know their codes. The problem is that pulling the right reference, for this project, at this location, in the moment, is harder than it looks.
Why references go wrong in the field
Most bad references are not mistakes of knowledge. They come from how the work is set up.
The governing document is not obvious. A single condition can be covered by the building code, a referenced standard, the project specification, the drawings, an approved submittal and a manufacturer's installation instructions. The right reference depends on which one actually governs on this job.
The project spec is not the office spec. Inspectors who move between projects carry habits from the last one. Section numbers, edition years and owner-specific requirements change from job to job.
Approved submittals and RFIs change the requirement. If the contractor got a substitution approved, the drawing detail may no longer be the standard. The inspector in the field often does not know that.
Looking it up takes time nobody has. Finding the exact section in a project manual that runs to hundreds of pages on a phone, in a stairwell with no signal, is not realistic. So the reference gets written as "per spec" with a plan to fill it in later. Later rarely comes.
Templates do not ask for it. If the report form has a big box for observations and no field for the reference, the reference becomes optional.
Before and after
Before: The inspector observes the condition, takes photos and writes a short note with "per code." At the end of the day she types the report from her notes. The reference stays vague. The contractor disputes it. She spends part of the next morning in the project manual and the submittal log, then reissues the finding. The item closes a week later than it could have.
After: The report template has a required reference line for every finding: the governing document, the section or detail, and the edition where it matters. Before mobilizing, the team builds a short project reference sheet for the inspection scopes on this job. In the field, the inspector records the finding by voice and photo, and cites the reference from the sheet. Anything she cannot confirm on site gets flagged as "reference to confirm" rather than left vague, and gets resolved before the report goes out. The contractor receives a finding that says what is wrong and exactly why.
The inspector still makes every call. She just stops having to defend findings that were right all along.
What good looks like, with or without tools
You can tighten this up on your next project without new software.
1. Make the reference a required part of every finding
Add a reference line to the template and treat a blank one as an incomplete finding. "Per code" does not count. The minimum is the document and the section, detail or sheet.
2. Build a project reference sheet before work starts
For each inspection scope on the job, list the governing code edition, the key referenced standards, the relevant spec sections and the drawing sheets that matter most. One or two pages, kept current. This is the single highest-value hour a lead inspector can spend at mobilization.
3. Check the submittal and RFI log for the area
Before writing up a condition that looks wrong, check whether an approved submittal or RFI response changed the requirement. Two minutes here can save a disputed finding.
4. Flag uncertainty honestly
If the inspector is sure of the deficiency but not of the exact reference, say so: "reference to confirm." A flagged gap that gets closed before the report goes out is far better than a confident wrong citation.
5. Review references before the report leaves the team
A quick QA/QC pass that only looks at references catches most of the problems. It should take minutes per report.
Where AI helps, and where it does not
The hard part here is not judgment. It is getting the right document in front of the inspector at the right moment and keeping the record consistent. That is where AI tools fit.
Where it helps:
- Turning spoken field notes into structured findings in the firm's own template, including a reference line that is always there
- Keeping finding language consistent across inspectors and shifts
- Making past reports searchable in plain language, so an inspector can see how the team cited the same condition earlier on the job
- Drafting recommendations from the observation for the inspector to review and edit
- Helping someone search large project documents in plain language, where the firm has set that up
Where people still decide:
- Whether a condition is a deficiency at all
- Which document governs on this project and at this location
- Whether a proposed correction meets the requirement
What to watch:
- AI can suggest a reference. It cannot own it. A model can surface a plausible section that does not apply on this job. Every citation needs an inspector's confirmation.
- Document quality limits the result. Scanned, outdated or incomplete project manuals produce weak answers. Current documents matter.
- Project specifics take setup. Owner requirements, approved submittals and RFIs only help if they are part of what the team works from.
How we approach it
At InstinctIQ, we work as a forward-deployed team. Before we change anything, we sit with your inspectors and QA/QC leads and look at real findings: which ones got disputed, why, and how long it took to sort out. We look at your templates and where references are supposed to go.
From there, IQ-Inspect fits the routine your team already runs. Inspectors capture findings by voice, photo and video on site, even offline, and the app produces a structured Word report in your firm's own template, so a reference line can be part of every finding. Reports and images are searchable in plain language across the team, and AI-generated recommendations are there for the inspector to review. Where a firm needs something specific, like working from its own project reference sheets, we scope it with you rather than assume it.
The goal is not to replace your inspectors' knowledge. It is to make sure the findings they write hold up the first time.
A useful next step
Pull the last ten findings your team issued on one active project. Count how many cite a specific document and section. Then count how many were disputed or reissued.
If the two numbers are related, which they often are, we are happy to walk through your inspection workflow with you and talk through what a reference-ready finding could look like on your projects.
Ready to transform your field reporting?
Join hundreds of AEC teams already saving hours every week.