Landscapt (CRM)

Snow Jobs & Storm Dispatch

Storm events, priority dispatch, and the invoicing flow built specifically for snow.

Storm events, not visits

Snow Jobs lives at CRM > Scheduling > Snow Jobs, and everything on that board is organized around a Storm Event — not individual visits. Instead of scheduling each client's plow separately, you create one event for the storm itself, add every client who needs service during it, and dispatch them together in priority order.

A storm event tracks a name, a date, an optional forecast depth, and an optional temperature. It also carries its own status — Pending → Working → Complete — which reflects the storm's actual life cycle: not yet touched, actively being dispatched and pushed, or wrapped up. Switching to another storm clears the board's Client and Date filters, so you never land on an empty list because of a filter set for the previous storm.

Creating a storm event

  1. From the Snow Jobs board, click + New Storm Event.
  2. The name defaults to Snow Event plus today's date — rename it if you want something more specific (e.g. "Feb 3 Nor'easter").
  3. Set the event date. Optionally set a forecast depth (inches) and a temperature — the forecast depth is used later, when adding jobs, to automatically exclude clients whose contract only triggers at a higher depth than this storm is expected to drop.
  4. The event opens on the board with status Pending until you start dispatching.

Adding jobs and setting priority

Click Add Jobs on an open storm event to bring up the candidate list — every client with a snow job, or just the stops on a chosen master route. With no route chosen, the list follows your saved master-route order (route by route, stop by stop), with jobs on no route after them, and each stop picks up its own saved crew (on a shared route) or its route's default crew unless you choose a crew in the dialog. Each candidate shows its trigger depth, its client's priority, and its assigned crew, and the list filters itself with three controls:

  • Max Trigger Inches — defaults to the storm's forecast depth. Any client whose own trigger depth (the snowfall needed before their contract kicks in) is higher than this number is highlighted and excluded by default — this storm isn't deep enough to trigger their service.
  • Min Priority — each client has a priority of High, Normal, or Low. Choosing "High and higher" here narrows the list to just your High-priority accounts; "Low and higher" (the default) includes everyone.
  • Default Crew — applied to any selected job that doesn't already have a crew assigned.

The dialog always opens on the storm you're viewing: Dispatch Date is that storm's date and Max Trigger Inches its forecast. When you change a filter, any row it newly excludes is unticked, so a highlighted row only goes out if you tick it again yourself.

Jobs are also excluded automatically if the dispatch date isn't one of the days their contract authorizes service on. A snow job whose contract has ended (cancelled, expired, inactive or deleted) no longer appears on this board at all, and neither does one whose contract is set to Don't service storms outside its dates when the dispatch date is before the contract's start date or after its end date. Contract dates are always checked against the storm's dispatch date, not today. Everything not excluded is pre-checked; uncheck or check individual rows before clicking Add to Dispatch.

Priority lives on the client, not the storm event — set it once on the client record and every future storm respects it. High-priority clients (hospitals, fire lanes, contracts with tight response-time SLAs) sort first wherever priority matters.

Dispatching, logging pushes, closing out

Once jobs are added, each one becomes a visit row on the board with a status you cycle through by clicking its icon: scheduled → dispatched → in progress → completed → skipped. Use Team Assign to move unassigned visits onto crews — drag a card, tap a card and then tap the crew column it should go to, or click a crew's name on the card for a one-tap assign. Then Dispatch Assigned pushes every crewed, scheduled visit to dispatched at once. Print generates a route sheet per crew with checkboxes for weather and site conditions, full plow, and salt bags, for a paper copy on the truck.

Dispatching a storm from a tablet? Tap-to-place is the one that works there — touch devices don't support the drag gesture, so tap the visit, then tap the crew. The card you picked up is outlined and every crew you can drop it on is highlighted.

The snow dispatch board fits phone widths too: the toolbar scrolls sideways and the controls get bigger tap targets below desktop width, so you can dispatch from a truck.

Snowfall depth is not pulled from a weather feed — it's recorded manually, per visit, when the crew's work is closed out. Select one or more completed visits and click Close Out… to enter the actual depth (in), temperature, and — for hourly-billed jobs — hours on site (the time the crew was at the property, not multiplied by crew size). Close Out writes only what you type: a depth or temperature already recorded on the visit stays if you leave that field blank (a blank used to wipe it, which un-priced Per Inch stops). Salt and other materials aren't entered here: the crew records what they used on each stop (see Salt and materials, per storm). Each visit is its own row with its own depth reading, closed out separately.

