| Property | Address | Active | Area | Division | Crew owner | Service days | Time window | Man-min | Visits/wk | Gate code | Lat | Lon |
|---|
Property instructions
Select a property row or map pin to edit its crew information.
Man-minutes, not clock minutes. A job that takes 3 people 2 hours is 360, not 120. Crew sizing is calculated from this number — get it wrong and every route built on it is wrong.
Lat and lon are two numbers in a table until you can see them. Zoom in far enough and you get street names and house numbers, which is how you catch the property that was typed in a block off — or on the wrong side of the freeway, which is what actually costs a crew twenty minutes.
Divisions
Crews and properties can only be matched inside the same division.
| Crew | Division | Color | Headcount | Onsite | Scheduled |
|---|
4 crews are scheduled. Use each crew's switch above. RouteLogic assigns work only to active crews in the property's division.
All of these as a spreadsheet
Download the sheet pre-filled with what is set now, change what you need in Excel, and upload it back. Blank a value — or delete its row — to leave that setting alone. You will see every change listed before anything is saved.
Effect of these settings
Advanced deterministic optimizer
Uses CP-SAT weekly assignment, exact route ordering, adaptive large-neighborhood search, and a hard publication gate. It will refuse an unsafe book instead of hiding a violation.
What the last import changed
Arrived
Ended
Auto-save to a file
Pick a .json file once. Confirmed editor saves also update
that file — no repeated downloads.
Export a copy
Downloads the current dataset as JSON. Keep one before any big change.
Import a property spreadsheet
Load the whole book from an Excel workbook or a CSV — property name, address, budgeted time, visits per week, service days, crew, gate code. Reads a Route4Me export as-is, understands hours or minutes, and builds your crews from the sheet’s own Crew column.
An .xlsx with several tabs is fine — you pick which one before anything is imported. Older .xls files need File → Save As → .xlsx first.
Find missing locations
Any property without a map location gets one from its address. Checks the 19,000 Clark County association parcels built into the app first, so most of the book resolves instantly and without the network; only what's left is asked of the county.
Runs automatically after a spreadsheet import. Safe to run again — anything already located is remembered.
Place the last few by hand
A handful of addresses exist but are in neither the county's parcel records nor the public map data — nothing can find them automatically. Download them as a spreadsheet with a Google Maps link on every row, paste the coordinates in, and load it back.
Only Latitude and Longitude are read — budgets, crews and service days are not touched. Rows left blank are skipped, so it is fine to do a few at a time.
Import a RouteLogic backup
Load a previously exported JSON file. Replaces everything in the current mode.
Reset
Throws away every edit in this mode and restores the baseline dataset.
Where this lives today: your browser, plus the shared cloud copy this office account syncs to. Publishing sends the book up; other signed-in office devices pick it up. Clearing site data wipes the local copy only — the published one survives. The file you connect above is a third, independent copy, and worth keeping before anything big.
Copy Live → Sandbox
Start from exactly what the crews are running, then experiment freely.
Discard sandbox
Throw the scratch copy away. Live data is never touched.
Publish Sandbox → Live
Overwrites what the crews see with the sandbox. One way, and it asks first.
Sandbox is a completely separate dataset. Editing it cannot change a route anybody is driving. Test a shift length, a rate, a crew count, a new property — see the result on the Rules tab — then either publish it or throw it away.