How do I go over my review results with Claude?
Quick answer: Once CrossBeam is connected to Claude, name the project in plain words: "Show me what failed on my pre-check for 123 Main St." Claude finds the project, reads the counts, lists the Fails and Flags, and can open any finding on its plan sheet beside the chat. Ask it to group, sort, or turn the list into a spreadsheet or a memo for your designer.
Steps
- Connect CrossBeam to Claude once. See Connect CrossBeam to Claude.
- Ask about a project by address, permit number or name: "What's left to fix on my 123 Main St pre-check?" You can also ask for "my latest review".
- Claude reads the summary first: how many Fails, Flags and Passes, by trade.
- Ask for the Fails first, then the Flags. Fails need a correction; Flags need a closer look or more information. See Read your pre-check results.
- Ask to see one on the drawing: "Show me #12 on the sheet." In Claude on the web or desktop, the plan sheet opens beside the chat with the pin highlighted.
- Ask for what you need next: "Group these by trade for my engineer", "Put the Fails in a spreadsheet", or "Draft an email to my architect about the electrical items."
What to expect
- Claude uses the same numbers your results page prints, so #12 in Claude is #12 on your pin.
- It reads your latest finished review. For an earlier round, open the version picker on the results page.
- Claude only sees projects your CrossBeam account can open.
- Anything Claude adds beyond what the review says is Claude's own advice. Ask it to say which is which.
Related
- Connect CrossBeam to Claude
- Read your pre-check results
- Which code your review checks against
- Fix your plans with Claude
From an AI assistantfor Claude and other assistants connected to CrossBeam
Read-only; no credits. Works for a PreCheck, a city review, and a corrections response alike.
crossbeam_list_projectswithquery(address, name or permit number) orowner. Keep theid; name the project by itstitle.crossbeam_get_project_summarywithproject_id. Readflow_typefirst, thenby_resultandby_category: their keys are the filter values.crossbeam_get_findingswithresult: "FAIL", thenresult: "FLAG". Narrow withcategory,statusorin_letter. A code-section question iscrossbeam_search_findingswithsearch_in: "code_section".- Before you say exactly what a finding asks for, open
crossbeam_get_finding_detail(the list cutssummaryat about 120 characters), or passresponse_format: "detailed"for a whole page. crossbeam_get_sheet_annotationswithfinding_idshows it on the sheet: a card host opens the review workspace on the pin; a text host getsimage_url(one hour) and should give the personviewer_link.crossbeam_get_sheet_indexfinds a sheet by discipline or content.
Watch for:
- Say finding numbers (
n, "#12"), never ids. Counts are fails, flags and passes; never add passes into a count of findings. - On a PreCheck with a brief, lead with the brief (Fix your plans with Claude). A PreCheck's letter is a Corrections Preview, never the city's letter.
- A pin marks where the review looked. Check it against the finding's text before calling the pin the defect.
- Group repeats by root cause and say which numbers each group covers, so nothing is dropped.
- Field meanings, paging and errors: How the CrossBeam tools behave.