π Run parameters β how this run picks its stops
A run picks orders that still need its window credit. Overdue orders are always flagged β° β they join a run only via the two switches above. Saving gas outranks overdue pressure; that's the policy. Danger thresholds unlock the midday sweep.
π΄ You're offline β new stops are added while connected. Everything about today's prepared stops is already on this phone.
Bulk in a hurry? Paste one stop per line as
address | label | name | notes:
π· From an ABC screenshot
Screenshot an ABC Legal order screen, pick it here, and the app reads the order for you β every field lands on a confirm screen first; nothing is saved until you tap Save. Works while connected; the order then lives on this phone like any other.
βοΈ ABC attempt rules
From ABC Legal's policy ABCOP-POL-07 rev 1.8: attempts at least every 48 hours, every 24 on rush jobs (Rule 10) β the β° chips and the "next attempt due" lines run on these. No attempts before 7:00 AM or after 10:00 PM (Rule 6f) β the app flags those in the attempt log, never blocks them.
Import a file (CSV / Excel)
Agencies and courts hand over spreadsheets β load a whole day at once. Happens while connected.
Match the file's columns to the planner's fields:
Saved places
π Serve Route Planner
Log attempt
One tap checks you in β time + outcome. That's the fuel for the windows and the cadence clock; ABC's app keeps the formal record.
π Getting GPSβ¦
π Set the pin
Map loads while connected. In the field, βUse my locationβ sets the pin where you're standing β usually the best fix of all.
π· Confirm the order
Read from your ABC screenshot β check every field. Nothing is saved until you tap Save.
β Court Requirements weren't visible in this screenshot (they sit at the bottom of the ABC page) β check them in ABC before serving.
Windows ABC already shows as done (Vary Your Attempts)