FieldRoutes calls it: Route, Route Template, Spot
From a read-only look at the FieldRoutes account on 2026-11-02 and its official manuals. Each line ends with its evidence: Observed in the account, Documented in a manual, or not tested. Capture numbers link to the screen below. All of FieldRoutes across the 20 blocks
Routing in FieldRoutes is the set of office tools that turn due work into technician days. A route is a dated container of appointment spots, usually built from a Route Template. The office prepares empty routes (Route Builder), groups subscriptions by technician or region (Visual Grouping), builds optimized plans (Intelligent Routing) and puts them on technician days (Assign Planned Routes), or does all of it in one step around existing visits (Fill Routes). Day-level tools (day view, Route Actions, Day Map, Dispatch Map, print) and the Route Reporting table complete the block. Office settings decide start/end points and optimization rules. The research has 48 screenshots that touch routing (25 placed here and 23 from other blocks), including a populated day with two unassigned routes, loaded maps and every planning screen. Nothing was created, optimized, assigned, locked, printed or saved, and no Fill Routes run was started because the manual says that is charged.
In short
- Grouping, planning and assignment are three separate steps in Intelligent Routing (Visual Grouping, Intelligent Routing, Assign Planned Routes). Fill Routes is a different, combined tool that schedules due work around existing appointments. Observed screens; documented by the official guides.
- Documented: Fill Routes charges a fee as soon as its button is selected, even if the next dialog is cancelled. Saving the routes is a separate step. A run is capped at 2,000 appointments and cannot cross technician or customer time zones. Observed: the account usage page lists Intelligent Routing at $0.50 per optimized route.
- Documented: Intelligent Routing has two objectives: Equal Stop (balanced stop counts) and Auto Optimize (efficiency with broader constraints). Fill Routes aims at efficiency, not equal workload.
- Route Templates define the spots on a route day (times, blocks, standard duration, buffer, timed-appointment limit, max spot capacity) and who may schedule into them, including API and Website Deals.
- Routes start and end at the office Physical Location unless a technician has their own Start/End Location on the User Card. Routing Options decide whether endpoints count in the route score and in optimization.
- Observed: a populated day shows two routes with "No Tech Assigned", each with one appointment (one completed, one pending). A completed appointment on an unassigned route does not prove a technician did it.
- "Distance Score" has no stated unit or formula and must not be read as miles. Maps render, but no live GPS or vehicle tracking was shown.
Screens: 25 captures
Upload a screenEach capture is a saved screen state from the FieldRoutes account on 2026-11-02. A screen shows what controls exist; it does not prove what happens when they are used.
Full description
Route Builder prepares empty route capacity for a range of dates before work is assigned. It shows a date range, a days-of-week choice (all days, weekdays only, exclude Sundays, exclude Saturdays), per-day sections with Add Route, Check All/Uncheck All, Apply To Checked and Save Routes. Nothing was added or saved.
Full description
Fill Routes picks due jobs and places them onto existing routes automatically. The screen shows the job filters, a choice to leave or re-route existing planned routes, an eligibility summary (19 of 29 appointments routable), a count of service types with a Fill Routes buffer, tabs by preferred technician, which routes to fill (all, only empty, only with appointments), technician filter and a separate route date range. The fill was not executed; the vendor manual says Fill Routes charges a fee on selection.
Full description
Visual Grouping lets the office group subscriptions on a map by preferred technician or by region. This early capture shows the mode choice, filters and Hard Reset Map Markers, but the map and subscription list had not finished loading. Superseded by the loaded views 522-524.
Full description
Intelligent Routing builds optimized route plans from due work. The screen offers routing by preferred technician or by region, the shared job filters (existing plans kept, special requests excluded), an eligibility summary (18 of 24 appointments), tabs per technician group, a Fill Routes buffer count, Toggle Map and the Create Optimized Routes entry. No optimization was run.
Full description
This is the step that puts optimized route plans onto technicians' days. It shows a destination date range, a technician selector (all, no tech assigned, individual technicians), Save Routes and Refresh, and two panels: Route Plans and Technicians Scheduled. Both panels are empty in this capture and nothing was assigned.
Full description
The Dispatch Map shows the day's routes, technicians and due work on a map with a filter sidebar. In this early capture the map area is only a shell and had not finished loading. Superseded by the loaded map in 525 (and the settled map behind 526).
Full description
Meant to show per-route performance. This capture shows only the heading and a loading indicator; captures 479 and 480 show the loaded report with its columns.
Full description
Reusable day template of appointment spots for routes: generate spots from start/end/interval, add or clear spots, block a spot with a description, and template-level settings such as auto creation, notifications, who can schedule, standard duration, buffer, timed-appointment limit and maximum spot capacity. The selected template shows half-hour spots. A popup partly covers this capture; capture 368 is the clear version.
Full description
Full-screen map for drawing the office's service territory boundary, with hand, draw-shape and delete tools, a 'select or create a new boundary' prompt, Map/Satellite toggle, Close and Save. Territory status is Not set; nothing was drawn or saved.
Full description
Routing policy editor with the office's current values (not saved): Minimum Spot Window 0 Hours; Fixed To Spot; Limit AM/PM No; Limit Call Ahead No; Lock Confirmed Appointments No; Route Distance Score Include Tech End Points; Expand Reschedule Events with no event chosen (options Day, Assigned Technician, Time Window changes, Adding a Time Window); Default Map Marker View Compact; Optimization Method Based on Location Settings (Recommended); Consolidate Multiservice Appointments Yes (groups eligible bundle visits in Fill Routes, Intelligent Routing and Optimize).
Full description
Dictionary of region labels used to group routes and filter triggers. Visibility filter, Search, + Region and Region/Visible columns; the list is empty.
Full description
Blank form with required Region name and Hidden/Visible, with save/cancel. It has no map boundary or ZIP field, so a region is only a label here, distinct from office territories and office ZIP codes. Nothing was saved.
Full description
Reusable day templates of appointment spots for routes. The Regular Routes template shows spot generation (start, end, interval, Generate, Add Spot, Clear, Fill Description), half-hour spots with block options, and settings: Auto Create (Yes), Send Notifications, Who Can Schedule (office staff, technicians, sales reps, API, website deals), standard duration, buffer, timed-appointment limit and max spot capacity. Nothing was generated or saved; replaces covered capture 126.
Full description
Name-only dialog to create a route template: Template Name, Save, Cancel and close. No template was saved.
Full description
Per-route performance table. Filters: route date and office, with Refresh, Export to CSV, search and page size. There are 24 columns: route ID, date, office, assigned tech, additional techs, route template, scheduled/completed/pending/no-show services, timed, AM, PM and anytime appointments, missed time windows and missed fixed times, scheduled and actual start time, end time, route distance score, total distance, overbooked accounts, production value and route value. The table states there is no data for the captured day.
Full description
The same Route Reporting view after pressing Refresh: same filters and 24 columns, and the table still states there are zero entries for the captured day. No CSV was exported.
Full description
The per-route action menu: Assign / Cancel Pre-Built Stops, Recommend Appointments, Map Route / Tech Tracker, Move Entire Route, Optimize Route, Route Summary Report, Auto Assign Times, Delete Route, Complete Entire Route, Cancel Entire Route and Lock Route. Only the menu was opened.
Full description
The Add Routes button opens a quantity menu from Add 1 Route to Add 15 Routes for the day. No option was chosen and no route created.
Full description
A map of the day's routes with a start/end location marker and a numbered appointment marker, route-state layers (Routes, Active, Canceled), map/satellite switch and standard map controls. The day had one completed and one pending visit, but the image does not show which marker is which. It loaded fully and was closed without changes.
Full description
Options for printing technicians' route sheets: style (none, compact, default, expanded), separate groups, print service notifications (pending-approval notices excluded), only customers without email or preferring paper, include overbooked services and technician selection. Canceled without printing.
Full description
A planning view across many days: nine mini calendars (August to April) with day counts, technician and route-group filters, group by technician or day, and links to Job Pool, Day Map, Print and Day Planner. The main route workspace is blank in this state.
Full description
Groups subscriptions on a map by preferred technician. The loaded view lists 33 unassigned subscriptions and one under a technician, shows map markers, a subscription list for the selected group, drawing tools (stop drawing, draw a shape), the current drawing target, Revert, Save and Hard Reset Map Markers. No boundary was drawn or saved.
Full description
Expands Visual Grouping's filters with the same due-work criteria as the Job Pool (service types, bundles, plans, add-ons, flags, preferred tech/day, region, measurement, category, skills), plus include/exclude currently scheduled customers and use of the Due Between dates. No grouping changed.
Full description
The region mode groups subscriptions by geographic region instead of technician: 34 subscriptions are Unassigned/Any Region, with the map, list and drawing tools. The on-screen prompt still says 'Select tech to begin drawing' although the context panel says Preferred Region. No regions were assigned.
Full description
The dispatch map with its filter sidebar (date range, Job Pool-style filters), the day's Regular Routes group (zero routes), Add new route, map/satellite, compact/detailed markers, layer toggles for Technicians, Routes and Job Pool, a selection tool and legend. Some map tiles still show gray bands; the map behind 526 is the settled version.
Their words for this block 20
Where it lives in FieldRoutes
Menus, pages and settings where this block appears 13 menu paths
- Scheduling menu: Calendar, Job Pool, Dispatch Map, Service Plan Management, Route Builder, Fill Routes, Visual Grouping, Intelligent Routing (with Assign Planned Routes).
- Route Builder 034-route-builder
- Fill Routes 035-fill-routes
- Visual Grouping: early view 036-visual-grouping (superseded), by technician 522-visual-grouping-loaded, advanced filters 523-visual-grouping-advanced, by region 524-visual-grouping-regions
- Intelligent Routing 037-intelligent-routing; Assign Planned Routes 038-assign-planned-routes
- Dispatch Map: early shell 039-dispatch-map (superseded), loaded 525-dispatch-map-loaded, settled map behind the top-bar date picker 526-global-date-picker
- Scheduling > Calendar: month view 030-scheduling-calendar, populated October 514-routing-october-calendar, day view 515-routing-populated-day.
- Day view > Route Actions 516-daily-route-actions; Add Routes 517-add-routes-options; Day Map 519-day-route-map; Print 520-daily-route-print-options; Multi-Day Planner 521-multi-day-planner.
- Scheduling > Job Pool (owned by Scheduling and appointments): 031-scheduling-job-pool, 032-job-pool-advanced, 556-job-pool-columns-clear; Recommended Routes 557-recommended-routes-clear and from the Customer Card 029-customer-schedule.
- Admin > Route Templates: 368-route-templates-clear (replaces popup-covered 126-admin-route-templates); + New Template 369-route-template-name-editor.
- Admin > Preferences > Office Settings > Preferences > Routing Options: 217-office-preferences, editor 219-office-routing-options-editor.
- Admin > Preferences > Office Settings > Office Info: physical location and territory 196-office-info, 200-office-invoice-address-editor, 201-office-territory-editor.
- Admin > Preferences > Customer Preferences > Route Regions: 344-route-regions, 345-route-region-editor.
- Admin > Users > User Card > Location (technician start/end): 553-owned-user-location.
- Reporting > Office > Route Reporting: loading 093-report-route-reporting (superseded), loaded 479-route-reporting-revisited, after Refresh 480-route-reporting-results.
- Reporting > Locations (staff location, owned by Technicians and licenses): 113-reporting-locations, 114-locations-all-employees, 116-locations-technicians, 117-location-history-demo.
- Dashboard > Stops Per Route help 394-dashboard-metric-help-6.
- Admin > Billing > Usage (routing fees) 362-admin-usage.
- Route-related fields on a customer: subscription Routing Region and preferences 439-existing-subscription-lower; appointment route link 448-customer-appointment-detail; Customer Search map 433-customer-report-map; bad geocode audit 471-audit-bad-geocodes.
Connections to other blocks
- Routing takes due work from Scheduling and appointments: the Job Pool lists due services without a future appointment, and Recommended Routes places single visits onto routes (observed; documented lifecycle).
- Routing reads service rules from Service agreements and renewals: subscription Routing Region, preferred tech/day/time, frequency, duration, Fill Routes buffers, early completion window and bundle consolidation (observed).
- Routing depends on Service location: valid geocodes decide eligibility (documented), the Audit flags bad geocodes (observed 471-audit-bad-geocodes), and filters use property type, map pages, ZIP codes and cities.
- Routing assigns work to Technicians and licenses: skills, technician start/end locations, route permissions and staff location reports (observed).
- Routing produces route sheets and day reminders for Customer messages and marketing: Print Service Notifications, contact-preference print criteria and the day Reminders dialog (observed).
- Routing feeds Work order: Complete Entire Route and per-appointment completion sit on the route (observed menu only).
- Routing is measured in Reporting and analytics: Route Reporting and the dashboard Stops Per Route card (total and average appointments per route split into regular, re-services, starts and other; the average counts regular services only) (observed 394-dashboard-metric-help-6).
- Routing exposes scheduling to Integrations and API: Route Template "Who Can Schedule" includes API and Website Deals; an appointment showed "Scheduled By" system/API (observed).
- Routing affects Mobile app: route view permissions control My Routes / All Routes visibility in the app, and Mobile Sales has "Show Nearby Appointment Distance" and "Technician Earliest Available Spot" (observed tooltips).
- Routing usage is billed to the company in FieldRoutes hub (FieldRoutes account usage) (observed 362-admin-usage).
How FieldRoutes does it
1. Set up capacity (observed screens, not saved).
- A Route Template defines spots. The office sets Start, End and Interval and presses Generate, or adds spots one by one; each spot can be blocked with a description. Template settings: Auto Create, Send Notifications, Who Can Schedule, Standard Duration, Buffer, Timed Appointments limit and Max Spot Capacity. The selected "Regular Routes" template shows half-hour spots, 25-minute interval and standard duration, 0-minute buffer, No Limit for timed appointments and 60-minute max spot capacity (account values, not product defaults). + New Template opens a name-only Save Template dialog. 368-route-templates-clear, 369-route-template-name-editor
- Route Builder takes a date range (November 2-16 here) and a days-of-week choice (All days, Weekdays only, Exclude Sundays, Exclude Saturdays; Exclude Sundays was selected), shows one section per day with Add Route, and offers Check All/Uncheck All, Apply To Checked and Save Routes. 034-route-builder
- On the day view, Add Routes offers Add 1 Route to Add 15 Routes. 517-add-routes-options
2a. Intelligent Routing path: group, plan, assign (observed screens; documented stages).
- Visual Grouping: choose Assign Preferred Technicians or Assign Regions, include or exclude currently scheduled customers, apply the due-date filter, then draw shapes on the map to set each technician's or region's area; Save or Revert. In technician mode 33 subscriptions are Unassigned/Any Tech and one is under a technician; in region mode all 34 are Unassigned/Any Region. Counts are subscriptions, not unique customers. The region view still prompts "Select tech to begin drawing their area" while its context panel says Preferred Region. 522-visual-grouping-loaded, 523-visual-grouping-advanced, 524-visual-grouping-regions
- Intelligent Routing: choose Route By Preferred Tech or Route By Region, filter jobs (Leave existing plans and Exclude Special Requests selected), check the eligibility summary ("Routing 18 / 24 Appointments") and press Create Optimized Routes. Not run. 037-intelligent-routing
- Assign Planned Routes: pick a destination date range (November 2-22), a technician scope, and move Route Plans onto Technicians Scheduled; Save Routes. Both panels were empty. The manual mentions drag/drop, Auto Assign and Map It; these were not seen in the empty view. 038-assign-planned-routes
- Documented (Intelligent Routing manual): Special Scheduling customers need manual scheduling; valid geocodes and matching skills decide eligibility; capacity and road parameters apply; reoptimizing unassigned work can delay due dates.
2b. Fill Routes path (observed setup; documented execution). The office filters available jobs, chooses Leave or Re-route existing planned routes, reads the eligibility summary ("Routing 19 / 29 Appointments", "0 Service Types with Fill Routes Buffer"), picks which routes to fill (all, only empty, only with existing appointments), a technician filter and a separate route date range (November 3-12, while job Due Between was May 2 - November 12). Documented: selecting the Fill Routes button is charged even if cancelled; Save commits; max 2,000 appointments; no routes across time zones; missing geocodes, skills and narrow windows can exclude work or make a route infeasible; the goal is efficiency, not equal workload. The 2021 vendor guide and a 2025 vendor article also say Fill Routes fills gaps around existing appointments and recommend human review of the result. 035-fill-routes
2c. One visit at a time (observed, nothing booked). From the Job Pool play button or the Customer Card Schedule button, the office enters a "Currently Scheduling" context and gets Recommended Routes: existing routes ranked by closest or soonest, with full-route, technician, group, Max Miles (30), date range and skill-match filters. The table was empty both times. Documented (Job Pool manual): a visit can be placed through recommendations or drag/drop, with skill-mismatch warnings. 029-customer-schedule, 557-recommended-routes-clear
3. Run the day (observed menus only).
- The month calendar shows per day Routes, Serv (completed of scheduled) and Sold. October 16 shows 2 routes, Serv 1/2, Sold 0. November is all zero for that month's data. 514-routing-october-calendar, 030-scheduling-calendar
- The day view shows route cards with technician (here No Tech Assigned), appointments, planned hours (0.5/11 hrs), Distance Score and Value; time slots offer Schedule Fixed Appointment; route groups can be edited; routes can be assigned map pages. Header: Add Routes, Job Pool, Reminders, Day Map, Optimize, Print, Multi-Day Planner. 515-routing-populated-day
- Route Actions per route: Assign Pre-Built Stops, CANCEL Pre-Built Stops, Recommend Appointments, Map Route / Tech Tracker, Move Entire Route, Optimize Route, Route Summary Report, Auto Assign Times, Delete Route, Complete Entire Route, Cancel Entire Route, Lock Route. None was used. 516-daily-route-actions
- Reminders on the day showed one pending appointment with SMS Undeliverable, Email/Voice Off and status Turned Off (see Customer messages and marketing).
- Day Map draws a start/end location marker and numbered appointment markers with Routes/Active/Canceled layers. The day had one completed and one pending visit, but the map image does not show which marker is which. 519-day-route-map
- Print builds technician route sheets; pending-approval service notifications are excluded per tooltip. 520-daily-route-print-options
- Multi-Day Planner shows nine mini calendars (August 2026 to April 2027) and groups by technician or day; its main workspace was blank. 521-multi-day-planner
- The Dispatch Map shows routes, technicians and Job Pool work as map layers with filters; zero routes for the shown day. 525-dispatch-map-loaded, 526-global-date-picker
4. Review (observed empty). Route Reporting lists one row per route with 24 columns. The table had no data for the captured day, also after Refresh. The 2025 vendor article says route-report exports support production-per-tech and production-per-mile analysis. 479-route-reporting-revisited, 480-route-reporting-results
Untested everywhere: route creation, optimization, assignment, drag/drop, locking, moving, completing or cancelling a route, auto times, printing, CSV export, round skipping and cycle closing.
Settings and controls
All settings and controls seen 69 rows
Route Templates 368-route-templates-clear, 369-route-template-name-editor
| Control | Options / limit |
|---|---|
| Templates list; + New Template (Template Name, Save, Cancel) | Choose or create a template. |
| Start / End; Interval (5-120 min in 5-min steps, 25 selected); Description | Spot generation inputs. Existing spots are half-hour, so the interval is not proof of spacing. |
| + Generate; + Add Spot; Clear; Fill Description | Generate, add, clear spots, fill descriptions. Not run. |
| Per spot: Start / End, Time Description, Block checkbox and Block Description, red minus icon | Spot times, label, block, remove. |
| Auto Create: No / Yes (Yes) | Trigger and scope unknown. |
| Send Notifications: No Notifications / Send Notifications (Send) | Recipients unknown. |
| Who Can Schedule: All Office Staff, All Technicians, All Sales Reps, API, Website Deals (All Office Staff) | Enforcement untested. |
| Standard Duration (5-120 min, 25); Buffer (0-135 min, 0); Timed Appointments (No Limit or 0-19, No Limit); Max Spot Capacity (5-120 min, 60) | Capacity rules; interaction untested. |
| Save Template; Delete Template | Not executed. |
Office Routing Options (Office Settings > Preferences) 219-office-routing-options-editor
Values shown in the unsaved editor (the office's current settings): Minimum Spot Window 0 Hours, Fixed To Spot, Limit AM/PM No, Limit Call Ahead No, Lock Confirmed Appointments No, Route Distance Score Include Tech End Points, Expand Reschedule Events with no event chosen, Default Map Marker View Compact, Optimization Method Based on Location Settings (Recommended), Consolidate Multiservice Appointments Yes.
| Control | Options / limit |
|---|---|
| Minimum Spot Window | 0-4 hours. |
| Fixed To | Spot / Route / Group. |
| Limit AM/PM; Limit Call Ahead; Lock Confirmed Appointments | Dispatch constraints and confirmation lock. |
| Route Distance Score | Include / Exclude Tech End Points. |
| Expand Reschedule Events | Day, assigned-technician, time-window changes or adding a time window. |
| Default Map Marker View | Compact / Detailed. |
| Optimization Method | Based on Location Settings / Start Location Only / End Location Only (decides which endpoints count). |
| Consolidate Multiservice Appointments | Groups eligible bundle appointments in Fill Routes, Intelligent Routing and Optimize (tooltip). |
| Other Options: Auto Scheduling | Automatic scheduling enablement; behavior untested. |
Office and technician endpoints 196-office-info, 200-office-invoice-address-editor, 201-office-territory-editor, 553-owned-user-location
| Control | Options / limit |
|---|---|
| Physical Location Address / City / State / Zip / Country | Office base; default route start/end. |
| Invoice Address | Correspondence only; not a route point. |
| Territories (Not set): stop drawing, draw a shape, delete, Save, Close | Office service area; enforcement untested. |
| Office map position / GeoCoordinates / Save Map Position | Office map point, saved separately. |
| Time Zone (PST, MST/Arizona, CST, EST, AKST, HST) | Office time zone; matters for Fill Routes' no-cross-time-zone rule. |
| User Card > Location: Start Location and End Location (address, ZIP, city, state, each with a map) | Per-technician override. Precedence and geocoding untested. |
Route Regions 344-route-regions, 345-route-region-editor: Visibility filter, Search, + Region; Region (required), Hidden/Visible, save/cancel. List empty.
Subscription and service definition fields used by routing 439-existing-subscription-lower, 540-service-type-editor-clear (earlier partial view 135-settings-service-type-form)
| Control | Options / limit |
|---|---|
| Routing Region (No Region Assigned) | Assignment icon tooltip refers to preferred assignment using Visual Grouping borders. |
| Preferred Tech; Preferred Day (Any Day, Sunday-Saturday); Preferred Time (Any Time / Specific Time Window) | Preferences, not route assignment. The 2025 vendor article calls preferred time, technician and day optimization constraints. |
| Duration; Call Ahead (none / 30 min / 1 hour) | Visit length and call-ahead. |
| Service Type: Skills | Required skills for dispatch; enforcement untested. |
| Service Type: Early Completion Window | Lets a service show in Flexible scheduling results before its due date. |
| Service Type: Use Fill Routes Buffer; Scheduling Buffer before/after; Followup Buffer before/after | Fill Routes date window around the next due date, and a separate one for follow-ups. |
| User Card > Information: Skills | Skill multi-select with no options populated. |
Visual Grouping 522-visual-grouping-loaded, 523-visual-grouping-advanced, 524-visual-grouping-regions
| Control | Options / limit |
|---|---|
| Assign Preferred Technicians / Assign Regions | Grouping dimension. |
| Include / Exclude Currently Scheduled Customers (pending appointments) | Include selected. |
| Use Due Between: Yes / No | Yes selected. |
| Basic/Advanced filters, Clear, Refresh, Actions (unopened) | Shared due-work filters. |
| Group color list with counts; selected group's Subscriptions list | Current grouping. |
| Stop drawing / Draw a shape; trash icon; "Currently Drawing For: Preferred Tech / Preferred Region; Service Type(s)" | Boundary drawing. |
| Revert / Save; Hard Reset Map Markers | Not used; reset scope unknown. |
Intelligent Routing and Assign Planned Routes 037-intelligent-routing, 038-assign-planned-routes
| Control | Options / limit |
|---|---|
| Route By Preferred Tech / Route By Region; Toggle Map | Grouping dimension for optimization. |
| Shared job filters; Leave existing plans; Exclude Special Requests | Eligibility. |
| Routing 18 / 24 Appointments; Any Tech and preferred-tech tabs; 0 Service Types with Fill Routes Buffer | Eligibility output. |
| Create Optimized Routes | Not run. |
| Assign: date range; All Technicians / No Tech Assigned / technician; Save Routes; Refresh; Route Plans and Technicians Scheduled panels | Plan-to-day assignment. Empty. |
Fill Routes 035-fill-routes
| Control | Options / limit |
|---|---|
| Jobs Available filters, saved filters, Refresh | Due-job selection. |
| Leave existing planned routes / Re-route existing planned routes | Leave selected. |
| Routing 19 / 29 Appointments; 0 Service Types with Fill Routes Buffer; Any Tech / preferred-tech tabs | Eligibility output. |
| Routes to Fill: Include All Routes / ONLY Empty Routes / ONLY Routes w/ Existing Appointments | All selected. |
| Filter Techs; Route Date Range; Refresh | Target routes and dates. |
| Fill Routes execution | Not touched (charged on entry per manual). |
Day view and Route Actions 515-routing-populated-day, 516-daily-route-actions, 517-add-routes-options
| Control | Options / limit |
|---|---|
| Date arrows; Add Routes (1-15); Job Pool; Reminders; Day Map; Optimize; Print; Multi-Day Planner | Header tools. Optimize untouched. |
| Regular Routes / Click To Edit / + Add Group | Route groups. |
| Route card: technician, appointments, hours, route ID, Distance Score, Value; completed check and pending play marker; service abbreviation, currency, FF, S, red and clock icons (some unexplained) | Route summary. |
| Schedule Fixed Appointment (time slots); Click to assign map pages | Booking and geography entries. |
| Route Actions (12 entries listed above) | None used. |
Day Map 519-day-route-map: start/end and numbered markers (completed and pending not distinguishable in the capture); Routes / Active / Canceled; Map / Satellite; fullscreen, camera, Street View, keyboard shortcuts; Google Maps and terms links; close.
Print Options 520-daily-route-print-options: Route Sheet (None / Compact / Default / Expanded Style); Separate groups; Print Service Notifications (pending approval excluded); Only customers without email; Only customers who prefer paper; Include Overbooked Services (checked); Technicians multi-select; Print / Cancel.
Multi-Day Planner 521-multi-day-planner: Job Pool / Day Map / Print / Day Planner links; nine mini calendars; Filter Techs; Group By Technician / Day; Filter Groups; Refresh; Toggle Mini Calendar.
Dispatch Map 525-dispatch-map-loaded: Filters header, Date Range, Job Pool, Filters; Clear, Refresh; Job Pool-style basic and advanced filters; Routes / Regular Routes (date) count; Add new route; Map / Satellite; Compact / Detailed markers; Technicians / Routes / Job Pool layers; selection tool; legend toggle; standard map links.
Recommended Routes 557-recommended-routes-clear: Sort by Closest / Soonest; Include Full Routes / Only Non-Filled Routes; Filter Techs; Filter Groups; Max Miles (30); Date Range; Match by Tech Skills; Refresh. Result columns: Date, Tech, Avg. Distance, Closest To, Capacity, Sub SF, Total SF, Sub LF, Total LF.
Shared due-work filters (Job Pool, Visual Grouping, Dispatch Map, Fill Routes, Intelligent Routing; subsets differ by screen) 032-job-pool-advanced, 523-visual-grouping-advanced
| Filter | Options |
|---|---|
| Special Requests | Include / Exclude / ONLY. Include on Job Pool, Visual Grouping, Dispatch; Exclude on Fill Routes and Intelligent Routing. |
| Pre-planned | Show / Don't show pre-planned. |
| One Time Services | Exclude / Include / Only. |
| Flexible Scheduling | Standard scheduling / Show services eligible for early completion. |
| Due Between; Follow-up Due Between | Service due dates, not route dates. |
| Potential Customers; Followup Services; Pending Cancels | Include / Exclude / ONLY (Pending Cancels: Exclude / Include). |
| Property Type | All / Residential / Commercial Properties. |
| Balance <=; Age <= | Account balance and balance age. |
| Map Pages; Zip Codes; Select Cities | Geography. |
| Production Value Min / Max | Service production value. |
| Include / Exclude Service Types, Service Bundles, Service Plans, Add-ons, Customer Flags, Subscription Flags, Skills | Selection lists. |
| Account For Wait After | Yes / No (No ignores the wait-after period, per manual). |
| Preferred Tech; Preferred Day; Region; Service Category | Preference and grouping filters. |
| Measurement | Measured and Non-Measured / Only Non-Measured / Only Measured / Only SF / Only LF. |
| Saved reports: Report Name, User / Office / Global (Global disabled), Default, Save, Save as New, Show Saved Filters | Reusable criteria; none saved. |
Route Reporting 479-route-reporting-revisited: Route Date range, Offices, Refresh, Export to CSV, Search, Show entries (50 / 100 / 500 / 1,000 / 5,000 / 10,000). Columns: Route ID, Route Date, Route Office, Route Assigned To, Additional Techs, Route Template, Total Scheduled Services, Completed Services, Pending Services, No Show Services, Timed Appointments, AM Appointments, PM Appointments, Anytime Appointments, Missed Window Timed Appointments, Missed Fixed Spot Appointment Time, Route Scheduled Start Time, Actual Route Start Time, Route End Time, Route Distance Score, Route Total Distance, Overbooked Accounts, Production Value, Route Value.
Routing permissions (Access Control, see Technicians and licenses): View Own Routes, View Other's Routes, Edit Own Routes, Edit Other's Routes, Create Routes, Delete Routes, Lock/Unlock Routes, Schedule On Locked Routes, Intelligent Routing, Assign Map Pages, Create/Edit Route Templates, Update Preferred Technician (Reports). Tooltips say edit includes view, and own-route editing covers route templates/builders, visual routing, assignment, move route and day-group tabs.
Usage fees 362-admin-usage: Intelligent Routing usage shows Routes Optimized and Optimization Total, at $0.50 per optimized route on the capture date (account rate, not a quote). No paid optimization was run.
What the research did not prove
- No route, template, group boundary, plan or assignment was created or saved. No optimization or Fill Routes run, so no algorithm output, feasibility or quality was seen.
- Fee triggers: Fill Routes is documented as charged on entry; whether day Optimize, Route Actions > Optimize Route or Create Optimized Routes are charged separately was not tested.
- Enforcement of spot capacity, buffers, timed limits, Who Can Schedule, Fixed To, locks, call-ahead limits, skills, wait-after and special requests is untested. Which rule wins when constraints conflict is unknown.
- No technician was assigned on the populated day. Distance Score and Value have no known formula; Route Total Distance was never populated.
- Maps rendered but no live GPS, tracker freshness, arrival tracking or vehicle telematics. Location reports showed no markers or tracks.
- Endpoint precedence (technician versus office), geocoding of endpoints and time-zone handling were not tested.
- Route Reporting and Assign Planned Routes were empty; Multi-Day Planner workspace was blank; Recommended Routes returned no rows.
- Job Pool showed 29 rows in one snapshot and 34 in a later one; criteria equality was not established, so the difference is not explained. Some Due On values precede the Due Between window.
- Several icons on route cards and early captures have no accessible names; their meaning is unknown.
- Superseded captures: 036, 039 and 525 (gray tile bands) are replaced by 522-526; 126 by 368; 093 by 479-480.
- Acceptance questions from the research: can dispatch keep promised windows, access restrictions, skills, capacity, travel limits and plan dependencies at once; demonstrate an urgent insertion, a technician absence, a customer reschedule and a missed visit; show which step only plans and which actually schedules, and how mistakes are reversed; reconcile Fill Routes fee authorization, run size and time zones before a controlled trial; include technician endpoints, confirmation locks, bundle consolidation and inter-office/ZIP boundaries; choose an explicit workload objective (Equal Stop or Auto Optimize).
- The fit conclusion lists optimization cost and time-zone limits as acceptance conditions. Confidence for scheduling/routing is medium: populated tools exist, but optimization and enforcement are untested.
Ideas for Our CRM
- Proposal: keep "plan" and "assign" as separate, reversible steps, as FieldRoutes does with Intelligent Routing, so a dispatcher can review before committing.
- Proposal: never charge or commit on opening a routing tool; show a free preview first (FieldRoutes charges Fill Routes on entry).
- Proposal: let the dispatcher choose the objective explicitly (balanced stops versus efficiency).
- Proposal: give every route score a stated unit and formula; FieldRoutes' Distance Score has neither.
- Proposal: model office base, technician start/end and service territory as separate settings with a clear precedence rule.
- Proposal: keep route regions, territories and ZIP claims as distinct concepts with distinct names.
Official FieldRoutes manuals
- Fill Routes (read; updated 2026-10-09)
- Intelligent Routing: Introduction (read; updated 2025-12-05)
- Job Pool (read; updated 2026-02-13)
- Indexed only, not read: Route Builder, Route Templates, Fill Routes: Route Visibility & Actions, Visual Grouping, Intelligent Routing, Assign Planned Routes, Flexible on Route versus Fixed to Spot
- Vendor articles: Make the Most out of PestRoutes in 2021 (2021-01-19), Routing tips from an industry leader (2025-06-25)
- Research reports: routing findings, routing controls, assessment, official manual findings
Screenshots kept in other blocks that also matter here 23
- 029-customer-schedule · Schedule from Customer Card, Recommended Routes (Scheduling and appointments): Clicking Schedule on a customer puts the office user into a 'Currently Scheduling' mode for that customer and opens Recommended Routes, which suggests technician route-days for the visit.
- 030-scheduling-calendar · Scheduling calendar, November (Scheduling and appointments): The month calendar is the scheduler's starting point: each day shows the number of Routes, a Serv count (services completed of scheduled) and a Sold count, with month navigation arrows.
- 031-scheduling-job-pool · Job Pool, basic filters (Scheduling and appointments): The Job Pool is the queue of due services that do not yet have a future appointment, so the office can find and schedule due work.
- 032-job-pool-advanced · Job Pool, advanced filters with results (Scheduling and appointments): Expands the Job Pool to all advanced criteria: production value range, include/exclude service types, bundles, service plans, add-ons, customer and subscription flags, preferred technician, preferred day, region, measurement (square/linear feet), service category and skills, plus 'Account For Wait After'.
- 033-service-plan-management · Service Plan Management (Scheduling and appointments): This screen tracks service-plan rounds and cycles for customers on a plan: plan, round, cycle start/end, round status and range, due date, completed and skipped rounds, subscription status and balance.
- 113-reporting-locations · Location Reports landing (Technicians and licenses): Shows where staff are, based on location data reported from the field.
- 114-locations-all-employees · Last known location, all employees (Technicians and licenses): The last-known-location map with 'All Employees' selected, with the same date range, Refresh and map controls.
- 116-locations-technicians · Last known location, all technicians (Technicians and licenses): The last-known-location map with 'All Technicians' selected, same controls as the other location views.
- 117-location-history-demo · Location history, one employee (Technicians and licenses): The location-history view for one employee (a demo technician record), meant to show where that person went over the chosen dates.
- 196-office-info · Office Info overview (FieldRoutes hub): The office's own setup page with separate sections: contact info, legal business info, authorized contacts, invoice address, physical location, territories, logo and map position.
- 200-office-invoice-address-editor · Office invoice and physical address editor (Invoicing and billing terms): Edit form for the return address printed on invoices, statements, service notices and emails (P.O.
- 217-office-preferences · Office Preferences overview (Invoicing and billing terms): Overview of office-wide policies in separate editable sections: contract defaults, routing options, billing preferences, other options, two-factor settings, brand colors and month closing (with a Close Month button, not used).
- 362-admin-usage · FieldRoutes account billing: Usage (FieldRoutes hub): Usage-based fees for a selected date range with a Refresh button: SMS (outbound, inbound, total, cost), Voice (outbound, inbound, total, cost) and Intelligent Routing (routes optimized, total).
- 394-dashboard-metric-help-6 · Dashboard help: Stops Per Route (Reporting and analytics): The help dialog for the dashboard's Stops Per Route card.
- 433-customer-report-map · Customer Search, map view (Customer account): Toggle Map shows the search result on a map with customer markers and map navigation controls.
- 439-existing-subscription-lower · Subscription detail, lower part (billing, schedule, invoice summary) (Service agreements and renewals): Lower part of the same subscription: billing frequency and next billing date, scheduling preferences, a timeline of scheduled and upcoming service dates, and Initial and Recurring invoice summaries.
- 471-audit-bad-geocodes · Audit check: Customers with bad geocode (Service location): One of the 19 Audit data-quality checks: customers whose address could not be placed correctly on the map.
- 514-routing-october-calendar · Scheduling calendar, October (Scheduling and appointments): The month calendar for October with populated days showing route counts, services completed of scheduled (e.g.
- 515-routing-populated-day · Daily route view, populated day (Scheduling and appointments): The day schedule shows routes as cards: here two routes with no technician assigned, one appointment each (one completed, one pending), planned hours, a Distance Score with no stated unit and a route value.
- 526-global-date-picker · Global date picker (FieldRoutes hub): The top-bar date control opens a month calendar (Sunday-Saturday grid with month navigation) used to jump to a working day.
- 553-owned-user-location · User Card, Location tab (Technicians and licenses): Sets the technician's own route Start Location and End Location (address, ZIP, city, state), each with a map.
- 556-job-pool-columns-clear · Job Pool, loaded with all columns (Scheduling and appointments): The Job Pool with basic filters loaded 34 due-service rows (an earlier 032 snapshot had 29; not reconciled).
- 557-recommended-routes-clear · Recommended Routes dialog (Scheduling and appointments): Opening a due service from the Job Pool starts a 'Currently Scheduling' context and shows Recommended Routes, which suggests existing routes for the visit: sort by closest or soonest, include full or only non-filled routes, technician and group filters, max miles (30), date range, match by tech skills and Refresh.
Research sections used for this page 68
The original research reports are kept unchanged in the archive. These are the sections that speak about this block:
- admin/controls.md › Admin navigation: Admin top navigation: Business Contacts, Users, Teams/Departments, Route Templates, Preferences and Billing (the company's own FieldRoutes account), each with its purpose.
- admin/controls.md › Route Templates: Route Templates: spot generation (start/end/interval), per-spot times and blocks, Auto Create, notifications, Who Can Schedule (incl. API and website deals), duration, buffer, timed-appointment limit and max capacity.
- admin/controls.md › Customer Preferences menu: Index of the Customer Preferences menu with a one-line purpose for each entry (contact types, cancel reasons, contracts, communication, sources, divisions, email/form templates, flags, notes, prepayment, estimation units, renewals, regions, skip reasons, structures, sub-property types, voice messages).
- admin/controls.md › Service Types list and editor: Service Types list and full editor: frequency, contract lengths, allowed products, commission %, billing terms/frequency, minimum charges, initial/recurring invoice templates and production value, skills, Fill Routes buffers, reservice, reminder/follow-up settings, sales visibility.
- admin/controls.md › Office Info: Office Info: company/office names, contact, SMS number, email domain authentication, time zone, legal entity, authorized contacts, invoice address, physical location (chemical base and route start/end), territories, logo and map position.
- admin/controls.md › GL Accounts and Office Preferences: GL Accounts and office Preferences: contract defaults, default cancel reasons, scheduling/routing options, statement layout, ZIP tax, net days, invoice consolidation, portal payment limits/renewal/plan display/tips, ACH returns, PO auto-freeze, soft declines, red notes, commission basis, auto scheduling, leads, sales reps 2/3, 2FA, brand colors and month closing.
- admin/controls.md › Route Regions and Skip Reasons: Route Regions (name-only labels, not territories) and service Skip Reasons (system reasons Auto-Skipped, Prepay Upsell, Unspecified).
- admin/controls.md › Admin Billing / Usage: Admin Billing: the company's own FieldRoutes account summary, invoices and payments, payment card, SalesRoutes add-on status (frozen) and SMS/voice/routing usage rates; separate from customer billing.
- admin/findings.md › Route Templates govern scheduling capacity: Route Templates define appointment spots and capacity (generate, block, duration, buffer, timed limit, max capacity) and who can schedule, including API and Website Deals.
- admin/findings.md › Service Types: service, billing, dispatch, and communication policy in one definition: Service Type definition combines frequency, season, contract, allowed products, commissions, tax, minimums, separate billing frequency and invoice templates, skills and Fill Routes buffers, communications and mobile-sales visibility; plus the Service Plans list.
- admin/findings.md › Office identity, correspondence address, routing origin, and service territory are separate: Office Info keeps contact, legal identity, authorized contacts (for the FieldRoutes account), invoice address, physical route origin and territory separate; territory editor.
- admin/findings.md › Office Preferences: routing, financial behavior, and security policy: GL Accounts and Office Preferences: contract defaults, routing options, billing/tax/portal/ACH/soft-decline policy, other options (leads, sales reps, auto scheduling), two-factor policy, colors and month closing.
- admin/findings.md › Composite Stat and Office Zip Codes: Composite Stat for the sales leaderboard (metric editor never appeared) and Office Zip Codes claim/sharing rules for creating customers in areas.
- admin/findings.md › Property classification, route labels and structure hierarchy: Property Estimation Units, Route Regions, Skip Reasons, Structure Templates hierarchy and Sub-Property Types.
- admin/findings.md › Own-user configuration panels 548–551: Own User Card tabs 548-555 summarised: information, licenses, notifications, access control, picture/signature, route start/end, commission rates, deductions.
- assessment.md › 5. Scheduling, dispatch and routing: Scheduling and routing: Calendar, Job Pool, Dispatch Map, Route Builder/Templates, Fill Routes (chargeable on entry, 2,000 limit, time zones), Visual Grouping, Intelligent Routing (Equal Stop vs Auto Optimize), assignment; office endpoints/territory/ZIP policy; populated day and maps.
- assessment.md › Decision evidence still required: Acceptance scenarios still needed before fit is accepted: residential, commercial multi-property, plans/bundles, dispatch, technician execution, financial close, communications, reporting, security, compensation, automation, integration/exit.
- assessment.md › Final visual edge pass 556–558: Final edge pass: Job Pool 556 shows 34 rows (vs 29), Recommended Routes 557 empty, Cancellation Reinstatement 558 Days Frozen 7-30; visual gaps only.
- coverage-gaps.md › Verified observations: Verified-observation table by area: app breadth, customer operations, search/reports, scheduling/routing, billing, reporting, output layouts (invoice, WDO, State Chemical), sales, global/admin, sources.
- coverage-gaps.md › Acceptance checklist and available follow-up states: Acceptance/follow-up checklist of unverified items: report filters, linked properties, mobile and portal runtime, roles/2FA, scheduling enforcement, financial and automation outcomes, integrations/migration, business requirements.
- customer-populated-controls.md › Recurring Services and scheduling preferences: Subscription service and scheduling settings: service type, frequency, duration, call ahead, seasonal, follow-up, routing region, preferred tech/day/time, timeline, initial and recurring invoice summaries ($120 charge vs $360 production).
- customer-populated-controls.md › Appointments: Appointments tab and detail: two pending visits, scheduled-by, route link, subscription/stand-alone/reservice selector, completion info (tech, time on site, interior), print/follow-up/mail buttons.
- customer-populated-findings.md › Billing cadence, service cadence and production value are separate: Billing cadence (monthly), service cadence (every 90 days) and production value ($360 vs $120 charge) are separate; subscription has its own payer, AutoPay and scheduling preferences; Actions only inspected.
- domain-model.md › Dispatch and field service: Dispatch and field service: job pool, calendar, route templates/builder, visual grouping, intelligent routing, fill routes fee; conditions, target areas/issues, products, checklists.
- evidence-quality.md › Corrections verified: Corrections table: which later captures supersede loading/clipped ones (form selector 451, maps 522-526, billing/report reloads, aging 537-538, settings recaptures 540-547, communication details, customer filters, subscription billing, Job Pool 556, Recommended Routes 557, reinstatement 558, invoice 443).
- evidence-quality.md › Final edge pass 556–558: Edge pass 556-558: Job Pool right columns (34 rows), Recommended Routes empty dialog, Days Frozen slider 7-30.
- final-evidence-review.md › Business-fit conclusion: Business-fit conclusion: conditional fit; acceptance conditions are non-US billing, separate linked-property payments, payment-plan compatibility, Fill Routes cost/time zones, shared access profiles, automation scope.
- reporting/controls.md › 093-report-route-reporting — Route Reporting: Observed controls for Route Reporting (loading) (093): Meant to show per-route performance.
- reporting/controls.md › 113-reporting-locations — Location Reports: Observed controls for Location Reports landing (113): Shows where staff are, based on location data reported from the field.
- reporting/controls.md › 114-locations-all-employees — Location Reports: Observed controls for Last known location, all employees (114): The last-known-location map with 'All Employees' selected, with the same date range, Refresh and map controls.
- reporting/controls.md › 116-locations-technicians — Location Reports: Observed controls for Last known location, all technicians (116): The last-known-location map with 'All Technicians' selected, same controls as the other location views.
- reporting/controls.md › 117-location-history-demo — Location Reports: Observed controls for Location history, one employee (117): The location-history view for one employee (a demo technician record), meant to show where that person went over the chosen dates.
- reporting/controls.md › 471-audit-bad-geocodes — Audit: Customers with bad geocode: Observed controls for Audit check: Customers with bad geocode (471): One of the 19 Audit data-quality checks: customers whose address could not be placed correctly on the map.
- reporting/controls.md › 479-route-reporting-revisited — Route Reporting loaded recapture: Observed controls for Route Reporting (479): Per-route performance table.
- reporting/controls.md › 480-route-reporting-results — Route Reporting refreshed result: Observed controls for Route Reporting after Refresh (480): The same Route Reporting view after pressing Refresh: same filters and 24 columns, and the table still states there are zero entries for the captured day.
- reporting/findings.md › What is directly observed: Per-capture table of every Reporting page (six categories, 44 Office reports, Inventory, Locations, Technician/Office Stats, Form Lookup) with visible controls and what is unverified; notes which blanks were later resolved.
- reporting/findings.md › Route Reporting recaptures 479–480: Route Reporting 479-480: filters and the 24 route columns (services, time windows, start/end times, distance score, value); explicit empty result.
- routing/controls.md › Routing and scheduling control inventory: Intro: routing and scheduling control inventory from 029-039, 514-525, 556-557; nothing executed.
- routing/controls.md › Navigation and common report controls: Scheduling navigation (calendar, job pool, dispatch map, service plan management, route builder, fill routes, grouping, intelligent routing) and saved-report controls.
- routing/controls.md › Shared due-work and advanced filters: Shared due-work filters with options: special requests, pre-planned, one-time, due/follow-up dates, potential customers, pending cancels, balance, geography, service types, bundles, plans, wait-after, add-ons, flags, preferred tech/day, region, measurement, category, skills.
- routing/controls.md › Recommended Routes / customer scheduling (029): Recommended Routes dialog (029): sorting, full routes, tech/group filters, max miles, dates, skill matching and result columns; nothing booked.
- routing/controls.md › Daily planner, groups and route cards (515–517): Daily planner route cards, header buttons, time slots, Distance Score/value, plus every Route Actions menu entry and Add Routes quantities.
- routing/controls.md › Day Map (519): Day Map markers, route-state layers and map controls.
- routing/controls.md › Print Options (520): Route sheet print options: styles, groups, service notifications, paper/email criteria, overbooked services, technicians.
- routing/controls.md › Multi-Day Planner (521): Multi-Day Planner: mini calendars, tech/group filters, group by technician or day; blank workspace.
- routing/controls.md › Job Pool (031–032): Job Pool controls and columns: flag display, result cap, multi-row selection, actions, account/service/due/measurement columns; 29 vs 34 rows.
- routing/controls.md › Route Builder (034): Route Builder controls: date range, days-of-week, per-day Add Route, Apply To Checked, Save Routes.
- routing/controls.md › Fill Routes (035): Fill Routes controls: plan reuse, eligibility fraction, buffer summary, which routes to fill, route dates; execution untouched (charged per use).
- routing/controls.md › Visual Grouping (036, 522–524): Visual Grouping controls: technician vs region mode, scheduled-customer inclusion, group lists, drawing tools, Revert/Save, Hard Reset.
- routing/controls.md › Intelligent Routing and Assign Planned Routes (037–038): Intelligent Routing and Assign Planned Routes controls: route by tech/region, eligibility, Create Optimized Routes, plan-to-technician-day assignment panels.
- routing/controls.md › Dispatch Map (039, 525): Dispatch Map controls: filters, day route group, add route, marker modes, technician/route/job pool layers, legend.
- routing/controls.md › Final Job Pool columns and Recommended Routes (556–557): Final Job Pool columns (bundle, plan, skills, due, days, measurement) and centered Recommended Routes dialog 556-557; nothing booked.
- routing/findings.md › Routing and scheduling findings: Intro: read-only routing/scheduling assessment; nothing created, optimized, sent or printed.
- routing/findings.md › Evidence states and corrections: Evidence state per surface, and which later captures supersede early incomplete ones.
- routing/findings.md › Calendar and daily route operations: Calendar counts, daily route cards, route actions, reminder status, Day Map, print options and Multi-Day Planner findings.
- routing/findings.md › Due work, recommendations and service-plan rounds: Job Pool due work and lifecycle rules from the manual, Recommended Routes criteria, and Service Plan Management rounds/cycles.
- routing/findings.md › Route preparation, grouping, optimization and assignment: Route Builder, Visual Grouping counts, Intelligent Routing concepts (grouping, optimization, assignment), Fill Routes eligibility and fee caveat.
- routing/findings.md › Dispatch Map and fit limits: Dispatch Map evidence (525 partial, 526 settled) and the remaining dispatcher fit gaps (tracking, locking, optimization cost, reminders, rounds).
- routing/findings.md › Final Job Pool and recommendation recaptures (556–557): Final Job Pool 34-row state vs 29 earlier, right-column supplement and centered Recommended Routes; scheduling context canceled.
- routing/findings.md › Final Job Pool and recommendation edges 556–557: Short recap of the 556-557 edge captures and that no appointment was booked.
- sources/manual-verification.md › Prioritized handoff queue: Prioritised queue of 20 indexed manuals (customer card, properties, subscriptions, billing tab, Job Pool, Fill Routes, Intelligent Routing, Service Plan report, convenience payments, disbursements, trigger rules, access profiles, 2FA, technician stats, portal, contracts vs forms) with official URLs.
- sources/official-manual-findings.md › Job Pool: Job Pool manual: lists due work without a future appointment, missed visits return next day, Special Scheduling manual, filters, Recommended Routes, skill warnings.
- sources/official-manual-findings.md › Fill Routes: Fill Routes manual: optimises due work around existing appointments, charged on button click, 2,000 cap, no cross-time-zone routes, efficiency objective.
- sources/official-manual-findings.md › Intelligent Routing: Introduction: Intelligent Routing manual: group, optimise, assign stages; Equal Stop vs Auto Optimize; geocode/skill eligibility; possible due-date delays.
- sources/official-source-checks.md › Corroborated business meaning: Public-source corroboration table: customer card, Conditions, Equipment as site devices, Properties, Service Type vs Plan, prospect/lead/customer, grouping/optimise/assign, Fill Routes, Job Pool map, AutoPay, Convenience Payments, Forecast and cancellation reports, payments, disbursements, AR Oversight, prepayments/bundles, condition codes and appointment notes.
- sources/official-source-checks.md › Direct manuals for the observed account surfaces: Indexed manual links per account surface (customer card tabs, subscriptions, billing, notes/communication, documents, appointments, invoices, properties, conditions, equipment, admin tab, Job Pool, routes, plans, AutoPay, credits/collections, batches, convenience payments, stored cards, disbursements); indexed only, not read.
- user-management.md › Information (548): Information tab fields: identity, recruiter, roaming/regional scope, password reset, commission rates, user type, experience, skills, supervisor, login location.
- user-management.md › Route start and end locations (553): Location tab: per-employee route start and end addresses with maps.