Putting the PDF online isn't putting the service online.

Two ways to apply for the same permit

Here's one small-business permit, applied for two ways. Both are made up, but if you work in a city or county office, both will look familiar.

Before. The applicant finds a link on the city website that says "Application (PDF)." It opens a six-page form. They're on their phone, so they email it to themselves, print it at the library, fill it in by hand, sign it, scan it with a phone app, and email it to a general inbox. They're not sure it arrived.

After. The applicant clicks "Apply for a permit." The first screen tells them what they'll need and how long it usually takes to fill in. A few questions in, the form already knows which sections apply to their kind of business and skips the rest. They upload one document, pay, and get a confirmation with a reference number and a short "what happens next." A clerk sees it in a queue that afternoon, with every field already typed.

Same permit. Same rules. The difference is what everyone had to do to get through it.

Before: what the PDF asks of everyone

A PDF form is a faithful copy of a piece of paper, and paper has habits that don't suit a screen.

It asks everything, every time. Every applicant sees every question, including the ones for situations that don't apply to them. Section 4 is "only for food businesses," but everyone has to read it to know that.

It speaks in the office's language. Field labels written for staff, such as codes, statute references, and internal terms, make sense to the people processing the form and very little to the person filling it in.

It can't help. It doesn't check that a date is real, a phone number has enough digits, or a required document is attached. Mistakes are found later, by a person, who then has to chase the applicant.

It goes quiet after you send it. No confirmation, no reference, no sense of what happens next. That's how a form turns into phone calls.

And for staff, it's a typing job. Someone retypes the handwriting into the system that actually runs the service, and does their best with the parts they can't read.

After: fewer, plainer questions

The best online forms are usually shorter than the paper they replace, because the people building them asked hard questions about every field.

Drop what you already know. If the applicant has an account, or you can look something up, don't ask again. If a field exists only because the paper form always had it, find out who uses it.

Show only what applies. A few early questions can decide which sections someone needs. A sole trader shouldn't scroll past the partnership section.

Ask in plain language. "What's the address of your business?" beats "Premises location (per zoning designation)." Give an example where people often get it wrong.

Say what's needed before they start. A list of documents and a rough time to complete stops people abandoning halfway to go find a lease.

Check as they go, and let them save. Catch the obvious mistakes on the spot, explain why, and let someone come back tomorrow without starting over.

After: the part behind the form

The difference people feel isn't just the screen. It's what happens once they press submit.

The submission arrives as structured data, not a scan, so nobody retypes it. It lands in a queue with an owner, not a shared inbox. The applicant gets a reference and a clear next step, and later can see where things stand. We wrote about why that matters in most "where is my application?" calls are a status problem.

If a fee is due, it's paid in the same flow. If staff need more information, they can ask through the same record, and the applicant answers there, instead of in a new email thread.

That's the shift from a form to a service: the request carries its context from the person to the team, and both can see what happens next.

The deadline that makes this practical

There's also a rule pushing in this direction. The Department of Justice's ADA Title II rule requires state and local governments' web content and mobile apps to meet WCAG 2.1 Level AA. In April 2026, DOJ extended the compliance dates by a year: April 26, 2027 for governments serving 50,000 people or more, and April 26, 2028 for smaller ones and special district governments.

Two details from DOJ's fact sheet matter for forms. Old PDFs posted before the compliance date are often exempt, but not when people still use them to apply for or access a service. DOJ's own example is a business license application posted as a PDF in 2020 that the public still uses. And third-party tools a government puts on its site, such as scheduling, payment and reservation systems, generally have to meet the standard too.

This isn't legal advice, and your counsel should read the rule for your situation. But for a busy office it changes the math. You can spend the next year remediating and maintaining a shelf of application PDFs. Or you can rebuild the most-used ones as accessible online services, which helps every applicant, not only the ones the rule is written for.

Pick one form and start there

Don't start with all of them. Pick the form that produces the most submissions, or the most follow-up calls.

Sit with the staff who process it for an hour. Count the fields they retype, the ones they chase, and the questions applicants call about. Read the form with someone who's never seen it. Then try it the way some of your applicants will: with a screen reader, with only a keyboard, on an old phone, and with someone whose first language isn't English. Each of those finds problems a design review misses, and fixing them early is far cheaper than fixing them after launch. Then design the online version around those findings, and build the queue behind it at the same time.

This is the work on our government and public sector page: understand intake, case handling and approvals, then build clear digital journeys with accessibility, permissions and traceability considered from the start. If there's a form your office would love to retire, bring us that form and we'll trace it with your team.

Related work: PatientIQ.