Home Dispatch

Dispatch

Dispatch
By Sebastian
• 21 articles

Create a dispatch

A dispatch is how work reaches your drivers. It says where (one or more addresses, a whole route, or everything inside a zone), when (a planned date and time) and what (the work type: salting, plowing, or whatever your business has set up). Drivers see it in the app the moment you send it. The dispatch list, where every sent dispatch appears Send a dispatch 1. Open Dispatch in the left menu. 2. Press Create dispatch and choose what you are dispatching: Address dispatch for single addresses, Route dispatch for whole routes, or Zone dispatch for everything inside a zone. (Manual dispatch is for registering work that was already done.) Choosing between addresses, a route and a zone 3. Pick the work type at the top, then tick the items to include. For a route or zone, every address it contains is included automatically; addresses whose owner has disabled dispatching for you are listed but left out, with a note saying why. The bar at the bottom keeps count of what you have selected. Ticking the route to dispatch On a zone dispatch, the search box (Search zone, address or customer) finds more than zone names. From three characters it also looks through the addresses your zones can dispatch, by address, address name, customer name and customer number, and lists every zone whose name matches or that holds a hit. Each hit reads In zone and the zone's name, with its customer, so you can tell which zone an address belongs to before you tick anything. While the search narrows a zone to its hits, that zone's box ticks only the addresses shown, not the whole zone; a zone found by its own name lists, and ticks, everything in it. Clearing the search closes what it opened and keeps every tick you made. On an address dispatch, an address that sits on a route of the business responsible for it goes out with that route's crew as well as the drivers you add in the popup, exactly as it would through a route or zone dispatch. An address on no such route takes only the drivers you picked. On a route dispatch, the filter beside the search decides whose routes are listed: All routes (the default), Our routes (the ones you drive yourself) and one entry per contractor, each with its route count. Tick as many as you like; ticking All routes clears the rest. A contractor's entry holds both the routes you handed to them and the routes they built themselves around your addresses. You can dispatch those too: only your own addresses on the route go out, to that contractor, and they add the rest of their route from their own screen. 4. Open a route (the arrow on its row) to see Drivers above its addresses. The people the route is configured with are already picked and sit at the top as chips; press the cross on one to take them off for this dispatch only. To add somebody, type in the search box under the chips: the drivers who match are listed in the small window below, and Add puts them on. The route's own driver list is never changed by this, so a stand-in tonight is not a stand-in tomorrow; to change who normally drives a route, use Drivers on a route. Leave the panel alone and the route goes out with its usual crew, exactly as before. A route cannot be dispatched with nobody on it. If you clear the last name, or a route you picked has no drivers configured, Dispatch now stops and names the routes that need a crew. Add somebody, or untick the route. Routes you have handed to a subcontractor, and routes a contractor built, are the exception: they crew those themselves, so the panel is not shown and they are never held up here. 5. Set the Planned on date and time in the bottom bar. The dates and times are your business's clock (the Time Zone under Settings → Business), not the computer's, so a dispatcher working from another country is offered the same days and times as the office. - Now fills in the date and the time together: five minutes from now, rounded up to the minute (after 23:55 that is tomorrow). - Today can be picked. If the time is still empty, or already gone, it becomes five minutes from now; the picker does not offer times that have passed, and a passed time you type is replaced the same way. - On any other date the time stays empty until you choose one, and Dispatch now says Choose a time for the planned date. rather than sending the work out at midnight. - Time spent filling in the rest of the form does not count against you: a planned time is accepted until five minutes after it has passed, so Now stays good for ten minutes. Older than that, the dispatch is refused with The planned date and time must be in the future. Beside the planned time, some businesses see a Snow depth field: US and Canadian businesses, and any business with a work type priced by snow depth. Type the depth on the ground, or leave it empty to take the weather snapshot's snowfall; the depth decides which tier a depth-priced address bills, and it can still be edited on the dispatch until completion. See Pricing by snow depth. Setting the planned time 6. On an Address dispatch only, decide about the money: Should be invoiced is on by default, and while it is on, Who should be invoiced? offers Customer and subcontractor, Customer only or Subcontractor only. Route and zone dispatches always bill both sides and ask nothing. What each choice does is in Who is invoiced for an address dispatch. 7. Press Dispatch now. A summary shows the work type, the planned time, the routes and who they are assigned to, and on an address dispatch the invoicing choice. Press Confirm and dispatch. Confirming the dispatch The dispatch appears at the top of the list with its planned time, and every driver on the route is notified. If you are told about an existing dispatch Two things can happen when you press Dispatch now: - You are invited to an active dispatch: another business that shares these addresses with you has already dispatched them. Join the existing dispatch adds your selection to theirs and accepts those addresses on your behalf; Create new dispatch keeps the two separate. See Why your dispatch was merged into another. - Active dispatch close to this time: you already have a dispatch near this planned time. Collect into existing adds the new addresses to it; Create new dispatch keeps them apart. With several such dispatches the prompt lists them newest first and you pick the one to collect into before pressing Collect into selected. Neither choice can be undone from this screen; if you picked wrong, open the dispatch and remove the stops you did not mean to add. A dispatch created from a complaint asks neither question. It is always a dispatch of its own, never joined to or collected into another, so the complaint's choice of who carries out the work and who is invoiced for it stays as you set it. See Handle a complaint. Why was my dispatch refused If the dispatch does not go out, the message says which rule stopped it and what to change. It lists every reason at once, not just the first, and it names the routes and addresses involved, so you do not have to press Dispatch now again to discover the next problem. | The message says | What it means | What to do | |---|---|---| | None of the selected routes has an address that can be dispatched on that date | The routes are yours, but every address on them was filtered out. The lines underneath say why: not active on the planned date, withheld by another business, or not yours. | Fix whichever the lines name, or pick different routes. | | None of the selected addresses can be dispatched on that date | Same thing for an address or zone dispatch. | See Active period on an address. | | ...(n) address(es) not active on the planned date | Those addresses are outside their active period on the day you are dispatching, not today. An address that stops being serviced in October cannot be dispatched for November. | Change the planned date, or extend the address's active period. | | ...(n) address(es) withheld from you by business | The business that delegated those addresses to you has switched dispatching of them off. You still service them; you may not start the dispatch. | Ask that business to allow it. See Who owns an address. | | ...(n) address(es) neither owned by you nor assigned to you | The route still carries an address whose assignment to you was revoked. | Take the address off the route, or have it assigned to you again. | | None of the selected routes belongs to your business | The routes are somebody else's. | Pick a route you own or one assigned to you. | | None of the selected zones belongs to your business | Same, for zones. | Pick a zone from your own zone map. | | A subcontractor chosen for one of the addresses is not one of yours | The subcontractor picked for a stop is neither below you nor one you have invited. | Choose one from your own list, or leave the address unassigned. See Assign a subcontractor. | | The dispatch you were adding this to has been completed or cancelled | You chose to collect into a dispatch that ended while the prompt was open. Nothing was added. | Open the list again and pick one that is still running, or create a new dispatch. | | Another dispatch for the same work type is being created right now | Someone else pressed the button at the same moment. Nothing was created. | Wait a few seconds and press Dispatch now again. | | Nothing could be added to this dispatch | Every address you picked was already on the run or was filtered out. | The lines underneath say which; see Add stops to a running dispatch. | A dispatch can also go out short. If some addresses were left behind but enough survived, the dispatch is created and the same lines are added to the confirmation, so you can see what did not go with it. Rules that skip a stop after the dispatch exists are a separate thing: Addresses skipped by a rule. If you see "An internal error occurred" on a dispatch create, that is now a genuine fault rather than a rule, and it is worth reporting. See also - Make an address inactive, now or on a date - Follow a dispatch live - Build a route - Drivers on a route - Who is invoiced for an address dispatch - Why your dispatch was merged into another

Last updated on Sep 16, 2026

Accept or decline a dispatch invitation

If a business you work for dispatches addresses it has handed you (by zone, by route or one by one), your business is invited. The dispatch appears in your Dispatch list with a banner: You have been invited to this dispatch. Until you answer, your stops are view-only and your drivers see nothing. Every business invited to the dispatch gets a bell notification, and its administrators a push, when the dispatch is created. There is no email or text message. Answer route by route Under the banner is a list of your routes on this dispatch, one checkbox per route, with the number of stops still waiting for an answer beside each. Every route starts ticked, and All routes at the top ticks or unticks the whole list. 1. Open the dispatch from Dispatch list. 2. Untick any route you are not answering for right now. The banner says so itself: Untick any route you are not answering for. Until you answer, the stops are view-only. 3. Press Accept or Decline. Both act on the ticked routes only. Routes you left unticked stay in the list, still waiting. You can come back and answer them later, the same way. If the invitation covers single addresses rather than routes, there is no list: Accept and Decline answer for everything at once, as the banner says: Accepting covers all of your routes and addresses on this dispatch. Accept The accepted routes become active and you manage the stops exactly as on your own dispatch. The drivers on each of your routes were attached to its stops when the dispatch was created; accepting is what tells them there is work. To add or change who drives, press the driver badge on the route's header, which opens Invite drivers (see adding drivers to an existing dispatch). On a route you have not answered yet the badge does nothing: answer the invitation first. Decline Pressing Decline opens Decline this work. A reason is required: Tell the dispatcher why, so they can re-plan. Type it and press Decline. The ticked routes are refused. Their stops are marked Declined for the owner, nothing is expected of your drivers, and no invoice line in either direction will ever be drafted toward your business for them. The routes you did not tick are untouched. The owner is told: their business gets a bell notification with your reason as its text, and their administrators a push. They also see it on the dispatch: the route header reads Declined instead of a progress bar, your reason shows when they hover over it, and each stop carries Declined. On a zone dispatch there is also a Denied pill beside your name. What accepting hands you The stops of the routes you accepted become yours to run and to record. Your drivers see them on their phones and close them there; your office can set times, complete a stop, mark one unable, add the note and the photos, from your own dispatch list. You are not waiting on the owner to write any of that down for you, and the owner sees each of those the moment it happens. What stays theirs is the plan: which addresses are on the dispatch, what work type each bills under, and the dispatch's own message and time. An address you cannot do is Mark unable, with a reason, rather than one you take off. See who may change what. Change your mind A decline is not final. Once every route in your part has been answered and at least one was declined, the banner changes to You have declined this dispatch. with the note Accepting again re-takes all of your declined addresses on this dispatch. and your reason under it. Press Accept there and everything you declined is yours again. While some routes are still unanswered, the list shows only those; answer them first, and the declined ones come back for re-taking. Once the owner cancels the dispatch, the invitation is gone with it. Dispatching the same addresses yourself If you start your own dispatch on addresses that are already on the owner's active dispatch, you are asked whether to Join the existing dispatch or Create new dispatch. Joining adds your selection to the owner's dispatch and accepts those addresses for you, so the night runs, and is invoiced, as one job; addresses of your slice that are not in the selection keep the answer they had, declined included. A separate dispatch runs in parallel while your addresses on the owner's one stay pending or declined. See Why your dispatch was merged into another. The owner's view On a zone dispatch, the owner sees one pill per contractor (Awaiting response, Accepted, Denied), which disappears as soon as that contractor's work is under way. A route on which every stop was declined is shown as Declined, not as an error, carries no driver badge, and does not stop the owner from completing and invoicing the rest. When the owner answers for you If you have not answered and the owner cannot wait, the owner can press your Awaiting response pill and choose Accept on their behalf or Decline on their behalf. The popup says what will happen before the owner confirms, and a decline needs a reason there too. - Accepted for you: your pending addresses become yours to run, exactly as if you had pressed Accept yourself. Your drivers on those routes are told there is work, and your administrators get a bell notification and a push saying the owner accepted for you. - Declined for you: your pending addresses are marked Declined with the owner's reason and go back to the owner to reassign. Your administrators get a bell notification with the reason as its text, and a push. The owner can only answer what is still waiting. Routes you already accepted or declined are left as they are, and the dispatch's changelog names the owner as the one who answered. If you answer at the same moment, whoever was first counts; the other is told the invitation has already been answered. See also - Who sees a dispatch - What a decline does - Add drivers to an existing dispatch - Why your dispatch was merged into another

