Sunday night planning is a symptom. If the week has to be rebuilt by hand every seven days, the recurring schedule isn’t doing its job. This is the sequence that turns three hours into fifteen minutes — and then into nothing.
The fifteen-minute version
Open the heatmap before anything else. You are looking for red days and the light days near them.
Swap stops between an overloaded day and a light one in the same area. Geography first, availability second.
Draw around the cluster the new property sits in, see what is already nearby, assign the tech and the day.
Let the system order every day you touched. Do not hand-sequence.
What to look at, in order
Red days. Anything at or over capacity. Each one is a promise you are about to break — either a late visit or an unpaid hour.
White days. Empty capacity next to a red day is free money. Most overload is a scheduling artefact, not a staffing problem.
Unassigned properties. Work that exists but sits on no route. This is where missed visits come from.
Last week’s exceptions. Skipped stops, gate-locked visits, anything that didn’t close. These need a decision, not a repeat.
How to stop needing Sunday at all
Every hour of Sunday planning maps to something that should be configured rather than decided:
- Sequencing stops → run optimization on save, every time.
- Deciding who takes a new client → place by cluster when the property is created.
- Chasing what happened last week → read it from visit history on Monday morning.
- Guessing capacity → set each technician’s general capacity once, so the heatmap means something.
Capacity configuration is in Assigning tech working capacity; the drawing workflow is in Quick Routes™; the underlying reasoning is in routing math.
Based on how PSS clients describe their planning routine, not a published study.
Sunday night planning is a symptom. If the week has to be rebuilt by hand every seven days, the recurring schedule isn’t doing its job. This is the sequence that turns three hours into fifteen minutes — and then into nothing.
The fifteen-minute version
Open the heatmap before anything else. You are looking for red days and the light days near them.
Swap stops between an overloaded day and a light one in the same area. Geography first, availability second.
Draw around the cluster the new property sits in, see what is already nearby, assign the tech and the day.
Let the system order every day you touched. Do not hand-sequence.
What to look at, in order
Red days. Anything at or over capacity. Each one is a promise you are about to break — either a late visit or an unpaid hour.
White days. Empty capacity next to a red day is free money. Most overload is a scheduling artefact, not a staffing problem.
Unassigned properties. Work that exists but sits on no route. This is where missed visits come from.
Last week’s exceptions. Skipped stops, gate-locked visits, anything that didn’t close. These need a decision, not a repeat.
How to stop needing Sunday at all
Every hour of Sunday planning maps to something that should be configured rather than decided:
- Sequencing stops → run optimization on save, every time.
- Deciding who takes a new client → place by cluster when the property is created.
- Chasing what happened last week → read it from visit history on Monday morning.
- Guessing capacity → set each technician’s general capacity once, so the heatmap means something.
Capacity configuration is in Assigning tech working capacity; the drawing workflow is in Quick Routes™; the underlying reasoning is in routing math.
Based on how PSS clients describe their planning routine, not a published study.