Why didn't putting the city's forms online make the work any easier?
Flow Forms · Government and public agency operations
The short answer
The forms went online, but the work that starts when they've been submitted didn't go anywhere. A fillable PDF on the city website still comes back as a printout at the counter, an attachment in somebody's inbox, or an envelope in the mail, and from there a person carries it: retyping what it says, walking it to the next desk, chasing the signature it still needs. Going digital moved the documents. Doing it well means treating the form as the first step of a process that runs on its own: filled out on a phone, routed to the right desks in order, signed, and on record, with nobody carrying anything.
The forms went online. The work stayed the same size.
Most city and town websites have made the same trip over the past decade. The forms that used to live in a filing cabinet behind the counter now live on the website as fillable PDFs: the facility rental, the business license, the burn permit, the employment application, the utility service request. On paper, that's digitization. The city went digital.
But look at what happens after someone finds one. They download it. They print it, because the signature line wants a pen. They fill it out at the kitchen table, and then it comes back to the office one of three ways: handed across the counter, dropped in the mail, or scanned into a photo and attached to an email. From there, someone in the office reads it, retypes whatever needs to go into another system, figures out who needs to see it next, and starts carrying it.
Nothing about that got smaller when the form moved to the website. The pile still exists. It just arrives in more formats than it used to, and the people handling it now do the same work with more screens in the way. The office didn't get a process. It got a scanner.
The web vendor did the job they were hired to do: build the website. Turning each form into a working process, one that moves on its own after somebody fills it out, was never in anyone's scope. So the forms page got built, the PDFs got posted, and the actual work stayed exactly where it had always been: with whoever picks the paper up.
Almost every form on the website is the first step of a process inside the building
A special event permit doesn't end when it's handed in. It goes to the fire department for a review, to the police department for traffic, to public works for the street closure, and back to the clerk to issue. A facility rental needs the insurance certificate checked and the custodial schedule confirmed before anything goes on the calendar. An employment application starts a sequence that runs through interviews, references, and onboarding paperwork.
In a larger city, that chain crosses several departments. In a town of three thousand, it crosses one desk several times, because the clerk is the records custodian, the licensing office, and half the other job titles besides. Either way, the chain itself belongs to nobody. It moves by email, by walked paper, and by one person's working knowledge of who signs what in which order. Ask where a specific request sits right now, and the answer is somebody's memory of who they handed it to.
That knowledge is real, and it's usually excellent. It's also unwritten. The process lives in how the office has always done it, not in anything a new person could pick up and follow. Drawing it out of people's heads and into something that runs on its own is genuine work, and no one in a small city government has been given that as their job. So the forms stay online, the chains stay informal, and every submission still needs a person to carry it through.
What doing it well actually requires
Getting a city's forms off the download list and into processes that run without anyone carrying them comes down to a few specific things.
Intake that works where people actually are. A form should open on a phone from a link, with no account to create and no password to remember. That matters more than it sounds: a resident reserving a park pavilion once a year will not maintain a login for it, and every abandoned attempt becomes a phone call to the office. It also means the form can meet people in the physical world. A QR code posted on the pavilion itself, at the counter, or on the notice board opens the request right where the question occurs to someone.
A route that's defined once, not remembered each time. When the process is built, who approves what and in which order gets decided one time. After that, a submission starts moving: each desk is notified when the step becomes theirs, and when an approver is out, the step can be reassigned so the chain keeps moving instead of waiting in an unwatched inbox. The City of Apopka, Florida runs its personnel action requests this way, routing each one through the approvals it needs without anyone walking it between offices.
Follow-up that doesn't depend on anyone's memory. The most expensive part of most city processes is the chasing: the signature that hasn't come back, the certificate that hasn't been sent. Doing it well means the reminder is automatic, not a freshly composed email, and the person responsible for the process can see at a glance what's still outstanding.
A record that can answer the question two years later. Public offices carry records obligations that don't scale down for small staffs. Every submission should build its own history as it moves: what happened, who acted, and when, down to the minute. When a council member, an auditor, or a records request asks about a decision, the answer is on file rather than in somebody's recollection.
The PDF actually retires. If the old form survives underneath the new process, the office is still managing documents, just with extra steps. Done well, the process replaces the form entirely. There's nothing to download, nothing to print, and nothing to retype on the other end, because what the person filled out is already the record. And when a rule genuinely requires a paper original in a file, that has its own answer, covered in Filling out required paperwork digitally, without losing the paper original you're required to keep.
Common questions
Questions we hear from city and town offices.
- We just paid for a website redesign. Does any of this touch it?
- No. The website stays, the navigation stays, and the vendor contract stays. The only thing that changes is where the form link points: instead of opening a PDF, it opens a working process. If anything, it finishes what the redesign started, because the city that invested in the website did it so residents would actually use what's on it.
- A lot of our residents aren't online. What about the people who walk in or mail things?
- They keep walking in, and the office keeps helping them. The difference is what "online" requires. Filling out a form this way takes a phone and a link, not a computer, a printer, or an account, and that covers far more people than the download-and-print version ever did. The QR code at the counter serves the person standing in front of you the same way it serves the one at the park. So does a tablet at the counter for anyone who walks in without a phone.
- We have about thirty forms on the site. Do we have to do all of them?
- No, and you shouldn't. Start with one: the form that generates the most calls, the most chasing, or the most walking. When it's running, the next one is easier to see, and the office decides the pace. Starting with one also changes what the council conversation looks like whenever you have it: instead of asking anyone to approve a system on faith, you're pointing at a process that's already running and showing what it changed.
- Who does the building? We don't have technical staff.
- You don't need any. The same team that builds your process runs it and stays on to change it when your process changes. Your staff never configures software. The build starts with a conversation about how the process actually works today, including the parts that only exist in one person's head. Drawing that out is part of the job.
- What happens when the person who knows the whole process retires?
- The process keeps running, because it no longer lives in that person. The routing, the order, the record: all of it is in the system rather than in someone's working memory. For an office where one person holds most of the institutional knowledge, that's the difference between losing a colleague and losing the way the town does things.
How Flow Forms handles it
Flow Forms builds and runs the processes behind a city's forms. We start with the form you bring us and a conversation about how it really moves: who touches it, who signs it, where it stalls. Then we build the process around exactly that, with the people whose names are on the steps, and it goes live working the way your office already works. Nothing like a typical software rollout. No IT project, no six-month timeline. We build it together around your process, and we stay on to make changes whenever you need them.
The form itself stops being a PDF. It opens from a link or a QR code, fills out on a phone with no account, routes itself, tells each desk when it's their turn, gathers its signatures, and files its own record. The last time anyone touches that PDF is the day they hand it to us.
Montana's Office of Public Instruction runs its workflows through Flow Forms, and so do county governments in Montana and Kansas. Cities are the same work in a different building. The City of Apopka, Florida already runs its personnel action requests, compliment forms, complaint forms, and employee exit checklist this way.
Have a form you'd like to see run this way? Bring us the worst one. We'll talk it through together: who touches it, where it stalls, and what it would look like running on its own.