Using RouteLogic

1. Start here

RouteLogic has two operating surfaces: the office application and Crew Mobile. The office builds and monitors the plan. Crew Mobile gives each crew its assigned stops, property instructions, navigation, completion controls, and quality points.

The RouteLogic logo always returns to the planner. On every other screen, Back to planner performs the same action using the same wording.

2. Navigation bar

The green navigation bar is shared by every screen. Its layout and menu wording do not change from page to page.

On the planner, the center of the navigation bar also contains crew count, Today/Optimize, Add property, Reset, and Crew points.

3. Route planner

The planner is the operational home screen. It builds the complete Monday-through-Friday book and displays the optimized route for every active crew.

Primary controls

Crews − / +

Changes the number of active crews, rebuilds durable territory ownership, and resolves the week. Use this only when staffing truly changes.

Today

Shows the existing/manual order so the office can compare it with the optimized plan.

Optimize

Shows the constraint-checked RouteLogic result.

Add property

Adds a newly won property, validates its location, assigns an owner, and re-solves the plan.

Reset

Returns the current view to its baseline data. Treat reset as a recovery action, not routine navigation.

Points

Opens the office quality dashboard and pending review queue.

Day and scope controls

Select Monday through Friday above the map. Each tab shows the planned hours for that day. This day summarizes the selected day; Full week aggregates the five-day result.

Crew cards

Each card shows stops, drive time, on-site time, finish time, and crew size. Select a card to isolate that crew on the map and open its numbered destination panel. Select it again or close the panel to restore the full valley view.

4. Map and route lines

The line motion follows travel direction. The solid and dashed paths always use the selected crew’s color; a blue crew never receives a red return path.

Selecting routes and stops

1. Select a crew card or click its route line.
2. Use the numbered destination list to review the exact order.
3. Select a numbered pin to highlight the matching destination card.
4. Close the destination panel to return to all crews.

Property and service points

The property pin identifies the actual parcel. The driving route ends at the validated curbside service point. A small connector can appear between them because the truck parks at the road and the crew walks onto the parcel.

Use Parcels to show or hide parcel boundaries. Parcel data is intentionally visible only at useful zoom levels.

5. Properties and search

Searching

Enter a street address in the map search field, choose the correct result, and RouteLogic places a temporary marker at the result. Search does not add the address to the customer book.

Adding a property

1. Select Add property.
2. Enter the property name, street address, expected man-minutes, visits per week, and access information.
3. Verify the parcel and curbside service point.
4. Save. RouteLogic assigns durable crew ownership and re-solves the week.
5. Review notifications and the affected crew-day before publishing operational changes.

6. Crew points and quality reviews

Points recognize documented, accepted work. Finishing faster contributes exactly zero points.

Office dashboard

1. Select Points.
2. Select a crew from the left side.
3. Review earned points, pending points, completed visits, and the rolling four-week standing.
4. Open each pending property and grade all four quality fields.
5. Select the review outcome and finalize only after the work is verified.

Accepted work uses a 1.0 gate, corrected-after-coaching uses 0.5, and failed or falsified closeout uses 0. Safety, hazard, damage, injury, and near-miss reporting must never reduce the score.

The crew sees its own weekly points. The office sees all crews. RouteLogic deliberately avoids a public first-to-last leaderboard.

7. Priority notifications

The bell shows exceptions that require office attention:

• Route split or locality/freeway constraint violations.
• Crew-day shift capacity violations.
• Urgent or emergency dispatches still active.
• Quality reviews pending more than 48 hours.
• An optimizer run that did not finish in a publishable state.

Select a notification to open the relevant screen. Mark all reviewed clears the unread badge but does not delete the underlying issue; an unresolved condition can appear again when its identity changes.

8. Monthly calendar

Calendar repeats the approved weekly book across the visible month so the office can see every crew-day without opening five separate planner tabs.

1. Open Calendar from Settings.
2. Use the arrows to move one month backward or forward. Use Today to return to the current month.
3. Select any date.
4. Review every active crew, stop count, total man-minutes, destination order, address, and property workload in the right panel.

Weekend cells have no standard route. Same-day dispatches are incorporated into their assigned weekday. Truly date-specific recurrence and multi-device updates require the shared production backend.

9. Rebalance book

Rebalance changes long-term crew ownership after customer churn. It is not the daily route optimizer.

Controls

Properties / Crews

Sets the book size used for the annual or quarterly ownership model.

Build the book

Creates the baseline crew territories.

Properties lost / won

Models the churn that occurred during the period.

Disruption budget

Caps how many existing properties may change crews.

Protect crews

Locks selected crew books so repairs cannot move their properties.

Repair the book

Fits new work and fixes territory violations within the disruption budget.

Reroute from scratch

Ignores continuity and computes an entirely new ownership model.

Use Back to planner or select the RouteLogic logo when finished.

10. Same-day dispatch

Dispatch evaluates new work against each crew’s current progress, location, territory, remaining shift, and return path.