Adding a push. When a crew has to go back to a site during a storm (say a 2–4" pass that isn't the final push), each return is its own visit with its own clock-in/out, depth, crew and notes, and a row on the client's timeline — your record of every trip. The office clicks Add push next to the client's name on that job's latest row; the crew can tap Going back? Add another push on a finished stop in the crew app. The new push (Push 2, Push 3…) goes on the same storm with the same crew and men, dated today, and shows on the crew's list as its own stop. Billing follows the job: Per Push and Hourly jobs bill every push; Per Event and Per Event, Per Inch jobs bill the storm once, on the first push. On a Per Event, Per Inch job a return trip is part of the event: a deeper reading on any trip sets the storm's price (the event is priced on the deepest reading across all its visits), and it doesn't bill separately — unless that depth lands in an hourly range, where the return trip's own hours on site bill too (see Rate tiers). On a flat Per Event job, Adding a push asks whether it is No charge (the default — recorded only, $0, never in Snow Invoicing) or Bill it (its own charge, the job's flat rate again — use this when a second crew salts again). A push's Charge / No charge tag can be clicked to flip it until it is invoiced. Pushes the crew adds from the crew app start as No charge. Only one push can be open at a time: if two crews tap Add another push at the same moment, one push is added and the other tablet is told another push is already open (it's on their list).

Two storms on the same day are two trips. If a job is on two storm events dated the same day, the crew app shows each storm as its own stop, so finishing the first trip never completes the second storm's visit.

Times from the crew app. Clock-in and clock-out times, breaks, hours and crew size on a visit are recorded by the crew app's Start Job, Pause, Resume and Stop Job buttons — a crew login can't change them any other way. To correct them, edit the visit from the office (Edit Job Times on the Dispatch Board, or Close Out here).

Skipped and cancelled stops are never closed out: they were called off rather than plowed, so Close Out (and Close Out Selected) leave them alone and nothing is billed for them. Once every visit for the event is closed out, move the storm event's status to Complete.

A Complete storm takes no new stops: Add Jobs and Add push are turned off until you set the storm back to Working. If a visit is added to a Complete storm any other way, the storm moves back to Working on its own, so it never reads as finished with work still to do.

Add Jobs also has a Service filter (alongside the search box) to narrow the list to one service. Actions > Cancel Dispatch puts the selected dispatched stops back to Scheduled; stops the crew has already started are left alone and the message says how many. Actions > Export Stops (CSV) downloads the stops the board is currently showing (after filters) with date, client, service, address, crew, status, depth, temperature, notes and amount. Old storms can be retired from the picker: on the status pill choose Mark storm inactive, and use Show inactive next to the picker to bring them back.

Invoice terms and times. A job's Invoice Terms (on its Invoice Description tab) overrides the client's default terms for invoices made from that job, including Snow Invoicing; leave it on the client's default to follow the client. An invoice that bundles several snow jobs uses the override only when they all agree. A service with Show visit times on snow invoice lines ticked (Settings > Services) adds the visit's clocked start and end, like (7:05 AM – 8:40 AM), to its Snow Invoicing line.

Filters, crews, route order, map, and weather

The Snow Jobs board has the same dark action bar as the Dispatch Board, so a storm can be run from one screen.

  • Status tabs and filters. Tabs for All, Scheduled, Dispatched, In Progress, Completed, Skipped and Cancelled (each with a count), a multi-select crew filter that includes Unassigned, and a search box that matches client, service, address, city, state, zip, notes and crew, plus a Priority filter. Above the dark bar, like the Dispatch Board, is a Select a Filter row: click Client (with a search box), Date, Service, City or Zip and tick the values you want (the pill shows how many are picked). The dark bar also has a Tags filter that shows stops whose client has any of the tags you tick. The buttons at the right of that row are Stats, Map, Optimize (with Nearest / Furthest first), Export and Print. The Legend button at the right of the dark bar explains every icon and tag. The checkbox in the header row (or Select All Shown in Actions) selects every stop the filters currently show, so you can filter to a zip and reassign or dispatch all of it at once. Add Jobs has the same select-all checkbox plus Select all / Unselect all links and a search box that narrows the list (Select all then acts on the jobs shown). For a storm that runs several days, each job in Add Jobs has its own Date (it starts as the dispatch date): tick the jobs for a day, pick the date and click Set date, repeat for the next day, then Add to Dispatch. Authorized-day checks use each job's own date; contract-date checks still use the dispatch date at the top.
  • Storms that run several days. Every stop has its own Date (a column, and a Dates filter). Click a stop's date to move just that stop, or tick several stops and use Move to date in the selection bar (or the map's selection panel). Finished and cancelled stops don't move, and a stop a crew has clocked into can't change day. The crew sees a stop on the day it is scheduled for. Route order is kept per crew per day, so Optimize Routes and the up/down arrows work within one day at a time.
  • Changing crews. The Crew column is a dropdown on every row. To move several stops, tick them and use Assign crew… in the selection bar. To put more than one crew on each selected stop (two trucks on a big lot), use Assign crews…: tick the crews and click Set crews. The first crew you tick is the lead and carries the stop's charge; each extra crew gets its own row (tagged Extra crew) with its own clock-in, hours and depth. Wherever a stop bills time, every crew bills its own hours on site (crew-hours): on Hourly jobs, and on Per Push or Per Event, Per Inch jobs whose depth lands in an hourly range (an extra crew that didn't record a depth uses the lead's). On every other billing type the lead carries the charge and the extra crew is not billed. If an extra crew is doing separate billable work (salt after plowing, another pass), give it its own job, or use Add push on a Per Push job. Crews can be added or removed until a crew starts the stop. A crew can also ask for help itself: Need help? Call in another crew on a stop in the crew app lists the other crews; the one picked gets the stop on its tablet straight away (even after the first crew has clocked in), tagged Extra crew here, with a line on the client's timeline. If a crew can't make it to a stop at all, Can't make it? Hand off to another crew(shown before they start the stop) moves the stop to the crew they pick — onto that crew's tablet and off theirs, same visit and same billing, with a timeline line and a Handed off from … flag on the board. A stop that already has several crews has to be moved by the office. Setting a stop to Unassigned pins it to no crew rather than falling back to the job's crew. A stop shows the crew on its visit, or the job's crew if the visit has none — Team Assign uses the same rule.
  • Route order. The default sort is crew, then day, then stop number, so a crew's stops sit together in route order (Client and Crew sorts keep that order within each value). The # column is each stop's position within its crew's route for that day; the arrows beside it move a stop up or down, and the order is saved. Optimize (next to a Nearest first / Furthest first choice) routes each crew separately by driving time, starting from the crew's own starting address or, failing that, the Company Address in Settings > Organization, and saves the result. With rows selected it routes only those. After optimizing, each row shows the drive time to arrive at it (⌂ from the shop for the first stop, ↑ from the stop above for the rest).
  • Invoiced badge. A stop that is already on an invoice shows a blue Invoiced # badge beside the client name. Click it to open that invoice in a slide-over without leaving the board; close the slide-over to land back where you were. Hover the badge to see the invoice's status.
  • Actions menu. Dispatch Selected (or Dispatch All Assigned when nothing is selected), Close Out Selected, Skip Selected and Cancel Selected, Team Assign, Optimize Routes, Show Crew Stats, Print Route Sheets, and Clear Filters & Selection.
  • Keeping the same order storm to storm. Once you've ordered the stops the way you want them (by hand or with Optimize), choose Actions > Save Order to Master Routes. A job already on a master route is written back to that route, so the next storm's Add Jobs comes up in that sequence. On a shared route (one with no default crew, such as All Plow Jobs or All Salt Jobs) the stops are grouped by crew and each stop remembers the crew it ran under, so you regroup the crews once instead of every storm. On a per-crew route (one with a default crew) the crew's order is written onto it. A job on no route goes to its crew's own route (created and named after the crew if there isn't one), unless your company uses shared routes: then it is left alone until you add it to a route in the Master Routes editor. Stops that weren't on this storm keep their place and crew, and jobs new to the route go on the end (a job is on only one route, so plowing and salting should be separate snow jobs). You can also edit the routes directly with the Master Routesbutton next to New Storm Event (the same editor is in Settings > Services > Snow Routes).
  • Assigning crews: this storm only, or Permanent. Choosing a crew in the selection bar's Assign crew… (or the map panel's Assign to crew…) changes this storm's stops only; next storm they come back on the crew their Master Route has. Tick Permanent beside the picker to also save the crew onto the Master Routes. The picker becomes two steps side by side: first pick the crew, then pick the route to save to. The route list has that crew's own routes plus every shared route (marked (shared), for example All Plow Jobs (shared)), and the assignment is saved when you pick the route. A job already on the route you pick keeps its place, others go on the end, and if the crew has no route yet one is created and named after the crew. Choosing Unassigned with Permanent ticked takes the stops off their crew's Master Route, or just clears the crew on a shared route. Many crews keep one route for plowing and another for salting so a salt-only storm loads only the salt route.
  • Building Master Routes. Click Master Routes on the Snow Jobs board, pick a route (or add one, then set its name, default crew and Active switch). Leave the default crew empty to make a shared route that covers several crews (for example one route for every plow job and one for every salt job); each stop then has its own crew picker. Find jobs for this route searches your snow jobs by client or address, service, zip code(s), and proximity (within 1–25 miles of an address you type or of one of the route's stops), with Not already on a route ticked by default. Tick the results and Add to route; each result shows the client's priority (high, normal or low), address, zip and service. A job can be on only one route. Snow jobs added since the routes were built, which are on no route yet, are listed at the top with a NEW flag so you can slot them in. Order the stops by dragging, by typing a position number, or with the arrows. Group Stops orders every stop by driving time from the crew's shop (or the Company Address); Optimize Route keeps stop 1 and routes onward from it. The Map button previews the route.
  • Skip and cancel with a reason. Skipping or cancelling asks for a reason — No snow at this site, Client cancelled, Equipment down, Site inaccessible, or your own. It is saved on the visit and shown on the client's timeline. The status icon on a row still just cycles status without asking.
  • Crew stats. Show Crew Stats opens a card per crew with stops, done, left, and billable total. Skipped and cancelled stops show a dash in the Amt column and are left out of the Totals row and the crew totals, since nothing is billed for them.
  • Notes to crew. A column you edit in place: click the cell, type, Save. It saves on the visit only and shows the job's note until you override it.
  • Columns. The column chooser shows or hides Date, Service, Address, City, State, Zip, Priority, Trigger, Crew, Depth, Temp, Notes to Crew and Amt, and remembers your choice.
  • Map. The Map button opens a working map: the stops currently shown, numbered by route position and coloured by crew. Three tools sit above it. Select: click stops to pick them (the table selection follows, so Dispatch, Close Out and the rest act on what you picked). Route order: left-click a stop to move it later in its crew's route, right-click to move it earlier. Draw area: click points on the map to outline a shape, then Select inside picks exactly the stops in the shape (replacing your current selection); Add to selection keeps your current picks too. With stops selected, the panel shows their services, budgeted hours and total, and lets you pick a crew and click Update, open Assign crews…, or Dispatch. Click a crew in the panel to hide or show it, and tick Show only selected stops (on the map, or in the table) to work on just those. Route lines draws each crew's order. The board's own filters apply to the map too
  • Weather. A chip above the storm bar shows the National Weather Service forecast and any active alerts for the storm date (US only, within about a week). It is only a heads-up — depth and temperature on a visit are still entered by hand at close-out.

Messaging clients: email, text, and templates

Tick the stops you want to reach, then use Email Clients… or Text Clients… (in Actions, or the buttons on the selection bar). You need the Send Emails / Send Texts permission to see them. A client with several stops on the storm gets one message that lists their stops.

  • Compose. Choose email, text, or both. Pick a saved template to pre-fill the message, then change anything you like before sending; the template is only a starting point. A text shows a live character and segment count, and a preview shows exactly what one client will receive.
  • Merge tags. [stormname], [stormdate], [snowservice], [snowcrew], [snowstatus] (scheduled, on our way, in progress, complete), [snowarrival] (only when the stop has a scheduled time) and [snowaddress], plus the usual client and company tags such as [clientfirstname].
  • Who is skipped. The confirm step lists the count and who will be left out: no email or phone on file, a bounced email address, a client who hasn't opted in to texts, or a number that replied STOP. Storm messages are service notices, so a client marked Do Not Market still receives them (and there is no unsubscribe footer), but a bounced address and a text opt-out are always respected.
  • Timeline. Every email and text is logged on the client's activity timeline, the same as any other message sent from the system.
  • Jobs Without Emails… lists the selected stops (or everything shown, with nothing selected) whose client has no email or a bounced one, with a link to fix each client.
  • Templates. In the compose dialog, type a name and choose Save email or Save text to keep your wording. Templates live in Documents as Snow – Email and Snow – Text Message, so you can also create and edit them there (for example "Service complete", "Storm delayed", "We're on our way").
  • Automations. The same templates can be picked in an automation's Email or Text step (for example on visit dispatched or visit completed) for messages that should go out on their own with fixed wording. In an automation the snow tags are read from the client's most recent snow stop in the last 7 days.

Worked scenario: a 6" storm

  1. A dispatcher sees a storm coming and clicks + New Storm Event, names it, sets the date, and enters a forecast depth of 6".
  2. They click Add Jobs. With Max Trigger Inches defaulted to 6, every client whose contract needs more than 6" to trigger is auto-excluded. Out of the org's full snow client list, 40 clients qualify and get added to the event, each carrying the priority already set on their client record.
  3. The event moves to Working. The dispatcher opens Team Assign, moves the High-priority clients onto the first crews out the door, and dispatches them — hospitals, fire lanes, and SLA accounts get plowed first, before the Normal- and Low-priority stops.
  4. As the storm continues, some clients need a second pass. Crews return, and each return visit is closed out on its own with its own depth reading — a morning push logged at 3", an afternoon push logged at another 3" once the storm finishes dropping its full 6".
  5. Once every crew has closed out every visit, the dispatcher sets the storm event's status to Complete. The event is now ready for Snow Invoicing.

Snow invoicing and the three rate types

CRM > Accounting > Snow Invoicing groups a client's uninvoiced storm visits and computes the amount from the job's own invoice type — a flat rate per storm event, a rate per inch of snowfall (charged once per event, or separately per push), or an hourly rate times actual hours logged. Only completed, non-contract snow visits that don't already have an invoice line item appear in the queue, so generating invoices twice never double-bills. A snow job linked to a contract is billed on the contract's cycle only while that contract is in force; once the contract is cancelled, expired, inactive or deleted, nothing else bills its visits, so they appear in this queue like any other snow visit — except storms inside a billing cycle the contract already invoiced (before it was cancelled, expired or switched off), which the contract price already paid for and stay out of the queue. If a visit's recorded depth isn't covered by any depth range or rate per inch on its job, the queue row says so (“isn't covered by any depth range or rate per inch on this job — add one to bill it”) instead of showing a silent $0.00; add a range or a rate per inch to the job and the row prices.

Storms outside the contract dates. Each snow contract chooses what happens to a storm before its start date or after its end date — open the contract and set Storms outside the contract dates (under its start and end dates):

  • Don't service — the contract's snow jobs aren't offered in Add Jobs for those storms.
  • Included in the flat rate — they're dispatched and covered by the contract price; nothing is billed for them here.
  • Bill per event (the default) — they're dispatched and billed here. A Monthly Flat Rate job bills the contract's Price per storm; a job with its own snow rate (Per Event, per inch, Hourly) bills that rate. If no price per storm is set, the visit stays in the queue at $0 with a warning telling you to set one.

The setting appears once a snow job is linked to the contract, and changing it (or the price per storm) on a signed contract flags the contract as changed since signed.

Salt and materials, per storm. Materials planned on a snow job (the job's Products, for example 10 bags of salt) are the plan for every storm. On each storm visit the crew records what they actually used, and that storm's usage comes off inventory then. Snow Invoicing lists each storm's used materials under its visit and adds them as lines on that storm's invoice, priced from the planned material on the job. They bill once: generating again doesn't add them a second time, and voiding the invoice puts them back in the queue with their visit. A visit that can't be priced yet keeps its materials until it is.

Two hourly jobs at one stop. When one crew's single stop includes more than one Hourly snow job (say plowing and salting billed separately), each job bills its share of the time on site — the same split the visit's hours get — instead of each billing the whole stop. A stop with one hourly job, and separate trips or crews, bill their full time as before.

A per-inch visit with no recorded depth (for example one completed from the crew app, where only the office Close Out records depth) is never priced at the bottom range — it shows no depth recorded, prices at $0 and waits in the queue. Type the measured depth into the box under its Billing column and the amount updates. When you Close Out a mixed batch, the hours you enter are split across the hourly jobs only.

Possibly already billed. An invoice made by hand for a snow push has no link back to the visit, so the visit would stay in the queue. When a queued visit's job already has a non-void invoice line for the same service date, the row shows an amber Possibly billed on invoice #N tag (or “a draft invoice” if that invoice has no number yet). If you generate with any of those visits selected, you're asked to confirm — Bill anyway bills it again, or cancel and check that invoice first.

Voided or deleted invoices release their visits. If you void (or delete) a snow invoice because the depth or rate was wrong, the storm visits it billed go straight back into the Snow Invoicing queue so you can bill them correctly — they're no longer treated as invoiced.

Snow invoices carry the client's terms. Each generated invoice is dated the day you generate it (your company's date, like Create Invoice), takes the client's Invoice terms (or the company default), gets a matching due date so it ages and appears in past-due reminders, and copies the job's PO number and sales rep when the invoice covers a single job. Each line keeps its storm's service date.

Depth is locked once invoiced. A completed visit on a live invoice keeps its recorded snow depth — void or edit the invoice first (or ask an admin to override) to change it, the same as its status and date.

Invoice typeHow it's computedWorked example (same 6" storm)
Per EventA flat rate charged once per storm, no matter how deep it snows or how many times a crew came back out.$75 flat × 1 storm = $75.00
Per Inch (Event, or Push)A rate per inch of snowfall. “Per Event” prices the storm’s single deepest reading once; “Per Push” prices every visit separately off its own logged depth. Either can instead use interval billing — a table of inch ranges, each with its own flat rate (see Interval billing below).Event: $12/in × 6" storm max = $72.00. Push: two 3" pushes × $12/in = $36 + $36 = $72.00.
HourlyHours on site × the job’s hourly rate — for jobs billed on time on site rather than snowfall. Billed once per visit, however many people were on the crew: from the crew app it’s clock-in to clock-out minus breaks; from the office Close Out it’s the hours you enter.1.5 hrs on site (3-person crew) × $150/hr = $225.00

For Per Event and Per Event/Per Inch jobs, every visit on the storm collapses into one charge — a morning push and an afternoon push during the same event are one line, priced off the storm's single deepest reading, not two separate charges. Per Push and Hourly jobs are the opposite: each visit prices and invoices on its own. The exception is a Per Event/Per Inch storm in an hourly range: it bills time, so each visit on the storm (the first push, extra crews, return trips) is its own line at its own hours × the rate.

Additional hours. Once a storm is invoiced it leaves the queue. On a Per Event/Per Inch storm in an hourly range, a crew that finishes after the invoice was made (a return trip, a second truck) comes back into the queue tagged Additional hours, priced on its own hours only — generate it like any other row to bill it on a new draft invoice. Hours already on the storm's invoice are never offered again.

Contract caps and overage (inches and salts)

A Monthly Flat Rate snow contract can include caps — an inch cap (for example 60 or 80 inches), a salt cap (for example 35 salt applications), an event cap (storms) and/or a push cap. The flat price covers snow work up to a cap; once it is used up, further work bills as overage in Snow Invoicing instead. On the contract, tick This contract includes snow service (it turns on by itself when a snow job is linked); that reveals the snow settings, including Snow Caps & Overage:

  • Inch, Salt, Event and Push caps — use any, all, or none. A blank cap shows N/A and means no limit.
  • Cap resets — each contract year (counted from the contract's start date, so a contract starting Nov 1 resets every Nov 1) or monthly (each calendar month).
  • Overage description — the text on the overage invoice line (default "Snow overage").
  • Overage per inch / salt / event / push — what each one over its cap bills. If a cap is set without its overage price, the overage visits stay in the queue at $0 with a warning telling you to set one.
  • Linked snow jobs count toward — each Monthly Flat Rate snow job is tagged plowing (counts toward the inch, event and push caps) or salting (counts toward the salt cap). Set it when you create the job (Counts toward contract caps as, which defaults to salting when a service is named like salt or de-icing, otherwise plowing), on the job's detail, or here on the contract. Several plowing jobs on one contract (say a truck plow and a shovel crew) never double-count inches or events — each storm counts once, on its deepest reading — but pushes are counted per job.

How work is counted. Only completed visits count — skipped and cancelled ones don't — and only storms the contract covers (storms outside its dates follow the "Storms outside the contract dates" setting and are never counted). Inches count once per storm, on its deepest recorded depth across the contract's plowing visits (the same "priced once on its deepest reading" rule as Per Event, Per Inch); a storm with no depth recorded counts 0, so enter depths. Storms add up through the period in date order. Events count one per storm with a completed plow visit, whatever its depth. Pushes count one per completed plow visit (an extra crew on the same stop doesn't add one). Salts count one per completed salting visit — a second push that salts again is a second application. Pushes and salts are counted per job, so one property's work doesn't use up another's cap.

What bills. Visits inside the cap stay covered by the contract. A storm that crosses the inch cap bills only the inches beyond it (an 8" storm that takes the season from 76" to 84" of an 80" cap bills 4" × the overage price per inch), as one line on the storm's first visit; later storms bill their full depth. A storm past the event cap bills the per-event price on its first visit; a push or salt past its cap bills its price on its own visit. If more than one cap is passed on the same stop, their charges add up on one overage line (so setting both an event cap and an inch cap can charge for both). These appear in Snow Invoicing with an Overage tag and the overage description, as their own invoice separate from the contract's invoice. Generating twice never double-bills, and voiding an overage invoice puts its visits back in the queue.

Seeing usage. The contract shows the period's usage ("42 of 80 in used", "28 of 35 salts used") and, on the Snow Jobs board, a stop whose cap is already used up shows an Overage chip so the crew and dispatcher know it will bill separately. Caps are counted from the visits, not stored, so correcting a depth or a completed visit updates the usage immediately — but a charge already invoiced is not changed afterwards.

Interval billing (rate by inches)

Many snow contracts price by bands of snowfall rather than a straight rate per inch — for example 0–3" is $165, 3–6" is $299, and 6–9" is $422. That is interval billing, and you set it while creating the job: choose Per Event, Per Inch or Per Push as the invoice type and an Interval Billing — Rate by Inches table appears. Click Add Range for each band (from, to, flat rate). Leave the last range's to blank for an open-ended top band billed per inch (for example 12"+ at $57 per inch). The same table is on the job's Details tab afterwards, with a Save Ranges button.

  • Per Event, Per Inch prices the storm's single deepest reading against the ranges. Per Push prices each visit by its own recorded depth against the ranges.
  • Start each range where the previous one ends (0–3, 3–6, 6–9). A depth exactly on a boundary bills the lower range — exactly 3" is the 0–3 band, and 3.1" is the 3–6 band. Saving ranges with a gap or an overlap between them is refused with a message saying where. Ranges saved earlier with a small gap (0–3, 3.01–6) still work: a depth inside the gap bills the lower range.
  • Pricing bands that end in .99 (0–1.99", 2–3.99", 4–5.99", 6–7.99", where exactly 4" counts as the 4–5.99 band): because a boundary depth bills the lower range and ranges can't have gaps, enter them as 0–1.99, 1.99–3.99, 3.99–5.99, 5.99–7.99. A push recorded at 4" then lands in 3.99–5.99 and bills the 4–5.99 price. Depths above the last range bill $0 unless the last range is left open-ended, so price anything deeper by hand or add a top range.
  • Hourly ranges. Each range has a Bill as choice: Flat (or Per inch for an open-ended top range) or Hourly. An hourly range takes an hourly rate and optional budgeted hours, and bills the hours on site (clocked out minus clocked in minus breaks) × that rate — the usual setup is an all-inclusive top range (for example 6"+ at $90 an hour) with flat prices below it. On a Per Push job each push is priced by its own depth, and an hourly range bills that push's hours. On a Per Event, Per Inch job the storm's deepest reading picks the range once; if it is an hourly range, the storm bills the on-site hours of every visit on the storm (the first push, return trips and extra crews) × the rate, each visit on its own line. Hours worked after the storm was invoiced come back as Additional hours rows. On either type, every crew on a multi-crew stop bills its own hours in an hourly range. Budgeted hours are for planning only and do not change what is billed.
  • A flat price per push (the same amount whatever the depth, for example a drive-lane-only push) is a Per Push job with a single range, such as 0–99" at the flat amount. The visit still needs a recorded depth to price; with none it waits in the Snow Invoicing queue at $0.
  • If no range matches a depth (below the first range, or above the last one with no open-ended range), it falls back to the flat Rate Per Inch on the job. Only the last range may be open-ended.
  • The Snow Jobs board totals and the Snow Invoicing queue both price from the ranges, and the queue's description column says when a row used them.

Services on a snow job: one per job, and when their price counts

A snow job's invoice type decides whether the Services table matters for billing, so the job form limits it. Make one job per service (plowing, sidewalks, de-icing), each with its own invoice type and depth ranges, rather than one job with several services.

Invoice typeServices on the jobService price
Per EventAs many as you need.Used — every service row is added together.
Per Event, Per Inch / Per PushOne.Not used — the depth ranges (or Rate Per Inch) set the price.
HourlyOne.Used — the service's Rate is the hourly rate.
Monthly Flat RateAs many as you need.Not used — the linked contract sets the price.
  • When the price isn't used, the Rate field shows Not used and the job is saved with a $0 service price. Billing never read it, and a price there would only have inflated the job's value in reports.
  • The Add Service button is disabled once a one-service type has its service. Choosing such a type after adding several services keeps the first and clears the prices, and the form says so. The same limits apply to the Services tab of an existing job and are enforced in the database, so imports and the API follow them too.
  • Monthly Flat Rate does not invoice by itself. It bills only through a linked, active contract that generates invoices automatically, so saving the job requires choosing the client's contract; without one it would never be billed. Its storm visits stay out of the Snow Invoicing queue.

Why snow billing has its own screen

A regular Landscapt invoice itemizes a fixed, known job — a monthly mow, a package installment — where the amount is settled the moment the invoice is written. Snow doesn't work that way: a single storm can generate several visits per client over hours or days, and the price isn't knowable until the storm is over and every visit has been closed out with its actual depth or hours. Snow Invoicing exists because that accumulate-then-rate step — grouping a client's visits by storm event, applying the job's own rate type to the group, and only then producing a line item — has no equivalent in the regular Invoicing screen's one-job-one-line model.

Because grouping and pricing both key off the storm event and the job's invoice type, a visit created outside the storm dispatch flow (say, logged directly from the field) still bills correctly — it just falls back to grouping by date instead of by storm event.

See also

Day-to-day, non-snow visit dispatch uses a different screen entirely — see the Dispatch Board guide for how the daily list-view board assigns and dispatches ordinary jobs. Snow storm dispatch is intentionally its own storm-event-centric flow rather than a daily board, since a storm doesn't respect calendar days the way a regular route does.

Good to know

  • Forecast column. The Snow Jobs board has a Forecast column next to Amt that estimates what each stop will bill before a crew logs a depth. Flat per-event stops forecast their price; per-inch and interval stops are priced at the storm event's forecast depth (set when you create the storm, or later from Actions → Edit Forecast Depth…) until a real depth is logged, so enter a forecast depth to get numbers. Per-inch stops without one, and hourly stops, show a dash. Until a depth is logged, Amt shows "Needs depth" for per-inch stops. Forecast is an estimate only — it is never billed, never appears in Snow Invoicing, and the Totals row shows it separately in italics. Cancelled and skipped stops have none, and the All tab leaves cancelled stops out (they keep their own tab and count).
  • Turning snow off. Not every company plows. Go to Settings → CRM → Services and untick We offer snow services to remove Snow Jobs and Snow Invoicing from the navigation. Nothing is deleted — existing storm events, snow jobs and snow invoices are kept and everything comes back when you tick the box again. New companies start with snow on. It only hides the menu items; it doesn't change permissions, and anyone who already has a direct link can still open the page.
  • Subcontractors. Set up each subcontractor as its own crew. There is no separate subcontractor setting on a snow job, and you don't need to add them as a vendor just to dispatch them. Go to Team → Crews, create a crew named for the subcontractor (for example "Sub – Smith Plowing"), then add their people under Team Assignments. Set those employees' employment status to Contractor so they show on the Contractor Phone List report. If their truck should show on the board, add it to the Vehicles registry in Equipt and load it onto that crew from the Equipment yard (use the pin to make it the crew's default). Then assign their stops to that crew like any other crew. Add them as a vendor only if you also want to track what you pay them through purchasing or on a project's Other Costs.
  • Status icon. Tapping a stop's status icon steps it forward through Scheduled, Dispatched and In Progress, and asks before marking it Completed (which invoices it) or reopening a completed stop. Skip a stop from the outcome dialog with a reason.
  • Reordering. The up and down arrows are disabled while a new order is saving, so two quick taps can't swap the wrong stops.
  • Tax-exempt clients. Snow invoices for a client marked tax-exempt carry no tax, even when the job came from a taxed estimate.

More in Landscapt (CRM)

Clients, Properties & Leads
Client accounts, commercial hierarchies, service properties, and the activity timeline that ties it all together.
Estimates & the Budget Engine
How an estimate is built, how its numbers are actually calculated, and how it becomes a job.
Jobs & Packages
The six job types, how a job's status differs from a visit's status, and how a Package template turns into a billed job.
Services & Pricing
The service catalog, bulk catalog price changes, and Price Adjustment runs — which prices seed new work and which ones actually bill.
The Dispatch Board
The daily scheduling screen crews and dispatchers live in — visits, crews, status, and how actual hours get calculated.
The Crew App
What a crew sees on their phone — the day's stops, clocking on and off, breaks, photos, and sending work back to the office.
Sales Meetings
Booking appointments per sales rep, the double-booking warning, and the split between a rep's direct reminder and the client-facing automation trigger.
The Waiting List
Jobs with a date range instead of a date, held for opportunistic scheduling — and how to actually get them dispatched.
Invoicing & Payments
How an invoice is born, how its status moves, and where the client's own PO number actually goes.
Contracts
Ongoing billing agreements — monthly amounts, seasonal overrides, sub-properties, and how signing and invoicing actually work.
Communication Automations
How sequences, triggers, and events work — and how Automations differ from Sales Campaigns.
Forms & Lead Capture
Building, publishing, and sharing public forms — and what happens to a submission once it lands.
Document & Email Templates
Building the reusable emails and text messages that go out with invoices, estimates, campaigns and automations — blocks, merge tags, buttons, previews and test sends.
Tickets
Support and service tickets — where they come from, how they're worked, and how they connect to the rest of a client's record.
Damage Cases
Tracking property damage and warranty claims tied to a job — what a case captures, how cost rolls up, and a real current limitation in how it connects to a client record.
Warranties
Tracking the warranties you give on walls, walkways, patios and renovations — when each starts and ends, how claims tie back to it, and expiry reminders.
Commissions
Paying sales reps a percentage of what they sell — plans and rules by service and sale type, how earnings are calculated, and locking a quarter into a statement.
Injury & Near-Miss Cases
Reporting injuries, illnesses and near misses from the field, following them up in the office, tracking self-paid costs, supervisor alerts, and the Accident Free Workdays KPI.
Job Photos
Field photo documentation, annotation, and before/after comparisons — attached to a job site, not a person.
Online Payments & Stripe
How a client actually pays an invoice online, how Stripe Connect keeps every org's money in their own account, and how the platform takes zero cut.
Browse all guides
© 2026 Landscapt. All rights reserved.