Last updated on Sep 01, 2026

Why an address was left out of a dispatch

You dispatched a route of twelve and got ten stops. The two missing ones were not lost: the system took them out on purpose, at the moment the dispatch was created, and it says why on each one. Here are the reasons, and what to do about each. A location rule excluded it Every address can carry service rules. An exclusion rule says "not on these days", "not in these hours" or "not in this weekly range", for some or all work types, and can be tied to the Holiday calendar. When the planned time of the dispatch falls inside such a rule, the address is removed and marked Excluded by rule, with the rule's name. The rule is judged against the planned time when the dispatch is created, merged or edited, not when the driver arrives. A dispatch planned for 06:00 and driven at 09:00 is judged at 06:00. A frequency limit is spent A limit rule says "at most N times per day / week / month / season". The count is of planned dispatches in that period (every dispatch on which the address still has a live stop), not of work actually done. When the limit is reached, the next dispatch drops the address with the limit's name. Weeks run Monday to Sunday; "season" is your business's season range (and the rule is skipped when no season is configured or the date is outside it). Too little snow fell An address can say Only dispatch when snow exceeds a depth, on its Prices tab. When the dispatch's snow depth is below it, the address's plowing stops are removed, with Below minimum snow depth: 3 in (the threshold, in your unit) as the reason; salting-only work on the same address still goes out. Unlike the other reasons this one is re-checked when the depth on the open dispatch is edited: the stop comes back by itself once the new depth reaches the minimum, and an unworked stop is removed again when it drops below. A stop you restored by hand stays, either way, and a stop with work recorded is never taken off. It raises no error or warning, because a dry night is not a mistake. See Pricing by snow depth. The owner switched off dispatching for you A business that handed you an address can turn May dispatch my addresses off for your business. You still service the address when they dispatch it, but you cannot dispatch it yourself: it is greyed out in your pickers, and a route that includes it is dispatched without it, with a note. The switch follows the address down the chain: if the address was handed on to you by someone who is themselves blocked, you are blocked too. The address is not active on that date An address can be made inactive, now or from a date, and active again from a date. An address outside its active window on the planned date drops out of route and zone dispatching. It is already on the dispatch Adding addresses to a running dispatch skips the ones already there (Already dispatched in the picker) rather than creating a second stop. The same applies when two overlapping routes go out together: the shared address is one stop, carrying one pass per route, and each crew registers its own. Restoring Open the dispatch and click the removed stop. - A stop a person removed comes back with Add to dispatch, and stays back: the next dispatch will not remove it again. - A stop a rule removed asks you to confirm that you are overriding the rule. It is then serviced and invoiced normally, this once. It is not made immune; the next dispatch applies the rule again and, if it still matches, removes it again. - A cancelled stop cannot be brought back. Dispatch the address afresh. Seeing it coming The dispatch picker already greys out what will be dropped and says why, and the summary before Confirm and dispatch lists the exclusions. The dispatch list adds a warning when a dispatch has Locations not in route or No business assigned, which are the other two ways an address ends up with nobody to do it. See also - When two routes cover the same address - Add a service rule to an address - Add a subcontractor

Last updated on Sep 03, 2026

Why your dispatch was merged into another

You pressed Dispatch now and, instead of a new dispatch, you were asked about an existing one, or your addresses ended up on a dispatch you did not create. This is deliberate. The system keeps one snow night as one dispatch, because two dispatches over the same addresses used to mean two invoices and a half-denied mess that nobody could read. Collect: your own second dispatch When you create a dispatch and you already have one that - belongs to your business, - has the same work type, - is planned within eight hours before or after the new planned time, - is not finished (not completed, not cancelled), and - is the same kind: address with address, route/zone with route/zone, you are shown it and asked to choose. When several qualify, Active dispatches close to this time lists them newest first, each with its planned time, how many addresses it has and how many are done, who created it and the routes or zones on it; the newest is selected, and you click another card to collect into that one instead. - Collect into existing (or Collect into selected): the new addresses are added to the dispatch you chose. Addresses already on it are untouched, and completed work is not dispatched again. - Create new dispatch: runs separately with its own progress and invoicing. Choose this for a second run on addresses that were already dispatched (a second pass the same morning, say). Nothing merges across the address ↔ route/zone line, and a manual registration (work already done) never absorbs anything. Test dispatches only ever merge with test dispatches. A dispatch that collected routes keeps the title of the route that was on it first, with +2 (or however many more) beside it for the routes that joined later, so the run does not look renamed after one of them. A dispatch with no route at all is titled by its code, for example Dispatch AB1050. A complaint dispatch is always its own A dispatch you create from a complaint is never collected into another dispatch and never joins one: the prompts above are not shown, and the server creates a new dispatch even when an active one of the same work type is close by. On a complaint dispatch you decide who carries out the work and whether it is invoiced (not invoiced, or the supplier only); collecting it into an ordinary run would give the stop that run's invoicing and its existing assignment, and your choice would be lost without a word. When you create it from the complaints overview, the new dispatch opens straight away and the complaint's row lists it. See Handle a complaint. Join: a subcontractor dispatching what the owner already sent If you dispatch addresses that another business owns and has already put on an active dispatch of its own (you were invited, maybe you declined), you are asked instead: - Join the existing dispatch: your selection here is added to the existing dispatch, and the addresses you brought are accepted on your behalf, whether they were still pending or you had declined them. Everything runs and invoices as one dispatch. Only the addresses you are dispatching change hands: an address of your invited slice that you left out of this selection keeps its answer, so a route you declined earlier stays declined when you later send out one small route of your own. - Create new dispatch: your own dispatch runs in parallel, and your addresses on the existing dispatch stay pending or denied. The card shows Dispatched by whom and Your addresses on it, with a count of how many were declined, so you can see what joining would take over. Re-taking the whole declined slice is the invitation banner's job, not the create prompt's: Accept on the dispatch, once every route is answered, takes every declined address back, see Accept or decline a dispatch invitation. One address, one stop Inside one dispatch an address is never there twice. If two of your routes overlap on an address and both are dispatched, the address is one stop with one visit per route, and it becomes one invoice line. Each route's crew still registers its own pass, so the stop is done only when both have been: when two routes cover the same address. Adding addresses to a running dispatch skips the ones already on it, and an address dispatched again while its stop is still running is attached to the running one rather than becoming a second. What still can happen The merge looks eight hours around the planned time. Two dispatches of the same addresses and work type on the same day that are further apart than that both go out and both bill; the invoice then marks the second line Possible duplicate, while the invoice is still a draft, so a person can judge whether it was a real second run or a mistake before it goes out. Two dispatchers pressing the button at the same second cannot produce twins; the second one waits and is collected into the first. If you chose wrong Neither choice can be undone from the prompt. Open the dispatch and Remove from dispatch the stops you did not mean to add, or cancel the separate dispatch you did not mean to create. Why was my dispatch refused Two refusals come from this same one-dispatch-per-storm machinery, and neither means anything is wrong with what you selected: - "The dispatch you were adding this to has been completed or cancelled." You chose Collect into existing, and that dispatch ended between the prompt appearing and your answer. Nothing was added and nothing was created. Open the list again and pick a dispatch that is still running, or create a new one. - "Another dispatch for the same work type is being created right now." Two dispatchers pressed the button at the same moment. The second one waits for the first so it can be collected into it, and if the wait runs out it refuses rather than risk producing twins. Nothing was created; press Dispatch now again in a few seconds. Everything else a create can refuse, and what to do about each, is listed under Why was my dispatch refused. See also - When two routes cover the same address - Create a dispatch - Accept or decline a dispatch invitation - When an invoice line is created

Last updated on Sep 16, 2026

Who sees a dispatch

