PM Route Batching by Geography
Group due preventive maintenances by zone into efficient day-batches so techs clear clusters of nearby sites instead of crisscrossing town — with a planner approval gate before anything hits scheduling.
A login-protected tool that turns your due-PM list into geographic batches with suggested days, lets a planner review and approve, then exports a clean scheduling-ready CSV.
Before you start
- A PM due list you can export as CSV or a Google Sheet (sites, addresses or zones, durations, due dates)
- Free Vercel, Supabase, and Resend accounts
- Claude Code installed on a Linux machine
The problem this kills
Your techs are driving all over the map. A preventive maintenance (PM) comes due at one site, another comes due across town the same week, and somehow they end up on opposite days — so a tech burns half the morning in traffic instead of turning wrenches. Meanwhile the planner is squinting at a spreadsheet, trying to mentally group nearby sites while making sure nothing slips past its due date. It's slow, it's error-prone, and it quietly leaks hours of paid drive time every single week.
This tool does the grouping for you. Feed it the list of PMs that are coming due, and it clusters them by zone into tidy day-batches that respect each PM's due window and keep day lengths sane — then it hands the planner a clean proposal to approve.
What you'll build
A small, private web app for your maintenance planning team. You paste or import your due-PM list. The tool groups the work by geography (your zones, regions, or postal areas), proposes which sites go together on which day, and shows you the estimated time per day so no route is overstuffed. The planner reviews the proposed batches, tweaks if needed, and approves. Only approved batches become a scheduling handoff — and you get a clean CSV in the exact columns your scheduling system expects.
What's inside the Implementation Plan
The plan opens by interviewing you about your business — your zones, your address and asset-naming conventions, your PM cycles, your typical and peak volumes, and your real approval rules — so the tool is tailored to how you actually work, not a generic template. Then it walks you, one copy-paste prompt at a time, through building the database, the import, the batching logic that respects due windows and balances day length, the planner review-and-approve screen, the audit trail, and the CSV export. Every step ends with a prompt you paste straight into your AI coding agent.
The governance it includes (this is the point)
- Login so only your planning team can open the tool.
- Row-level security so each organization only ever sees its own sites and PMs.
- A full audit trail — who proposed a batch, who approved it, and exactly when.
- A human approval gate — the AI drafts the batches, a planner reviews and approves, and only then does anything become a scheduling handoff.
- Duplicate guards so the same PM (asset + cycle) can't be batched or released twice.
Who it's for
Maintenance planners, dispatchers, and route coordinators who own a recurring PM schedule across multiple sites and want to stop techs from crisscrossing town — without buying a heavyweight routing platform.
You've got this — paste the first prompt.