Run a drawing review
A drawing review returns a table of findings plus marked-up pages you can open in Bluebeam or any PDF tool that supports annotations.
Start in chat
- Attach the drawing set (a PDF, or a folder of PDFs) to a new conversation.
- Ask for the review — for example, "Review this set for coordination conflicts and missing information."
- Answer the scoping questions. Assistant surveys the set first, then asks what to optimize for and, on large sets, whether you want a light sample pass or the full set.
You do not need a workflow or a standards document to start. Assistant applies built-in discipline checklists (architectural, structural, mechanical, plumbing, electrical, civil, plus sheet-wide checks) and streams findings in as it verifies them, so you can start reviewing before the run finishes.
For accessibility, egress, or other code questions, enable Codes Search in the same session — see Run a code compliance check.
Add your own standards
The built-in checklists cover general constructability, coordination, and missing information. Your standards are what tell Nomic what "good" looks like on this project.
- Attach your project standards, client criteria, internal checklist, or approved example comments and ask Assistant to review against them.
- Tell it what not to flag, especially on early design packages where placeholders and unresolved details are expected.
- No formal standard yet? Start from a handful of past review comments or RFIs and ask Assistant to turn them into a checklist first.
What you get back
- A findings table — sheet, location, discipline, severity, description, and the check or standard it came from.
- Markups on the source pages — a leader line pointing at the issue with a short comment.
- A summary — counts by issue class, plus anything that was skipped.
Review the table and markups before sharing. Accept the useful findings, reject false positives, and leave unresolved items for a human reviewer when more context is needed.
Make the output more useful
- Steer with follow-ups. "Go deeper on the door schedules" or "only flag issues my GC would raise as an RFI" starts new passes without redoing covered work.
- Be concrete. "Flag any door that swings into an egress path narrower than 44 inches" beats "flag egress issues."
- Trim the standards. A few highly relevant standards work better than dumping every spec.
- Sample first. A short pass over a few sheets shows whether Assistant understood the task before you spend on a full set.
When to make it a workflow
Turn a review into a workflow once the same review runs repeatedly and you want every reviewer to get comparable output: instructions and standards are fixed in advance, reviewers just attach the set. See Build a workflow from a real task.