Checklists & custom checks
Every firm has standards that no off-the-shelf check covers: cover-sheet requirements, naming conventions, the way your details must be referenced. Most firms also already have their review checklists - in a spreadsheet, a Word document, or the back of somebody's head. This tool turns both into something runnable.
The two words describe one thing at two sizes. A custom check is one question you've written. A checklist is the list it lives in - and every check you create lands in one. Describe a single question and you get a one-item checklist; import your MEP completeness spreadsheet and you get a forty-item one. Either way, the checklist is the thing you keep: it lives in your library, outside any project, so you do the work of writing or importing it once and run it on every job.
Use case: create a check for your office's specific cover-sheet requirements and reuse it on every job.
A checklist is a list of questions to ask of a drawing set. A workflow is a whole multi-step review procedure - pull the schedules, cross-reference, write it up. Start here if you have a standard or a document to encode; save a workflow if it's a procedure.
Creating one
In a project, open Project QAQC, press Add a resource, choose the Checklists folder and press Or build one step by step. It asks "What do you want checked?" and gives you four ways in:
- Describe a single check - type one thing to verify. It's only split into several checks if it covers more than one thing.
- Upload a checklist - Excel, Word, CSV or PDF. We read it and split it into checks.
- Select a checklist from project documents - pick a document already in the project that holds your list.
- Start building - go straight to the chat and describe what you need there.
You can also just ask the chat in a project: say what to look for, what counts as a violation, and what evidence matters.
To keep a checklist for later without running it, ask the chat to save it - "save this checklist to my library" - and point it at the list: pasted in, or a document in the project. It goes into your library as it stands. Nothing is researched, run or charged, and it isn't tied to the project you asked from, so you can run it on any project when you're ready.

If you upload a file that's already in your library, it's reused rather than read again. If a new file looks like the same list as one you already have, you're offered Use the existing list or Keep as a new list.
The plan
Either way, the platform researches your project documents first, so the checks are grounded in what's actually in the set. Then it proposes a plan in two parts: the checks that will run, and the ones it's ignoring because this set doesn't contain what they look at. It tells you roughly how long the run will take, and you approve before anything runs. If you want an ignored item run anyway, say so.
That plan step is the one that saves you time later. A plan that says "eight of your twelve items will run, four don't apply to this set" is worth more than twelve items that all appear to run and four of which quietly return nothing.
If you'd rather skip it, turn on Run my QA/QC checks without asking first in My Dashboard > Settings (the Preferences panel). The chat then launches as soon as it has read the drawings, and tells you afterwards what ran, anything it left out, and what it will cost.
What custom checks can do
A custom check can do most of what a human checker does with a drawing set:
- Keep values consistent - the project name, address, sheet titles against the drawing index, spelling - everywhere they appear.
- Follow references - a door tag to its schedule row, a callout to its detail, a circuit number to its panel schedule, a model number to its datasheet.
- Do the arithmetic - sums, ratios, breaker and wire sizing, with the numbers taken from schedules and notes and compared against a limit.
- Trace connections - a single-line diagram from source to load, risers, duct and pipe runs, egress paths.
- Confirm something is shown - a north arrow, a legend, a vent, a required label.
- Count what's drawn - for example, that the number of inverters on the plans matches the schedule.
- Judge how things relate on the sheet - a door swing that hits furniture, a fixture under a window.
- Coordinate between disciplines - the same item in the same place on two disciplines' sheets, such as a roof penetration and its structural opening, with evidence from both.
- Measure off the drawing - distances, clearances, spacing and widths against a limit you state ("at least 900 mm", not "adequate"). The scale is checked against the title block, and a result right at the limit is flagged as borderline rather than passed.
- Quote the code - a check built from a clause in your code library carries that clause's exact wording, and cites it in each finding.
Checks read the sheets themselves as well as the text on them: schedules and tables, title blocks, tags and notes, across every sheet in the project. Every finding is double-checked before it's reported.
Each finding lands in Issues with a citation and a marked-up evidence image, so you can verify it at a glance.
Where they show up in a project
Checklists are not a separate panel. Inside a project, your checklists appear in Project QAQC on the Pick it myself tab, next to our standard checklists. Once a checklist has run, it shows under Already run with a Custom or Shared pill, so you can tell yours from ours. The checklist is the grouping; the checks under it are the rows.
A checklist run is a run like any other: it appears in the tasks tray, its findings go to Issues, and it shows in your activity.
Your library
Your checklists are in the Checklists folder under Resources, in the sidebar. See Resources. Each team page has a Checklists tab too, for what's shared into that team. Each row shows where it reaches you from: you, your organization, or a team.
On the legacy layout this lives under Dashboard → Personal view → My library. See The legacy layout.

A checklist here is the recipe, not a run. From a row's menu:
- Run on a project - pick the project and the run starts straight away. Only the items that apply to that project's documents run. To see what will run first, open the project and pick the checklist in Project QAQC instead.
- Share..., Rename, Open, Delete.
- Download original - the file you imported. The source document is the thing your team recognises, and having it attached to the runnable version means nobody has to hunt for "the real checklist".
Deleting a shared checklist deletes it for everyone it's shared with. Past run results on projects are kept.
The checklist page
Open a checklist to see its checks and manage it in one place:
- Edit items - add, edit or delete checks.
- Edit checklist (the pen next to the title) - tell the checklist what you want back and rate what it found. See Checklist editor.
- Original file - download what you imported. Older checklists, imported before we kept source files, say "Original file not retained" rather than offering a link that goes nowhere.
- Run on project..., Share, Rename and Delete.
Reusing and rerunning
Saved checklists run on the next revision or the next project; the checks adapt to the new set rather than expecting identical drawings - so last year's checklist works on this year's job.
Sharing
Sharing a checklist lets colleagues run it, not edit it. Only you, your organization's owners, and leads of a team it's shared with can change or delete it - so there's one authoritative version instead of five forks.
Share with a team or with the whole organization. A team lead's share into their own team goes straight through; anyone else's is reviewed first. See How access works. A checklist shared with a team appears on that team's Checklists tab.
From chat to check
If the chat just did something you'll want again, ask it to save the work. A single question becomes a check in your library; a whole procedure becomes a workflow.
If a checklist keeps sending back things you don't need, or rates them wrong, use the Checklist editor: tell it what you want back, rate a few of its issues, and the next run takes it in.
If a check you built keeps landing slightly wrong, you don't have to rewrite it from scratch. Open Edit from its ⋯ menu in Project QAQC to change its instructions yourself, or ask the chat to propose a change. A proposed change shows as Proposed edit on the check - open Review proposed edit to see the difference and approve or reject it.