The Waiting List

Landscapt → Scheduling → Waiting List holds jobs that don't have a firm date yet — only a date range, like "From May 1" or "May 1 – May 15." Two job types end up here: jobs created with type Waiting List, and Package jobs whose next visit hasn't been given a real date yet (more on that below).

It exists for the case where you know a client needs service sometime in a window, but don't want to commit a crew to a specific day until you have a reason to — usually because a crew has an opening nearby and it makes sense to fill it opportunistically rather than run an extra trip later.

A job qualifies for the Waiting List page if its job_type is waiting_list or package, it isn't soft-deleted, and its date window overlaps whatever range you've got selected (jobs with no date set at all are always included, on either type). Two things keep the list honest as jobs move through dispatch:

• A Waiting List-type job drops off the page the moment it has an active (non-deleted) visit — once it's dispatched, it's not waiting anymore, so it won't double up between here and the Dispatch Board.
• A Package job's services are often bulk-generated for the whole season up front — one placeholder visit per service, sitting in a plain scheduled status, sometimes with a crew already pre-assigned. That placeholder state doesn't count as "handled" — only a visit that has moved past it (actually dispatched, worked, or resolved) gets filtered out. So a package can keep resurfacing on this page, one service at a time, all season. Until a step is dispatched it appears only here — the Dispatch Board hides a package step's placeholder visit — so a package behaves like a Waiting List job. A step that can't be dispatched yet says so under its service name: Too soon — earliest Nov 8 (in amber) when the package's Min Days spacing after the previous step hasn't passed. Dispatching it earlier asks you to confirm: the dialog shows the spacing message and a Dispatch anyway button, which overrides Min Days for that step (one step at a time). Anyone who can schedule visits can do this. Turn on Ready to dispatch in the filter bar to hide steps still inside their spacing and jobs whose date window hasn't started, leaving only what can go out today.

The Date Window bar at the top is the primary filter — it's a server-side query, not a client-side narrow, so it also controls which jobs get fetched in the first place. The dropdown on the left offers presets: Next 30 days (the default), This week, This month, This quarter, This year, and Next 90 days. Or edit either date yourself and the preset switches to Custom range. Your choice is saved to your login, so it's still there after a refresh or the next time you open the page. A preset like "This quarter" is remembered by name, so next month it still means the current quarter; a custom range keeps the exact dates you picked. Below that, Select a Filter lets you narrow the fetched set by one field at a time: Client, Service, City, Zip, or Crew. Crew is picked from a list of your active crews (or Unassigned) rather than typed. A separate free-text Search box matches client name, service name, street address, city, zip, crew code, and notes to crew independent of that filter; it has an × button, and pressing Escape clears it.

A package job with more than one active service — or any waiting-list job carrying more than one service — is expanded into one row per service rather than one row for the whole job. That's what lets you dispatch "Mulch" to one crew this week and hold "Spring Clean-up" for another opening, instead of both going out together on whatever date you pick.

Every row has its own Schedule button, and the dark actions bar has an Actions → Dispatch Selected… option for whatever you've checked. Both open the same dialog — pick a Date and, optionally, a Crew, then confirm. Dispatching:

• Creates a real visit for the job (or, for a package row, for that specific service).
• Assigns the crew you picked, or leaves it unassigned if you skip that field — either way the job now has a firm date and behaves like any other scheduled visit on the Dispatch Board.
• Removes it from this page on the next refresh — a waiting-list job because it now has an active visit, a package service because its visit has moved past the placeholder state.

From the client's record. You can also schedule a waiting-list job without leaving the client. On the client's Home tab, open the job's MORE menu and choose Schedule Job. It opens the same Date and Crew dialog; a job with several services schedules all of them on the date you pick. The item only appears while the job is still waiting (no visit yet), and only for logins that have the Waiting List permission. View Upcoming in the same menu lists each waiting service and has a Schedule button per service if you want to send one service out and keep the others waiting.

Skipped or cancelled visits. A waiting-list job leaves this list once it has a live visit. A visit that was skipped or cancelled never happened, so it doesn't count: if a job's only visits were skipped or cancelled, the job goes back on the Waiting List. Scheduling it again creates a fresh visit and takes it off again.

A crew wraps up a job in the 44057 zip code an hour ahead of schedule. Rather than send them back to the shop, the dispatcher opens the Waiting List:

1. Clicks the Zip filter under "Select a Filter" and types 44057. Three jobs come back — a one-time mulch job, a waiting-list mowing job, and one service off a fertilizer package.
2. Checks each row's Date Range and Rate columns. The mulch job's window doesn't open until next week — too early. The package service and the mowing job are both eligible today; the mowing job pays more for less time on site.
3. Clicks Schedule on the mowing job's row, sets the date to today, assigns the crew that's already in the area, and confirms.
4. The job now has a real visit and shows up on today's Dispatch Board like any other stop — the crew heads there next instead of driving back empty.

On this page, "find something nearby" means filtering by City or Zip — there's no map or live proximity check built into the list itself, just text matching against those two fields. It's fast and it works, but only as well as the address data behind it.

The Dispatch Board has a separate, more literal proximity tool — a Nearby Waiting List button that geocodes today's scheduled visits and every waiting-list job (plus package jobs whose next step is due), then returns matches within a set radius (3 miles by default) using actual distance, not just matching text fields. It's a different feature living on a different page — see the Dispatch Board guide below — but it's the closer equivalent to true geofencing if City/Zip filtering here isn't narrowing things down enough. Its Schedule Today dispatches a job the same way this page does: a job that goes out one service at a time gets one visit for each service still waiting, never a single visit that would bill every service again.

Map positions stay current on their own: when a job's address, its property, or the client's service or billing address changes, the saved position for the affected jobs is cleared and looked up again the next time you use Nearby Waiting List or the map.

Schedule Today never doubles anything up. While a waiting-list job waits, it has no visit at all: what you see on the Waiting List is the job and its services, not visits. Dispatching a service gives it its one visit, and that is what moves it off the list and onto the board. Here is how it plays out for a job with two services, Spring Clean-up and Mulch:

1. Both services sit on the Waiting List. The job has no visits.
2. You dispatch Spring Clean-up for Monday. It gets its visit, lands on Monday's board, and leaves the list. Mulch stays.
3. The crew completes Spring Clean-up on Monday.
4. On Thursday a crew is working next door, so you open Nearby Waiting List and click Schedule Today on that client. Spring Clean-up already has a visit (completed), so only Mulch is scheduled: it gets its first and only visit for Thursday, leaves the list, and lands on Thursday's board.

The job ends with exactly two visits, one per service, each billed once. A visit that was skipped or cancelled never happened, so its service goes back on the list and Nearby can offer it again.

Package jobs work a little differently. Each package step already has a placeholder visit from the day the job was created. So Nearby, like the Waiting List's own Schedule button, moves the next due step's placeholder to today and marks it dispatched; it never creates a second visit. A package only shows up once its next step's window has opened (and hasn't passed) and its Min Days since the previous step are met, and the row names the step, e.g. Step 3: Grub Control. Later steps stay where they are.

• Estimating guide — converting an estimate to a job can set its Job Type to Waiting List directly, skipping a separate step to move it here.
• Dispatch Board guide — once a waiting-list job or package visit is dispatched from this page, it behaves like any other scheduled visit there, including the radius-based Nearby Waiting List lookup described above.

• Dispatching as Unassigned. Choosing Unassigned when dispatching a job that has a default crew really leaves the visit unassigned instead of putting it on the job's crew.
• Skipped visits come back. A waiting-list service whose visit was skipped is offered again under the client's Schedule Job menu, the same as on the Waiting List page.