Skip to content
You can read this page without signing in.Sign in

Help

How to use CodeCheck

From a new project to an export in six steps. CodeCheck is a second pair of eyes: an AI reads every sheet, fixed rules check what it read, and every line stays the AI's reading until a person decides it. Hosted drawing reads use Anthropic's Claude Opus 5.5 through Anthropic's API. Under Anthropic's commercial API terms, inputs are not used to train its models. CodeCheck never trains or changes any model.

  1. Start a project

    On the home page, press New project. Type the project's name, choose the country, the province or state and the city, and say what's being built (House, Apartment / multi-unit, Commercial / office, Industrial / warehouse, Institutional or Civil / site works). The sheet shows what the project will be Checked against: the code set for that place, marked not verified where the edition is unconfirmed, and where no code is loaded, code items say check by hand. Press Create project. A new project is saved in the space you have open. To change the place later, use Location and code in the project's menu.

  2. Add the files

    Drop the drawing set into Drop the drawings here: PDFs, images, a ZIP or a whole folder, and hundreds of sheets is fine. Specs go in the Specs box. A checklist, a City letter or lines you type go in What should be there; leave it empty for a blind review. When CodeCheck asks What are these files?, say what each one is: a study or option that isn't part of the set, or correspondence such as RFIs and minutes, is kept aside, never reviewed and never used as proof. Before you add anything, read what never to upload.

  3. Let it review

    Press Review, then Start review. The first review of a project always waits for that press. It runs on CodeCheck's review computer, so you can close the page; the card shows the steps and roughly how long is left, and reviews from every company wait their turn in one line. A set read for the first time takes a while: about an hour for 200 sheets. When you add revised sheets later, a review of the new pages starts by itself after a 30-second countdown that you can pause.

  4. Read the results

    The results open on the Checklist: one line for each thing that should be there, with its status and the sheets that show it. The tiles at the top filter the lines, and the trade filter shows only the trades you pick. By item and By sheet show the same lines another way. Open a line to see the close-up on the sheet. Every line is the AI's reading, checked by fixed rules, until a person decides it: Reviewed by a person counts the lines someone has marked, and What the labels mean explains every label.

  5. Decide and discuss

    On each line, press It's there, Not done or Doesn't apply (on a problem the AI found: Resolved, Real problem or Dismiss). Your name is recorded with every decision. Discuss, beside each line's status, opens that line's thread: write a comment or reply to one, and type @ and a name to bring someone in. They see it under Mentions in their Inbox and as a badge on the project's card. CodeCheck doesn't send emails or texts about it. Send to a teammate, in the project menu, puts the project in a teammate's inbox.

  6. Export and share

    Export, at the top of the results, gives you the Condensed PDF (recommended: each open line with a close-up of the sheet), the Full marked-up PDF with the circles drawn on the sheets, the Spreadsheet (CSV) with every line, its decision and its thread, and the Comparison sheet (CSV) for laying CodeCheck's list beside your own. Group the exports by trade, source or status; with a trade filter on, each export holds that trade's lines only. To send one trade to a consultant who has no account, pick that trade in the trade filter and press its Share button (Share Electrical, for example): they get a read-only link to the sheets confirmed as that trade and the lines whose proof is all on them, and the dialog says how many of your lines stay out and why. Shared links, in the project menu, lists every live link and who made it, and switches any of them off.

What each status means

Not done
— Every page was read and no sheet shows it.
Problem
— Raised by reading the sheets the way a plans examiner would. A lead to check, not a ruling.
Partly done
— Some of it is shown, or it wasn't confirmed. Look at what is left.
Check by hand
— The AI is not sure: the words on the sheets can't settle it. Confirm it by eye.
Not checked yet
— Added after the last review, so the AI hasn't looked at it yet.
Done
— The words are on the sheet and the review agreed they cover it. A person still confirms it.
Doesn't apply
— Marked as not applying to this project.

A problem shows its severity instead: Serious (The City would likely send the set back if it went in like this.) or Fix before submitting (Should be fixed before the set goes in, but less likely to hold up the permit.) Each problem is a lead to check, not a ruling. Once someone decides a line, it says who marked it and when.

Spaces, people and invites

A space is one company, or a group of companies working on the same projects. Each space keeps its own projects, comments, messages and saved checklists, and only the people in it can open them. If you are in more than one, the space switcher at the top says which one is open.

People, in the menu under your name, lists who is in the space. A space's admins make a one-time invite link there (it works once, for 7days) and a password reset link for someone who has forgotten theirs. CodeCheck doesn't send email yet, so you send the link to the person yourself.

Some accounts open on one trade and are locked to it, for example a consultant who sees Mechanical only. Their counts and lists are that trade's; it limits what the screen shows, not who can open the project.

Deleting a project

Only the person who created a project, or one of the space's admins, can delete it. A deleted project stays in Recently deleted on the home page for 30days, where anyone in the space can put it back. What is and isn't removed after that is on How we handle your drawings.

Feedback: a voice note is easiest

No need to write anything up. Record a voice memo on your phone (Voice Memos on iPhone, Recorder on Android), talk for as long as you like, and send it in. If it's about one line, say the project and the number beside the line, for example “Churchill, E10”. A call works too. This site has no contact address set yet, so ask the person who gave you your CodeCheck sign-in to pass your question to Michael O'Brien, who runs CodeCheck.

Who to ask

Michael O'Brien runs CodeCheck. This site has no contact address set yet, so ask the person who gave you your CodeCheck sign-in to pass your question to Michael O'Brien, who runs CodeCheck. If you forget your password, ask an admin of your space for a reset link on People. To sign out, press your name at the top right. What happens to your drawings is on How we handle your drawings, and where the AI is and isn't used is on Standards & compliance.