A facility request process almost never fails at the form. It fails in the fortnight after the form, in the gap between a community group asking to use the gym on a Saturday and somebody with the authority to say yes actually saying it. In between sit the custodial schedule, the insurance certificate that has not arrived, the fee schedule that only one person understands, and a calendar that two people are editing from different assumptions.
That is why facility request pages on school district and campus sites tend to be a list of PDFs and a phone number. The work is not collecting the request. The work is routing it through three or four people, holding the space while that happens, and telling the requester where it stands. What follows is about how to design for that, and where the tooling boundary genuinely sits.
Two different requests wearing the same name
The single most common design mistake is running internal and external facility requests through the same form.
An internal request is a member of staff asking for a room next Tuesday. They know the building, they need no insurance, there is no fee, and the only real questions are whether the space is free and whether anyone needs to unlock or set it up. The right form here is short enough to finish on a phone between lessons.
An external request is an outside organisation asking to use a facility, usually at a weekend, usually with an audience. That request needs a named responsible person, proof of insurance, a fee category, a decision about whether the event is open to the public, custodial cover outside normal hours, and in many cases sign off from someone who was not involved in any of the above. It also needs a much earlier deadline, because the approval chain is longer than the notice most requesters give.
Running both through one form produces the familiar compromise: a long form that internal staff resent and skip, with half the fields marked "if applicable" so that external requesters can ignore the parts they should not. Two forms, linked from the same page, with a sentence explaining which is which, removes most of the friction on both sides. The internal form can be six questions. The external one has to be thorough, and that is fine, because an organisation renting a gym for a season expects paperwork.
Fields that let a request be approved without a reply
The test is the same as anywhere else: a field earns its place if the answer changes the decision. In facility requests, what changes the decision is almost always time, people, and liability.
The actual window, not the event time. An event from 10:00 to 12:00 occupies the space from 08:30 to 13:00 once setup and clearing are counted. Asking only for the event time is how two bookings end up overlapping on paper by zero minutes and in reality by ninety. Ask for setup and takedown separately, or ask for access time and vacate time and treat those as the booking.
Spaces and equipment as separate questions. A request for the hall plus the projector plus forty chairs plus the sound desk involves three different people. One combined free text box headed "requirements" guarantees that one of them finds out late.
Expected attendance. This sets occupancy limits, custodial cover and often the fee tier. It is also the number requesters underestimate most, so it is worth asking as a range with an upper bound they are committing to.
Whether it is open to the public. This one question changes safeguarding, security, parking and sometimes insurance. It is frequently absent from facility forms and it should be near the top.
Food, alcohol, and anything being brought in. Catering changes cleaning. Alcohol changes permissions. Vehicles, marquees, inflatables and amplified sound each have their own consequences, and a checklist surfaces them better than an open question.
The responsible person and who pays. A named individual who will be present, with a phone number, plus the organisation being invoiced. These are often different, and assuming they are the same is a common cause of unpaid invoices.
Document upload. Certificate of insurance, and whatever else local policy requires. A form that cannot accept a file turns into an email thread, and the email thread is where the request stops being trackable.
One field to reconsider: asking requesters to pick their own fee category. Published fee schedules usually distinguish internal use, affiliated non profit use, and commercial use, and requesters self select generously. Ask the questions that determine the category, and let the category be assigned.
Approval is a chain, and the chain is the product
A facility request typically needs several yes answers: the person responsible for the site, facilities or custodial for out of hours cover, sometimes IT or catering, and sometimes a business office to raise the invoice. The design question is whether those happen one after another or all at once.
Serial approval feels orderly and is slow, because each step waits for the previous one and each person has other work. Parallel approval is faster and produces contradictions, because the site says yes while custodial says there is nobody available. The practical arrangement is a single gatekeeper who decides whether the request is viable at all, followed by parallel checks from everyone whose resources are involved, and one final confirmation that goes to the requester.
Whatever the shape, three things have to be true for it to work. Every step needs a named owner rather than a department, because departments do not open email. Every step needs to be visible on the request itself, so the coordinator can answer "where is it" without four phone calls. And the requester needs to be told at submission what the steps are and roughly how long they take, because a silent three week approval chain is indistinguishable from being ignored.
This is the part that general purpose form tools historically did not cover and the reason so many institutions ended up with a PDF. It is also the part request handling with an owner and a visible stage is specifically shaped for.
Double bookings are a sequencing problem
Two facility requests for the same space at the same time is not a form problem. It is a question of when the calendar gets written to.
There are two workable sequences. In the first, submission creates a tentative hold on the calendar immediately, marked clearly as unconfirmed, and approval converts it to confirmed. This prevents the overlap and creates a second problem: abandoned holds clutter the calendar, so tentative entries need an expiry.
In the second, nothing touches the calendar until approval, and the approver checks availability at the moment of approving. This keeps the calendar clean and relies entirely on the approver looking at a current view. It fails when two approvers work the same queue on the same afternoon, or when one of them is working from a printout.
Which one to choose depends on volume. Below a few requests a week, approval time booking is simpler and the risk is low. Above that, tentative holds are worth the clutter. What does not work is the arrangement most places drift into, where some requests are held on submission because a helpful coordinator does it manually and others are not, so the calendar is authoritative for some bookings and misleading for the rest.
One detail regardless of sequence: recurring requests need to be handled as a series rather than as one booking with a note attached. A season of Saturday training is twenty bookings, twenty possible conflicts with one off events, and twenty instances where a holiday closure has to be excluded.
Fees, deposits, and the documents that hold everything up
Most delays in external facility requests come down to waiting for one of three things: a certificate of insurance, a signed agreement, or payment.
The certificate is the worst offender, because requesters often have to ask their insurer for it, which takes days they did not budget for. The mitigation is stating the requirement at the point of request with the exact wording needed, rather than telling the requester after approval that a document they have never heard of is now blocking their booking.
Fees deserve the same treatment. A published fee schedule with the categories and the hourly rates, linked from the form and referenced in the acknowledgement, converts the most common follow up question into something the requester answers themselves. Deposits and cancellation terms belong in the same place. If a cancellation inside a certain window forfeits the deposit, that has to be visible before submission, not in an agreement sent afterwards.
The pattern across all three is that documents and money are a sequencing problem as much as approvals are. Asking for a certificate of insurance before anyone has checked whether the space is even available wastes the requester's time. Asking for it after approval delays a confirmed booking. Asking for it in parallel with the approval checks, with the request visibly waiting on it, is the arrangement that keeps both sides informed.
What each option actually covers
| Email and a shared calendar | Free online form plus a spreadsheet | Form tool with response management | Facility or facilities management platform | |
|---|---|---|---|---|
| Structured request data | No | Yes | Yes | Yes |
| Owner per request | No | By convention | Field on the record | Assignment and roles |
| Visible stage for the requester | No | No | Yes | Yes, via a portal |
| Multi step approval | Manual | Manual | Stages with owners | Configurable workflows |
| Calendar availability check | Manual | Manual | Manual | Built in |
| Recurring bookings as a series | Manual | No | Manual | Yes |
| Fee calculation and invoicing | Separate | No | No | Often included |
| Document upload | Attachments | Varies by tier | Yes | Yes |
| Typical pricing basis | Included | Free | Per person | Per user, or per site |
| Published entry price | Zero | Zero | Often free for one person | FMX publishes no prices and quotes on the number of users and features enabled; UpKeep lists Essential at 24 dollars per user per month and Premium at 55 dollars per user per month |
Two facts are worth pulling out of that last row. FMX gives public K to 12 schools pricing based on student enrolment, with as many users as they need at no extra cost, which changes the arithmetic considerably for a district weighing a platform against a form. And in maintenance and facilities platforms generally, the public portal where requesters submit and follow their own requests is often not in the entry tier: UpKeep places an external request portal in its Professional plan, which is quote only.
The middle column is the one that gets forgotten. A team whose facility requests are failing at ownership, visibility and the reply, while the calendar itself is working fine in Google Calendar or Outlook, is looking at a smaller purchase than a full scheduling platform. The features that matter there are stages, owners and replying from the same screen as the request, not room inventories.
What to change first
Split internal and external requests into two forms, and change the time question so it asks for access and vacate times rather than event times. Those two changes remove the majority of both the overlap problems and the abandoned half completed submissions. If the remaining pain is that nobody can say which of the four approvers a request is currently sitting with, move intake to a tool that puts an owner and a stage on every request, such as Halict.
Q1. What should a facility request form ask for?
Access and vacate times rather than just the event time, the specific spaces and equipment as separate questions, expected attendance as a committed upper bound, whether the event is open to the public, food and alcohol, a named responsible person who will be present, the organisation to be invoiced, and an upload for the certificate of insurance. Let the fee category be assigned from those answers rather than chosen by the requester.
Q2. How far in advance should facility requests be submitted?
Far enough to cover the slowest step in the approval chain, which is usually the insurance certificate rather than any internal decision. Published notice periods of two to four weeks for external requests are common, and whatever the number, it works only if the reason is stated and the chain is visible to the requester.
Q3. How do you stop two groups being booked into the same room?
Decide when the calendar gets written to and apply it consistently. Either submission creates a clearly marked tentative hold with an expiry, or nothing is held until approval and the approver checks a live calendar at that moment. The failure mode is doing both inconsistently, which leaves the calendar authoritative for some bookings and misleading for others.
Q4. Should internal room bookings use the same form as external rentals?
No. An internal booking needs about six questions and no paperwork. An external rental needs insurance, fees, a responsible person and several approvals. One combined form ends up long enough that internal staff avoid it and vague enough that external requesters skip fields they should not.
Q5. Is a form tool enough, or is facility scheduling software needed?
If the calendar is already working and the problem is that requests have no owner, no visible stage and no reply, a form tool with response management covers it. Scheduling software earns its price when room inventories, recurring series, fee calculation and invoicing all need to live in one system, and when a public portal for requesters is a requirement rather than a nicety.