Run them in order: 1 → 2 → 3. There is little point checking the quality of work that isn't there yet.
How to run
In Claude, type: "Run a Completeness Review on [PDF] for [phase]." (or Quality / Technical)
Claude never asks how to save. It marks up a copy named [original name] - Markup YYMMDD.pdf next to the original. For sets over 30 MB it marks up the file open in Revu and tells you to Save As that name. Never save over the original IFC file.
Claude returns:
Bluebeam markups on the PDF
The DMai - CA - Stamp - Reviewed stamp on the title page (upper right)
An Issues Log in Markdown. Claude shows it in the chat when the review finishes so you can copy it into Slite, email or Obsidian, and also saves a copy (.md) next to the PDF. It lists every item by sheet with a Status column you can edit.
A short summary in the chat: totals by priority, the top items, and any gaps found in the Slite standards
Markup conventions
All markups are Light Violet (#8000FF). Each issue has a callout reading #ID [H/M/L] comment : Light Violet text and leader, white box fill.
Claude chooses the markup that best shows the fix. Every markup is Light Violet, and each issue still gets a callout carrying its #ID:
Intent
Markup
Missing, incomplete or general comment
Revision cloud + callout
Delete an element, view, note or tag
Large X (two crossing lines) over it + callout "DELETE…"
Wrong text, value or dimension
Strike line through the wrong text + the corrected text written beside it
Move or relocate
Arrow from the current to the new location + callout "MOVE…"
Add a line, wall, dimension or leader
Sketch it in place (line or polyline) + callout "ADD…"
Same issue in several places
One callout with a leader to each place
Subject is DMA Completeness , DMA Quality or DMA Technical .
Custom columns are Issue ID, Sheet, Category, Checklist Item, Priority and Review.
High : affects construction, permit or code compliance. Medium : missing standard or coordination item. Low : cosmetic.
Review rules
Sheet numbering on legacy projects
Do not renumber sheets on a project that is already underway. Changing sheet numbers mid-project confuses construction teams.
If a set uses older numbering than the current A - Sheet Standards , the Completeness Review records it in the Issues Log as information only.
No Bluebeam markup is placed for legacy numbering.
Sheets are matched to their standards by sheet type, not by number.
Seals
Only the licensed Architect seals drawings, using the sealing software for the province(s) they are licensed in. The seal is applied to the final PDF, not in Revit.
Drawings are sealed for Building Permit only. On some smaller projects, the IFC and BP sets are the same deliverable, and that set is sealed.
Reviews never flag an empty seal box, in any phase. No Bluebeam markup is placed for it.
Combined DP + BP/IFC sets
At setup, the review asks whether the project issues a combined DP + BP/IFC set (common on single detached homes).
If it does, DP-only sheets in the set are not flagged as "not in phase".
Sheets far from complete
When a sheet has many gaps, mark the whole sheet once as "requires more input" (a cloud around the drawing area) and list the main gaps in that one comment, rather than itemizing each one.
Correcting a review
Tell Claude the # and what's wrong. Claude will:
edit or withdraw the markup
update the Issues Log (.md) next to the PDF and show you the revised version
suggest where the rule belongs in DMA-Docs
Nothing is written to Slite without your approval. Standards approved in Slite are used on the next run.
Known limits
This is a first-pass QA, not a sign-off. A person reviews every markup.
Sheets whose standard page has no Drawing Checklist get general checks only.
Claude reads the PDF visually, so small text or dense areas can be missed.