A dispatch often involves several businesses (the owner of the addresses, a subcontractor, a subcontractor's subcontractor), and each of them sees a different amount of it. The rule is simple to state: you see what is yours. When a dispatch is in your list Your Dispatch list shows a dispatch if any of these is true: - your business created it; - your business is assigned a stop on it (you were invited, whether or not you have answered); - it works addresses you own, even if a subcontractor created the dispatch on them; - it runs a route you handed to a subcontractor. A cancelled dispatch stays in the owner's list only; everyone else stops seeing it. Users who may not create dispatches land in the Own view (work assigned to you); users who may dispatch also have Group, the dispatches your business manages. How much of it you see - The owner of the addresses sees the whole dispatch: every route, every contractor, every stop, with the pills and counts per contractor. - A subcontractor sees only its own slice (the stops it was assigned) and nothing about the other contractors on the same dispatch. Its drivers read the message it wrote for them, not the owner's message. - A subcontractor that dispatched your addresses itself shows up in your list too, sliced the other way round: you see your addresses on its dispatch, read-only, and nothing else it sent its drivers to. Zones are only ever shown to the business that drew them; routes only to whoever runs them. Internal comments never leave the business that wrote them. What you can do with what you see Seeing a stop and being allowed to change it are different things, and the line falls between recording what happened at a stop and changing what the stop is. Recording the work (check-in and check-out, completed, unable, the note, the photos) belongs to the business that accepted the stop, to anyone above it in the chain whose address it is, and to the owner while no live assignment exists. It works from the phone and from the web, so a subcontractor's driver closes the stop on their route and that subcontractor's office can correct it afterwards. An invitation you have not answered is view-only, and a declined one hands the stop back to the owner. Changing the plan stays with the business that dispatched it: taking a stop off the dispatch, editing the dispatch's own note and planned time, and cancelling the dispatch. If you cannot do the work, say so with Mark unable rather than removing it. Only the business responsible for a route can change its drivers. The work type a stop bills under sits in between. On the web it is still the dispatching business's to change. In the driver app, the drivers of the business responsible for the stop may change it too, a subcontractor's drivers included, so the crew that salted instead of ploughed can say so: they choose from the dispatching business's work types that are priced on the address, and not once a line of the stop is on an invoice past draft. See record a stop. What you do not see - The company two links away. Where a run has passed down the chain, the names you read are the company you deal with: if you gave the work to A and A gave it to B, the dispatch, the stops, the drivers' lines and the confirmation before invoicing all say A. B's crews keep their pins and trails on the map but are named as the company that sent them, without email addresses or photographs. See owner, subcontractor, sub-subcontractor. - Other businesses' customers, prices and invoices: the settlement between an owner and its subcontractor is visible to those two and nobody further down or up the chain. - A dispatch you have no part in at all. Asking for it by its link answers "not found", not "no access", so its existence is not revealed either. - Nothing of this reaches the customer portal beyond the customer's own addresses: a customer sees planned and past dispatches on their property, with photos, times and notes, but not who the subcontractor was or what anyone was paid. See also - Follow a dispatch live - Owner, subcontractor, sub-subcontractor - What a customer sees in the portal

Last updated on Sep 16, 2026

Address, route, zone, auto or manual: which dispatch?

Pressing Create dispatch asks you what you are dispatching. Every type ends in the same thing (stops for drivers, with a planned time and a work type), but the shape you choose decides who gets involved and how the stops are picked. The five dispatch types Address dispatch You tick individual addresses. Use it for the odd job: one customer called, a handful of addresses need a second pass, a complaint needs a visit. The addresses go to whoever is responsible for them: your own drivers if the address is yours, the subcontractor if it is assigned out. Drivers are picked per address. It is also the only type that asks who is invoiced, the customer, the subcontractor, both or neither; see Who is invoiced for an address dispatch. Route dispatch You tick whole routes. Every address on the route is included in its order, and the route's drivers come with it. This is the everyday dispatch for a business that runs its own routes, and it is what a subcontractor uses for the addresses it has been handed. A route may mix addresses you own with addresses you are subcontracted on; each is billed to the right party. Zone dispatch You tick zones drawn on the map. Everything inside goes out at once: every subcontractor with addresses in the zone is invited, and the routes they hold that touch the zone are dispatched for the addresses inside it. This is the large-operation dispatch (a city with a hundred addresses split across ten contractors), and it is the one where invitations, acceptance and merging matter most. See What happens when you dispatch a zone. Auto dispatch The system picks for you from the rules and assignments you have set up, and you confirm the result. Use it when the same selection goes out every time and you would rather check a list than build one. Manual dispatch Not a dispatch at all in the usual sense: it registers work that was already done (a past date and time, one or more routes, a work type) so that the stops are closed and the invoices follow, without any driver being told anything. Use it for the night the app was not used, or for a subcontractor reporting after the fact. It needs its own permission and refuses a future date. Two things every type shares - Work type and planned time are set on the dispatch, not per address. A second work type on the same addresses is a second dispatch. - Merging. If you already have an unfinished dispatch of the same work type within eight hours of the planned time, you are asked whether to collect the new selection into it or keep it separate. Address dispatches and route/zone dispatches never merge with each other, and manual registrations never absorb anything. See also - Create a dispatch - Register work that was already done - What happens when you dispatch a zone - Why your dispatch was merged into another - Who is invoiced for an address dispatch

Last updated on Sep 01, 2026

When two routes cover the same address

Large addresses often need more than one pass in a night, and the usual way to plan that is two routes that both include the address: one crew early, another later. Sending both routes on the same dispatch does what you would want, and the wording for it is one stop, two visits. What the office sees The address appears once on the dispatch. It is one stop, in one place, with one set of notes, photos and complaints, and it becomes one invoice line, not two. Beside it is a badge counting the passes: 1/2 means the address is planned for two visits and one of them is done. Hover it for the explanation, and under it one line per route: where that pass stands and when it ran. The stop itself keeps showing as in progress until the count is full. Open the stop and the usual Check In and Check Out pickers are not there; a note says the address has several passes and points you to Time at the address, where each pass is listed with its route, its driver and its times, and each open pass has its own pickers and a Complete pass button. Passes are closed one at a time from the web, and the stop follows from them; the steps are in complete, mark unable, remove or restore a stop. What each driver sees Each crew sees the address on their own route, and it stays open work for them until they have registered it. The first crew finishing does not tick the address off for the second one, and a driver who runs both routes registers twice, once per pass. Everything the driver does (start work, check in, check out, confirm, mark unable) lands on their own pass. That holds for anyone the app lets register work there, not only drivers with an accepted place on the crew: an administrator driving the run, for one, lands on the pass of the route they are on, and somebody on none of the routes takes the earliest pass still open. A registration never closes the stop while leaving its pass open, so a finished run does not linger on the phone's Home as started. Photos, notes and the stop's history stay shared, because they belong to the address rather than to one visit. When the stop is done The stop is completed once every planned pass is registered: - All passes completed: the stop is completed and bills normally. - One crew cleared it, another could not: the stop is completed. An address that got done is done, whoever managed it. - No pass managed it: the stop is unable, and it does not bill. The stop's check-in is the earliest arrival of any pass and its check-out the latest departure, so the times you see on the stop cover the whole night's work on that address. While a planned pass is still open the stop shows In progress and no check-out of its own, whether the other pass was closed by its crew or by the office. What it bills One line, whatever the address is priced by. For an hourly address the quantity is the sum of the passes, not the stretch between them: two visits of 45 and 30 minutes, four hours apart, bill 1.25 hours, not 5.5. See what makes an invoice line appear. If the second crew never comes Nothing bills while a pass is open, so an address waiting on a crew that will not arrive holds up its line. Close it from the web: open the stop and, under Time at the address, give the open pass a check-out and press Complete pass. When that was the last open pass the stop completes on its own. If nobody is going to do that pass at all and the first crew's work is not enough, Mark Unable on the stop settles every open pass with it, and completing the whole dispatch does the same. See completing and correcting a stop. Two runs, not two routes This is about one dispatch. Sending the same address twice in two separate dispatches is a different thing: two runs, two stops, two invoice lines, which is the right answer when a second storm arrives in the evening. Why your dispatch was merged explains which of the two you are about to get. Older dispatches Addresses dispatched before this was built have a single pass and behave the way they always did: one registration closes the stop. The badge only appears where more than one pass was planned. See also - Why your dispatch was merged into another - Add drivers to an existing dispatch - When an invoice line is created

Last updated on Sep 16, 2026

Add addresses to a running dispatch

Only the business that created a dispatch can add to it, and only while it is not cancelled. A subcontractor invited to it can only activate its own route addresses, described at the end. Add more 1. Open the dispatch from Dispatch list and stay on the Addresses tab. 2. Press Add More above the stops. 3. On a route dispatch the picker opens straight away, with a Routes tab and a Locations tab. On a zone dispatch a small menu asks what shape the addition has first: Address dispatch, Route dispatch or Zone dispatch; pick one and the picker you used to create the dispatch opens (see Create a dispatch), but what you tick lands on this dispatch instead of a new one. A route adds every address on it; a zone adds the addresses inside it. 4. Confirm with Add now. The toast reads Locations were added to the dispatch. and the changelog gets a line. The picker shows the dispatch's planned date and time greyed out, without the Now button: you are adding to a dispatch whose time is already set, so its time is not checked again, and a dispatch planned an hour ago still takes more addresses. Routes and addresses in one go On a route dispatch the picker has two tabs, Routes and Locations, with one Add now button under both. Tick routes on the first tab, single addresses on the second, and switch back and forth as much as you like: nothing you ticked is lost, the number beside each tab shows what it is holding, and one confirmation sends the lot. A zone dispatch keeps its zone picker and an address dispatch its address picker. Route addresses that were never dispatched On a route dispatch the Addresses tab can show a banner instead: This route contains addresses that are not dispatched. Do you want to add them? The route has grown since the dispatch was created. Press Add locations: the Active locations list opens with every missing address ticked. Untick what you do not want and confirm. Sending the crew back to the same address Sometimes an address needs a second pass on the same run: the car park that fills up again, the access road that drifts shut behind the plough. You do not make a second dispatch for that, and you do not add the address twice as two stops. You ask for another visit. Addresses the dispatch already carries stay in the picker with an Already on this dispatch mark. Tick one, press Add now, and a question appears: These addresses are already on this dispatch. Add them again? with the addresses in a table, each with the route it came in on and a tick. All of them start ticked; the tick in the header takes them all on or off. - Cancel leaves the picker open with everything still ticked, so you can change the selection and try again. - Add again (n) tells the dispatch to expect one more visit at each ticked address; an unticked one is left as it is. The stop shows 1 of 2 visits on the address list and in the driver app, and a timeline line records it. With nothing ticked and nothing new in the selection the button stays off, because there would be nothing to add. Whatever you add lands in its place in the run, not at the top: an address on a route the dispatch already drives slots into that route's order, and anything else goes to the end. Two things stay true whatever you do here: - The address stays one stop and one invoice line. It never becomes two rows on the dispatch, and the customer never sees the same address twice on the invoice. On per-task pricing the one line simply carries the number of visits actually driven; on hourly pricing nothing changes, because hourly already bills every pass. See When two routes cover the same address. - The count is a plan, not a rule. The stop still completes on the first pass and the driver is not blocked from finishing it. The extra visits are recorded as further passes over the address as they happen, and the "1 of 2" tells you and the driver what was asked for. An address you took off the dispatch earlier, or one that was cancelled, is not "already on" it: ticking that one simply puts it back to work, and no question is asked. What is skipped - An address already on the dispatch is skipped unless you confirm a second visit. Adding a route that overlaps the stops you already have adds only the new ones, and ticking the same address twice adds it once. If everything you ticked was already on the dispatch, the request is refused and the message names the addresses, so you can decide whether you meant Add again. Picking a route the dispatch is already running does not add the route a second time; it re-dispatches its addresses under the same rule. - Addresses a business above you has withheld. If the business that handed you an address has switched off dispatching for you, it is left out, and the toast says how many and who withheld them. A route whose every address is withheld is dropped. If nothing is left, the request is refused. - Addresses a service rule excludes today. The rules run on the new stops exactly as at creation (a no-Sundays rule, a spent frequency limit, an address outside its active window). See Why an address was left out. What the new stops get A new stop starts not started and stamped with the address's customer as of now (see Moving an address to another customer). An address that sits on a route of the business responsible for it brings that route's crew with it, as it would have at creation; any other new stop starts without a driver. A subcontractor whose addresses you added gets the same invitation alert it would have got had the dispatch started with them, as long as it still owes you an answer; one that has already answered is not asked twice. See Who is told what. Only the same contractor A route or address dispatch is one contractor's work, or your own. The picker therefore offers only what belongs with it: routes handed to, and addresses assigned to, the contractor the dispatch is already with, or, on a dispatch you drive yourself, your own unassigned routes and addresses. Work for another contractor goes on that contractor's dispatch. A zone dispatch is not held to this. If you are the subcontractor On a route the owner dispatched to you, Add More opens no picker. The banner above the stops says Your routes contain addresses that are not activated in this dispatch, with a count, and Activate my addresses (n) opens a table of them: each with its route, a tick, and From, which says whether the address is your own or one the dispatch owner assigned to you. Everything starts ticked; untick what should stay off, and Activate (n) brings the rest onto the dispatch. The service rules run on those too. See also - Create a dispatch - Who is told what - Why an address was left out of a dispatch - Moving an address to another customer - When two routes cover the same address

Last updated on Sep 16, 2026

Cancel a dispatch

Cancelling ends a dispatch that should not run, or run on. Only the business that created the dispatch can cancel it; a subcontractor invited to it cannot. If the problem is one address rather than the whole night, remove that stop instead, see Complete, mark unable, remove or restore a stop. Steps 1. Open the dispatch from Dispatch list and go to the Details tab. 2. Under Actions, press Cancel dispatch, next to Complete and Change work type. 3. Confirm in Are you sure?. The text is plain about it: the dispatch will be cancelled without a restore possibility. Press Cancel dispatch again, or Close to keep it. The toast reads Dispatch was cancelled, the slider closes, and the row in the list now reads Cancelled with no progress bar. What changes - Every stop nobody had finished (not started, or in progress) becomes cancelled. The Overview column counts them as Cancelled. - Stops already Completed, Unable or Removed keep that outcome. Cancelling never erases done work. - Route runs still open are cancelled; a run the driver already finished keeps its completion. - The changelog gets the line "Dispatch cancelled" with who and when, and the header of the dispatch shows Cancelled with the time. - Every action on the dispatch is disabled from then on: Actions are disabled because the dispatch is cancelled. When it is refused - The dispatch is already cancelled. - The dispatch has no pending locations to cancel. Nothing was open: every stop was already finished and every route run settled. Complete it instead, see Complete a dispatch and create the invoices. Who is told Nobody. No bell notification, push, e-mail or text message goes to drivers, subcontractors or customers, see Who is told what. Tell them yourself. A subcontractor that had not answered its invitation can no longer answer it; the invitation goes with the dispatch. Invoices Cancelling creates no invoices, and confirming invoicing is refused on a cancelled dispatch. Lines already drafted for stops that were completed earlier are not touched by the cancellation. The cancelled dispatch stays in your list; filter Status on Cancelled to find it. Who else keeps seeing it is in Who sees a dispatch. See also - Complete a dispatch and create the invoices - Who is told what - Who sees a dispatch

Last updated on Aug 22, 2026

Find dispatches and fix the error chips

Dispatch in the sidebar opens Dispatch list (the Live map sits beside it). Every dispatch you may see is a row: Job details, Type / Zone, Progress, Overview (the unable, completed, removed and cancelled counts) and Actions with Details. Clicking the row opens the same details. The dispatch list Small marks on a row say more than the counts: - A speech bubble with a number means somebody wrote something on the dispatch: the dispatch's own Message, its Internal comment, the message to a business, or a note on a stop. Hover it for Messages, one line per text with where it was written, so you can see whether a driver left a reason without opening the run. The internal comment is counted for the business that dispatched only, and a subcontractor counts the dispatch's message only when no message of its own replaces it. Notes on removed and cancelled stops count too, because why a stop was taken off or called off is exactly what you would open the run to read. - A yellow complaint mark with a number means the dispatch was sent out to put complaints right. Hover it for Linked complaints and how many complaints it carries. Complaint dispatches only in the filters lists just these runs. - Where the stops of one dispatch were not all worked under the same work type, the work-type cell shows one chip per work type with its stop count. Each work type keeps one colour of its own, the same on every row and inside the dispatch, so you can tell Saltning from Snerydning & Saltning at a glance without reading the chips. Hover for Mixed work types and the addresses that were changed, with who holds them. Inside the dispatch the same chips sit on its zone, contractor and route headers and on each stop's row, and a Filter button narrows the stops by work type, note, missing photo or admin completion. On a zone dispatch that button sits in the title line of the stop list, right of Expand All / Collapse all; elsewhere it sits beside the status tabs. A stop's work type is changed on the stop itself; both are described in Complete, mark unable, remove or restore a stop. Find a dispatch 1. The list opens with a Planned dates chip set to your business's standard date range, so older dispatches are hidden. Press the x on the chip to see everything. 2. Type in the search box to search by text. A dispatch's six-character ID (for example AB1050, shown on the row and under the title when the dispatch is open) finds exactly that dispatch, and both you and your subcontractor see the same ID. After two letters the box also suggests Zones, Routes and Addresses that have been dispatched: your own zones, your routes and the routes handed between you and a subcontractor, your addresses and the ones you handed out, plus whatever you reach through stops assigned to you. The best match comes first (the exact name, then names that start with what you typed, then a word that starts with it, then any match, shorter names before longer), so the one you mean is usually the top line. Picking a suggestion filters the list to those dispatches and becomes a chip you can remove again. 3. Sort with the dropdown: Created newest (the default, so a dispatch you just sent is the top row), Planned date newest, Planned date oldest, Work type or Business. A sort you choose is kept. 4. Press Filters to open Filter dispatches. The filter panel 5. Pick what you need and press Apply filters: - Dispatch type: Address dispatch, Route dispatch, Zone dispatch or Manual dispatch, one at a time. - Status: Planned, In progress (the chip reads InProgress today), Completed, Cancelled, any combination. - Planned dates: a range. - Dispatched by: one business, or All dispatchers. Useful when you work for several. - Errors: Locations not included in a route (yours), Locations not included in a route (subcontractors), Missing driver, No business assigned. - Manual dispatches only: work registered after the fact, see Register work that was already done. - Mixed work types only: dispatches where at least one stop was worked under another work type than the dispatch's own, the rows showing more than one work-type chip. - Complaint dispatches only: dispatches sent out to put a complaint right, the rows with the yellow complaint mark. Only complaints on stops you can see count. See Handle a complaint. Every active filter becomes a chip above the table; press its x to drop just that one. Reset all clears the panel. The error bar When something needs attention a slim red bar above the list counts the Dispatch errors. Each error type is its own chip with a count, and a type with nothing wrong shows no chip at all. Clicking a chip opens a popup listing exactly the things behind the number. The error bar, and the popup behind one of its chips The three chips: - locations not in a route: every address you own that the business managing it has no route for: the ones you kept, against your own routes, and the ones you handed to a subcontractor, against theirs. The popup is a list of businesses, you first; open one to see which of their addresses are missing from their routes, and Notify asks a subcontractor to route them. Fixing it works from either side: assign the address to a business whose routes cover it, or add it to a route; open dispatches pick the route up automatically either way. A dispatch that is only planned, or already completed or cancelled, does not count. The popup has one section per business, yours first and then each subcontractor whose route book is missing addresses; a subcontractor section has a Notify button that sends them a notification asking them to put the addresses into the right route. - dispatches missing a driver: planned or running dispatches of yours where work that is yours to drive has nobody on it: a route of your own with no crew and your stops on it, or a stop outside any route that is assigned to you and has no driver. Work handed to a subcontractor is theirs to staff, and an unassigned stop shows under no contractor instead: one problem, one place. Each row shows the dispatch's ID and date, and Show in list filters the list to that dispatch. Fix it on the dispatch, see Put drivers on a dispatched route. - locations with no contractor: addresses on your dispatches that no business is responsible for. This popup carries the fix: each address has a contractor picker, preselected to whoever last had that address, and Assign and notify assigns them on every dispatch where the address is unassigned and sends them the usual dispatch invitation. One address is one row even when it is unassigned on several dispatches. A route on which every stop was declined is not a missing driver: nobody is going to drive it, and crewing it is not the fix. The dispatch shows Declined on that route instead, see What a decline does. The same goes for a single stop whose every assignment was declined. On a row, the red Errors link under the type opens that dispatch on what is wrong. A zone dispatch opens on its Alerts tab, filtered to the stops and subcontractors concerned. A route or address dispatch lists every stop in trouble above its addresses and scrolls to that list: each line names the address and the reason (No business assigned, No drivers assigned, Location not in a route, or Awaiting answer from the business it was assigned to) with the button that fixes it: Assign business opens the subcontractor picker (for the business that dispatched), Invite drivers opens the driver popup, and View opens the stop. See also - Follow a dispatch live - Add drivers to an existing dispatch - What a decline does - Who sees a dispatch

Last updated on Sep 16, 2026

Read the forecast

Forecast in the sidebar opens Weather Forecast: a weather map on the left and the numbers for one point on the right. It opens on your business's own address (Copenhagen if the business has no coordinates), so a Swedish business starts over its own routes. The forecast for a point picked on the Greenland ice sheet, well below freezing Pick a point 1. Click anywhere on the map, or type an address in the search box above it. The panel says so itself: Click the map or search to pick a location. The Location card shows what you picked. 2. Switch the map layer between Temperature and Wind. Rain and Snow are offered as well once the map subscription allows them. Your Zones and Routes can be drawn on top, All of them or Yours only, so you read the weather against where you actually work. 3. Press the fullscreen button in the corner of the map for a bigger view. The status light The card at the top is a traffic light for the hour you are looking at: - SAFE, above 3 °C. Temperatures well above freezing. No action needed. - WARNING, between 0 and 3 °C. Near freezing. Monitor conditions closely. - DISPATCH, below 0 °C. Below freezing. Dispatch recommended. UNKNOWN means the weather has not loaded yet. The light is a hint, not a rule: it looks at temperature only, not at precipitation. The timeline Timeline covers one day back and seven days ahead, hour by hour. The bar is coloured by temperature (below 0 °C, 0 to 3 °C, above 3 °C), with a marker at the present hour and a label at each midnight. Drag the slider to any hour: the temperature shows beside the time, the map moves to the same hour, the status light follows, and the conditions card switches from Current conditions to Conditions at selected time with a Forecast badge. Press Now to come back to the present. Conditions Temperature in °C (red at or below zero), Wind in m/s, Precipitation in mm and its Type: Snow, Rain, Sleet or None. Freezing point Freezing point names the first coming hour at which the temperature falls through zero, as Drops below {0} at {1} with the day under it. The time is interpolated between the two hours around the crossing, so it can read 22:40 rather than 23:00. If the curve never crosses downwards in the period: No freezing point crossing in the forecast period. Trackers A tracker is a point you want watched without having to click it every morning. It is a named point with the thresholds that mean "we would send a crew to this address", and the page checks every tracker against the same forecast it draws for the point you picked. The Trackers card sits under the conditions. Each tracker shows its name, its coordinates and a verdict for right now: Recommend dispatch with the reason (Temperature is -3 °C, Snowfall reaches 1.2 cm/h, Precipitation reaches 4 mm, Wind reaches 12 m/s, Freezing point crossed at 22:40) or No dispatch needed with No threshold reached. While the weather is being fetched it reads Checking the weather…; if a point cannot be read, Weather could not be read for this point. Tracker pins are drawn on the map as well. With none yet, the card says No trackers yet. Pick a point on the map and add one. Add a tracker 1. Pick the point on the map or through the search box. The card tells you which point a new tracker will take: The new tracker will use the point you picked. 2. Press + New tracker. The popup opens with Name, the Latitude and Longitude you picked (editable), and an optional Work type. 3. Under Thresholds, fill in only what matters at this point. Any one of them is enough to recommend a dispatch: - Temperature at or below (°C), read at the current hour. - Snowfall at or above (cm/h), Precipitation at or above (mm) and Wind at or above (m/s), read over the coming Look ahead hours (12 by default). - Freezing point crossed within N hours, using the same crossing time as the Freezing point card. Saving with no threshold at all is refused: Set at least one threshold. Without one the tracker can never recommend anything. 4. Leave Active on. An inactive tracker stays in the list, marked Inactive, and never recommends anything, which is how you park a point for the summer without deleting it. 5. Notifications: you can tick Notify me and choose In app, Push or Email, but as the popup says, Your choice is saved with the tracker, but nothing is sent yet. The verdict only shows on this page for now. The checks run in a fixed order: temperature now, then snowfall, precipitation and wind within the look-ahead window, then the freezing crossing. The first threshold reached is the reason you see. Times are local to the tracker's own point. Edit a tracker with the pencil on its row. The bin removes it after This point will no longer be watched. The tracker and its thresholds are removed. Trackers belong to your business; a subcontractor does not see yours. The footer shows when the numbers were fetched (Updated {0}). The data comes from Open-Meteo, and the times are local to the point you picked, not to your browser. To act on what you see, go to Create a dispatch. See also - Create a dispatch - Address, route, zone, auto or manual: which dispatch? - Draw a zone

Last updated on Sep 13, 2026

Download the driving documentation for a stop

When a customer, or their insurer, asks whether an address was serviced on a given night, the answer is one PDF per stop: the Insurance report (in Danish, Kørselsdokumentation). It is built on demand from what the platform recorded, and it exists only for a stop that is Completed. Steps 1. Open the dispatch from Dispatch list and click the address on the Addresses tab. The stop panel opens. A stop's pin on the Live map opens the same panel. 2. Scroll to Actions and press Insurance report. 3. The PDF downloads, named insurance-report-.pdf. The button is shown on a completed stop only. A stop that is still open, or that ended Unable, has nothing to certify; the server answers An insurance report can only be generated for a completed stop. Any business that can open the dispatch can download the report, not only its owner, so a subcontractor can document its own stop on the owner's dispatch. What the report contains - Service provider: your business, with its logo if one is uploaded. Client: the customer and the address. - Operation details: Work type (with any extra work types added to the visit after it, for example Saltning + Grusning, see Extra work types on a stop), Work started and Work completed (the stop's check-in and check-out, in your business's time zone), Duration, and the Driver names taken from the GPS visits. When a Snow depth was recorded for the stop or its dispatch, it is printed here too, in the business's own unit (see Pricing by snow depth); a stop without one leaves the line out rather than printing a dash. If nothing recorded when the work started, Work started and Duration are left out rather than printed empty, and the report keeps the rest. - GPS trail & marked area: a satellite image of the address with everything drawn on it and the Driver route, with start and end pins. Every shape the address carries is on the picture in its drawing tool's own colour (see Draw the areas to clear): areas as filled outlines, lines as strokes, points as markers. The names under the map are the drawing tools they were drawn with. The route is what the vehicle did at this address: the positions recorded between arriving in the marked area and leaving it, the same line the stop panel's own map draws. The rest of the round is not on it, because the report certifies one address. A stop with no GPS at all, no visit and no recorded position, has no map section: the report is the same document without it. - Photo documentation: up to two of the stop's photos, each with Photo taken: {0}. - Verified by SnowManager: SnowManager certifies that the data in this report (timestamps, GPS trail and photo documentation) was recorded automatically by the SnowManager platform and has not been altered. with a Certificate ID and a Data fingerprint. A stop completed from the web had its times typed in by a person, and the report says so rather than claim otherwise. Its completion line reads Work completed (registered manually by name**)**, or Work completed (registered manually) when no name is on record, and the certificate adds The times were entered manually and not recorded automatically; the GPS trail and photos were recorded by SnowManager. The fingerprint is not affected, so a report downloaded before this wording still verifies. Keeping the duration out of it Some customers should see that the work was done, not how long it took. Under Settings → Customer invoice, the Insurance report card has one switch, Hide start times and duration on the report. With it on, every report your business generates from then on shows Work completed only: Work started, Duration and the Photo taken stamps under the photos are left out. Nothing else changes, and nothing recorded is touched; the switch decides what is printed, not what is kept. It applies to every stop and every download, so switch it back off before generating a report that must show the full timing. See Invoice settings. Certificate and fingerprint The fingerprint is computed from the stop's times, its GPS visits and trail, and its photos. Generate the report again from the same data and you get the same fingerprint; add a photo or change a time and it changes. The certificate ID is issued the first time a report is made for the stop and is kept from then on, so every download for that stop carries the same ID while the fingerprint tells whether the data behind two copies is the same. A report printed with the start times hidden verifies against the same certificate as the full one: the fingerprint is taken over the recorded data, before anything is left off the page. Where the times come from, and why they can be trusted, is in How GPS check-in and check-out work. See also - How GPS check-in and check-out work - Draw the areas to clear - What a customer sees in the portal - Invoice settings

Last updated on Sep 16, 2026

Register work that was already done

A manual dispatch is not a dispatch at all: it registers routes that were driven earlier, so the work is on record and invoiced. The app's own warning: Should always be used with caution and is only enabled for authorized users. It needs its own permission, so most staff never see the entry. Steps 1. Press Create dispatch and choose Manual dispatch. The form opens with Add dispatch at the top and Added dispatches below. The manual dispatch form 2. In Add dispatch, pick one or more routes under Select route, the Made on date and time, and the Work type, then press Add. The line appears in Added dispatches. The composer keeps its values, so for a whole season you change the date and press Add again. A Snow depth field sits beside them for businesses that record one (imperial units, or a work type priced by snow depth); the line's depth is frozen the moment it lands, because its stops close at once, and a depth-tiered address bills the tier it falls in, see Pricing by snow depth. 3. Add as many lines as you need. Each line can still be edited in the table, or deleted. 4. Press Create dispatch and invoices. Confirm manual dispatch lists every line; press Confirm and dispatch. The moment must be in the past: Manual dispatch requires a past date. It is judged on your business's clock, not the computer's: the calendar stops at your business's today, and Now beside the time fills in the current minute. A time up to five minutes ahead still counts as now, so a clock that runs slightly fast does not refuse it. Closing the form with lines in it asks Are you sure? with Discard all or Keep. The Hourly tag A route in the picker can carry an Hourly tag: at least one address on it is priced by the hour for the chosen work type. A registration is one moment, so such an address is checked in and out at the same instant and bills zero hours; its invoice line carries the note Hourly duration is missing or invalid for this location. What happens For every line one registration is created, closed and billed, in that order: 1. The addresses of the chosen routes become stops, each stamped with its customer as of now. The service rules run first, so an address excluded that day is removed and never billed, see Why an address was left out. 2. The stops left standing are marked completed, with both check-in and check-out at the Made on time, in your name. 3. Invoices are generated at once, as after a normal completion. In the list the row reads Manually registered in place of worked time, and the Manual dispatches only filter finds them. A line that could not be closed is left open and is not billed; complete it by hand like any other dispatch. Nobody is told No invitation, bell or push goes to subcontractors or drivers, and customers hear nothing: the work is weeks old, and announcing it would announce a job nobody can still go and do. A manual registration is also never merged with a running dispatch, see Why your dispatch was merged into another. See also - Address, route, zone, auto or manual: which dispatch? - Who is told what - When an invoice line is created - Why your dispatch was merged into another

Last updated on Sep 16, 2026

Moving an address to another customer

An address can change hands mid-season: the property is sold, a housing association splits, a management company takes over. Open the address from Locations, change its Customer and save. What that does to dispatches is governed by one rule. The stamp Every stop is stamped with the customer of its address at the moment the stop is created: when the dispatch is created, when addresses are added to it later, and when work is registered manually. From then on the stop belongs to that customer, whatever happens to the address. What a move does When you move an address to another customer: - Stops that are Not started or In progress follow the address to the new customer. Work still to be done belongs to whoever holds the property now. - Stops that are Completed, Unable, Removed or Cancelled keep their stamp. Work already done stays with the customer who ordered it. So the night before the move is still the old customer's night: it shows in their portal, their reports and their history, and the invoice for finished but not yet invoiced work goes to them, not to the new owner. Tomorrow's planned dispatch, and tonight's stop a driver is still at, go to the new customer. What it means in practice - Moving an address never rewrites dispatch history. The customer portal shows each customer the dispatches that were theirs, see What a customer sees. - Finished, uninvoiced work is billed to the customer who ordered it. If the price changes with the new customer, that applies to work dispatched from now on, see which price applies. - Work recorded before this rule existed carries no stamp and follows the address, so old dispatches show under today's customer. - A stamped customer that is later deleted leaves the stop pointing at nobody: it bills nothing, rather than billing whoever holds the address now. Check such stops before invoicing. The stamp is not shown on the stop; you see its effect in the portal, the reports and the invoice drafts. See also - Add an address - Which price ends up on the line - What a customer sees in the portal - When an invoice line is created

Last updated on Aug 22, 2026

What a decline does

When another business dispatches addresses you service, each of your stops carries an assignment that is pending until you answer. Declining is the answer "not us, not this time". How to press the buttons is in Accept or decline a dispatch invitation; this article is what the decline does underneath. Scope You can decline one stop (from the stop itself), the routes you tick in the banner, or the whole slice still waiting for an answer. A reason is required each time, up to 500 characters; the server refuses a decline without one, whichever client sent it. Two details of scope are worth knowing: - A slice-wide decline touches only stops that are still pending. Stops you already accepted are never backed out of by declining; hand those back one by one. - If two of your routes cover the same address and you decline only one of them, the stop stays yours through the route you kept. Decline both in the same answer and the stop is declined. What it changes - Your business is no longer responsible for those stops. They fall back to the owner, who sees Declined on each stop and on the route header (no progress bar, no driver badge), and on a zone dispatch a Denied pill beside your name. Your reason shows when they hover. - Nothing is ever billed or settled toward you for a declined stop: no customer line in your name, no subcontractor line in either direction. - A stop that every assigned business declined, and that nobody started, is denied and untaken. It does not block the owner from completing the dispatch, it stays unbilled, it is not a missing driver, and it still reads Declined after the rest is completed. - The owner's business gets a bell notification, {0} declined {1}, with your reason as its text, and its administrators a push. The changelog records the answer, the scope and the reason. Reversible A decline is not final. Accepting the same stops again re-takes them and retires the reason; the banner offers exactly that once the rest of your slice is answered. Re-declining a route with a new reason replaces the old one. Once the owner cancels the dispatch, there is nothing left to answer. The owner's side The owner can also record an answer on your behalf, for example after a phone call, from the stop's subcontractor status; that marks it Denied. Same effect, same reason requirement. What the owner sees and hears is in Who is told what. On a zone dispatch the owner can do it for your whole pending slice at once: your Awaiting response pill opens Accept on their behalf / Decline on their behalf. A decline done that way is the same decline described above, with the owner's reason instead of yours, applied only to the addresses you had not answered yet; your administrators are told, with the reason. See When the owner answers for you. See also - Accept or decline a dispatch invitation - Who is told what - Complete a dispatch and create the invoices - When an invoice line is created

Last updated on Sep 01, 2026

How GPS check-in and check-out work

While a driver runs a dispatch, the app sends the phone's positions to the server, which works out arrivals and departures from those positions and the address. The zone Each stop has a geozone: the union of the drawn areas on the address, see Draw the areas to clear, each with 15 metres of tolerance outside it. The tolerance is there because the vehicle sits at the edge of what it clears as often as in the middle of it, at the mouth of a drive or in the bay beside a yard, and a phone on a dashboard is accurate to about ten metres. It is not drawn anywhere; the map shows the area exactly as it was drawn. A drawn line counts too: a curb or a path drawn with the line tool has no area, so the phone is at the stop when it is within 20 metres of any part of the line, a lane's width plus the usual GPS error. That band is not drawn anywhere; the map shows the line as it was drawn. An address with no drawing at all uses a circle of 40 metres around its pin, enough for a villa frontage plus the usual GPS error, too small for a business park. Points drawn on the map do not count. An address with neither drawing nor pin cannot be checked in by GPS at all. A visit - A position inside the zone opens a visit, or extends the one that is open. - A position outside changes nothing on its own. The visit ends only once the driver has been outside for five minutes without a break, and it ends at the last position inside, not five minutes later. - A return after five or more minutes away is a new visit. - Positions the phone itself reports as worse than 75 metres are ignored; they can neither open nor close a visit. - Only positions count. A zone narrower than the distance between two positions can be driven through unseen, and a parked vehicle sends nothing. The stop's times - Check-in is the first arrival by any driver. It is written only when the stop has no check-in yet, so a time the driver entered by hand is never moved. - Check-out is the end of the latest finished visit. It only moves later, never earlier; a manual check-out further ahead stands. - Leaving the zone finishes the stop: when the visit closes, the stop is marked Completed under the same conditions as a manual check-out (a check-in if the address is priced hourly, a photo if the address requires one). If a condition is missing, the times are kept and the stop stays open for the driver to settle. - Unless the route says not to. With Location completion by GPS switched off on the route, see the settings of a route, leaving the zone still records the arrival and the departure but never completes the stop: the driver marks each one done. Routes are switched on by default, and the driver app shows a note on a route that is not. - A stop that is Completed, Unable, Removed or Cancelled is never rewritten. Driving past afterwards is not a return. Completing a stop from inside the zone closes the visit at the last position inside. Hourly work is billed on check-out minus check-in, see which price applies. On the web, check-in and check-out can be edited while the stop is open, not once it is completed or unable. Where you see it The stop panel shows it all under Drive at the address: the zone, the drive inside it, and a Visit timeline with Arrived and Left per driver. The bar under it is the record of the address: coloured where somebody was inside the zone, grey for the time nobody was. A stop worked in two passes has a gap in the middle. The same trail is what the insurance report prints. Under the map the ground itself is listed, one line per drawing tool, in the colour it was drawn in: an area with its size, a line with its length, a point tool with how many pins it has. It is the same measurement the address carries, so the stop panel and the address never quote two different figures for the same ground; see Draw the areas to clear. Still inside is only said while the phone is actually reporting from the zone. If it stops sending, the line reads Last seen 12:17 instead, because that is the last moment anybody knows they were there. A stop that was settled without the GPS ever seeing it, because an office user completed it or the driver never had the app reporting, says No GPS recorded instead of an arrival and a departure. It is not the same as Not started, which is kept for work that genuinely has not begun. A visit registered with a departure and no arrival names the time it does have rather than hiding it. A visit that never ended A visit ends when the phone reports from outside the zone. A driver who drives away is closed automatically five minutes later, whether or not the app is still open. A phone that dies on the property is different: nothing more is coming, and the system will not guess a departure, because silence there can just as easily be a plow still working. Such a visit stays open, and while it does the stop has no check-out and its hours cannot be counted. There are two ways it ends: - Close it yourself. On the visit's line, press Set departure, enter when the crew actually left, and save. It settles exactly as it would have if the phone had reported the departure itself. Only while the dispatch is open, and only for the business responsible for the stop. - Complete the dispatch. Marking the run completed closes any visit still open, each at the last moment its driver was recorded inside the zone. Completing is you saying the work is over, so nobody is left on an address; the time is not invented, it is the last one on record. See also - Draw the areas to clear - Download the driving documentation for a stop - Which price ends up on the line - Route settings

Last updated on Aug 30, 2026

Who is told what

SnowManager tells people about a dispatch in two ways: a bell notification in the web app (the Notifications list, see The notification bell) and a push to the phone of anyone signed in to the app. Bell notifications belong to a business: you see them in the business you are working in. What is sent, and to whom, depends on the event. When a dispatch is created Every business invited to it (a subcontractor holding addresses on it, by zone, by route or one by one) gets one bell notification, {0} has invited you to a dispatch, and each of its administrators a push: New dispatch invitation, {0} has invited you to a dispatch. Open the app to respond. That is the whole alert; the invitation itself is answered on the dispatch, see Accept or decline a dispatch invitation. Your own drivers on the dispatch get a bell notification, You have been assigned to a dispatch, and a push: New dispatch, You have stops assigned to you on a new dispatch. Only your own: a stop you handed to a subcontractor belongs to that business, and its drivers hear about it when it accepts. Stops a service rule left out alert nobody, because the alert is sent after the rules have run. A driver who creates a dispatch from the app gets a confirmation push for it instead. When a driver is put on a stop afterwards That one driver gets the same bell notification and push, for that one stop. Nobody else on the dispatch is told again. See Put drivers on a dispatched route. When addresses are added to a running dispatch Any business invited by the new addresses, and still owing an answer, gets the same invitation alert it would have got at creation. A business that has already answered is not asked twice. See Add addresses to a running dispatch. When an invitation is accepted Each driver of the accepting business on the accepted stops gets a bell notification, You have been assigned to a dispatch, and a push: New dispatch, Your business accepted a dispatch with stops assigned to you. The same goes out when the owner records the acceptance on the subcontractor's behalf. When an invitation is declined The owner's business gets a bell notification, {0} declined {1}, with the reason as its text, and its administrators a push: Dispatch declined, {0} declined {1}. Reason: {2}. See What a decline does. When the owner answers for a contractor When the owner presses a contractor's Awaiting response pill on a zone dispatch and answers in its name, the contractor's business gets a bell notification, {0} accepted {1} on your behalf or {0} declined {1} on your behalf, with the owner's reason as its text when it was a decline, and its administrators a push: Invitation answered for you. A forced accept also sends the contractor's drivers the same You have been assigned to a dispatch alert an ordinary accept sends. The owner hears nothing: they did it. See When the owner answers for you. When a driver marks a stop unable When a driver marks a stop Unable from the app, an e-mail goes to the address saved under Settings → Business, Email on error (see Set up your business). Two businesses can get one: - the business that dispatched, and - the subcontractor responsible for the stop, when that is another business that has accepted it. Each gets its own mail, in its own language, with the time the stop was marked in its own time zone, date order and clock. The subject reads Address could not be done: and the address; the mail names the dispatch code and planned date, the route, the work type, the driver and their company, The driver's note, how many photos the stop has, and carries a link that opens the dispatch. Names follow the usual rules of who may know whom, and the customer is named only to a business that holds the address for a customer. A business with no address saved, or an address that is not a valid e-mail, gets nothing; when both businesses saved the same address it is mailed once. The mail goes out once per unable registration, after it has been saved. A double tap, or an offline retry of a stop that is already unable, sends nothing more, and a mail that fails is logged without stopping the driver. Marking a stop unable from the web sends no mail: that is the office acting, and it already knows. Nothing is sent for - Cancelling a dispatch, see Cancel a dispatch. - A manual registration of work already done, on purpose: it would announce a job nobody can still go and do. - Completing a dispatch or a stop. The job-completed and job-incomplete message templates under Settings can be edited, but nothing sends them today. - Customers. The portal shows them their dispatches; it does not alert them. E-mail and SMS Apart from the Email on error mail above, no dispatch event produces an e-mail, and none produces a text message. SMS is used for sign-in codes only. If a subcontractor has nobody signed in to the app and nobody watching the bell, the invitation waits unseen; a phone call is still the only way to know it was read. The other operational event that goes by e-mail is a new complaint, to the colleagues each business picks for it; see Get an e-mail when a complaint is created. See also - The notification bell - Accept or decline a dispatch invitation - What a decline does - Cancel a dispatch - Add drivers to an existing dispatch - Add addresses to a running dispatch - Get an e-mail when a complaint is created

Last updated on Sep 16, 2026

Add drivers to an existing dispatch

A route carries its drivers, so a route dispatch normally needs no driver work at all: the people on the route are attached to every stop the moment the dispatch goes out, or, on a route you were invited to, the moment you accept. An address dispatch gets the drivers you pick when you create it, plus the crew of any route of the responsible business that the address is on. This article is for the cases in between: a driver is ill, an address went out with nobody on it, or a plow needs help. You can also choose the crew as you dispatch, per route, without touching the route itself: see dispatch a route. Where the crew shows On a route dispatch, each dispatched route has a row above the stop list with a badge showing how many drivers are on it (their names on hover), or a red No drivers assigned to route when it has none. The badge opens Invite drivers for that route: adding somebody puts them on every stop of it that is yours to crew, and removing them takes them off. A zone dispatch lists your routes under each zone with the same badge; the zone itself has none, see On a zone dispatch below. What the panel also shows is the gap. The dispatch list flags it first, as Missing driver in the error banner (see finding dispatches and reading the error banner), and the open dispatch repeats it as a red line with an Assign button. Add a driver to a stop that has none The Assign line on a dispatch with an uncrewed stop 1. On the All tab, a red line No drivers are assigned to this dispatch sits above the stops as long as one of the stops you are responsible for has nobody on it. Press Assign. 2. Invite drivers opens for the first such stop; its address and business are in the header. Search by name or e-mail and press Add beside a person. Every press saves at once (Driver added successfully), and the counter next to the search box reads how many are added. 3. Press Close when the list is right. The red line goes away once every stop has someone; if another stop is still empty, press Assign again and it opens that one. The Invite drivers popup for one stop The popup covers one stop. When one route visits the address, the driver is attached to that route's pass; an address that two dispatched routes share (see when two routes cover the same address) gets the driver for both passes. On a zone dispatch Drivers are added to routes, never to a zone. A zone dispatch groups the stops by zone, and inside a zone by the business responsible for them. Under your own business, every route you crew that has stops of yours in the zone is listed by name with its number of addresses and a driver pill of its own: a red No drivers while nobody is on the route, otherwise a dark count (hover for the names). Press it to open Invite drivers for that route. Add puts the driver on the route's active stops in that zone that you are responsible for; someone already on a few of them still shows Add so the rest can be covered, and Remove takes them off all of them. The zone header carries no driver pill. A route is yours to crew when you own it and have not handed it to a subcontractor, or when a business handed it to you. A subcontractor's routes never get the pill in your view: who drives them is the subcontractor's decision. A subcontractor sees its own slice grouped by route, and there too the pill appears only on the routes it crews itself, never on a route that belongs to another business. The server holds the same line: a driver added to a route that is not on the dispatch, or not yours to crew, is refused. The route pill is also the only way, on this version, to change a crew that is already complete. On a route or address dispatch the Assign line shows only while a stop is empty, so a fully crewed route cannot take a third driver, or swap one, from the web. Change the crew on the route itself before the next dispatch instead (see drivers on a route). Answering for a driver Above the search box, Assigned drivers lists who is on the stop (or route) with Accept, Decline and Remove. A driver starts as pending; when you know their answer, press Accept or Decline and the row reads Accepted or Denied. For a route with mixed answers the row stays pending until they agree. The answer is your record of who is coming; nothing waits for it, and a driver on the stop can check in whether or not it has been given. Who may do it Staffing a stop belongs to the business responsible for it: the subcontractor it is assigned to, once they have accepted, and otherwise you as the dispatch owner. While a subcontractor's invitation is unanswered the stop is view-only for everyone, and a declined assignment hands the stop back to you. The server refuses anyone else, and refuses every change on a cancelled dispatch or a removed stop. Who is offered Everyone on the responsible business's own staff: administrators, drivers, dispatchers and support users, never a customer login. The server then insists the person is active in that business. Someone you invited who has not set a password yet is refused when you press Add, and so is a user another business shared with you: Share profile with contractors lends a driver to a route, not to a dispatch (see sharing a user). Removing a driver Remove takes the driver off the stop, or off every stop of the route, on this dispatch only; the route keeps them for next time. Stops they already completed stay completed, with their name on them. What the driver is told A driver you add gets a bell notification and a push on their phone saying they have been put on the dispatch, the same alert your own drivers get when a dispatch is created; it appears under Invitations in their app for them to accept (see who is told what). Removing a driver tells them nothing; the dispatch simply leaves their phone. There is no e-mail or SMS either way. Every addition and removal is written to the dispatch's Timeline. See also - Drivers on a route - Accept or decline a dispatch invitation - Who is told what - Find dispatches and fix the error chips

Last updated on Sep 16, 2026

Complete a dispatch and create the invoices

Drivers close stops; you close the dispatch. Nothing is invoiced until you do, and nothing is invoiced automatically just because the last driver pressed "done". The invoicing section of a dispatch When it can be completed Every stop in your part of the dispatch must be finished (Completed, Unable, Removed or Cancelled), and at least one must be Completed. A completed stop needs a check-out time; an hourly-priced one also a check-in. An address that requires a photo holds the driver to it, but an office user may complete the stop from the web without one, and the timeline says so. Stops that are still Not started or In progress hold the dispatch open; close them from the stop panel (see Complete, mark unable, remove or restore a stop) or remove them. An address two routes cover stays In progress until each of its passes has been closed, by its crew or from the web with Complete pass. While something holds the dispatch open, the message beside the button names what is in the way, up to three addresses and a count for the rest: These addresses must be completed, marked unable or removed from the dispatch before it can be completed: or These completed addresses are missing a check-out time (or a check-in time when billed by the hour):. A stop nobody started, which every business it was assigned to declined, does not hold the dispatch open. A stop you cannot close yourself, because the subcontractor it was assigned to has not taken it, still has Remove from dispatch on its panel for you, which is the way past it. Complete it 1. Open the dispatch from Dispatch list. 2. Check the Details tab: every route shows its count of finished stops. 3. Press Mark as complete. The dispatch is now Completed; its stops are frozen. It stays on the Live map for the rest of the day it worked, marked done, and is on that day's record after. If the dispatch carries a Snow depth, the confirmation shows it and, for the owner, lets it be corrected one last time: completing freezes the depth along with the stops, and a depth-priced address bills the tier the frozen depth falls in. A depth found to be wrong later is fixed on the draft invoice lines, never by reopening the dispatch. See Pricing by snow depth. Create the invoices Under Invoicing, the dispatch tells you where the money stands: - The work on your addresses is done. Confirm to create the invoice drafts for your customers. Press Confirm & create invoices. One draft line per completed address appears on the customer's invoice for the month. - Confirm each subcontractor's finished work to create the invoice drafts. You don't have to wait for the whole dispatch. Each subcontractor's slice can be confirmed on its own as soon as that subcontractor is done. A slow contractor never holds up the others' invoices. - Your completed work is invoiced by each business below once they confirm it. You are the subcontractor here: the owner of the addresses confirms, and your settlement line appears when they do. Confirming the same work twice does nothing; the system remembers which stops it has already drafted. From the phone Both steps are on the driver app too, for administrators of the business that owns the dispatch. Open the dispatch, and below the driving actions: Complete dispatch closes the run, and an Invoicing section lists the same per-business rows with Confirm and create invoices. The rules do not change with the screen: a subcontractor's administrator never sees Complete dispatch (the run is not theirs to close), and a dispatch not ready to complete says what is still missing rather than closing. See drive a dispatch, stop by stop for what drivers get instead. What gets a line, and what does not - Only Completed stops are invoiced. Unable, removed and cancelled stops bill nothing. - A stop with no price on the address for this work type is skipped (not a zero line) and stays available to bill later, once a price exists. - A test dispatch is kept apart from real ones in the list and bills nothing on either side. - An address dispatch bills the sides its Who should be invoiced? choice named at creation, or was changed to later from its Details tab; route, zone and manual dispatches always bill both. See Who is invoiced for an address dispatch. - Changing the Work type of a dispatch after invoicing rewrites the draft lines, and is refused once an invoice has been sent (the warning says so). If something is wrong after completion A completed dispatch's stops cannot be changed. Cancel is no longer possible either: cancelling is for open work. Fix the money on the invoice instead: lines can be edited, added or archived while the invoice is a draft. See also - When an invoice line is created - Review and send a customer invoice - Who is invoiced for an address dispatch

Last updated on Sep 17, 2026

Follow a dispatch live

Once a dispatch is out, two views follow it: the Live map for everything your company has out today, and the dispatch's own details for one job at a time. The Live map Open Dispatch → Live map in the left menu. The map opens on today, by your company's own date: every run that was planned for today or did any work today, the finished ones included, with the drivers' last positions and speed on the map. The view refreshes itself every fifteen seconds. On a road route the driven part of the route is drawn over the planned one, so you can see how far a plow has got. A dispatch left open from an earlier day is not on today's map unless somebody works it today; pick its day to see it. The panel on the left is today's work sorted the way you would ask about it: - Zone first, when anything went out on a zone dispatch, with the zone's own colour. - Then the company doing the work, your own company first and then each subcontractor. - Then that company's routes. Addresses no route covers, a single-address dispatch or a zone address none of the crew's routes reach, share one Unrouted row. - Then the addresses, each with its status (Not started, In progress, Completed, Unable) and its check-in and check-out. When nothing went out on a zone, the panel starts at the companies. When part of the day did and part did not, the rest gathers under Not in a zone at the bottom. A zone crew's route that crosses two zones appears under both, each time with only the addresses in that zone. Every row shows how much is done, as a count of addresses or, for a road route, as a percentage, and the drivers on it as coloured dots: green is reporting now, amber has gone quiet for a few minutes, grey has not reported for ten. Click a row to move the map to it. The arrow opens and closes it. The eye, Hide from map / Show on map, takes that row and everything under it off the map without closing anything; hiding a zone hides only that zone's addresses, even on a route that crosses into another. Each address is drawn with the areas and lines drawn on it. An address with nothing drawn shows the circle its GPS check-in is measured by instead, so you can see where a driver has to be for the arrival to count. Zoomed out, addresses that sit close together are gathered into one bubble carrying the number of them, in the colour most of them have, so a storm-sized night is a handful of counts instead of a wall of pins. Click a bubble to zoom to what is inside it, and zoom in far enough and every address is its own pin again. Drivers are never gathered up: where the crews are is the question the map is open for. Before anything has gone out today, the page says Nothing has run today yet. A subcontractor is not shown its customer's zones, so a subcontractor's panel starts at the companies. The Live map Watch a day again The panel is titled Today, with today's date under it. Click the date: the calendar marks the days that have a run behind them, and the unmarked days cannot be picked. Today can always be picked, and picking it is the live map. Choose an earlier day and the map becomes that day's record: it stops refreshing, and the timeline scrubber runs over that day's work. Back to today returns to the live map. Two things about which day a run belongs to: - A run counts for the day it was planned for and for every day it actually worked. A route dispatched at 23:00 and finished at 04:00 is marked on both dates. - Whichever of the two you pick, you get the whole run. Nothing is cut off at midnight, and the scrubber runs from the first thing that happened to the last, not to the end of the date you clicked. Days are your company's own dates. A dispatch is dated by the clock your business runs on, not by the browser's or the server's, so a night shift reads the same for everyone in the office. A dispatch's details Open Dispatch → Dispatch list and click the dispatch. The slider that opens is the control room for that job. Its title is the route or the address; a dispatch over several routes is titled by the route that was put on it first, with +1, +2 and so on for the others, and a dispatch with neither reads Dispatch and its code. Under the title sits ID and the run's six-character code, which is what the run is called on the phone, in the changelog and in a message to your subcontractor about it. A dispatch opened from the list - Details lists the routes and addresses with a status per stop (Not started, In progress, Completed, Unable, Removed, Cancelled) and a progress count per route and per contractor. Expand All / Collapse all folds the routes; on a zone dispatch the stop Filter sits right beside it. Once a crew has been out, the addresses are listed in the order the work was actually done rather than the order you planned it: a driver who starts at the fourth address puts that address at the top. Addresses nobody has reached yet keep their planned order and sit at the end, so a run reads top to bottom as the night went. Until the first check-in there is nothing to reorder and the list is your plan exactly as you built it, which is also the only time you can drag an address to a new place in it. - Map draws the whole run on one map, on every kind of dispatch: the addresses with the ground drawn at each of them, the paint of any road route with the part actually driven over it, and every driver's trail from their first recorded position to their last. A run whose crew reported no positions at all, an imported season or a round worked off paper, is drawn as the order the addresses were taken in, one line per route. Click an address pin for the stop's route, its status, its check-in and check-out, the note the crew left and its newest photo, and to open the stop itself. The switches at the top left turn the addresses, the drawings, the routes, the trails and the driver pins on and off, one at a time or all at once, which is how you get a fifty-stop night down to the one thing you are looking for. Drag the scrubber under the map to wind the run back to any moment. The map's own buttons zoom, reset north, switch to satellite and open it fullscreen, and addresses gather into counted bubbles while the map is zoomed out, exactly as they do on the Live map. A dispatch that is over loads once and stays put; one still running refreshes itself. You see on that map exactly what you see in the stop list: your own addresses, the routes you were given, and the drivers you work with. - Timeline is the dispatch's history: created, invited, accepted, declined, stops added or removed, completed, who did it and when. Every entry is written in your language and names the address, route or driver it is about, including a stop an office user completed without the photo the address requires, which reads photo required, none provided. - Photos gathers every photo the drivers took, by address. - There is no crew list on the panel: who is on a stop shows inside Invite drivers, reached from the Assign line or a route badge, see adding drivers to an existing dispatch. - Message is what the drivers were told; Internal comment is yours alone. A zone dispatch adds a pill beside each contractor (Awaiting response, Accepted or Denied) until their work is under way. The visit timeline of one address Click a stop to open it. Beside the check-in and check-out times, the Visit timeline shows what the driver's GPS recorded at that address: Arrived, Left and, while the driver is there, Still inside. The times come from the address's drawn area (or a 40-metre circle around its pin when nothing is drawn) and are how check-in and check-out get filled in when the driver does not press anything; see How GPS check-in and check-out work. Who can follow what You see a dispatch if you created it, if your business is assigned a stop on it, or if it works addresses you own. A subcontractor sees only its own part; the owner sees the whole thing. The names on the run reach you one link at a time: a company you have no dealings with is reported as the counterparty you handed the work to, see owner, subcontractor, sub-subcontractor. See also - How GPS check-in and check-out work - Who sees a dispatch

Last updated on Sep 17, 2026

Who is invoiced for an address dispatch

A completed stop normally produces two kinds of invoice line: one toward the customer who owns the address, and a settlement toward the subcontractor who did the work (see When an invoice line is created). Sometimes only one of them is wanted. A goodwill visit after a complaint should pay the subcontractor and cost the customer nothing; a job the customer ordered and your own crew drove has no subcontractor to settle; a check-up drive should not bill anybody. On an address dispatch you say so when you create it. The choice On the Address dispatch form, above Dispatch now: - Should be invoiced is on by default. Switch it off and the dispatch is not invoiced at all, on either side. The stops are still driven, recorded and completed as usual. - While it is on, Who should be invoiced? offers three answers: - Customer and subcontractor, the default: exactly what every dispatch did before. - Customer only: the customer line is drafted; no settlement line is drafted toward any subcontractor on the chain. - Subcontractor only: the settlement lines are drafted; the customer is not billed. A dispatch sent from a complaint starts on a different default, set by Carried out by: when the business held responsible for the complaint redoes the work, Should be invoiced is switched off, because the customer paid for that work once already and the supplier is not paid twice for it. When anybody else redoes it (another subcontractor, or your own crew), the answer is Subcontractor only: whoever redid it is paid and the customer is not billed again. Changing Carried out by resets the default; you can still change the answer yourself afterwards. Such a dispatch is always created as a dispatch of its own and never joined to a running one, so its answer is not replaced by that dispatch's. See How a complaint is assessed, timed and settled. The summary before Confirm and dispatch repeats the answer. Afterwards the dispatch's Details tab shows the same switch and dropdown to the business that created the dispatch, and a change there is saved at once. What it changes, and when The choice is applied at the moment lines are drafted, which is when a business presses Confirm & create invoices (or when a retroactive-billing offer is accepted). It never overrides the other rules: only Completed stops bill, a stop with no price is skipped, a declined business is never settled, a per-season address still bills in instalments. The scope only decides which of the two sides the generator is allowed to draft. Changing the scope on a dispatch that was already confirmed does not undo anything. Lines that exist stay on their drafts until you archive them; the new scope governs whatever is drafted from then on, and a side you have just switched on becomes billable at the next confirmation. Bill completed work? (the offer that appears when an address gets a price) follows the same rule: a customer-only dispatch is never offered for a missing settlement line, a subcontractor-only one never for a missing customer line, and a dispatch that should not be invoiced is not offered at all. See Bill completed work that had no price. Which dispatches have it Only address dispatches. A route, zone or manual dispatch always bills both sides and shows no choice; if a stop on one of those must not be billed, mark it Unable, remove it, or archive its line on the invoice afterwards. A single-address dispatch created from the phone has a plain Should this be invoiced? switch instead of the three-way choice: on means both sides, off means neither. See Start a dispatch from your phone. A test dispatch bills nothing whatever the scope says. Who decides The business that creates the dispatch. A subcontractor invited to it cannot change the scope on the owner's dispatch; what it can do is settle its own work with its own subcontractors under the owner's choice. When the scope leaves your side out, the dispatch's Invoicing box on the Details tab has nothing to confirm for it, which is the sign to look at the scope before looking for a missing price. See also - Create a dispatch - Complete a dispatch and create the invoices - When an invoice line is created - Invoices to and from subcontractors - Bill completed work that had no price - Mobile: Start a dispatch from your phone

Last updated on Sep 16, 2026