Use CrossBeam from Claude, ChatGPT or Copilot

How do I go over my review results with Claude?

Where: Connect CrossBeam in Settings → AI Connectors, then ask Claude about your project

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

  1. Connect CrossBeam to Claude once. See Connect CrossBeam to Claude.
  2. 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".
  3. Claude reads the summary first: how many Fails, Flags and Passes, by trade.
  4. 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.
  5. 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.
  6. 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

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.

  1. crossbeam_list_projects with query (address, name or permit number) or owner. Keep the id; name the project by its title.
  2. crossbeam_get_project_summary with project_id. Read flow_type first, then by_result and by_category: their keys are the filter values.
  3. crossbeam_get_findings with result: "FAIL", then result: "FLAG". Narrow with category, status or in_letter. A code-section question is crossbeam_search_findings with search_in: "code_section".
  4. Before you say exactly what a finding asks for, open crossbeam_get_finding_detail (the list cuts summary at about 120 characters), or pass response_format: "detailed" for a whole page.
  5. crossbeam_get_sheet_annotations with finding_id shows it on the sheet: a card host opens the review workspace on the pin; a text host gets image_url (one hour) and should give the person viewer_link. crossbeam_get_sheet_index finds 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.

Related

How do I go over my review results with Claude? · CrossBeam Permits Help