Checklists

A checklist is a project's own list of checks: the questions your team wants answered about its drawings and specifications every time they're reviewed. Agents run each check against the documents, record a result for it, and file what they find as issues. Unlike a design quality review, which plans its own scope each time, a checklist stays fixed until you change it, so you can run it again on a new package and compare.

Open Checklists in a project's sidebar to see its checklists, their last results and their runs.

Creating a checklist

Managers and Admins create and edit checklists. Choose Add checklist:

• Create with AI opens a chat with the Checklist Creator. It asks what the checklist should focus on, such as coordination, constructability, design quality or code compliance, and anything the owner is worried about, then how detailed it should be: only the key risks, every system that carries risk, or one check per building or element where they differ. It reads the project's drawings, specifications and addenda, looks up standard failure modes in Specset's reference of checks, and writes the checks around this project. Before it creates the checklist it tells you what it will check and what it will leave out, so you can correct it. A card in the chat opens the new checklist.
• From your organization copies one of your organization's published templates onto the project. The copy is the project's own: changing it doesn't change the template.
• Start blank gives you an empty checklist to name and fill in yourself.

Creating a checklist doesn't start a review. You run it when you're ready.

Editing a checklist

• Edit with AI on the checklist opens the Checklist Creator on that checklist. Ask it to add a section, reword checks or drop what doesn't apply. Its changes appear on the open checklist as it makes them, marked Added just now, and it sums up what changed in the chat.
• Edit opens the checklist builder, where you change sections and checks by hand.

Past runs keep the wording they ran with. When a check's wording changes after it ran, its last result shows as Edited since this run and the check counts as not run until it runs again. To ask a different question altogether, add a new check instead of rewriting an old one, so earlier results and issues stay with the question they answered.

Running a checklist

Anyone with access to the project can run its checklists. Choose Run to run every check, or tick some checks first to run only those. You can give a run its own instructions, such as what to skip or watch for. A Manager's instructions are saved with the checklist for future runs; anyone else's apply to that run only.

You can also run a checklist from a chat: type / and choose Checklist Run.

A run works in the background and records each check's result: issues, no issues, inconclusive or not applicable. Issues it files are verified before they reach the project's Issues tab. The checklist's Issues tab shows them grouped by section and check, and Runs lists every run of the project's checklists.

Coverage

Coverage in the Run dialog sets how much of the project each check is worked across:

• Medium reads the places most likely to show a problem for each check, such as where disciplines meet and the most complex or repeated conditions, and lists the places it didn't read in each check's result. It's the default.
• High works the same way and reads more of those places, so fewer go unread. It takes longer and uses more AI.
• Max tries to read every place each check reaches, and lists any it couldn't. It takes the longest and uses the most AI. Max is available on request: email support@specset.com.

Templates

Organization templates live under Settings → Checklists. A template starts as a draft that only Managers and Admins see, and becomes available to every project when it's published. Create one blank, save a project's checklist as one from its settings, or choose Create with AI to have the Checklist Creator write one with you.