Setting up hospitality and pay
Travel allowance, meals, housing, per diem, and pay policies, what each field means.
Officials decide whether to apply partly based on what's covered. Filling in the hospitality and pay sections accurately gets you better applicants and avoids day-of misunderstandings.
Hospitality toggles
- Travel allowance, mileage or a flat travel stipend. Toggle on and describe the policy (e.g. "$0.65/mile"). Cap per official, per trip sets the most any official is paid for travel, mileage or a custom amount; leave it blank for no cap. When the description states a per-mile rate, Bluebridge prices each official's drive from it. See Travel and mileage.
- Meals provided, lunch, dinner, snacks. Toggle on and describe what's included.
- Housing available, hotel block or local lodging. Officials opt in when applying.
- Per diem, a daily stipend separate from meals and travel. Describe it, and put the dollar figure in Per official, per day. That amount is added to invoices and payouts once for each day an official works, on their earliest match that day, so a doubleheader never charges it twice.
Reviewing housing requests
When housing is on, officials pick the specific hotel nights they need while applying (night before and/or night of each day they're applying to). The event's Finance tab gains a Housing requests section grouping every request by pipeline stage (Accepted, Assigned, Applied), with one chip per requested night. Click chips to select a subset, then Approve or Deny; with nothing selected, the action covers every night, and decisions are per-night, so a request can be part-approved. A request locks read-only once you assign that official (you may already be booking rooms); it unlocks if they decline and reapply.
- Distance gate: optionally set a minimum driving distance from the event site, in miles, so only genuinely out-of-town officials can request housing. Officials without a geocoded address are never locked out.
- Miles pill: each requester's row shows how far they live from the event site, one way: the driving distance when a route is on file, otherwise a straight-line figure. It's a sanity check at a glance, not the distance travel is paid on.
Pay policies
Pay lives in Billing details on the event's Finance tab (tap Edit), and in Compensation on the new-event form.
- Tournament: Policy. Describe the daily or match rate, payment timing, whether it's 1099 or W-2. Mileage written here is shown to officials but not priced; put a per-mile rate in Travel allowance.
- College: Referee and Umpire are separate pay lines, since referees and chair umpires are often paid differently. A plain amount like "$310" or "$310 per match" is one Bluebridge can use when you mark a match completed or invoice it.
Default referee pay and Default official pay
Below the pay lines, Billing details (and Compensation on the new-event form) can show two dollar inputs: Default referee pay and Default official pay. On a tournament they're always there. On a college season they appear only when the Referee or Umpire line isn't a plain amount. "$310" is already a number, and asking for it twice would only let the two disagree; "$310 first day, $285 after" isn't, and that's when a default earns its place. Whichever supplies the number pre-fills each official's amount when you mark a match completed or invoice it. A pay text with role lines, such as "Referee: $305/day", "Additional Officials: $230/day" and "Overtime: $40/hour after 8 hours", is read too, and Billing details shows those figures as the boxes' placeholders. Overtime rate (per hour) sets what overtime added on the roster pays.
If you run pay through Bluebridge
If the event's Payment vendor is Bluebridge, these rates feed the payment request; see Bluebridge fee modes and Marking a match completed. They also feed the invoice, whoever pays the officials; see Invoicing a match.
Where it shows up
On the event detail page, the Hospitality card shows each perk as a check or X with the description inline. Officials see this before they apply.