RouteLogic logo
Returns directly to the Route planner from anywhere.
Every screen, control, decision, and field workflow in one reference.
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.
The office application requires an office email and password — no data is shown until you sign in, so opening the web address alone never exposes the customer book. Crews open Crew Mobile and enter their own PIN. Sign out from the bottom of the Settings menu (office), or the top-left corner of the screen (Crew Mobile).
Closing the tab signs the office out. An office session lasts only as long as the browser tab, so a machine left unattended in the office cannot be walked up to and used. Opening the application again asks for the password. Crew Mobile is deliberately the opposite: a crew stays signed in on their phone across closing the app and going offline, because re-entering a PIN at every stop would be unworkable in the field.
The planner is the operational home screen. It builds the complete Monday-through-Friday book and displays the optimized route for every active crew.
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.
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.
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.
Direction chevrons. Small arrows sit along each route line and point the way the truck actually drives — toward a stop as the crew arrives, and away from it as they leave for the next job. This makes the "going" and "leaving" halves of a route easy to tell apart at a glance. Zoom in to see them clearly.
The property information card is fixed in place — it no longer drifts if you brush over it — and closing it lets the route panel rise back up.
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.
Once saved, searching that same address again drops the pin exactly where you placed it — it never reverts to the geocoder’s guess. Drag and confirm again any time to move it. Searching does not add the address to the customer book; to add a property, use Add property below.
Three people working for two hours equals 360 man-minutes. Incorrect man-minutes corrupt crew sizing and finish-time calculations.
Points recognize documented, accepted work. Finishing faster contributes exactly zero points.
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.
The bell shows exceptions that require office attention:
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. A short chime plays when a new priority notification arrives — different from the crew-activity tone below.
The Crew activity button at the bottom-right corner opens a live feed of every crew’s check-ins and completions as they happen across all devices. A soft tone plays each time new activity arrives.
Open Activity history from the Settings menu. This is a dedicated calendar — separate from the routing Calendar — that permanently stores every crew check-in and completion by day. Days with activity show a count; select any day (past or today) to read every event: which crew, what they did, the property, the time, and the man-minutes. Use it to look back on any date after the live feed has been cleared.
Sounds can be silenced on a device; ask your administrator to turn the tone off if a quiet office is preferred.
Calendar repeats the approved weekly book across the visible month so the office can see every crew-day without opening five separate planner tabs.
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.
Rebalance changes long-term crew ownership after customer churn. It is not the daily route optimizer. The planner answers "what does Crew 3 drive on Tuesday?"; Rebalance answers the quarterly question "we lost some properties and won others — who has to change crews, and how do we disturb the fewest?"
Why the map. The map shows the churn visually: every property is colored by its owning crew, a property that changes hands gets a white ring, and a newly won property gets an amber ring. You can literally see how contained a repair is.
Editing "properties lost / won" or the disruption budget does nothing on the map until you select Repair the book (or Build the book). That is expected — set the numbers first, then run it, and the map updates.
Use Back to planner or select the RouteLogic logo when finished.
Dispatch evaluates new work against each crew’s current progress, location, territory, remaining shift, and return path.
Crew progress is where you tell RouteLogic where each crew is right now, because there is no live truck GPS yet. For every crew you set how many stops they have finished and their current status (at a job, returning on surface streets, or returning on the freeway). Dispatch uses that to pick the crew that is best positioned — nearest and least disruptive — to take the new job. Once you assign it, the emergency job appears on that crew’s phone.
Separate trades are solved as separate labor pools. RouteLogic never assigns a job across divisions—not even as an emergency override.
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.
The Data editor controls the inputs the solver trusts. Changes save as you work.
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.
Edit crew names, headcount, and colors. Crews also carry a division; changing it releases incompatible properties for reassignment within their proper division.
This tab holds the values the solver treats as hard limits. Each has a sensible default; change them only when the real operation changes:
An optional heavier optimizer can run on the office machine for the most exhaustive solve; it is a power feature only, is never required for daily use, and never runs on a crew’s device. If it is not running, RouteLogic simply uses its built-in solver.
Export a dated JSON copy before structural changes. A connected file can receive later saves directly in supported browsers.
Sandbox is a separate copy of the operating book. Crews always read Live data.
Every confirmation in RouteLogic — publish, delete, discard, remove — is now an internal styled dialog, never a raw browser pop-up.
It replaces the live property book, crews, routing rules, and settings. Crew Mobile and the planner begin using the published data immediately.
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.
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.
Check-in only unlocks when the phone confirms the crew is at the property, and the line above the button always says why it is not unlocked yet:
RouteLogic accepts the crew as on site if they are near either the property pin or the parking/service point, and it widens the allowance to match the phone's reported GPS accuracy — so a poor fix between buildings does not block a crew who is genuinely standing on the property. A wildly inaccurate fix still cannot unlock a check-in from across town.
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, and freeway rules. The crew cannot opt out by simply skipping a request button.
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.
Select ES or EN to switch field instructions without changing the property data or route.
Sign out sits in the top-left corner of the screen, with Signed in — C5 on the right of the same row. Below that on the left is the crew name and its day line (day, stops, crew size); on the right, stacked, are the ★ points button, the ES / EN language switch, and the sun/moon theme button beneath it. Nothing floats over the job list or the Check in button.
Signing out clears the crew from the device and returns to the PIN screen. A PIN is always required — there is no code-free preview.
An office user (signed in to the office application) who opens Crew Mobile sees the app with the navigation bar, so they can return to the planner. This is only for office accounts; a crew signed in with a PIN never sees office navigation, and previewing never changes what a crew sees.
RouteLogic treats the following as constraints, not suggestions:
If the work cannot fit, RouteLogic reports that another crew or route split is required. It does not quietly manufacture a bad route.
It contains gate codes and manager phone numbers. It is safe on the company’s own machine, but it should not be emailed or shared casually. The Save & backup tab only writes to your own device — nothing is uploaded by it.
Open Admin settings from the Settings menu. It controls which parts of RouteLogic this company uses. The route planner, map, calendar, rebalance, zones, dispatch and data editor are always on and cannot be switched off — everything a routing engine needs stays.
Crew Mobile is the master switch for field operations. Switching it off also switches off Crew points & quality reviews, Live crew activity and Activity history, because all three are fed by crews checking in from the field. Each of those three can also be switched off on its own.
Use this when a company routes with RouteLogic but runs its field operation somewhere else. With Crew Mobile off, the app is a routing engine and nothing else: the crew app refuses to open, the Points button leaves the planner, the Crew activity button disappears from every office screen, and Activity history leaves the menu.
Changes are staged: the page lists what you have altered and shows the menu you are about to create, and nothing is applied until you select Save. Switching off Crew Mobile asks for confirmation first.
Open Route sheets from the Settings menu, or select ⎙ Print on the planner to print exactly the day you are looking at. If a crew is selected on the planner, the button prints that crew only.
One crew-day per page. A crew with no work that day is not printed, so a five-crew Monday is five pages.
Every stop in the scheduled order, numbered, with the address first — the association name is underneath it, because the address is what the crew navigates to. Each stop also carries the start time, the gate code in large type, the man-minute budget, how long the crew is expected to be on site, drive time from the previous stop, the on-site contact and phone, access notes and the water shutoff location. A time window prints on the stop it applies to.
The header shows yard-out and yard-in times, total drive time, road miles and total time on site. If a day does not fit the shift, the sheet says so at the top rather than sending a crew out on a day the office already knows is over.
Each stop has blank boxes for actual in/out times, initials, and a done tick, and the page ends with foreman and office signature lines. This is what makes the sheet a record the office can enter afterwards, rather than a handout.
The language switch changes the labels and the property instructions — access notes and water shutoff locations print in Spanish where a translation exists, and fall back to English where one does not, so a gate instruction is never blank.
Route sheets are deliberately never switched off by Admin settings. They are the way to run RouteLogic with no phones at all: the office routes, prints, and hands out paper exactly as before.