Marking a match completed
Open the Match Complete dialog, confirm per-official pay, set the Bluebridge fee, and submit — what each control does and what the payor-pays banner means in each fee mode.
On any event powered by Bluebridge, once at least one official has accepted on a given date, the assignor view of that roster shows a Mark match completed button. This article walks through the dialog it opens.
Where the button is
On mobile the button is a full-width emerald pill below the official list. On desktop it's a compact outline pill anchored to the right of the date header. Either way, it only appears once at least one official is accepted — there's nothing to mark complete if the match hasn't been staffed.
What the dialog shows
- A title with the matchup plus a gender chip (college) or the event name (tournament).
- A subtitle with the date label.
- One row per accepted official, with a role badge — Head referee or Official — and a dollar input pre-filled from the event's defaults.
- A Bluebridge fee field on the right.
- A payor-pays total banner at the bottom.
- A notes textarea below that.
Where the per-official defaults come from
Each row's dollar amount pre-fills from the event's Default head referee pay or Default official pay — whichever matches that official's is_head_referee flag. If you left those fields blank on the event, the row starts blank and you fill it in here. You can override any row inline; the override only applies to this payment request.
The Bluebridge fee field
The fee field on the right is auto-computed from the running officials total times the event's fee percentage (3% by default). It re-computes live as you change per-row dollars — until you edit it manually. The moment you type a value into the fee field, that override is pinned: changing per-row amounts after that point won't clobber what you typed. Closing and re-opening the dialog resets the pin so the fee starts auto-syncing again.
Pre-fee mode: the Net hint under each row
When the event is in Pre-fee mode, each official row also shows a faint Net: $X.XX beneath the dollar input. That's what the official actually receives — sticker amount times (1 minus the fee percentage). The dollar input itself is still the sticker amount; the net is just a heads-up so you can sanity-check what hits the official's account.
The payor-pays banner
At the bottom of the dialog, a banner shows what the payor actually pays. It changes by fee mode:
- Post-fee — sticker total plus the Bluebridge fee. Officials receive the full sticker.
- Pre-fee — sticker total only. The fee is deducted from each official's payout, so the payor doesn't pay it on top.
- No Bluebridge fee — sticker total only. No platform fee.
See Bluebridge fee modes for a worked example with concrete numbers in each mode.
Travel, on events that reimburse it
If the event has a mileage rate, each official row also carries a miles field, pre-filled with that match's share of their drive. The amount is computed at the event rate and shown beneath the row as +$X.XX travel. It is part of what the payor pays.
A row reading "(1 of 3)" means one drive covering three matches — an official who stayed over, or who worked two matches in a day. Edit the miles freely; you know what was actually driven. See Travel and mileage for how the distance is worked out.
The notes textarea
Anything you want the admin to know when they process the request. A typical use is reimbursement context — e.g. "Official paid out of pocket for hotel, reimburse $120." Notes travel with the payment request to the admin detail view and are preserved if you later edit.
Submitting
Save creates a payment request with one item per official row, plus the fee and notes. The roster flips to show a Completed pill with the relative time. While the request is still Open, you can edit or undo it — see Editing or undoing a payment request.