Skip to main content

How do counties handle internal approvals without an enterprise system?

Flow Forms · Government and public agency operations

The short answer

Most counties route internal approvals through some combination of paper, interoffice mail, email, and a person in each office who knows where things actually are. The reason is structural rather than technological: the offices that have to cooperate on a document frequently do not report to the same person, do not share a budget, and cannot be made to adopt anything by a single decision. Doing it well means a process that crosses those lines without requiring any office to surrender its own systems or its own authority, that lets people outside the courthouse act without becoming users, and that makes the position of a document visible inside an order that is often fixed by statute rather than by preference.

Why there is no single system, and why that is not neglect

If you work in a county office, you have probably watched a vendor demonstration that assumed a chain of command your county does not have. The demonstration shows an administrator configuring a workflow, assigning roles across departments, and enforcing a standard. It is a good demonstration. It also quietly assumes that somebody in the building can tell the Clerk's office what software to use.

In most counties, nobody can. The Clerk is elected. The Treasurer is elected. Depending on the state and the office, the Appraiser or Assessor may be appointed by and answerable to the county commission instead. In Kansas, that is exactly the split: the clerk and the treasurer are independently elected officeholders, and the appraiser is appointed by and reports to the commission. Arrangements differ from state to state, and in some states functions that are county-level elsewhere sit with the state entirely. What holds across nearly all of them is that a county is not one organization with departments. It is several offices with separate mandates that happen to share a building and a parcel of work.

What that structure does to a document

A document with a legally fixed path through three offices travels by whatever carries documents, which is usually email and interoffice mail, and nobody can say where it is without asking. The asking is the part that costs. It is a phone call from one office to another, made by someone who has to interrupt a person in a different chain of command to find out whether their own work can proceed.

The absence of an enterprise system is not the problem to solve. The problem is the asking, and fixing it does not require the county to agree on anything county-wide, replace what any office already runs, or find a single person with authority over all of them.

What doing it well actually requires

An approval process that survives in a county has to respect the way a county is actually put together, and that comes down to a few specific parts.

  • It has to be worth adopting one office at a time

    Any process that only works once every office has signed on will not get past the first office. The practical version starts with one chain that one office already cares about, proves itself there, and gets adopted next door because the office next door watched it work. Montgomery County, Kansas runs a routed chain that starts in the Appraiser's office, moves to the Clerk's office, and ends with the Treasurer, with a fourth department, Public Works, now scoping its own.

  • People outside the office have to act without becoming users

    A county approval routinely involves someone who does not work in the courthouse: a title company, a landowner, a contractor, a school, a member of the public. If acting on a step requires an account, a login, and a training session, the step goes back to email and the chain breaks there. The workable version sends the person a link, they do their part, and the record captures it.

  • The order is frequently fixed by law, not by preference

    In a property sequence, the appraiser's office certifies the appraisal rolls to the clerk by a statutory date, the clerk prepares the tax roll after levies are set, and the treasurer bills and collects. Nobody in that chain is choosing the sequence. So the useful thing is not the ability to redesign the order. It is knowing, on any given day, exactly where a specific document sits inside an order that cannot move, and how long it has been sitting there.

  • Public-facing intake is part of the internal process, not a separate project

    In a district, most forms start with staff. In a county, a large share of the work starts with a resident or a business filing something, which means the first step of an internal approval chain is often a stranger with a phone. Montgomery County's build covers nine form types spanning how ownership changes hands by sale, by death, or by court order, and how parcels get split and combined. One of the nine, a change of mailing address, is initiated by the public rather than by staff, sitting in the same system as the internal chain rather than in a separate citizen portal.

  • The office cannot be the one that builds it

    The person who knows which exception applies is usually the same person who processes it, and any fix that depends on that person building and maintaining it is a fix with a retirement date attached. Gallatin County, Montana shows the alternative in a different kind of county office. The County Superintendent of Schools is a county-level education office rather than county administration, and John Nielson, the County Superintendent, described the goal plainly: reduce the workload in the office, stop doing data entry, save paper and time. The office supplied the process knowledge and none of the labor. Somebody else did the work, including a process that had not been built before, and stayed on to adjust it as the office's needs changed. Intent to homeschool went online first. It worked, so the educator licensure registry followed. His note on who benefited is the county reality stated exactly: county educators who never have time to visit an office during work hours, and a homeschool community that no longer has to.

  • Whatever gets built has to change without a project

    Statutes change. An office reorganizes. A commission adds a review step in March. If changing the process means opening a ticket and waiting in a queue, offices go back to email within a year and the record goes with them.

Common questions

Questions we hear from county offices.

Does every office have to adopt this at the same time?
No, and counties that wait for that generally never start. A single chain can run with the offices that are ready, and the offices that are not can stay exactly as they are, because the step that touches them can go out as a link rather than as a system they have to join. Adoption tends to move office by office for a practical reason: the second office signs on after watching the first one stop chasing paper, which is a more persuasive argument than any demonstration.
Who actually owns the process when it crosses offices that do not report to each other?
Operationally, the office that starts the chain usually owns it, and each office keeps authority over its own step. What changes is that ownership of the record stops being distributed across three inboxes. The chain's history exists in one place, timestamped, visible to everyone on it, without any office having handed control of its own work to another one. That distinction matters more in a county than almost anywhere else, because it is the specific objection that kills county-wide software.
Does this change the order our offices have to act in?
No, and it should not. Where a sequence is set by statute, the order is not a design decision anyone is free to make. What changes is visibility inside that order: which step a document is on, who it is waiting on, and how long it has been there. Counties usually do not need a different sequence. They need to stop discovering in late June that something never left the first office.
Someone outside the county has to sign. Do they need an account?
No. The step goes to them as a link, they complete their part, and the action is recorded in the same history as every internal step. That covers the title company, the landowner, the contractor, the parent, and everyone else whose participation is required and whose willingness to create a login is zero.

How Flow Forms handles it

Flow Forms builds one chain with the offices that actually run it, one office at a time, without requiring the county to agree on anything county-wide first. Each office keeps the systems it already uses and the authority over its own step. Steps that reach outside the courthouse go out as a link rather than as an account. The same team that builds the chain stays on to change it when a statute changes or a commission adds a review, so the process does not quietly revert to email the first time it no longer matches the law.

See what one county process would look like →

Related