Start Here

The builder had the plans done.

Not perfect. Nobody's first set is perfect. But done — measured, drafted, the obvious things checked twice. Before loading the drawings into the car and driving them down to the counter, he ran the set through the city's pre-check. Think of it as the pass a plan reviewer's eye would make, run first, at the kitchen table, by the person who drew it.

This is round one. It is not a pass or a fail. It is the city coaching the applicant on what to change before the city ever sees the plans — the whole point being that the set lands at the counter clean enough to clear with one correction letter instead of several.

Here's what used to come back.

A number. A big red count at the top of the screen, every problem tallied and stacked like a parking ticket. Below it, the findings, sorted by sheet — every comment that happened to touch the same page piled together, whether or not the comments had anything to do with one another. On one run, nine of thirteen notes landed under a single sheet. The order you'd read them in had nothing to do with the order you'd fix them in. And the one question the builder actually had — where do I start? — wasn't anywhere on the page.

A list, or a path

That's the thing a wall of red can't do. It tells you how bad it is. It never tells you what to do next.

A list tells you what's wrong. A path tells you what to do.

So the pre-check stopped handing back a verdict and started handing back a plan.

The new brief opens with the good news. Before a single fix, it lists what already works — a few plain lines drawn from everything that passed. The setbacks check out. The egress window is sized right. The cover sheet agrees with itself. You read what you got right before you read what you didn't, which is both kinder and, it turns out, more useful: it tells you how much of the set you can leave alone.

In the order you'd actually do it

Then the things to fix — not scattered by sheet, but sorted into the order a person would actually work them:

Start here
Finish your drawings
Submit with your plans

Start here is deliberately short. It holds only the decisions and the few items that gate everything else — the report another professional needs before they can begin, the scope call that changes what you draw. It's meant to be the applicant's first week. Finish your drawings is the drawing work. Submit with your plans is the paperwork and the forms. Work the list top to bottom and you're working it in roughly the order the job wants to be done.

And every step is written twice.

The line the builder reads names the action, the place, and who does it, in plain words — no code sections, no engineering values, nothing that sounds like a plan checker. "Hire a structural engineer. They design the foundation and the retaining walls, and stamp the S sheets." Or: "Mark the escape window in each bedroom on the floor plan." The technical freight — the section numbers, the dimensions, the detail callouts — rides alongside, under a line marked for your designer, where the engineer or the architect will actually look. The applicant gets the human sentence. The professional gets the spec. Nobody has to translate.

Your choice

Some fixes aren't a fix at all. They're a decision.

Where the set could go two ways — keep the wall or move it, gas or all-electric, an addition or new construction — the brief doesn't quietly pick for you, and it doesn't dump the question in your lap either. It lays out two or three options, says what each one takes, and then does the thing a good plan expediter does for a nervous client: it recommends. One line. Your choice. We suggest… The call stays yours. The counter is still the counter — local amendments and a plan checker's read are the last word — but you walk in having already made the decision instead of discovering it.

A hundred ways to be wrong, a handful of things to do

Underneath the brief is a review that ran hundreds of code and city requirements against the set. That depth matters, and the old screen wore it like a badge — the bigger the red number, the more the review seemed to have done.

But the applicant was never going to action a hundred rows. So the brief does the collapsing a reviewer does in their head: when the city would write several nitpicks as one correction with a bulleted list, the brief writes them as one step. A review of hundreds of checks comes back as a short page. On one run it was thirteen steps — that's an illustration, not a promise; some sets run shorter, some longer — but it's always a page a person can hold in their head.

What it never shows is a grade. No accuracy percentage. No readiness score ticking toward green. No line claiming the city will approve, because no honest pre-check can say that. It shows the work, not a verdict on the work.

Walking up knowing

That's the whole turn, and it's a small one, and it's the kind of small that changes how a Saturday feels.

Before, a builder closed the laptop knowing exactly how wrong the set was and not much else. Now he closes it knowing what already works, what's left, and the order to do it in — a short, plain list he could read aloud to a friend. He drives to the counter not hoping, but knowing what's in his hand.

A list of what's wrong and a path to a permit are not the same document. The pre-check finally hands back the second one.