1. Enter and verify the incoming job address.
2. Enter the job name, man-minutes, weekday, priority, and division.
3. Set each crew’s completed-stop count and current status.
4. Select Find eligible crew.
5. Read the recommendation, detour, projected finish, and any required override.
6. Assign now, or save the work to the approved job pool for automatic end-of-route assignment.

Emergency override can relax ordinary insertion rules, but it never silently hides the violation. Boulder City should not inherit North Las Vegas work simply because one crew appears idle.

11. Data editor

The Data editor controls the inputs the solver trusts. Changes save as you work.

Properties

Edit names, addresses, areas, divisions, compatible owners, man-minutes, visit frequency, gate codes, coordinates, and service points. Use the map to verify any moved pin.

Crews

Edit crew names, divisions, and colors. Changing a crew’s division releases incompatible properties for reassignment within their proper division.

Rules and costs

Configure shift length, active crews, maximum crew size, freeway and surface assumptions, locality limits, rescue detour, finish balance, hourly cost, and optimizer limits.

Save and backup

Export a dated JSON copy before structural changes. A connected file can receive later saves directly in supported browsers.

12. Sandbox and publishing

Sandbox is a separate copy of the operating book. Crews always read Live data.

1. Select Sandbox in the navigation bar.
2. Select Copy live data in to start from the current production book.
3. Make and evaluate changes.
4. Choose Discard sandbox to throw the experiment away, or Publish to live to replace Live.
5. Read the full confirmation pop-up. Select OK only after reviewing routes, alerts, and data.

13. Crew Mobile

Crew Mobile presents one crew and one day. The desktop page centers the phone and keeps simulated GPS, signed-in crew, weekday, and the user guide beneath it. On a phone, the app uses the available screen.

Destination cards

Each card shows stop number, property, address, expected man-minutes, drive time, gate code, and a direct navigation icon. Selecting the card opens full access notes, water shutoff, contact, estimate, crew size, navigation, and completion controls.

Completing work

1. Navigate to the destination.
2. Check in after GPS confirms the property.
3. Complete the work and select Mark complete.
4. Review the completion animation and immediate points.
5. After the final planned job, wait while RouteLogic checks approved same-division work.
6. Complete the automatically assigned job, or use Head to yard only after RouteLogic issues clearance.

The eligibility calculation includes actual completed work, current-to-job travel, conservative service time, the drive back to the yard, a protected return buffer, locality, freeway rules, and division. The crew cannot opt out by simply skipping a request button.

Star points

The star shows earned weekly points. Select it for earned, pending, recent visits, and private four-week quality standing. Simulated completions are labeled practice and never enter the live score ledger.

English / Spanish

Select ES or EN to switch field instructions without changing the property data or route.

14. Routing rules

RouteLogic treats the following as constraints, not suggestions:

• Maintenance, Irrigation, and Arbor work remain in separate qualified labor pools.
• No interior freeway re-entry after the crew reaches its work territory.
• Only the initial outbound and final yard-return freeway legs are permitted.
• Maximum local distance and time between jobs.
• Maximum crew-day territory diameter.
• Approved geographic corridors only.
• No shift overrun.
• Protected time remains for the final drive to the yard.
• Balanced finish times within each division’s configured tolerance.
• Same-day rescue work must remain within its detour and vicinity limits unless explicitly overridden.

If the work cannot fit, RouteLogic reports that another crew or route split is required. It does not quietly manufacture a bad route.

15. Backup and recovery

• Export JSON before publishing sandbox changes, resetting data, or performing a major rebalance.
• Name the file with the date and whether it is Live or Sandbox.
• Import only a RouteLogic JSON file containing properties and crews.
• Remember that browser-local data is device-specific until the shared backend is deployed.
• Do not clear browser site data without a current export.

16. Troubleshooting

The map has no streets

The online basemap is unavailable. RouteLogic falls back to bundled Clark County geometry; routing data can still render.

A route is temporarily straight

The road geometry is still loading or unavailable. The immediate straight segment is replaced when the road service responds.

A pin is slightly off the route

The pin marks the parcel while the route reaches the validated service point. This can be correct.

The points dashboard is zero

Practice completions never enter real totals. Real completions appear after Live GPS check-in.

Another device does not update

The current build synchronizes browser tabs on one device. Different phones and office computers require the shared backend.

Old data appears

Confirm the correct Live/Sandbox mode, then refresh. Import the latest backup if local browser data was cleared.

17. Operating checklist

Every morning

• Review the notification bell.
• Confirm crew count and staffing.
• Check every crew-day for locality, shift, and split alerts.
• Confirm urgent dispatches.

During the day

• Use Dispatch for incoming work.
• Do not manually send a free crew across the valley outside the rescue radius.
• Monitor completion progress without rewarding speed.

End of day

• Review pending quality work.
• Resolve urgent dispatch status.
• Investigate materially incorrect service times before changing estimates.

Before publishing or rebalancing

• Export a backup.
• Use Sandbox.
• Review all notifications and affected routes.
• Read the publish confirmation and verify the target is Live.