How do school districts pay game officials who are not on payroll?
Flow Forms · Business office operations
The short answer
Districts pay game officials through vouchers, not payroll, because an official who works Tuesday's game is not an employee and nothing about the payroll process fits them. The money often comes from an activity fund with its own rules rather than the general fund, and the volume runs with the sports calendar: every game generates a voucher, every season generates dozens. Most districts run this on paper vouchers and athletic director memory, because payroll systems are built for employees and the accounting system only sees the payment after everything upstream already happened. Doing it well means each voucher moves through a defined approval path from the event to the business office, the rates and required details are built into the form instead of remembered, and the season's record assembles itself as the games are played.
Why this is nobody's system
An official who referees Tuesday's game is not an employee, so nothing about the district's payroll process fits them. The athletic director who initiates the voucher is not the business office, so the request starts outside the office that has to finish it. And activity fund money carries its own approval expectations, because it is often student-generated and separately audited, which makes the paper trail matter more, not less. Districts end up with a process that belongs to everyone partially and no one completely: the athletic director tracks who worked which game, the business office processes what arrives, and the connecting tissue is paper vouchers moving between buildings on whatever schedule the season allows. Extra-duty pay for the district's own staff, the coach stipend, the teacher covering a class, is a different process with its own path, because those people are on payroll and this one is for the people who are not.
How districts handle it now
The voucher is usually a paper form the official signs at the game or the athletic director fills out after it. It rides to the district office in a mailbag or an athletic director's truck, sometimes one at a time, sometimes as a stack at the end of a busy week. The business office receives them in batches, checks them against rates that live in a handbook or a spreadsheet, and processes payment. Questions run backward down the same path: a missing voucher, an unclear rate, an official asking where their check is, each one a phone call or an email to reconstruct something that happened at a gym two weeks ago. Activity fund purchase requests move the same way, a form or an email to whoever approves that fund, with the fund's balance and the request often living in different places.
Where it goes wrong
Volume is the multiplier. One voucher on paper is fine; a basketball season of them is a stack, and a district running multiple sports across multiple schools is processing hundreds of small payments a year through a channel built for none of them. Vouchers arrive late or not at all, and the official who worked the game becomes the person calling to ask about it, which is a bad position to put someone the district needs back next season. Rates get applied from memory and drift from what the board actually set. And because activity funds draw audit attention out of proportion to their size, the thin paper trail lands exactly where scrutiny is highest: money moving, approvals implicit, documentation scattered between the gym and the office.
What doing it well actually requires
Handling athletic vouchers and activity fund requests well means routing each one from the event to the office with the rate and the fund's rules built in, and it comes down to a few specific parts.
The voucher starts where the game happens and routes itself to the office
The request enters the workflow at the event, from the athletic director or whoever initiates it there, and follows a defined path to the business office. Nothing rides in a truck. A Wyoming district running one of the highest-volume workflows in Flow Forms uses exactly this shape for its athletic officials vouchers: per-game volume, all season, moving through the same routed process instead of accumulating as paper.
The rate is in the form, not in anyone's memory
Pay scales for officials are exactly the kind of number that should be calculated by the form itself. Flow Forms builds calculation into forms directly, computing amounts from what is entered against rates stored in the workflow, and those rates never change silently: the district updates them, or tells Flow Forms to. Every voucher in a season pays against the same current rate, and the business office stops checking arithmetic on paper forms against a handbook.
People outside the district can complete their part
Officials, like parents and outside agency staff, do not have district logins, and the process cannot depend on them having one. Forms reach people outside the organization wherever they are, which for an official can mean signing their part of the voucher at the game on a phone rather than on a carbon form that then has to survive the trip to the office.
The activity fund's own approval rules are the routing
An activity fund request routes to whoever the district says approves that fund, with whatever conditions apply, in the order they apply. The fund's rules stop being tribal knowledge enforced by the one person who remembers them and become the path the request physically follows.
The season's record assembles itself
Which officials worked which games, what each was paid, who approved it, and when it moved: that record accumulates as vouchers flow, searchable when the athletic director gets asked, when the official calls, or when the activity fund audit comes. Nobody reconstructs a season from a folder of carbons.
Common questions
Questions we hear from every business office.
- How do school districts handle payment paperwork for athletic officials who aren't employees?
- Usually on paper vouchers, precisely because officials do not fit the payroll process built for employees. The durable version keeps the distinction but fixes the channel: the voucher is a routed request initiated at the game, carrying the official's information and the correct rate, arriving at the business office approved and complete instead of as a carbon form in a stack. The payment itself still runs through the district's normal accounting; what changes is everything upstream of it.
- How does the business office keep track of officials' pay rates when they change?
- In most districts, a handbook or a spreadsheet, checked by hand against each voucher. Built into the form, the rate is applied automatically to every voucher and updated in one place when the board changes it. Nothing pays at last year's rate because someone grabbed last year's form.
- What does an approval process for student activity fund purchases look like?
- It looks like whatever the district's own rules for that fund say, which is the point: the request routes to the fund's approver, with any conditions the district requires, before money moves. The common failure is not missing rules but unenforced ones, requests approved conversationally and documented after the fact. A routed request makes the rule and the path the same thing.
- Do we have to process hundreds of paper vouchers every season?
- The volume does not go away; the paper does. A district running high per-game voucher volume through a routed workflow processes the same number of requests with none of the physical accumulation, batching, or transport, and every voucher is findable afterward.
- Does this replace our activity fund accounting?
- No. The fund accounting stays where it is. This is the request, approval, and documentation layer in front of it, so what reaches the accounting side is complete and already approved through the path the district defined.
How Flow Forms handles it
Flow Forms builds the district's actual voucher and activity fund process as routed workflows: initiated where the event happens, rates calculated in the form and kept current under the district's control, signatures reachable for people outside the organization, and approval paths that follow each fund's own rules. The record of the season builds itself as the requests flow, and the same team that built the routing adjusts it when the sports, the rates, or the rules change.