Set how much work each tech can take in a single day, then watch the load bar fill up as appointments are booked. The cap is a soft signal — never blocks booking — but it drives the per-tech load bar in Day view and demotes overbooked techs in smart-slot ranking.
Setting a cap
- 1Open the team page
Open /portal/team and click Edit on a tech (or use the inline 'Add tech' modal).
- 2Pick the cap type
Fill in 'Daily capacity — minutes' for a minute-based cap (e.g. 480 = 8 hours of work). OR fill in 'Daily capacity — appointments' for a count-based cap (e.g. 6 = max 6 jobs/day).
- 3Save
The next time someone opens /portal/schedule the load bar appears under the tech's name in Day view.
Both can be set simultaneously — the load bar prefers minutes when both are present (more accurate when job sizes vary widely). Leave both blank for no cap (the default; matches legacy behavior).
Reading the load bar
| Green (<80%) | Plenty of room — book away. |
| Amber (80-100%) | Approaching cap. Smart-slot still picks this tech happily, but consider spreading load. |
| Red (>100%) | Overbooked. Smart-slot demotes this tech ~5 detour miles per ranking. >150% = ~15 mile penalty. |
Dispatchers know their crew best. Some days a tech volunteers a 10th appointment because they're already in the area, or pushes through a long day because the customer is loyal. Capping at a hard ceiling would just route around the dispatcher's judgment. The load bar shows the cost; the dispatcher chooses.
What the smart-slot scorer does with capacity
When the AI receptionist or smart-slot composer ranks options, candidates that would push a tech past their daily cap get a small detour-mile penalty added (5 miles for 100-150%, 15 miles for >150%). That's enough to prefer an unflexed alternative when one exists, but not enough to block all options when the busy tech is genuinely the closest fit.