Every government form is a service in disguise.

It has a job to do. It asks for information. It delivers a result. And somewhere in between, it either respects the person holding it or it doesn’t.

Most don’t.

Not out of malice — out of accumulated habit. Layer by layer, form by form, department by department, nobody ever stepped back and asked: what is the minimum burden required to accomplish this?

This post is a framework for asking that question. I call it a Civic UX Teardown.

What a Civic UX Teardown is

A teardown is a structured read of a public document — a form, a notice, a permit, a renewal packet — from the citizen’s perspective.

The goal is not to complain. The goal is to identify every unit of friction and then ask: is this friction load-bearing? Does it serve the service? Or does it just exist?

You can run this on anything: a business license renewal, a building permit application, a utility enrollment form, a voter registration card.

The structure is the same every time.

The framework: eight layers

1. Identifying marks

What makes this document official? Look for: agency name, logo, seal, letterhead, jurisdiction, case or account number, document type label.

These elements exist to establish authority and traceability. They’re load-bearing — but often overdone. Two agency logos where one would do. A seal and a letterhead and a footer that repeat the same address three times.

For each identifying mark, ask: does the citizen need this, or does the agency?

2. Addressee and account

Who is this for? Does it name the recipient clearly? Does it include the account or license number so the recipient can reference it?

This is where many documents fail immediately. The letter arrives addressed to “BUSINESS OWNER” or to a name that hasn’t been current in four years. The account number is buried on page two.

Friction here costs call center minutes. People call because they’re not sure the document applies to them.

3. Deadline

When does action need to happen? Is the deadline prominent? Is it expressed in a way that leaves no room for confusion — a specific date, not “within 30 days of receipt”?

Ambiguous deadlines generate late renewals. Late renewals generate penalties. Penalties generate disputes. Disputes cost both sides more than the renewal ever did.

4. Instructions for paper (analog)

If someone is completing this on paper:

How many steps are there?
Are the instructions in plain language?
Is the sequence logical?
Are there fields that appear to require information the recipient cannot reasonably have?

Paper forms also carry implicit instructions: signature lines, checkboxes, “office use only” zones. Each one is a potential point of confusion.

5. Instructions for online (digital)

If there’s an online option:

Is the URL provided?
Is it short and memorable, or a 60-character path that has to be typed manually?
Does the online flow match the paper flow, or does it introduce new steps?
What happens if the online system is down?

The online path should be unambiguously easier than paper. If it isn’t, you haven’t digitized the service. You’ve just added a second channel.

6. Financial information

What does it cost? Is the fee stated clearly? Are accepted payment methods listed? Are there penalty fees, and are they explained?

Fee confusion is one of the most common sources of incomplete submissions. People stop when they’re not sure how much to write the check for.

7. Additional verbiage

Everything on the document that isn’t instructions or data fields. Legal disclaimers. Statutory references. Privacy notices. Return address. Processing time estimates.

This layer is usually where the document’s age shows. Language gets added over time for legal reasons and never removed. Most of it is never read.

Some of it is load-bearing — legally required. Most of it is not. Distinguish between the two.

8. Decoration

Visual elements: borders, logos, shading, seals, watermarks, colored headers. Physical elements: paper weight, envelope design, postage.

These elements signal legitimacy and seriousness. But they also add cost and visual complexity. A cluttered document trains people to stop reading.

Applying the framework: business license renewal

Let’s run the teardown on a typical city business license renewal. This example draws from common patterns across California municipalities. The specifics vary, but the friction points are consistent.

What arrives in the mail

A standard business license renewal packet typically includes:

A one-page renewal notice
A one-page instruction sheet
A pre-addressed return envelope
Sometimes: a current-year license for display

Three pieces of paper. One envelope back. The total time to complete, if everything is clear, should be under five minutes.

Often it isn’t.

Layer by layer

Identifying marks. The city logo, department name, and “Business License Renewal” label are usually present. The account number is present — but sometimes formatted differently than it appears in prior correspondence. One document, two formats for the same number. Now the citizen isn’t sure which to use on the check.

Addressee and account. Addressed to the business name, which is correct. But the address may be the business address on file, which may have changed. No prompt to update it. The city will send next year’s renewal to the wrong address.

Deadline. Usually present, often clear. This is one of the better-executed elements of most renewal notices. The “renew by” date is prominent. Penalty language is nearby.

