Project QAQC
Project QAQC runs automated consistency, completeness and coordination checks across your drawings, specs and models - schedules versus plans, missing details, mismatched tags. Every issue is flagged and linked straight to the spot on the sheet, so you can confirm it in one click.
Use case: flag every door missing its fire rating before the set goes out.
The panel at a glance
Open Project QAQC from the project's Tools panel. From top to bottom:
- Project context for reviewers - facts you already know about the set, like "sheet 15 intentionally omitted" or "client prefers no ROW dims on typicals". Every check takes this as fact when deciding what's worth flagging. It's background, not a list of what to check.
- Add a resource - bring a checklist, a code book, a standard or a document into the project, or build a checklist step by step. See Resources.
- Two ways to start a review: Describe it and Pick it myself.
- Already run - everything that has run on this project, with its results.
On a project that has run checks before, the two tabs sit behind a green Start new review button.
Running a check
Describe it
Write what you want checked under Just ask, in plain language - see Review intent for what to write. Then press Run plan.
We work out the checklists and codes that fit this set and your brief, and open a chat so you can follow along and ask about anything that couldn't run.
- Tick Review plan before automatically launching if you want to talk the plan through in that chat before anything starts. Leave it unticked and the run starts straight away.
- A review that runs 10 minutes or more emails you when it finishes. Turn that off in Settings → Preferences (Email me when my long-running tasks finish).
- Use a workflow starts from a review you saved earlier, and Save as workflow keeps this one for next time. See Workflows.

Pick it myself
Tick exactly what to run. The tab has three sections:
- Checklists - our standard checklists and your own, listed under YOURS, ORGANIZATION SHARED (our standard checklists come first here) and a heading for each of your teams. A chip on each row says where it came from: Standard, Shared by a colleague, or From your request. If you ran Run plan first, what the plan chose is already ticked here.
- Codes - the code books on this project. Tick one to review the drawings against it. See Code Review.
- Spec audit - pair a spec with the drawings to audit it against: all current drawings, or one discipline's drawings. See Spec Audit.
Type in the filter box to find anything by name. Then press Run (it shows how many items you ticked) and findings land in Issues.
Checks work in the background. Watch them in the tasks tray and keep reviewing while they go.

While documents are still processing
If the project's documents are still processing, the check doesn't fail and you don't have to wait for it. It's saved with a Waiting for documents badge and starts on its own the moment processing finishes.
From the upload wizard
The upload wizard's Ask step ("What should we check?") has the same two tabs. Describe what to check or pick it yourself, and it starts as soon as your set has been read. Leave both empty to set it up in the project later. See running checks at upload time.
Reviewing findings
Under Already run, each checklist shows its status and how many findings it raised. Filter by Flagged, Passed or Running. A row marked Custom or Shared is a checklist you or a colleague built, rather than one of ours.
Click a check to open its findings in Issues:
- Every finding is cited. Click it and the viewer jumps to the exact location, already zoomed, with the evidence highlighted.
- Resolve what's fixed, and Waive a correct finding the team is deliberately not fixing, with a reason.
- Assign real issues to teammates.
- If a check was simply wrong, send feedback and tick "These were not issues (false positives)". That goes to our team, so we can fix the check.
A check that ran but couldn't reach a verdict shows no verdict - click it to see why. Use Re-run all checks to run everything again on a new revision.

How checks work
Different checks use different techniques under the hood: some read the drawings visually, some cross-reference schedules against plans, some reason across many pages (for example, matching every tag on the plans against the schedule and flagging mismatches in both directions). What they share:
- Evidence-first. A finding always points at something you can see on the sheet.
- Set-wide. Checks cross-reference between sheets, schedules, and details, not one page at a time.
- They know what you've told us. Checks take the Project context as fact, and agent-based checks also read the project's memory. That's how you stop a check re-raising something you've already settled - "the east wing is built and barricaded", "we review to the 2021 IBC on this job" - without switching the check off.
Which checks do I have?
Your organization's check library is tailored to what you review. If there's a check you need that isn't in your library, or a check your firm runs that no one else does, you have two options:
- Build it yourself as a custom check.
- Talk to us and we'll build it into your library.