Extra details for each engineer on the roster above — phone number, vehicle, home/start postcode, and any skills or notes worth having to hand. These sync live with the team the same way the roster does.

Sharing this roster, holidays & ad-hoc tasks with your team: this page syncs them live to every Freedomfibre teammate who opens this artifact's link — no separate publish step needed, and it's never visible outside your organisation. So if one person books an engineer off, anyone else who opens the link sees that booking too, usually within a second or two. The status line above turns green once a change is confirmed synced; if it turns amber or red, hover the message for what's happening (not connected, or a sync problem).

Your TomTom API key and the scheduling-rule numbers above are never part of this shared sync — they're saved only in this browser, on this device. Each teammate enters their own TomTom key.

One trade-off worth knowing: this in-page view cannot reach TomTom for live routing (a Claude platform restriction, not a bug in this tool) — so use this view for booking holidays and managing the roster, and keep using Download standalone copy or Export/Import for the actual day-to-day route generation, same as before.

For one-off changes to a specific engineer's day — a different finish time, stock collection before their first job, an ad-hoc support task at a set time, or any other extra work with its own label and duration. Leave start/finish blank to use the normal day above. These apply to the schedule you generate now and aren't saved between visits.

This preview panel blocks the live TomTom calls the schedule needs, so you'll need a copy of this tool open in its own browser tab to get real routing. The most reliable way to keep one up to date: click Export all areas below, then open Import all areas in a copy you already know connects to TomTom (e.g. one downloaded via a link, rather than the button below).

Alternatively, this button below builds a new standalone copy directly with everything currently configured already baked in — quicker, but on some Windows/Edge setups a file generated and downloaded from inside an already-local file gets treated with more suspicion than one delivered via a link, which can block TomTom in that specific copy even though the roster/settings inside it are correct. If Test API connection fails in a copy made this way, use Export + Import above instead rather than troubleshooting the key.

Book time off up to a year ahead. On any day (or half-day) an engineer is off, the schedule routes their jobs to someone else automatically.

Book an engineer out for a job ahead of the day — e.g. blockage support booked today for tomorrow. Give it an address and duration and it's routed with real TomTom travel times alongside their other jobs automatically on the day, with nothing to add manually when you generate that schedule.