What we check

The closeout documents GCs kick back most.

Each check compares your documents against your spec. If we can't resolve an item, the report says Couldn't confirm — it never quietly passes. Not a compliance certification or a substitute for professional review.

O&M coverage and equipment references

What the check does

Compares the equipment identified in your requirements and schedules against the equipment referenced in the supplied operation and maintenance manuals.

Not our job

Does not judge whether the manual content is technically adequate for the installed equipment.

Warranty duration, start dates and identifiers

What the check does

Catches 1-year warranties where the spec says 2, wrong start dates (startup vs. substantial completion), and wrong project names.

Not our job

Legal opinions on enforceability.

TAB report presence

What the check does

Checks whether a testing, adjusting and balancing report appears in the supplied files, covering the systems the requirements name.

Not our job

Does not validate balancing figures or re-calculate airflow and water flow results.

Startup and commissioning record presence

What the check does

Checks whether startup reports and commissioning records appear present, signed where required, and covering the required scope.

Not our job

Does not verify that the described tests actually occurred on site.

Training documentation

What the check does

Checks whether owner training records appear present with the attendance, duration or content details your requirements call for.

Not our job

Does not assess training quality.

Record drawing presence and labels

What the check does

Checks whether record drawings are present, labelled as record documents, and carry revision and preparer identification.

Not our job

Does not assess the technical accuracy of the drawings or whether they match installed conditions.

Cross-document project, equipment and revision inconsistencies

What the check does

Flags project names, equipment tags, and revision identifiers that disagree between documents in the same package.

Not our job

Does not decide which document is correct — it tells you what to confirm.

Requirement statuses

How we grade every line.

Found, Problem, Missing or Couldn't confirm. None of these means approved — we never mark a requirement Compliant, Approved or Certified.

Evidence found

The supplied files contain material that appears to satisfy the requirement, and we cite where.

Issue identified

The supplied files appear to conflict with the requirement, or cover it only partly.

Not found in supplied files

Nothing in the supplied files appears to address the requirement.

Unable to verify

A file was unreadable, ambiguous, or outside what a document review can determine.