Resources / How Flow Forms Works / Who does the work

Do you have to build your own forms and workflows, or does someone do it for you?

The short answer

With most form and workflow tools, building it is your job: the software provides the builder, and someone on staff provides the hours, the design decisions, and the ongoing upkeep. That works for organizations with someone who has the time and the inclination. It quietly fails in offices where nobody does. The alternative model exists: the vendor builds the forms and the approval routing around the office's actual process, and the same people who built it stay on to maintain and adjust it after it's live. In that model, what the office provides is knowledge of its own process, not construction labor. Which model a tool follows is the single most important thing to find out before adopting it, and it's the thing pricing pages say least clearly.

On this page

Why the existing system doesn't cover it How districts and agencies handle it now Where it goes wrong

What doing it well actually requires Common questions How Flow Forms handles it

Why the existing system doesn't cover it

Self-serve form and workflow tools are built on an assumption that's rarely said out loud: that someone at your organization will do the building. The product is the builder, not the built thing. That assumption holds fine where it came from, teams with technical staff and slack in the calendar. It breaks in a two-person business office or a county department where everyone already wears three hats. The tool isn't defective; the labor it assumes just doesn't exist at that desk. And the part that gets discovered latest: the building is never actually finished. Approvers change, processes change, exceptions accumulate, and whoever built it becomes the person who maintains it, permanently, alongside the job they were already doing.

How districts and agencies handle it now

A few ways, all familiar. Some offices assign the build to whoever seems most computer-comfortable, and it becomes an unofficial second job with no backup. Some get partway through setting up a tool, hit the routing and exception logic, and stall, leaving a half-adopted system running alongside the paper process it was supposed to replace. And plenty look at the setup work honestly, conclude nobody has the hours, and stay with email, spreadsheets, and paper on purpose. That last one isn't a failure of will. It's a correct reading of what the self-serve model actually costs in staff time.

Where it goes wrong

The clearest signal is what happens when the builder leaves. A workflow that one person constructed and quietly maintained stops being adjustable the day that person retires or changes jobs, nobody else knows how it works, and the safest option becomes not touching it. The other signal is subtler: the workflows that exist are the ones that were easy to build, not the ones the office most needed, because the hard ones, the multi-step approvals, the exception paths, were exactly the ones nobody had time to figure out.

What doing it well actually requires

The done-for-you model isn't just self-serve with someone else at the keyboard. A few specific things set it apart.

The build starts from a conversation, not a blank canvas

A working meeting covers who submits, who approves, and what the exceptions are, knowledge the office already has, just not yet translated into routing logic.

The construction happens in that same conversation

The workflow takes shape live on the video call as the office describes the process, and the office watches it come together and asks for adjustments in the moment, rather than assembling anything themselves or waiting on a project that runs between calls.

What the office actually provides is short

Names and email addresses of the approvers, a description of how the process currently works, and existing forms or documentation if they exist. No IT team, no project manager, no specification document.

The form itself is designed, not just assembled

A form that produces clean, usable data is structured deliberately, fields hidden behind selects so someone only sees what applies to them, longer forms broken into stages so they invite completion instead of abandonment. That's craft that comes with the build, not a template the office is left to figure out.

Maintenance belongs to the builder, permanently

When an approver changes, a threshold moves, or a process gets restructured, the same team that built the workflow adjusts it. Lois Lopez, HR Generalist at Belgrade School District, described three years of exactly this: processes that kept evolving with the district, "hiring, resignations, change of position, credentialing, FTE allocation," rather than a system frozen the way it was first set up.

Common questions

Questions we hear before every build.

Who sets up your forms and approval workflows, you or the vendor?

Depends entirely on the tool's model, and it's worth asking directly before adopting anything. Self-serve tools hand you a builder; the setup, the routing logic, and the upkeep are yours. In a managed model, the vendor does all three. The demo rarely makes the difference obvious, because demos show the finished workflow, not the hours that produced it.

Can we keep using the software we already use for everything else, or does this replace it?

Keep it. Nothing about it needs to go away, this handles the specific gap it leaves open, not the rest of what it's used for.

If we already built some workflows ourselves, does switching mean starting over?

No. That existing work describes the process, which is exactly what's needed to build it properly, it's a head start, not a sunk cost.

What if the person who knows our process best doesn't have time for long meetings about it?

The build is designed around that constraint. The workflow gets built live, on the video call itself, with the process knowledge coming out in conversation as the build takes shape, not in documentation the office has to write or a project that runs between meetings.

Does someone doing it for you mean losing control over how the forms work?

The opposite, in practice. Every build is reviewed and adjusted until it matches how the office actually works, and anything can be changed after it's live. Control over what the workflow does stays with the office; what goes away is the construction and maintenance labor.

How Flow Forms handles it

Flow Forms is the second model. The forms and the approval routing get built around the office's actual process, through conversation rather than a project, and the same team stays on to adjust everything as approvers, thresholds, and processes change. What the office provides is knowledge of how it works; the building and the upkeep are never its job. Nothing already in use for anything else needs to go away to make room for it.

See how it would work for your district or agency →