Every athletic director has a version of the same folder: a PDF contract template, a chain of replies with the other school's AD, a spreadsheet that says which games are confirmed, and a calendar that may or may not match it. It works until the one time it doesn't, and then a bus is on its way to a field that was double-booked.
The fix is not a better PDF. It is treating the game as one event that lives on one calendar, with the contract as the thing that puts it there.
Where email contracts break
An emailed PDF has no state. You cannot tell from your inbox whether the other school has opened it, whether they want a different date, or whether the version you signed is the version they signed. Reminders are manual. Changes are a new attachment. And nothing about the contract reserves your own stadium, so the game exists in the contract folder before it exists on the facility calendar, which is exactly how a JV practice ends up scheduled on top of a varsity game.
Multiply that by forty to sixty contests a year across every sport, and the AD's job becomes reconciliation.
Draft the matchup once
Start from your standard terms and add only what changes per game: the date and time, the facility, the level (varsity, JV, freshman), and any guarantee or fee. If you play the same school in three sports this season, put all three contests on one contract rather than three separate agreements. The other AD signs once.
Because the draft names a facility, it can check that facility's calendar as you write it. If the stadium is already held that Friday, you find out before you send anything, not after.
Send it as a link, not an attachment
The other AD should be able to open the proposal on a phone, read the terms, and either accept, decline, or propose a change (a different date, a swap of home and away) without creating an account or installing anything. Every response is timestamped, so there is a record of who changed what and when. If the counter-proposal works, you accept it and the contract is ready to sign. If not, you send the next version and the history stays attached.
Signing works the same way: type a name, done. No login for the visiting school.
Let the calendar do the coordination
The moment both sides have signed, the game should appear on both schools' calendars with the facility reserved, and both ADs should get the confirmation. This is the step that separates a contract tool from a scheduling tool. The signed contract is not filed somewhere; it is the event.
From there the rest of game day hangs off the same event. Set the ticket types once and the gate is on sale. Concessions ring up against that game. If the date moves, the contract, both calendars, the tickets, and the reports move with it.
One workflow for every contest
Head-to-head games, multi-school invitationals, home-and-away series: the shape is the same. Draft, send, respond, sign, and the calendar takes it from there. The visiting school never needs an account, and your business office sees the guarantee, the gate, and the concessions on one event when they reconcile.
If you already keep your schedule in Arbiter, you can import it and use contracts for the games that still need agreeing.
---
In Admittee: game proposals and contracts are part of the platform and carry no fee to send or sign. A fee applies only if a guarantee or forfeit payment actually moves: 5% + $0.50 on a card, or 1.5% capped at $20 by bank transfer. See game proposals and every rate.