Work orders in PDFs and DMs
The rigger gets a PDF, the trucking vendor gets a WhatsApp message, the AV subcontractor gets a Dropbox link. Nobody has the same version. Nobody can audit who saw what.
Work Orders
Send, track, sign-off.
Every external vendor gets a token-gated portal — view, acknowledge, complete, sign. No ShowOps login, no shared-drive PDFs, no "confirmed via Slack." A real audit trail, a real sign-off, a real hand-off to Budget when the work is done.
Live
External vendors do most of the work. Most platforms pretend they don't exist.
Dispatch is built around the reality that half your dispatch goes to people who don't have accounts with you. The public portal is the product, not an afterthought.
Sign-off that isn't a signature
"Confirmed" over Slack. "Acknowledged" via thumbs-up. When a dispute lands, there's no signed record, no timestamp, no chain of custody.
External parties locked out
You can't hand every freelance vendor a ShowOps login. But you also can't hand them nothing — the work needs tracking, the completion needs proof.
Actuals arrive via invoice
A work order ships. A month later an invoice arrives. Somebody books it to a budget line — maybe the right one, maybe not. By then the overrun is locked in.
Sign-off that holds up.
Every capability makes the dispatch → acknowledge → complete chain auditable — and makes the external-vendor surface actually pleasant to use.
Work orders with templated types
Rigging, trucking, catering, security, tech ops — each with its own template, required fields, and scope language. Scope changes happen in the template, not in hand-edited copies.
External stakeholders via token
HMAC-signed tokens give external vendors a single-use, time-limited portal URL for view / acknowledge / complete. No ShowOps login, no password reset emails, no IT ticket.
State machine with audit
Draft → sent → acknowledged → in_progress → completed | cancelled. Every transition timestamped against the actor. Nothing happens without a record.
Completion → budget actualization
When a WO completes, matching budget line items actualize — the dollars follow the work, not the invoice cycle. If the variance trips the threshold, Command Center hears about it.
E-signature on high-value orders
For work above a configurable threshold, completion requires an e-signature captured through the same token portal. The signature embeds in the audit log, not a separate tool.
Rate-limited public endpoints
Token-gated endpoints are rate-limited, IP-tracked, and single-use by default. Token reuse is logged and blocked — the external surface is locked down.
Timed reminders & expiry
Tokens carry expiration — 30 days to view, 7 days to complete. Auto-reminders go out before expiry, not after — no stranded work orders.
Real-time status propagation
WO state changes emit platform events. Command Center, Budget, and Suppliers all see the change the moment it happens — no polling, no refresh dance.
Connected by Design
The hand-off layer between plan and payment.
Dispatch is where a decision in the platform turns into action from a vendor in the field — and where the proof-of-work turns back into a number in the budget.
Inbound — data flowing into Dispatch
SuppliersDispatch
When a work order needs routing, the dispatch router asks Suppliers for the category ranking. The chosen vendor comes back with full scoring signals, not a name.
suppliers.ranking.requestedOutbound — events Dispatch publishes
DispatchBudget
On completion, matching budget line items actualize — the money follows the signature, not the invoice. Variance alerts fire from the actualization, not from an accountant.
dispatch.wo.completedDispatchSuppliers
Post-completion rating opens against the vendor record — scoring updates, reliability trend moves, next-time ranking shifts accordingly.
dispatch.wo.completedRoute, not dispatch.
The dispatch specialist proposes vendors and surfaces stalled orders — never sends a WO on its own. Humans dispatch; the specialist makes sure every dispatch is informed.
Vendor routing with signals
The dispatch router ranks vendors by category fit + reliability score — every ranking shows the signals behind it. Producers pick; the router proposes.
Stalled-WO detection
Work orders sitting too long in "sent" or "acknowledged" surface with the responsible vendor and the scope dollars at stake. The escalation writes itself.
Scope-mismatch flagging
If a completion includes items or amounts outside the original scope, the audit trail flags it for review — mismatches get caught at sign-off, not at audit.
Completion-evidence summary
At completion, the trail is packaged: who acknowledged, when, the signature (if required), and the line items actualized. Dispute defense is one click.
Get Started
Every work order ends with a signature.
The platform is live. Request a demo to see Dispatch in action.
Part of a 13-module platform that adapts to your operation. No commitment required.