for the dispatcher · in private build
Stop chasing fourteen threads to fill one call.
Dispatch pulls every show request — email, text, voicemail, booking page — into one ranked queue. Every decision logged. Every premium calculated. Every grievance defensible.
onboarding by invitation · one local at a time
who built this
Built by someone who works the calls.
The dispatch software that exists today was built by people who never had to wake up to a venue-changed-its-loading-dock email, never had to figure out who’s ETCP-certified at 6am, never had to defend a dispatch decision in front of a grievance committee.
Dispatch’s author has done all three — a working IATSE journeyperson with thousands of show hours across theatre, festival, corporate, and broadcast. The data model encodes every one of them.
That’s the difference between a tool that gets used and one that lives in a Slack channel labeled “we’ll get around to it.”
your morning
Before and after.
before · fourteen threads
- advance from producer · 7:14am
- text from steward "need 2 more"
- voicemail · 2 mins · employer
- spreadsheet · last update unclear
- group chat "anyone available Sat?"
- reply chain re: rate · 4 deep
- missed call · 9:02am
- cert binder · physical · in office
- member "passing the Friday call"
- "please confirm" — from who?
- callback to producer · time check
- another text · same question
- OOW list · paper · last quarter
- grievance email · 2 days old
after · one queue
Corporate AV · downtown convention center
ranked · 18 eligible6 stagehand · Sat · 6am call
parsed from email
Historic theater · indie tour
2 of 2 confirmed2 audio · Fri · 10am · IMAG
text from producer
Foundation gala · Arts center
day 3 dispatching14-day install · varied
booking page submission
post-mortem queued
ready to reviewTouring production · 8-show run · settled
settlement
Same morning. Same calls. One queue. Every request parsed, classified, ranked, and ready for the BA’s call.
the queue · annotated
What you see on the call.
The dispatcher’s primary surface. Five things on screen at once.
corporate av · convention center · sat 6am
dispatching1incoming
- corporate av · 6 stagehand sat
- fox · 2 audio fri 10am
- foundation gala day 3
- callback · employer
2ranked pool · 18 eligible
- 1L. MarquezJourney4dETCP
- 2R. SatoJourney5d
- 3K. BellJourney6dETCP
- 4J. ParkApprentice3d
- 5D. WuJourney7d
- + 13 more · sorted by tier → days → tenure
3premium math
4override controls
5steward report
pre-populated · matches local’s xlsx format
generate report →
Incoming requests
Parsed from email, text, booking page, voicemail. The TD reads the inbound, extracts show, dates, classifications, headcount. The BA reviews — never has to retype the request.
Ranked member pool
Tier-aware. OOW-ordered (lowest days-worked-in-period first). Cert-verified against the call’s requirements. Recurring-unavailability blocks applied. Ties broken on the local’s configured rule.
Premium math
Rate stack: base + premiums + fringes + must-be. CBA-bound. The BA verifies, doesn’t compute. The number on screen is the number that lands on the call sheet.
Override controls
BA can override any ranked decision. Required reason field — not optional. Every override writes to the audit log and teaches the TD one more exception about how this local actually runs.
Steward report builder
Pre-populated worksheet matching the local’s expected format. Generated at settlement. Steward reads, signs, returns — no manual rekey.
defensibility
When a member grieves a call, can you show why you made the decision?
The grievance committee asks one question: walk me through it. Dispatch hands you the receipt.
Every decision stamped
Timestamp, actor, member ranked position, classification, premium structure. Captured at the moment of decision — not reconstructed after.
Every override captured with reason
Required field. Not optional. The override is in the log, the reason is in the log, the BA is named.
Grievance-ready export
Audit log by call, by member, or by time range. PDF or CSV. Hand to the grievance committee in one click.
CBA-bound math
Agreement triggers applied automatically. The BA verifies what the system computed; doesn’t compute it themselves. Wrong numbers are an investigation question, not a recurring fight.
ranking · how it works
The local’s rules. Not ours.
Pool composition
Which classifications are eligible for this call type. Configured per local during onboarding.
Tier-aware ordering
Journey before Apprentice before Permit, etc. Tier definitions match the local’s rules verbatim.
OOW math
Lowest days-worked-in-period ranks higher. Period defined by the local (rolling 365, calendar year, quarter — configurable).
Tie-breakers
Explicitly configured: last-dispatched date, seniority/tenure, alphabetical. Whatever your local agreed on, encoded once, applied consistently.
Override conditions
The BA can override at any time. Every override writes to the audit log with the BA’s required reason. No silent decisions.
your dashboard · example view
The numbers your local is actually run by.
Days, calls, start times — and what changed when Dispatch went live. Below: example numbers for a Local in its third quarter on Dispatch.
volume
calls dispatched · this quarter
↑ 31% YoY
days on call · this quarter
2.5 avg days per call
members dispatched · unique
7.0 avg days per member
rhythm
start-time distribution
day-of-week distribution
call shape
efficiency
office turnaround · avg
↓ from 2hr 14min baseline
crew confirmation · avg
↓ from 4hr 30min baseline
override rate
↓ from 8.1% in month 1
fairness
OOW order respected
days/member · Journey / Apprentice
grievances this quarter · 1 YTD · resolved
baseline comparison · before dispatch vs now
Office turnaround
↓ 83%
Threads to fill one call
↓ 91%
Grievance defense
audit-ready
methodology
Days on call counts each member-day dispatched. Office turnaround measures request-received (email parsed, text received, voicemail transcribed) to offers-sent. CBA minimums (5 hr extras, 8 hr heads) are applied to each call but aren’t used as the workload aggregation unit — days are. See the full measurement methodology →
integration
Additive. Not replacement.
Runs alongside
Your existing webtool keeps running during onboarding. Dispatch operates in parallel for 30 days if you want a shadow period.
CSV roster import
Member data imports via CSV. Mapped to your tier structure during a structured onboarding session.
Dispatch is dispatch
Dues, grievances, executive-board records stay where they are. Dispatch is the dispatch surface, not union-management.
common question
Why this isn’t Union Impact.
Union Impact is a generalist union-management platform mostly used by trades outside entertainment — carpenters, electricians, plumbers. It does dues, grievances, basic dispatch. Dispatch is the first SaaS purpose-built for live-entertainment crew dispatch. The data model encodes the way entertainment crews actually get called: classifications that are specific to the trade, must-be premiums, recurring unavailability shaped by tour schedules, CBA minimums per call rather than per member-day.
security · member privacy
Your members’ personal records are not visible to you.
Not to Dispatch. Not to AI TD. Not to anyone outside the member. Enforced by the database, not by policy.
Row-level security in Postgres
The database refuses to return cross-org rows. The boundary is mechanical, not procedural.
User-scoped personal records
Pay stubs, W-2s, 1099s, mileage logs in the xHand module are scoped to the individual member.
No model training
Anthropic and Voyage are contracted to not train on your data. Your corpus stays yours.
Consent audit log
Every data-contribution toggle and opt-in is timestamped, attributed, and exportable.
Full security writeup at /security.
pricing
The system replaces hours. Not headcount.
Flat monthly subscription based on member count. Design-partner locals pay nothing during the prototype phase. Production locals can expect pricing in line with what you’d pay a single part-time administrator’s hourly load. The BA still runs the dispatch desk; Dispatch absorbs the thread-management work.
every action trains the TD
The longer Dispatch runs in your operation, the more it knows about your operation specifically. Override rate drops as the TD learns your patterns. Answer quality climbs as the corpus deepens.
for your local
Walk it through with us.
30 minutes. Your roster, your CBA, your existing flow. We’ll show what the queue looks like with your data — or scope a private onboarding if it’s a fit.