Referee and Match Official Assigning Software: Why Saturday Morning Still Runs on Phone Calls

Why assigning is the operation, and the rest is paperwork

Friday afternoon. Three hundred and forty games this weekend across four age groups and two competitions. Two officials have just declined, one because a shift changed and one without a reason. A senior referee has pulled a calf. Somebody has to fill six slots before Saturday morning, and the only way anyone knows to do it is to open the assigning tool, filter a list, and then start texting.

The tools in use are real products. ArbiterSports, Horizon Web Ref, RefTown and Assignr all exist, all handle availability and publishing, and Assignr in particular is a sensible answer for a small association. What none of them do is solve. They present a filtered list and let a human choose, which means the assignor is the solver, and the assignor is one experienced person who holds an enormous amount in their head: who has an unspoken conflict with a club, who is being developed for promotion and needs a higher level game, who cannot make a 9am after a late Friday, who will accept a two hour drive and who will resent it.

The consequence of failure is unambiguous. An unfilled assignment means a game does not happen, or happens with an unqualified official, which is worse. And underneath the weekend scramble sits a slower problem that every director of officiating recognises: officials leave, recruitment is difficult across almost every association, and two of the most common reasons for leaving are being assigned badly and being paid late. Both are software problems.

Problem 1: assignment is a matching problem, and the tools give you a filter

The real constraint set is longer than any dropdown. Grade level must meet or exceed the game level, and ideally not exceed it by so much that you waste a senior official on an under-13 fixture. Availability is a window, not a checkbox, and it interacts with travel: two games are compatible only if the drive between the venues fits between the end of one and the start of the next with a margin, and that is drive time in Saturday traffic rather than distance on a map. Conflicts are layered: an official who lives in the town, whose child plays for the club, who officiated that team three weeks ago, who was involved in a contentious match with them last season. Crew composition matters, because a trainee needs a mentor on the same crew and two trainees together is a failure waiting to happen. Pay scale varies by level and by travel, so the cheapest legal assignment and the best one are frequently different.

What a custom build does: express all of that as hard and soft constraints and let a solver propose a full weekend in seconds, with the assignor editing rather than constructing. Hard constraints, meaning grade, availability, travel feasibility and declared conflicts, cannot be broken. Soft constraints, meaning development goals, variety, fairness of workload across the season, and cost, carry weights the director sets. Fairness matters more than people expect: officials notice when the same person always gets the marquee fixtures and they notice when they always get the 8am on a wet field an hour away. A solver that balances that across a season removes a recurring source of attrition that no assignor can track by hand.

Problem 2: declines are the actual workflow, and they run on group texts

Every assignment is provisional until accepted, and a meaningful percentage will not be. Right now that gap is filled by an assignor manually texting people they think might say yes, in an order held in their memory, with no record of who was asked.

What a custom build does: automate the cascade. When an assignment is declined or expires unaccepted, the system offers it to the next best candidate by the same constraint model, with a response window measured in minutes on a Saturday morning and hours during the week. Offers go to a phone with one tap to accept, and the moment somebody accepts, the offer closes everywhere else. Escalation is explicit: after two rounds, the director gets alerted with the shortlist and the reason each option was ranked where it was. A standby pool can be paid a small retainer for a window and drawn on automatically, which is a policy change the software makes possible rather than a feature by itself.

The second effect matters as much as the first. Because every offer, decline and acceptance is recorded, you finally get reliable data on responsiveness. An official who declines 40 percent of offers is not a bad person, but that pattern should influence how far down the cascade they sit, and today no association can see it.

Problem 3: grading drives assignment, and it lives in a filing cabinet

Officials hold grades. Grades are maintained through assessment, observation reports, minimum games at a level, and sometimes fitness testing and written examinations. Promotion pathways have criteria. In most associations the assessment reports are documents, the criteria live in a policy PDF, and whether an official has met them is worked out manually each year by a promotion committee reading a pile.

Because grading is disconnected from assigning, development becomes accidental. The official who needs three more games at a higher level to be considered may or may not get them, depending on whether the assignor remembers.

What a custom build does: connect the two. Assessment reports are structured, attached to a specific assignment, and visible to the official with whatever feedback policy you operate. Progress against promotion criteria computes automatically, so both the official and the director can see what is outstanding. Then development becomes a soft constraint in the assignment model itself: this official needs two more games at this level before the cut-off, so weight them accordingly. That single connection is what turns a scheduling system into a workforce development system, and it is the reason associations that build tend to keep officials longer.

