Workflow
Operations
Scheduling and dispatch coordination
The schedule is rebuilt each morning from the same inputs by the same person, and every change after work starts is a phone call. This is how an agent proposes and records while the dispatch decision and every field contact stay the dispatcher’s.
When the dispatcher is out, so is the schedule
Today
Rebuilt each morning from the job list, the whiteboard and whoever called in
- The schedule is rebuilt each morning from the job list, the whiteboard and whoever called in.
- The double-booking is found by the crew that turns up second.
- A change made after the day starts reaches some of the people it affects, by phone, and the dispatcher is the only person who can answer who is where.
- When the dispatcher is out, so is the schedule.
With agents
The proposal is built from the record and every dispatch decision stays the dispatcher's
- The schedule starts from the record rather than the whiteboard.
- Conflicts are named before the day starts.
- Every change has a record.
How an agent runs it
The schedule is built every day from the same inputs by the same person. The workflow assembles the proposal from what is on record, names the conflicts, and puts it in front of the dispatcher to confirm; every dispatch decision stays the dispatcher's.
01
Assembles
Builds the schedule proposal from the jobs, availability, requirements and constraints you record, for the period you set.
02
Detects
Finds double-bookings, missing requirements and constraint breaches against your written rules, and names each one.
03
Drafts
Prepares the dispatch proposal per person or crew, with the jobs, the order and the constraints that shaped it visible.
04
Human gate
Routes the proposal to the dispatcher for confirmation before anything is dispatched. Dispatching, every change once the day is running, and every contact with a person in the field is a person's, and the schedule can be built by hand at any point because the jobs and the constraints are yours.
05
Recommends
When a job or a person drops out, proposes a reassignment against the same rules, for the dispatcher to accept or reject.
06
Records
Keeps the confirmed schedule and every change the dispatcher makes, with who changed what and when.
07
Reports
Lists what changed since the confirmed version and what remains unassigned, so the next proposal starts from the record.
Results
What changes when the schedule starts from the record
The record, not the whiteboard
Assembly runs from the jobs and constraints on record, so the proposal is the same whoever is in the chair.
Conflicts named before the day starts
Detection runs on the proposal against written rules, so the second crew does not discover the first.
Every change has a record
The confirmed schedule and each dispatcher change are kept with who and when, so the question of who is where has an answer that does not depend on one person.
Where this fits
Workflow / Automate a Workflow
Tier 1 through the Automate a Workflow door: one process, from inputs to a confirmed schedule. The boundary is dispatch: the decision, the act of dispatching and every contact with the field are a person's, and the workflow ends at the confirmed proposal. It extends toward The agent-run operations back office as a possible next step rather than a promised state, where the schedule and Job and project status reporting, continuously read the same job records. How It Works shows how the confirmation gate is built.
Tier 1 / Prove
How It Works
Questions, answered
No. It proposes and the dispatcher confirms. Dispatching and every field contact are a person's, gated by default and opened only on your decision. The jobs and the constraints live in your systems, so the schedule can be built by hand at any point without the agent.
AI Opportunity Audit
See which of yesterday's changes had a record
Bring yesterday's schedule and the list of changes made after it was set, and see which changes had a record.
Related use cases
Back to Use Cases
Workflow
Back office
Meeting scheduling and calendar coordination
Every scheduling thread re-derives the same rules about your time by hand. This is how an agent holds those rules in one place, proposes against
Learn More
Workflow
Operations
Job and project status reporting, continuously
The status report is a reconstruction of things the job records already know, done by the person least able to spare the time. This is
Learn More
Department
Operations
The agent-run operations back office
The workflows each prove one process; the function is what happens when they run together under one set of roles and one gate structure. This
Learn More