CrossBeam Pre-Check

Cities & Builders

Every sheet. Every code.
Cited.

One AI plan-review engine with two faces. Builders run it before they submit. Cities run it after. Same reading, same code, same findings — a different letter at the end.

Start a Pre-CheckGet Access for Your City
Architectural miniature of a small home on a parcel — the kind of plan set Pre-Check reviews

Fails and flags.

Findings come in two kinds. Fails go into the corrections letter — they’re violations with citations. Flags don’t — they’re judgment calls, held out for staff, who can promote a flag into the letter or demote a fail out of it. Every finding carries its citation — grounded in California state code and your city’s municipal code, read across the full plan set.

AI drafts. Humans decide. Nothing goes out without staff sign-off.

Failgoes in the letter

Smoke alarms not shown in bedrooms — CRC R314.3

Flagheld out for staff

Water heater strapping detail unclear on sheet P-2

Staff can promote a flag into the letter — or demote a fail out of it.

How It Works

Four steps. A human always reviews before anything goes out.

1

Upload Plans

Drag and drop construction plans or a corrections letter. PDF, any size.

2

AI Reviews

CrossBeam reads every page and cross-references California law + your city's municipal code.

3

Draft Generated

A corrections letter — or a builder’s pre-check report before submittal — drafted with code citations and sheet references.

4

Human Reviews

Your staff reviews, edits, and approves. Nothing goes out without a human sign-off.

Watch It Handle a Real Letter

Full corrections analysis on a real Placentia ADU permit — 14 items parsed, verified, and responded to.

Builder

Before you submit.

Upload your plan set. Pre-Check returns:

Findings

Every issue in the plan set, cited to code.

Action Items

Plain language, written to hand straight to your architect or engineer.

Questions

The open items your plans don’t answer.

Corrections Preview

The letter CrossBeam thinks the city will send you — so you can make it never exist.

Start a Pre-Check
City

After submittal.

The same engine drafts your corrections letter — item by item, code-cited, exported under your letterhead in your city’s own writing style.

Draft corrections letter

Item by item, every finding with its code citation.

The voice of the city

A final pass restyles the export to match how your city writes — not the voice of a robot.

Staff stays in charge

Your staff promotes, demotes, edits, and signs. Nothing goes out without them.

Two Departments That Read Plans

Community development has two desks that review plans. Pre-Check works both — because they read differently.

Building: it’s math.

Ministerial review is “by right” — objective. The plan either complies or it doesn’t: setbacks, spans, fire ratings, stamps. It’s the most compute-intensive review in the building, and the most automatable.

This is spell check for building code — it catches the missing stamps, absent citations, and overlooked code sections, so reviewers spend their time on the judgment that actually requires their expertise.

Planning: it’s judgment.

Discretionary review is judgment. For cities, Pre-Check runs a fast, checklist-style planning screen so routine items are settled before the judgment starts. For builders, it trends toward advocacy — density bonus law, waivers, builder’s remedy, with the record to back the ask.

Get Access for Your City

Around the engine.

Screener gates what reaches the engine. Scout scopes the project before plans exist. Corrections Analysis handles the letter you already got. Corrections Response closes the loop at resubmittal. And the Permit Assistant answers the questions in between.

14 items, ~15 minutes

A real Placentia corrections letter handled end to end.

480+ city codes researched

Plus 16,000+ pages of state code and local rules.

40+ permit types

Reroofs, pools, solar, EV chargers, signs, and more — deepest coverage in Huntington Beach.

1st Place

Anthropic’s Claude Code Hackathon 2026 · 13,000 applicants.

Ask a question first