The office drops its monthly worklist spreadsheet on the planning page and gets a proposed day-by-day plan for the month: objects matched to master data, visits grouped by location, real driving times between stops. Nothing is written to the live schedule until a human reviews and applies it, and every run keeps progress and history.
What ports as-is
- The propose-then-apply schedule model (proposed rows carry their run and stay out of live views until applied)
- The durable background run pipeline (queue, worker, progress tracker, diagnostics)
- AI extraction of an arbitrary spreadsheet layout
- The object resolver
- Travel-time and proximity services
- The review screens with run history
What we build for you
- The worklist columns and the buyer's own object numbering
- Matching rules and thresholds
- Working-day and slot defaults
- The maps API key
- The review policy for unmatched rows
