Only What the Code Actually Requires

Every builder has a version of this story.

You do the work. You draw the set, you meet the code, you walk it to the counter — and you get sent back for something that, when you finally chase it down, isn't in the code at all. It was on a handout. It was how the office had always done it. It was a line someone typed years ago that nobody ever struck.

That's the gap this is about: the distance between what a city's adopted ordinance actually requires and what the city's own paperwork asks for. They are not always the same thing. And a builder pays for the difference — in a stamped set they didn't need, a fee that was never owed, a week lost to a barrier the law never wrote. CrossBeam is built to hold that line.

The handout that asked for more than the code

Here's a real one, offered as an illustration of the kind of over-ask the review is built to catch.

A city's ADU guidance handout stated, in plain language, that building plans had to be submitted concurrently with civil improvement plans prepared and stamped by a licensed civil engineer for an encroachment permit — and that "building plans will not be accepted for processing" without both. Miss either piece and the submittal was rejected at intake. Not corrected. Rejected. Turned away before anyone read a single sheet.

Sit with what that means. This is a ministerial ADU review — the kind the state requires a city to act on within sixty days, the kind a city is not supposed to gate behind discretionary hurdles. And the demand for stamped civil plans and a concurrent encroachment application? It appeared in no ordinance. Not in the ADU chapter. Not in the zoning code. Nowhere in the adopted law. It lived only on the handout.

An applicant reading that handout would do the sensible thing: hire the civil engineer, front the cost, and wait — for a requirement the code never set.

What the review does with a demand like that

This is the turn.

The review doesn't take the handout's word for it. When a demand shows up — from a handout, a checklist, a counter practice, a "we always ask for this" — the review checks it against the ordinance itself. And the test is simple: is this actually in the adopted code?

If a demand isn't in the code, it doesn't become a correction.

So the stamped-plans-at-intake rule got handled the way an over-ask should be. The applicant was told about it up front — this counter expects a civil set and an encroachment application with the building plans, so plan for a civil engineer's cost and schedule. A heads-up, so nobody gets blindsided at the window. But it was never raised as a correction, and never counted as an incomplete submittal. The review would not fail a compliant applicant for skipping a barrier the law doesn't contain.

That's the whole difference. A warning helps you. A correction sends you back. The review knows which one the code supports.

The part that makes it hard

It would be easy if every counter demand were pure fiction. They aren't — and this is where a blunt "ignore the handout" rule would get a builder in trouble.

Because some of what sat near that demand was real. A detached ADU does independently need a new utility connection. And connecting to a city main does independently need an encroachment permit. Those are genuine code triggers, and the review holds you to them.

The unlawful part was never the encroachment permit itself. It was conditioning acceptance of the building plans on producing the stamped civil set up front — turning a real downstream step into an intake gate the ordinance never authorized. The review has to tell those two apart: the requirement the code actually sets, and the paperwork barrier bolted on beside it. That's the reasoning the reader is paying for.

Not the only over-ask

The stamped-plans demand wasn't alone. Two more claims on the same city's paperwork didn't survive a look at the adopted record.

One said every new and existing utility service line had to be undergrounded to city standard. It read like code. It appeared in no ordinance, no guideline, nowhere in the record — so it didn't become a requirement.

The other was a non-refundable deposit attributed to the local fire district. Chased down, the number turned out to belong to a different county bureau entirely — one that doesn't even serve the city. A fee from the wrong agency, quietly assigned to the right-sounding one. It didn't survive either.

None of these was malicious. This is just how paperwork drifts: a line gets copied forward, an agency's number lands on the wrong form, a "we always ask for this" hardens into "the code requires this." Over years, a handout accretes demands the ordinance never made.

Why it's built this way

A permit is expensive enough when the code is the only thing standing in the way. It shouldn't cost more because a handout over-asked.

So the rule underneath the review is narrow and stubborn: hold the permit to what the adopted ordinance actually says. Warn a builder about what a counter will expect. Hold them to every requirement the code really sets. But refuse to manufacture a correction the law never wrote — because a correction sends a real person back, and no one should be sent back for a rule that doesn't exist.

Treat the examples here as illustrations of that behavior, not a promised result on any given permit. Counters differ, codes change, and the demand on one city's handout is not the demand on the next. Always verify a requirement against the jurisdiction that will actually stamp your set — the review's job is to make sure that when they do, you're being held to the code, and only the code.