How do I reschedule or reassign a job that is already on the board?
Every dispatch action — reassign crew, move the date or time, offer appointment slots, plan a reschedule or put a job on hold — runs from the job card actions menu with guards and an audit trail.
Updated August 31, 2026 · Verified against dispatch/RESCHEDULE_POLICY.md & AI-DISPATCH-INTEGRATION-GUIDE.md
Steps
- 1Open the Dispatch Board and find the job card
- 2Open the card actions menu
- 3Pick Reassign crew to swap the employee, or Move date or time to change the schedule
- 4Use Plan reschedule when you want the full set of suggested steps first
- 5Resolve or acknowledge any guard warnings, typing a reason where required
- 6Commit the change, then use Offer appointment slots if the customer needs new times
Moving live work is not a separate mechanism. Each job card on the Dispatch Board has an actions menu, and every change is guarded and recorded so the crew and the customer are told once, correctly.
Actions on a job card
| Action | What it does | Customer texted? |
|---|---|---|
| Report issue | Logs a disruption against the job | No |
| Mark sick | Marks a crew member sick for the day, frees their assignments and opens the recovery flow | No |
| Reassign crew | Swap the assigned employee, after the crew guards run | No |
| Move date or time | Change the work date and hours, after the guards run | No |
| Offer appointment slots | Offers up to three slots to the customer using the project's phone number | Yes, on send |
| Plan reschedule | Advises a full set of steps, including putting the job on hold | No |
How a reschedule is committed
A reschedule opens a one-day draft plan that replaces the live assignment. The original booking stays on the schedule until the replacement plan is committed, so nobody is told twice. Choose the new dates first, tell the customer the original date is moving, then offer the new options.
Notes and limits
- Plan reschedule never writes. It only advises; choosing a step opens the matching manual tool pre-loaded with that step's context, and a person confirms.
- Guards run before a manual change saves: a never pair rule is a hard block, a never schedule rule blocks automatic picks, and missing skills, time-off overlaps or double-bookings are warnings that require a typed reason.
- Changes are stamped with the dispatcher as their source, so the history reads the same whether a person or automation made the call.
- Freshness is checked on commit: if the assignment changed since the draft was built, the change is rejected instead of overwriting someone else's edit.
Related articles
What it looks like in WorkSkedge
Frequently asked questions
Does rescheduling notify the crew twice?
No. The reschedule draft replaces the live assignment, and the original booking stays on the schedule until the replacement is committed, so the crew is told exactly once.
Does Plan reschedule change anything by itself?
No. The planner only advises. Choosing a step opens the matching manual tool — reassign, move, offer slots, or put the job on hold — pre-loaded with that step context for a person to confirm.
Which changes are blocked outright?
A never pair crew rule is a hard block that cannot be applied from the board. A never schedule rule blocks every automatic pick, though a dispatcher can still assign that person by hand.
Is the customer contacted automatically?
Only when you use Offer appointment slots, which resolves the customer number from the project and texts up to three slots on send. Reassigning crew or moving a date does not text the customer.
What if someone else edited the job while I was planning?
The commit carries the assignment timestamp from when the draft was built. If the row moved in the meantime the change is rejected rather than silently overwriting the other edit.