Set Up a Saved Route
Build a route that runs on set days — once a week, twice a week, or every few weeks — with each site served only on the days its agreement calls for, and know where every rhythm lives.
Updated November 15, 2026
A saved route is a standing plan: which sites, in what order, who runs it, and which days it goes out. Set one up once and every week's booking comes from it — by a click on the calendar, or automatically. This article is about getting the days right, including the common case where one round mixes customers on different frequencies.
A route's days and a customer's days are two different things
A route has Service days — the days the van goes out. A customer has an agreement that says how often they are served: every 7 days, twice a week on Monday and Thursday, two visits a week. The route's days are the union of what its stops need; on any given day, only the stops that are due that day are booked.
Which days a stop is due is worked out per stop, in this order:
- The agreement's named weekdays, on the days the route runs. If the customer's contract says Monday and Thursday, no route setting and no pin can move the stop off those days. A named day the route does not run is simply not served by this route; if the route runs on none of the named days, the stop is not dropped — it falls through to the rules below and is served on the route's day anyway. That is a mismatch to fix on one side or the other, and OpsVara says so: the apply result lists the stop in amber, and route health counts it as served on days their agreement doesn't name (see After the route exists).
- The stop's own Visit days pin. Set on the route, for stops whose agreement leaves the day open. Pin one day, or every day the route runs — a pin of both days serves the stop on both, even when its agreement says once a week.
- The agreement's frequency or interval, spread over the route's days. Once a week, or every 5 to 7 days, takes the route's first service day. Twice a week, or every 3 or 4 days, takes the first two. Never more days than the route runs. A count per month is treated as once a week: a site sold as three visits a month is due on the route's first day every week the route runs.
- Every route day, when nothing else says otherwise — an agreement with no interval, weekdays, or visits per period. A site with no active agreement at all is due every day but never gets a new job: applying the route skips it as having no active agreement. A job already on the day for it is still added to the run.
Before any of that, the agreement's dates are checked. A site whose active agreement for the work does not include the day — it starts later, or it ended and has not been marked expired yet — is not due that day at all, and applying lists it as outside agreement dates and creates nothing. As with a site with no agreement, a job the office already put on that day is still added to the run. An agreement with no start or end date is open on that side, as it always was.
So a Monday-and-Wednesday route holding five twice-a-week customers and two once-a-week customers books seven stops on Monday and five on Wednesday, with nobody choosing per stop.
Auto favours the first day
A once-a-week stop on Auto always lands on the route's earliest service day (Sunday counts as first). On a Monday-and-Wednesday route every once-a-week stop is a Monday stop until you pin one to Wednesday. Nothing balances them across the days for you.
Three ways to make a route
The first two start on Dispatch → Saved Routes; the third starts on the Assign Work or Route Planner tab.
By hand — New Route
Open New Route
On the Routes view, click More → New Route. The New Saved Route dialog opens.
Name it and say who runs it
Fill in Name. Pick a Default worker — the person the route is applied to — and, if you like, a Backup worker for days they are out.
Set the schedule
Under Schedule, set How often and the Service days. The fields are described in the next section. You can leave it on Manual — apply by hand and come back later.
Add the sites
Under Add Site to route, type two or more letters of a site or city name, choose the work type, and click a site to add it. Sites already on the route for that work type say so. Drag stops into driving order, or press the Driving order button — it names the miles it would save, and reads In driving order when there is nothing to gain.
Set Visit days if you need to
Once the route has two or more service days, each stop shows Visit days chips — Auto plus one chip per service day. Leave Auto for the agreement to decide, or click one day — or more — to pin them. Clicking a pinned day again unpins it; unpin every day, or click Auto, to hand the stop back to the agreement.
Create Route
The route appears in the table with its days in the Cadence column.
With the Route Builder — Build Routes
Build Routes proposes a whole set of routes from a map of sites and packs them to the capacity you set. Five steps: Scope, Capacity, Review, Sequence, Commit.
- Scope: pick a work type, optionally a territory or site tags, or draw an area on the map.
Tags keeps a site when the site or its customer carries any tag you pick. Only sites
not already on a route is on by default. Every site also needs a map location, no service
hold, and an active customer; the step says how many qualify and how many were skipped for a
hold or a missing map location. Only sites with an active contract is also on by default:
a site then needs an agreement for that work type that has started and not ended. Untick it to
include every active site of that type, with or without an agreement — for example to plan next
season after this season's contracts have ended, or before contracts that start on your
switch-over day. The step says how many of the sites have no active agreement. With Only sites with an active contract off and All work types, a site with no contract is offered once, under the first work type in scope that applies to it, and Building from N sites counts sites. The routes are
built now, but applying one still books nothing for a stop without an agreement covering the
day; the stop is skipped as no active agreement or outside agreement dates.
For a big book (above about 15 routes) the step offers Build in parts: the sites are split into side-by-side areas of about 10 routes each, labelled by direction (for example Part 2 of 4 · West). Press Build this part, review and save it; the builder marks the part Saved and moves to the next, saving every part into the same route book (Part N saved to … Part N+1 is next.). Build everything at once instead skips the split.
Save these as one route here skips the planner and saves exactly these sites as a single
route straight away, with no schedule.
- Capacity: Stops per day and Hours per day sit first, prefilled from your work types. Hours take decimals, so 7.5 is seven and a half hours.
Under Build for specific people, tick the people who will drive: each gets their own
routes, starting from their own start location and holding only work they are qualified
for. Each name shows Home, Start location, or Main office — what you set on
that person under Settings
Team → Start location (Company dispatch address (default), a yard, or Their own address). Leave Routes each blank (Auto) and the caps decide how many routes each person needs — a week of stops becomes a week of routes; type a number to pin it. Or describe the day in a sentence, below the fields, opens Say what you want instead. If your visit lengths mean the day fits fewer stops than Stops per day, the step warns (for example visits average about 90 minutes, so a 480-minute day fits about 5 of them — plans will come out near 5 stops a day, not 10), with a link to Work Types settings in a new tab so the plan you are building is kept.
- Capacity: Stops per day and Hours per day sit first, prefilled from your work types. Hours take decimals, so 7.5 is seven and a half hours.
Under Build for specific people, tick the people who will drive: each gets their own
routes, starting from their own start location and holding only work they are qualified
for. Each name shows Home, Start location, or Main office — what you set on
that person under Settings
- Review: rename routes and move stops. Expand a route with Show N stops. Each stop has Move to… — pick another proposed route to move it there. On the map, square dark pins are origins, not stops: Main office (shop glyph) or Home (house glyph). Hover reads Route starts and ends here (or N routes start and end here when several share a yard). One pin per distinct place. Clicking a stop pin moves it onto the route you have selected, as long as exactly one destination is lit; otherwise the click selects that stop's own route. A route you have not selected is drawn from its first stop to its last; select it to see its drive to and from the shop. Every route gets a road path; a route still drawn straight says why on its card (for example Loading the road path… or that the drive time is an estimate). The day length set the route count, not your stop cap appears when visit lengths fill the day before the stop cap is reached. If you build again after moving stops, a route that keeps most of its stops keeps its name (including one you typed) and its crew and schedule picks.
- Sequence: drag stops into driving order. Pins on this step do not move a stop to another route — a re-solve would throw the order away.
- Commit: under Save into, pick a new route book (fill in Route Book Name, marked Required, and choose Ongoing or For one season) or an existing book that is not archived (Route book to save into; these routes join that book and take its season and status). If you press the button with no name, the builder takes you to the field and says Give the route book a name to save these routes. Confirm Assigned to on each route, and open Set a schedule on each route to give it service days. Then press Create N routes.
Who Drives Each Route
Unless you ticked people under Build for specific people, the builder groups the sites first and then recommends a driver for each route. The Assigned to list on the Review and Commit steps shows that person as — recommended, with the reason under it, for example no routes yet · starts 6 mi away or 2 route(s) already · starts 17 mi away.
The recommendation is worked out in this order:
- Only people who can do every stop. They need every work type on the route, every required skill, the Licensed applicator mark when any stop needs one, and to be allowed by any territory rule.
- People with room before people with a full week. A person is full once they drive one
route for each day they work. Working days come from Weekly Hours under
Settings
Availability, which each person sets for themselves; someone with no days ticked counts as five. Their live routes in other route books count, so a person with a full week elsewhere is not recommended again. Routes in a draft book do not count, and neither do routes you are rebuilding in this plan. - Preferred skills, then territory.
- Whose day starts nearest. Everyone within about five miles of the nearest person counts as equally near, and the one with the fewest routes wins. Farther out, the nearer person wins.
The route is ordered and timed from its driver's start, so a route's card reads Starts at Home when that person starts from their own address. Pick a different person and the stop order, the drive time and the start pin on the map change to match.
You can pick anyone. People who cannot do the route are listed last as — not qualified for this route. If you pick one, the card says what is missing, for example Sam is missing the Routine Service work type.
| What is missing | What happens |
|---|---|
| A work type, a skill, or a territory rule | A warning on the card and by the button. You can still save; fix it on the person's profile under Settings |
| The Licensed applicator mark, on a route with work that requires one | Create N routes is greyed out and a red message names the route. Pick a licensed driver or Nobody yet. |
Licensed work cannot be saved to an unlicensed driver
A work type set to Requires a licensed applicator under
Settings
The Scope map already pins Main office with the tooltip Routes start and end here, until a proposal brings its own origins.
Build routes is a preview. Create N routes is the save.
The button at the end of the Capacity step reads Build routes, but it only proposes. Nothing is written until you press Create N routes on the Commit step (it reads Save N routes as draft when Save as a draft is ticked). If you leave the builder before that — back link, menu, refresh — the proposal is discarded and no route exists.
The builder does not set per-stop Visit days. Open the route from the Routes view after committing to pin any. Routes committed with Save as a draft are listed with a Draft badge and can still be applied by hand, but they do not auto-apply and do not count in route health until the book is activated under Route Books.
From a planned day — Save to Saved Routes
On Dispatch → Route Planner, the day you have planned for the focused person can be saved as a route with Save to Saved Routes, with that person as the Default worker. On Assign Work, the ⋮ menu's Save Current Route saves every job on the board for that single day — all crew, one stop per site, no Default worker. Both open the Save to Saved Routes dialog. Routes made this way start on Manual with no days: open them from the Routes view and set a schedule, or wait until the run has gone well and use Repeat weekly on the calendar — see Put a Route on the Calendar.
The Schedule block, field by field
The same block appears in New Saved Route, in a route's Edit dialog, and under Set a schedule on the builder's Commit step.
| Field | What it does |
|---|---|
| How often | Manual — apply by hand (no pattern; runs when somebody applies it), Every week, or Every few weeks. |
| Service days | Sun–Sat chips. Pick every day the route goes out. At least one is required for a recurring route. |
| Repeat every / Starting week of | Every few weeks only. Repeat every is 1 to 8 weeks. Starting week of is the first day of an "on" week — pick that week's Sunday or Monday, or the first service day itself. OpsVara counts the cycle in seven-day blocks from that exact date, so a date later in the week than a service day pushes that service day into the week before. Required for anything over 1 week. |
| Season starts / Season ends | Optional. Only the month and day matter; the route runs inside that window every year and skips the rest. Set both or neither. |
| Put this route on the calendar automatically | Off by default. When on, the jobs are created Lead time days ahead of each service day, assigned to the Default worker (or the Backup worker when they are out). A day you already booked by hand is left alone. Greyed out until a Default worker is set. |
| Lead time | 1, 2, 3, 5, 7, 10 or 14 days (3 by default). How far ahead the jobs are created. Only shown once the automatic option is on. |
Watch a pattern before automating it
A schedule on its own only draws dashed Plan cells on Schedule → Routes. Nothing is booked until you click one or turn on the automatic option. Run a new route by hand for a week or two first.
Sites at different frequencies on one route
The worked example: one technician, seven sites on Monday, five of the same sites again on Wednesday, because five customers are on twice a week and two are on once a week.
One route, two service days
More → New Route → How often = Every week → Service days = Mon and Wed → Default worker → add all seven sites → Create Route.
Let the agreements decide
Leave every stop on Auto. The five twice-a-week customers are due both days; the two once-a-week customers are due Monday. Wednesday books five.
Move a once-a-week stop to Wednesday, if you want
Open the route, find the stop, click Wed under Visit days. The pin outranks the agreement's frequency, but never the agreement's named weekdays.
This only works when the five agreements actually say twice a week — a Visit Schedule on Set weekdays with Mon and Wed, on Set frequency at 2 Per Week, or a visit interval of 3 or 4 days. An agreement that says every 7 days is served once, on the route's first day, however many days the route runs — unless you pin that stop to both days.
Pinning both days does not change the agreement
Clicking Mon and Wed on a stop serves it on both days, even when its agreement says every 7 days. The agreement still says once a week: its contract page, its expected visit count, and any automatic job creation still count one visit a week. On an agreement billed per visit, every visit the route books is billed on its own, so the customer is billed for the second visit too. Change the agreement when the customer has really moved to twice a week, and then clear the pin — a pin stays put, so it would keep the stop on both days after the agreement later drops back to once a week. Route health lists every stop pinned to more days than its agreement asks.
Change the agreement from its contract page
On Sales and Billing
The alternative: two routes
If the agreements say every 7 days and you would rather not change them, build two routes for the same person: a Monday route with all seven sites and a Wednesday route with the five. Each must have a schedule — Every week, or Every few weeks — with its own service days. A site on two routes that run on different days is not reported as a conflict; a route left on Manual conflicts with every other route holding the site, because a route with no days might run on any day, and it draws no Plan cell and never auto-applies.
Where each rhythm lives
| You want | Set it on the route | Set it on the agreement |
|---|---|---|
| Once a week | Every week, one service day | Every 7 days, or 1 per week — either lands on the route's first day |
| Twice a week | Every week, two service days | Set weekdays naming both route days, Set frequency at 2 Per Week, or every 3 or 4 days — one of these, or a Visit days pin of both days, is needed for the stop to be due both days |
| Every 2 weeks | Every few weeks = 2, plus Starting week of — the whole route | An agreement on every 2 weeks does not skip weeks on a route that runs every week; give it its own every-few-weeks route |
| Every 10 days | Not possible — routes are built from weekdays | Visit Schedule = 10 days between visits (a work type on Fixed interval), and keep the site off routes that run every week: a stop with an interval longer than 7 days is served every week the route runs |
| Twice a week in summer, once in winter | Both days, all year | Seasonal Frequency windows stored on the agreement itself, set when it is created — seasons on the work type alone are not read by routes. In winter the seasonal stops are skipped on the second day; the day itself is skipped only when nothing on the route is due. See Change Frequency by Season. |
After the route exists
Find it. On Dispatch → Saved Routes → Routes, the Show control narrows the list: All Routes, Hide Drafts, or Drafts Only. After you save an edited route, the list turns to the route's page, tints its row for a few seconds and reads Saved with the route name. Amber marks the line that crossed its limit: the stops figure, the hours line (which adds · over 5.6h), or both. Its info tip says which limit and, when the route set none of its own, whose default it is (for example 8 stops against a limit of 6 (from Routine Service).), the same note as on the Schedule lane. Hover the figures to see the limits in force even when nothing is over: Limits from Routine Service: 10 stops and 5.6h a day. In a route's Edit dialog, Max Stops and Max Minutes are blank when the route has no limits of its own, and the grey placeholder shows the default it uses (for example 10 · from Routine Service). Leave a field blank to keep using the default.
Last Run is the latest day the route was booked for (for example Wed, Nov 4), not the day someone pressed Apply; hover it to see when Apply was last used. A day still ahead reads Booked for Wed, Nov 18. Moving a run to another day moves it too. A route nobody has applied since this column changed shows Applied Nov 8 (the day Apply was pressed) until its next Apply. A site's Routes card reads the same way (Last run Wed, Nov 4).
Book it. On Schedule → Routes, each route is a row and each service day shows a dashed Plan cell. Click one to open Apply Saved Route, check the Preview, and press Apply Route. Or press Apply on the route's row under Dispatch → Saved Routes and pick the Target date yourself; Crew member starts on the route's Default worker (and is fixed when you have only one field worker). The Preview lists every stop on the route, not just the ones due that day.
The result says how many stops were applied and names the ones skipped. A stop that was not
due on that weekday is listed as not due on this service day; it means the stop is served on
its other day, not that something failed. A stop listed as outside agreement dates has an
agreement that does not cover the day — check its start and end dates. A stop listed as
already assigned to someone else that day already has that visit with a different worker;
Apply leaves it alone and books no second visit, so reassign it on the board if this route should
have it. A stop whose work type needs a licensed applicator shows Needs a licensed applicator
when the Crew member is not marked Licensed applicator; the summary says how many stops
need a licensed applicator and will be skipped, that this person is not marked Licensed
applicator in Settings
Under that, an amber box headed 1 stop was served on a day its agreement doesn’t name (or N stops were served on days their agreement doesn’t name) lists stops that were booked, but on a day the customer's agreement does not name, one line each — for example Kona Palms — agreement names Fri; this route runs Mon, Thu — served Mon anyway. The agreement names only days this route never runs, so the stop fell through to the route's own day. The job is still created or linked exactly as before; the box is there so the mismatch is seen. Change the agreement's days, or move the stop to a route that runs them. A due stop that ends up skipped — for example with Create Jobs for stops that do not have one yet on this date unticked and no job to link — is listed under skipped only, not in the box.
Or let it book itself. Turn on Put this route on the calendar automatically in the Schedule block. The daily sweep creates the jobs Lead time days ahead, and skips a service day on which nothing is due — or on which none of the stops due has an agreement covering that day and none of them already has a job there, since applying would book nothing. A skipped day is not claimed, so a later sweep still books it once an agreement covers it. A day whose only work is jobs the office already put there is still booked: the sweep adds them to the run. It books off-agreement stops the same way a manual apply does and does not show them to anyone; route health is where they appear.
A day you already put the route on yourself (with Apply, a Plan cell, or Put on Calendar) before the sweep reached it is left to you for good. The sweep never applies the route to that day again, because a second apply re-orders the crew's stops. This holds even if you later move that run to another day or cancel its visits, so the sweep never brings back a day you cleared. Cancel rather than delete: if you delete a hand-booked day's visits before the sweep reaches that day, it no longer knows you booked it and books the day itself. Visits the recurring schedule created on the route don't count as booked by hand; the sweep still books those days and puts the route's crew on them. A run you moved onto one of the route's own days doesn't stop that day either. The sweep still books it: for stops due that day, the visit you moved there becomes that day's visit (never a second visit to the same site) and is put in route order. Moved stops that aren't due that day, such as a once-a-week site moved from Monday to Thursday, are left as they are ahead of the route's stops, so re-order the day on the board if needed. Turning the switch on mid-week is therefore safe for days you've already booked by hand.
Route health. Dispatch → Saved Routes → Health (when the Big Board is on for your account) counts from three different clocks, and each tile's info tip says which:
- Routes Breached and Routes Close count routes by their most urgent stop, with the stops on those routes beside them (Routes Breached 13 · 97 stops). A close stop on a breached route counts under Routes Breached. A stop's days overdue count from its last completed visit. Only a completed visit resets them: a visit that was booked, or even checked in, but never closed out does not. Each card shows the date under Time to Breach (Last completed: Jun 29), and N visits booked, not closed out when the route has visits on past days still Scheduled, Delayed or In Progress. A line under the tiles adds them up. If a route crews drive every week reads months overdue, close out those visits. On work that uses Season Periods, the days count down to the end of the current period instead, and the card says so (July window ends Jul 31).
- Behind Cadence counts from the last time Apply was used for the route, by someone or by auto-apply. The card's chip reads Last applied 12d ago or Never applied.
- Show N stops needing a visit lists the card's breached and close stops, each with its own last completed date and any visits booked, not closed out.
Soliven's summary above the cards takes a few seconds. If it can't be written, the page says Summary unavailable. with Retry.
Health also flags routes with No assignee, routes that are Over capacity (judged on the same limits as the Routes list, the route's own or its work type's default; hover the chip to see which), and stops that are also on another route. Three chips compare each stop's agreement, as it reads today (including its Seasonal Frequency window), with the days apply actually books:
- N stops need more visits than their routes give — the agreement names a day that no active route holding the site runs, or asks for more visits a week (or a shorter interval, or a tighter every-few-weeks cycle) than those routes give together. Every route holding the site counts, so a Monday route plus a Thursday route for a twice-a-week customer is fine, and so is a twice-a-week customer on a route that runs both days.
- N stops served on days their agreement doesn't name — this route serves the stop on a day the agreement does not name, because the route runs none of the agreement's days. These are the same stops the apply result lists in amber.
- N stops pinned to more days than their agreement asks — a Visit days pin on this route gives the stop more days than its visit count or interval asks for, such as an every-7-days stop pinned to Mon and Wed. The stop's line reads "Agreement asks for every 7 days; pinned to 2 days (Mon, Wed)." Each extra day is an extra visit, and an agreement billed per visit bills every one. Change the agreement if the customer really moved to twice a week, or click Auto on the stop.
Under the card, Show N stops to check against the agreement lists each one as site · customer — what is wrong. A route whose season has ended, a route outside its own Season starts / Season ends dates today, a route with no service days (a Manual route usually has none), and a stop with no active agreement report neither. A route outside its season dates also does not count as serving anyone: a summer-only Friday route leaves a Friday customer uncovered in October, and Health says so.
Dispatch. While Saved routes in dispatch on Settings
Route books
Dispatch → Saved Routes → Route Books opens on Current: the active book first, then drafts, ten to a page. Choose Archived to see past books. Each choice shows its count, and the counts follow the search box on the right, which finds a book by name. A clone is a draft, so it always lands in Current. Each tab of Saved Routes has its own search box in the same place, and what you type on one tab stays on that tab.
Click a book to open it. Archived books open too, read-only, so last season's routes stay readable.
- List shows the book's routes with the Routes tab's columns. Click a route to show its stops in driving order.
- Map puts every route of the book on one map: a pin per stop in the route's colour, joined by the road the route drives. A dashed straight line joins the stops while the road loads, or when it cannot be drawn. That line is not the road. Hover a road to see the route's name. Click a route in the list beside the map, a pin, or a road to pick that route out and dim the rest; Show all brings them back.
- Route, worker, or site… narrows both views to the routes that match.
- A stop whose site has no map location is not drawn. The line under the map says how many: 3 stops have no map location and are not shown. Set the site's address or pin to put it on the map.
Create a route book from routes you already have
Routes made by hand, saved from a planned day, or imported are in no book. To group them:
Press Create Route Book
On the Route Books tab, press Create Route Book. The Create Route Book dialog opens.
Name it and say how long it runs
Fill in Book name (it starts as Current Routes). Under Runs, pick Ongoing (year-round), or One season and type the year.
Pick the routes
Every route that is not archived is listed with its stop count and Default worker. Routes in no book are ticked already. A route in another book is shown now in that book and starts unticked; tick it to move it, because a route belongs to one book only. Select all and Clear tick or untick every route.
Create the book
Press Create book with N routes. The book is created active. You can also create a book with no routes and add them later.
Add or remove routes in a book
Open the book and press Add routes. The Add routes to dialog lists the routes that are not already in that book; tick the ones you want and press Add N routes. To take a route out, press Remove on its row. The route leaves the book and keeps running.
Adding or removing a route changes only which book it belongs to. Its stops, service days, crew, status and season stay exactly as they were, so nothing the crews drive today moves. An archived book has no Add routes or Remove, and archived routes cannot be added to a book.
Archive a route book
Press Archive on a book's card on the Route Books tab. The Archive dialog asks you to confirm, and it archives every route in the book. Those routes leave Dispatch, route health and automatic booking. Visits already booked on them stay booked, but nothing books their next runs.
There is no restore in the app. To use the routes again, clone the book, which starts their run history over.
If crews have driven the book's routes in the last 14 days, or have open visits booked from today on, the dialog lists them under Crews are driving these routes, with the count for each route in use. The 14-day count is every visit booked on those days, done or not. You must tick I understand these routes stop running from Dispatch and auto-apply. before Archive book works. A book no crew is using archives without the checkbox.
Trying out route books? Clone instead
Press Clone on the book rather than archiving it. A clone is a draft and doesn't touch the routes crews drive, so you can rearrange it freely and activate it when you are ready.
An archived route's past runs stay on the Schedule's route grid, on a read-only row labelled Archived — past runs only. See Put a Route on the Calendar.
Route colours
A route's colour is picked from the route palette when the route is made. The app accepts only
a hex colour such as #0F8F85; any other value sent to it is refused, and one stored before
that check is shown in a palette colour instead.
Verify it worked
- Dispatch → Saved Routes lists the route with the right Cadence and Assigned person.
- Schedule → Routes shows the route's row with a dashed Plan cell on each service day in the coming week.
- Open the route: on a route with two or more service days, each stop shows Visit days with Auto or the days you pinned.
- Apply the first service day: the result says Applied 7 stops with no skipped list, the day's run shows on Schedule → Routes, and the crew sees the day on their phone.
When something looks wrong
| What you see | Why | What to do |
|---|---|---|
| Wednesday booked nothing, or everything came back skipped | Every stop is due Monday — their agreements say once a week or every 7 days, so Auto puts them on the route's first day. | Change the twice-a-week agreements to named weekdays or 2 per week, pin those stops to both days under Visit days, or use two routes. |
| Every once-a-week stop is on Monday | Auto puts a once-a-week stop on the first service day. | Pin the ones you want elsewhere under Visit days. |
| I pressed Build routes and the list is empty | Only Create N routes on the Commit step saves. | Run the builder again and finish on Commit. |
| Move to… is greyed out | There is only one proposed route, so there is nowhere else to send the stop. | Add capacity or split on Review until a second route exists. |
| The house pin is missing, or everyone starts at the shop | Start location is still Company dispatch address (default), or a home address did not geocode and fell back to the office. | Edit the person under Settings |
| The Scope step shows 0 sites, or fewer than you expect | Sites need a map location, no service hold, and an active customer. Only sites with an active contract also hides sites whose agreement for the chosen work type has ended, starts later, or does not exist, and Only sites not already on a route hides routed sites. A site's type must also match the work type (a pond treatment only finds sites typed Pond). The step says how many were skipped for a hold or a missing map location. | If the contracts have ended or start later, untick Only sites with an active contract. Otherwise check the site type, or untick Only sites not already on a route. |
| 5 stops also on … on Health | Two routes hold the same sites and either both run the same weekday or one of them has no service days (a route created on Manual). | Give each route its own service days. |
| N stops need more visits than their routes give on Health | A day the agreement names is on no route holding the site, or the routes give fewer visits than the agreement asks. | Open Show N stops to check against the agreement; add the missing day to a route, add the site to a route that runs it, or correct the agreement. |
| N stops served on days their agreement doesn't name on Health, or an amber box after Apply | The agreement names only days this route never runs — e.g. agreement names Fri; this route runs Mon, Thu — served Mon anyway — so the stop is booked on the route's day instead. | Change the agreement's days on its contract page, or move the stop to a route that runs them. |
| A dashed Plan cell shows the route's full stop count on a day that books fewer | The calendar shows the route's size, not the stops due that day. | Apply it — the result line says how many stops were booked and names the ones skipped. |
| Auto-apply is greyed out, or missing | Greyed out means no Default worker — the note under it says Assign a worker first. It is not shown at all while How often is Manual. | Pick a Default worker and a recurring How often, then tick it. |
| The route is listed as Draft | It was committed with Save as a draft. | Activate its book under Route Books. Draft routes can still be applied by hand. |
| Saving the routes said the request timed out | A very large build can take up to two minutes. | Check Saved Routes first: the save may have gone through. Build again only if the routes are not there. |
Frequently asked questions
I booked next week by hand. Will turning on automatic booking book those days again?
No. A day you already put the route on yourself, with Apply, a Plan cell, or Put on Calendar, is left alone for good, even if you later move that run or cancel its visits. Automatic booking only books the days you haven't. If you don't want a hand-booked day to go out, cancel its visits rather than deleting them; once deleted, the sweep can't tell you booked it.
Can one route serve some sites twice a week and others once a week?
Yes. Give the route both service days, and leave each stop's Visit days on Auto. A site whose agreement says 2 per week, or names both of the route's days, is due on both days; a site on once a week or every 7 days is due on the route's first service day only. The route's second day simply has fewer stops.
Can I pin a stop to both of the route's days?
Yes. Under Visit days, click both day chips — Mon and Thu on a Monday-and-Thursday route. The stop is served both days even if its agreement says once a week, but the agreement still says once a week, so an agreement billed per visit bills both visits. Click Auto, or unpin every day, to hand the stop back to the agreement. A contract that names its own weekdays still wins over any pin.
Which day does a once-a-week site get on a Monday-and-Wednesday route?
Monday — Auto puts a once-a-week stop on the route's first service day. To serve it on Wednesday instead, open the route and pin that stop's Visit days to Wed.
Can a saved route run every 10 days?
No. A route's schedule is built from weekdays — every week, or every few weeks on the same weekdays — so every 2 weeks works and every 10 days does not. Put a 10-day rhythm on the customer's agreement as a visit interval and keep that site off routes that run every week, or it will be served every week.
I pressed Build routes in the Route Builder and nothing was saved. Why?
Build routes only proposes. The routes are written when you press Create N routes (or Save N routes as draft) on the Commit step. Leaving the page before that discards the proposal.
Do I need two routes for a twice-a-week round?
Not usually — one route with two service days is the intended shape. Two routes on different days that share sites also work, and are not reported as a conflict as long as each has its own service days; a route with none conflicts with every other route holding the site.
Why did Wednesday's apply say "skipped" for some stops?
Those stops were not due on Wednesday — their agreement or their Visit days put them on the other day, so the line reads "not due on this service day". They are not missing; they are booked when you apply their own day. Any other reason (inactive site, no active agreement, outside agreement dates, active permit required) is a different problem.
Why was a stop skipped as "outside agreement dates"?
Its site has an active agreement — for that work, or, when it has none for that work, for other work — but no agreement's start and end dates include the day you applied. It starts later, or it ended and has not been marked expired yet. The stop gets no new job that day; a job already on the day for it is still added to the run, unless it is assigned to someone else. When the site holds an old agreement and its renewal, the one whose dates include the day is used, and the job is linked to it.
Why was a stop skipped as "already assigned to someone else that day"?
The site already has this visit on the day, and a different worker holds it. Apply does not take it over and does not book a second visit, so the site is not visited or billed twice. Reassign it on the board if this route's worker should have it, then apply again. See [Put a Route on the Calendar](/help/dispatch-and-routing/put-a-route-on-the-calendar).
Why does Apply say a stop was served on a day its agreement doesn't name?
The customer's agreement names weekdays this route never runs — for example Friday on a Monday-and-Thursday route — so the stop fell through to the route's own day and was booked there anyway. Nothing was skipped. Fix it on one side, either by changing the agreement's days or by moving the stop to a route that runs them. Route health lists the same stops.
How do I move one stop onto another proposed route?
On Review, expand the route (**Show N stops**) and use **Move to…** on that stop, or click the stop's pin on the map once one destination route is selected. Sequence does not move pins — it only sets driving order.
Can I build routes before my customers' contracts start?
Yes. On the Route Builder's Scope step, untick Only sites with an active contract. Every active site of that type is then included, whether its contract starts later, has already ended, or it has none — useful for planning next season once this season's contracts are over. Applying a route still books nothing for a stop without an agreement that covers the day, so you can plan early without creating early jobs.
How do I get routes I built one at a time into a route book?
On Dispatch → Saved Routes → Route Books, press Create Route Book. Routes that are in no book are ticked already; name the book and press Create book with N routes. Joining a book does not change a route's stops, days, crew or status.
What are the square shop and house pins on the builder map?
Where that day's drive starts and ends. Scope mode shows **Main office** (Routes start and end here). After Build routes, each proposed route gets its own origin — the shop, a dispatch yard, or a worker's **Home** — from **Assigned to**. Pick a different person on Review and the start pin, the road path, the stop order and the drive time change to that person's start. One pin per distinct place. Set **Start location** on Settings → Team.
I archived a route book by mistake. Can I get it back?
Not with a restore, because the app has none. Clone the book to use its routes again; the clone is a draft, and the routes start their run history over. Nothing was cancelled when you archived it, so visits already booked on those routes are still on the calendar. They stay booked, but nothing books the routes' next runs until you have cloned and activated the book.
Why did Build Routes recommend someone who starts farther from the route?
The nearer people were either not set up for every stop on it or already had a full week. A person is full once they drive one route for each day they work, counting their live routes in other route books. People with room are recommended first, however near a full person starts. You can still pick anyone under Assigned to.
Why is Create N routes greyed out on the Commit step?
A route with work that needs a licensed applicator is assigned to someone who is not marked Licensed applicator, or a route's schedule is incomplete. The red message above the button names the route. Pick a licensed driver or Nobody yet, or mark the person Licensed applicator under Settings → Team. A missing route book name does not grey the button; pressing it takes you to the name field.
What does "not qualified for this route" mean in the Assigned to list?
That person cannot do every stop on the route as it stands. Pick them and the route card says what is missing, such as a work type, a skill, the Licensed applicator mark, or a territory rule. Only a missing license on licensed work stops the save; the others are a warning.
Related guides
- Put a Route on the CalendarRead your set routes as a calendar — one row per route, one column per day — then book a day, move a rained-out run, or flip the same week to crew lanes and read it by person.
- Add New Customers to Existing RoutesPut newly signed sites onto the routes that already pass their door, with capacity counted as each one lands, instead of building them a route of their own.
- Assign the Day's WorkPut people on the day's jobs from Dispatch, by hand, with Soliven's two-step Assign the Day, or one person at a time with Find Jobs to Add to Crew.
- Schedule Visits on Set WeekdaysServe a customer on fixed days of the week — twice a week on Monday and Thursday, for example — instead of every set number of days.
- Schedule a Number of Visits per Week or MonthSell and bill a customer on a count — twice a month, three visits a week — and let the office pick the days.
- Change Visit Frequency by SeasonServe a customer twice a week in summer and once a week the rest of the year, with the contract billing the real number of visits.