Problem 4: officials get paid late, and that is why they quit

Match officials are usually independent contractors paid per game plus travel, often by more than one payer: a league, a school district, a tournament organiser. Payment typically depends on someone reconciling game reports against a fee schedule, then a finance department running a batch, then a cheque or transfer. Four to six weeks later, an official who officiated four games on a wet Saturday in October gets paid, if the game report was filed correctly.

Existing assigning tools are largely disconnected from payment, which is why the reconciliation is manual, which is why it is slow.

What a custom build does: make payment a consequence of the assignment record rather than a separate process. The fee derives from the game level and the schedule you configure, travel computes from the actual venue, cancellation and short-notice rules apply automatically, and the official confirms completion from their phone at the ground. Approved amounts batch to your payment provider or to finance in the format they need, with year-end tax reporting built from the same records rather than reconstructed. Officials see their own earnings ledger, which removes a large share of the emails your office currently answers. In the United States this also means contractor tax reporting thresholds are tracked continuously rather than discovered in January.

Problem 5: certification, safeguarding and eligibility expire quietly

Officials hold certifications, background checks and safeguarding clearances with expiry dates. In youth sport especially, an official working a game with a lapsed check is a serious governance failure, and the check usually lapses without anyone noticing because the record is a spreadsheet column.

What a custom build does: make status a precondition of assignment rather than an annual audit. Certification, background check and safeguarding validity are attributes with expiry dates that the assignment engine treats as hard constraints, so an official whose clearance expires next Tuesday simply stops being eligible for Wednesday's games. Renewal reminders go out on a schedule you set, and the compliance report you need for your board or your national body is generated rather than assembled.

What this costs and how long it takes

Digital Heroes has delivered more than 2,000 projects, and the shape here is this. A first release covering official profiles and availability, constraint-based assignment with conflicts and travel feasibility, mobile accept and decline, and the automated cascade runs $50,000 to $120,000 over 10 to 16 weeks. A full platform adding assessment and grading with promotion criteria, pay and expense processing with payment provider integration, certification and safeguarding tracking, multi-association operation and reporting runs $140,000 to $350,000 phased across 6 to 12 months.

What pushes cost up: payment integration, because moving money to thousands of contractors brings verification, tax reporting and reconciliation requirements that are real work. Multi-association operation, where an official works across several bodies with different rates and rules and you need one identity and separate ledgers. Integration with league scheduling systems, since assignments depend on fixtures that change. And travel time computation at scale, which needs a routing service and sensible caching rather than naive distance.

What holds it down: one association, one season, one sport. Get assignment and the cascade working before you touch pay, because pay is where the compliance surface lives.

Build versus buy, and when buying is right

Buy if you are a small association covering a few hundred games a season with a stable pool of officials and simple conflict rules. Assignr is inexpensive, it works, and a custom build would cost more than the problem. RefTown and Horizon Web Ref are similarly reasonable at that scale. ArbiterSports is the default in large parts of American school and college sport and if it fits your governance model, use it.

Build when two or more of these are true. You handle more than roughly 5,000 assignments a season, so manual solving has become the bottleneck. Your conflict and grading rules are association-specific enough that filters cannot express them. Officials work across multiple bodies and payers and nobody can see a single picture. Payment delay is a stated reason people are leaving. Or your development pathway is disconnected from assignment, so promotions depend on who the assignor remembered.

Our position: the honest justification for building here is retention, not efficiency. Efficiency saves an assignor's weekend, which matters. Retention keeps games covered next season, which is existential for an association, and it responds directly to fair assignment, visible development and prompt pay. Those are the three things a build can actually change.

How to choose a developer for officials assigning software

Ask them how the assignment engine works before anything else. If the answer is a filtered list with a manual pick, you are buying what you already have with a new interface. You want hard and soft constraints, an explainable ranking, and the ability for the director to override with a recorded reason.

Ask how they compute whether two consecutive games are compatible. The right answer involves routing time between venues with a buffer, not straight-line distance, and caching so a weekend solve does not make thirty thousand routing calls.

Ask what happens at 8:40am on a Saturday when an official does not appear. The answer should be a same-day cascade with short response windows, escalation to a named human, and a standby pool, all on mobile. If the demonstration only shows a desktop screen, it was not built for the moment that matters.

Ask who owns the code, the official records and the cloud accounts, and settle it in writing before kickoff. Your officials' personal data, background check status and payment details sit in this system, so also ask how access is controlled and logged. At Digital Heroes the client owns everything from the first commit.