For school districts

The work that keeps a district running.

A school district runs on the request that needs three signatures, the paperwork a parent has to return, the hire that touches four offices before anyone starts, the record the auditor will ask for in two years. We build the processes behind all of it, take them off your hands, and keep them moving.

Book a conversationAbout 30 minutes
In a district right now
District office · submissions on file
This week, partial
Ref2214
ProcessRequisition
Started byA teacher, high school
HandledTue 1:12 PM
StatusOrdered
Ref2209
ProcessIEP signature
Started byA parent, from a phone
HandledTue 7:48 AM
StatusSigned
Ref2201
ProcessLeave request
Started byA paraprofessional
HandledMon 3:20 PM
StatusCovered
Ref2194
ProcessMaintenance request
Started byA head custodian
HandledMon 6:55 AM
StatusIn the shop
Ref2188
ProcessBus conduct report
Started byA driver, from the yard
HandledFri 4:07 PM
StatusAnswered
Five processes, four offices, one week. Nobody walked any of it anywhere.
01 · The condition

Your systems each do their job. Nothing owns what crosses between them.

Every district already owns its big systems: one for students, one for the books, one for special education, one for payroll. Each does its own job well. None of them was built for the work that crosses from one to the next. So that work gets done the old way.

01A printed form walked to the next building.
02A fillable PDF that comes back as an attachment and gets printed anyway.
03A spreadsheet somebody keeps because nobody else does.

None of them was built for the work in between.

02 · The work

It is the same kind of work everywhere. It looks different at every desk.

01
The approvals that cross buildings
A purchase, a leave request, a field trip, a facility rental. Started in one office, signed in the superintendent's, filed in a third.
02
The signatures that leave the building
Parents, substitutes, vendors, board members. People who will never log into your systems and should not have to.
03
The records someone will ask for later
Who approved it, when, and what it said at the time. Built into the process, not reconstructed after the fact.
04
The work the state puts on the calendar
The forms with a statute behind them and a deadline nobody in the building chose.
05
The work that lives in one person's head
How it actually gets approved, who to call when it stalls, which folder it's in. Built into the process, so it does not leave when they do.
03 · The desks

Which desk does it land on?

Requisitions, reimbursements, leave, the forms in between.
Parent signatures and meeting paperwork without the two-week wait.
From application to exit, every step on record.
Bus conduct reports, vehicle requests, driver time off, resolved the same day.
Work orders and facility use approvals, cleared before they hit the calendar.
Enrollment, records requests, and out-of-district agreements, signed from wherever the family is.
And if it does not land on one of these, it still lands somewhere. That one is usually the place to start.
04 · With Flow Forms

That work in between is what we take.

We sit down with you and walk one process, step by step, the way it really runs in your district. Who starts it, who has to sign, where it waits, what happens when that person is out. What you get is your process, running.

From then on it moves on its own. It goes to the next desk without anyone forwarding it, asks again when nobody answers, collects the signatures from whoever has to give them, and keeps the record of who approved what and when. Your people approve the way they approve now, and nobody has to learn a different way of doing anything.

Your student system, your finance system, and your payroll system all stay exactly where they are. We build the work that crosses between them. And when the process needs to change next year, you tell us and we change it.

How we build it →
What goes away is the carrying.
That's the work we take off your hands.
05 · Tomorrow

What a district looks like after.

A parent signs from her phone on the way to work. The requisition is in the business office by afternoon, with every signature on it. The new hire's paperwork is done before her first day, and nobody walked it anywhere. The record is there when someone asks, exactly as it was.

Requisition 2214 · three offices
Carried by: nobody
Tue 9:40aHigh schoolSubmitted from a classroom
Tue 10:05aPrincipalApproved, and on its way
Tue 11:30aBusiness officeBudget code checked against the account
Tue 1:12pBusiness officeOrdered
Tue 1:12pOn fileWith every signature and the time it was given
Three offices, one afternoon, nobody walked it between buildings.

All of this, and all anyone does is fill out a form. That is a district where the work moves and nobody carries it.

06 · In districts' own words

“Before Flow Forms, we struggled with the approval process—making sure the right people were involved, keeping track of steps, and constantly having to explain processes to new staff members. Now, that stress is gone.”

Stephen Schreibeis, Superintendent
Glendive Public Schools

“It is, by far, one of the most useful and beneficial investments the district has made to date.”

Tamra Covington, Director of Student Services
Billings Public Schools
From the register
What runs there
Billings Public Schools
IEP parent signatures, two weeks to 48 hours
Belgrade Public Schools
HR paperwork, 75% less processing time in month one
Glendive Public Schools
Every department. 12+ processes on file
Columbia Falls Public Schools
Bus conduct, mechanic shop, building maintenance
Harlowton Public Schools
Requisitions, leave, travel reimbursements, P-card
Hardin Public Schools
Job applications, onboarding I-9s and W-4s
Philipsburg School District No. 1
Purchase orders and maintenance requests
Teton County School District #1
Professional development requests
Sublette County School District #9
Employee exit and stay interviews
Big Horn County School District #1
Vehicle repair and vehicle requests, kept separate

Bring us the first one.

Come with the process that's costing you the most. We'll talk it through together and show you how it could work in your office. No slide deck. No generic walkthrough.

Book a conversationBuilt around your district. We do the setup.▊
07 · Questions

Questions we hear from every district.

Can a parent sign without an account?
Yes. A parent gets a link by text or email and signs from a phone. No account, no password, nothing to install.
What happens when the approver is out?
The process routes to whoever covers for them. You decide who that is when we build it, and a request never sits waiting on one person to come back.
Does this replace our student or payroll system?
No. Whatever you use for students, finance, and payroll stays where it is. We build the processes that cross between them.
Can we pull a record back up two years from now?
Yes. Who submitted it, who approved it, when, and what it said at the time.
How is it priced?
Per process, so the office that needs it can say yes on its own.
Who builds it?
We do, with you, on a video call while you watch. Nothing like a typical software rollout. No IT project, no six-month timeline, and we stay on to make changes whenever you need them.
Still have a question?
hello@flowforms.io
A real person reads it