Clearing insurance, safety, and custodial approval before a facility use request hits the calendar
Flow Forms · Student and school operations
The short answer
A calendar is where a facility use request ends up, not where the actual decision gets made. Before a community group, booster club, or outside organization can use a gym, cafeteria, or classroom after hours, someone has to confirm the group carries the right insurance, someone has to check the date against everything else already happening in that building, and someone has to tell custodial staff the space needs to be unlocked, set up, or cleaned differently than a normal day. None of that is a scheduling problem. It's an approval problem that happens to end with a calendar entry. Doing it well means the calendar is the last thing that happens, not the first: a record of what already cleared, not a placeholder waiting on three different people to get back to someone.
What has to clear before a facility is actually available
A gym, cafeteria, or classroom doesn't become available to an outside group just because a date on a calendar is open. Before that date goes anywhere, three separate people usually have to agree to something. Someone has to confirm the group carries liability insurance that names the district, because if something goes wrong on district property, the district needs to know who's covering it. Someone has to check the date against everything else already happening in that building (an athletic practice, a maintenance closure, an evening class) so a booster club dinner and a wrestling meet don't end up needing the same gym. And someone has to tell custodial staff what the space actually needs: unlocked at a certain time, set up a certain way, cleaned on a schedule that isn't the normal school-day routine.
None of that is a scheduling question. It's three separate approvals that happen, if they all clear, to end in a calendar entry.
Why a request turns into a string of phone calls
Plenty of districts already have a facility use form linked on their website, a PDF the requester prints, fills out by hand, and mails in or drops off. Then they wait. There's no way to check where the request actually stands, so they call to ask if it's been approved yet, or email, or call again a few days later when nobody's gotten back to them. On the receiving end, whoever's handling it has to stop and mentally reconstruct where things are every time the phone rings (has insurance come in, did anyone check the date against the calendar, has custodial been told), on top of actually doing that work in whatever minutes exist between calls.
None of that back-and-forth is the approval itself. It's the cost of nobody being able to see where a request stands without asking someone. A request submitted from a link (posted on the district's website or as a QR code at the building itself) routes in order instead: insurance to safety to custodial, each person seeing only their step and passing it forward once cleared. Anyone holding a piece of it can see exactly where it stands without reconstructing anything from memory, and when a group's insurance needs updating for a repeat request, that happens through the same link, not a phone call.
Why the calendar entry comes last, not first
Once every approval on a request has actually cleared, the event can write itself onto the district's shared calendar automatically, the same general mechanism that already handles this for other approved processes. Nobody has to remember to go add it afterward, and nothing shows up on the calendar that hasn't actually cleared every step ahead of it. The calendar becomes a record of what was approved, not a placeholder someone has to double-check before trusting it.
What doing it well actually requires
Getting a facility use request right isn't about better scheduling software. It's about making sure nothing reaches a calendar until everything ahead of it has actually happened.
Every approval moves through one place, in order
Every approval (insurance, safety, custodial) moves through one place, in order, instead of living in three different inboxes.
The calendar entry is generated once approval clears
The calendar entry is generated once approval clears, not added by hand afterward and not trusted until someone double-checks it.
The outside group doesn't need an account or a login
The outside group submitting the request doesn't need an account, a login, or any familiarity with how the district's internal process works.
Anyone handling a request can see where it stands
Whoever's handling a request can see exactly where it stands without reconstructing anything from memory or waiting for a phone call to ask.
Lincoln County School District #1 runs this today
Lincoln County School District #1 runs this today under what they call a Facility Check Out Form (their own name for the same process).
Common questions
Questions we hear from the people who manage facility use requests.
- What happens if a request comes in but the group can't provide proof of insurance?
- It simply doesn't move to the next approval. Whoever holds the insurance step can deny the request there, and the requester hears back without anyone downstream (safety or custodial) ever seeing a request that was never going to clear the first step.
- What if the person who normally signs off on custodial notification is out that week?
- That approval step can be reassigned to someone else so the request keeps moving instead of sitting until a specific person is back at their desk. This works the same way for any approval step in Flow Forms, not just this one.
- Does this replace the calendar we already use to track building use?
- No. The calendar stays exactly what it is. Flow Forms handles what happens before something is allowed to go on it: the insurance, safety, and custodial approvals. Once those clear, the event can post to the calendar automatically instead of needing someone to remember to add it.
- Can an outside group submit a request without creating an account or logging into anything?
- Yes. The group fills out what they need (the space, the date, the reason) from a link, without needing a login or any familiarity with how the district's internal approvals actually work. That link can sit on the district's website the same way any other form does, or go out as a QR code posted somewhere physical, like a building entrance or a community bulletin board.
How Flow Forms handles it
Facility use approval isn't one form. It's whoever verifies insurance, whoever checks for a scheduling or safety conflict, and whoever tells custodial staff what the space needs, all routing through one place in the order a district actually uses. Flow Forms builds that chain around how a district's own approvals already work, so a date only reaches the calendar after everything ahead of it has actually cleared.