A planner selects a day from the calendar. The proposal assigns appointments to technicians using their working schedule, absence, business base, valid skills and limits for working time and driving time. Urgency takes priority within those rules. Promised appointment times are preserved. The planner can configure business bases, skills with expiry dates and requirements for each job.
The Routekaart component shows real coordinates on a geographic grid. Numbers identify the technician and stop order. Straight connections are overview lines, not driven roads. Missing locations appear in a list and are never given invented points. There is no external mapping service, Google connection or live traffic information. Driving times are estimates. A separate bounded Utrecht trial has run against real local VROOM/OSRM services. That trial is not a connected production source and does not establish Benelux capacity or total monthly costs.
Drag a stop on the Board, use its card menu or move it with Alt and the arrow keys. Arrivals and driving times recalculate immediately. On a phone, technicians appear below each other. Selecting another day hides the old proposal until the new source has loaded.
Each stop shows its reasons, rule violations and unknown information. Unknown calendars, business bases, capacity or driving times never count as available capacity. Work that cannot be scheduled stays under Unscheduled with a reason. In this phase, any started work blocks the entire day proposal. For exceptions during the day, use a separate replanning proposal.
Saving only creates a snapshot. It changes no appointment or route. An up-to-date proposal with no unresolved checks can go to To sign. Applying is an R2 action that always requires a human signature. The server rechecks current permissions, sources and hard rules, then applies the planning in one transaction. Changed sources require a new proposal. No customer message is sent and nothing is written to Google.
Signature requested means the proposal is listed under To sign. A signature or approval does not yet confirm that the planning has changed. The day proposal receives the Applied status only after successful execution. If execution is Refused or Failed, application is not confirmed: open the proposal and review the current sources, permissions and displayed message before making another request. If sources have changed, create a new proposal first.
Via MCP and the director
planning_dagvoorstel_lezen shows a calculated day or a saved proposal with the source hash the other tools need. planning_regels_lezen shows the planning rules (limits, calendar source, skills) without customer addresses; changing them is only done by a person in the screen. planning_dag_voorstellen saves a local proposal and planning_voorstel_toepassen only requests a signature: applying is always a person, also on an automatic setting. Everything needs planning.beheren.