Instructions for paper. Typically three to five steps: verify business information, note any changes, calculate the fee, write a check, mail it back.

Where this breaks:

Fee calculation requires a table that is either not included or referenced by a URL that leads to a PDF.
“Note any changes” usually means write in the margin. There’s no structured field.
Signature line exists but its legal significance is not explained.

Instructions for online. A URL is provided. Often it looks like: https://aca.accela.com/[cityname]/Cap/CapApply.aspx

That URL cannot be typed without error. It cannot be remembered. It communicates nothing about what it is or what will happen when you visit it.

The online portal, once reached, often requires creating an account. The account requires an email address that may not match what the city has on file. The license number must be entered exactly as formatted — but the format is not shown on the form.

Three obstacles before the form is even open.

Financial information. Fee amount is usually stated. Payment methods for online are sometimes listed, sometimes not. Credit card fees — a surcharge for using a card — are sometimes mentioned, sometimes discovered at checkout.

Discovering a fee you didn’t expect at the last step is a conversion killer. In government, it’s a compliance killer.

Additional verbiage. Renewal notices typically carry a paragraph of statutory language citing the municipal code section that requires the license. A privacy notice. A statement that false information is subject to penalty.

None of this is read. Most of it is required. It should be there — in a smaller font, at the bottom, clearly secondary. Usually it’s in the same font, in the middle of the page, competing with the instructions.

Decoration. City seal, department header, colored band across the top. Return envelope with city address. Pre-printed account number on the envelope stub.

The stub is a good idea — except when the stub instructions say to include it with payment but the envelope flap covers it when sealed. A detail that breaks the physical flow.

What this tells us

Running the teardown produces a list of friction points. The goal is not to count them. The goal is to sort them.

Load-bearing friction: required by law, required for identity verification, required for traceability. Keep it. Minimize its footprint.

Reducible friction: formatting inconsistencies, redundant information, unclear payment instructions, unusable URLs. Fix these without a policy change.

Eliminatable friction: verbiage that exists because no one removed it, decoration that adds visual noise, steps that exist because the paper and online flows were never reconciled.

For the business license renewal, most of the friction is in the second and third categories. The legal requirement is simple: verify you’re still in business, confirm your information, pay the fee. That’s a three-minute task.

The document, as typically designed, makes it a twenty-minute task — with a non-trivial chance of error, a support call, or an incomplete submission.

The ROI question

Let’s put a number on this.

Assume a city has 3,000 business license renewals per year. Assume the current process takes the average business owner 20 minutes to complete. At $75/hour in opportunity cost, that’s $25 of the owner’s time per renewal. Across 3,000 renewals: $75,000 in aggregate citizen time, per year, for one administrative transaction.

Now assume 8% of renewals require a follow-up — a call to clarify the fee, a resubmission because the form was incomplete, a penalty dispute. That’s 240 support interactions. At 15 minutes of staff time each, at $30/hour fully loaded: $1,800 in staff cost.

The direct staff cost looks small. The citizen cost is substantial.

Now redesign the process:

Clear fee table on the form, no external URL required
Online path with a short, memorable URL
Account pre-populated from city records
No account creation required for returning filers
Payment confirmation sent by email

Reasonable target: 8 minutes to complete, 3% follow-up rate.

Citizen time savings: 12 minutes × 3,000 = 600 hours = $45,000 returned to the local economy. Staff savings: 150 fewer support calls = $562 saved.

The design investment pays back in the first year. Every year after that is pure return.

This is what ROI looks like at the service level. Not just the cost to the city. The cost to the people the city exists to serve.

Why this matters

Government services are not optional. You can’t choose a different business license vendor. You can’t comparison-shop your utility connection. When the service is burdensome, the burden is inescapable.

That asymmetry is a civic obligation. Every unnecessary minute a citizen spends navigating a confusing form is a minute extracted by the institution — without consent, without acknowledgment, without recourse.

The teardown is a way to make that extraction visible. Name it. Measure it. Fix what you can.

I’ll be doing more of these. Next: building permit applications.

Have a civic form you’d like to see torn down? Get in touch.

This teardown is the public version of our Service Experience Review — a secret shopper for government services, with a service map, ranked recommendations, and hands-on help for your team.

Civic UX Teardown: Business License Renewal