Skip to main content
Back to Help

Run a code compliance check

Code compliance checks help you compare drawings, screenshots, or design documents against applicable codes and standards. They work best when you provide a clear jurisdiction, a focused design area, and enough visual information for Nomic to reason from.

What to provide​

Prepare:

  • The drawing, screenshot, or PDF pages you want reviewed
  • The jurisdiction or standard to apply
  • The building type or project context, if relevant
  • Any known constraints, such as occupancy, phase, or discipline
  • A specific question, not just "check this"

For example: "Check these restroom plan and detail pages for New York City accessibility issues. Return a table with issue, drawing location, code reference, and recommendation."

Run the check​

  1. Open Assistant, or open the workflow your team uses for code compliance checks.
  2. Attach the drawing pages or screenshots.
  3. Open Integrations/Tools and turn on Codes Search if it is not already enabled.
  4. Click the pencil next to Codes Search and choose the most specific jurisdiction available, such as a city or county when applicable.
  5. State the jurisdiction and what type of issue to look for. Your prompt can override the saved jurisdiction for that run.
  6. Ask for a structured output, such as a table.
  7. Review the citations and drawing references before using the answer.

Reviewing a whole drawing set rather than a few pages? Ask for a code review of the set. Nomic runs it as a drawing review with code as the criteria, so findings land in a findings table with a code citation and a markup on each cited sheet.

Use Assistant first when you are exploring. Turn the prompt into a workflow once the review should be repeated by other users.

What good output looks like​

A useful code compliance result usually includes:

  • The potential issue
  • The drawing page or image where the issue appears
  • The applicable code or standard citation
  • The requirement that may apply
  • Why the design may not meet it
  • A recommendation or follow-up question

Nomic may call something a potential issue when the design information is incomplete. Treat those as review prompts, not final determinations.

Common mistakes​

  • Asking for a full code review with no jurisdiction.
  • Uploading pages with no scale, dimensions, or reference measurements when the check depends on dimensions.
  • Mixing too many unrelated disciplines into one run.
  • Expecting full codebook access instead of cited excerpts.
  • Sending results onward without human review.