Manual Milestone Check-in Logger
A mobile-friendly logger where drivers and dispatch record pickup, in-transit, and delivered milestones for carriers that have no automated tracking feed - with a dispatch approval gate before any shipment closes.
Drivers and dispatch log shipment milestones from their phone; each shipment gets a clean timeline; dispatch reviews and approves the delivered milestone with proof of delivery before the shipment closes and the customer-facing status updates.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account
- A phone or laptop the drivers can open a web link on
The problem this kills
Some of your carriers and owner-operators have no tracking feed at all. You find out where a load is by calling the driver, texting back and forth, and writing the answer on a whiteboard or a spreadsheet that's already out of date by lunchtime. When a customer calls asking "where's my freight?", you're guessing.
Worse, the moment that actually matters - the delivery - lives in a blurry photo on someone's phone and a "yeah it's dropped" text. There's no clean proof of delivery, no timestamp you'd trust, and nothing stopping two people from logging the same drop twice.
What you'll build
A short, mobile-friendly web logger. A driver or dispatcher opens a link, picks the shipment, taps the milestone (Picked up / In transit / Delivered), and adds a location, a timestamp, and optionally a photo and a geotag. Each shipment builds a tidy timeline automatically. When a delivery is logged, it does not silently close the load - it waits for dispatch to review the proof of delivery and approve it. Only then does the shipment close and the customer-facing status flip to "Delivered."
It's built to work in the cab: short forms, big buttons, and tolerant of a weak signal.
What's inside the Implementation Plan
The plan opens by interviewing you about your actual freight operation - your shipment ID format, the milestones you really track, who's allowed to log versus approve, your typical and peak load volumes, and your messy edge cases (re-deliveries, partial drops, wrong-address attempts). It reads a short tailored spec back to you and waits for your thumbs-up before building a single thing. You get a tool shaped around how your dispatch desk actually runs - not a generic template.
From there it walks you, one copy-paste prompt at a time, through standing up the database, the mobile logging form, the per-shipment timeline, the dispatch approval gate with proof-of-delivery upload, email notifications, and a CSV export of the full milestone log.
The governance it includes (this is the point)
- Login so only your team and drivers can open the logger.
- Row-level security so each company only ever sees its own shipments and milestones.
- A complete audit trail - every check-in records who logged it, from where, and exactly when.
- A human approval gate - a delivery milestone is a draft until dispatch reviews the proof of delivery and approves it. Only an approved delivery closes the shipment and updates the customer-facing status.
- Duplicate guards - the same shipment + milestone type can't be logged twice, so you never get two "delivered" entries fighting each other.
Who it's for
Dispatchers, drivers, and owner-operators running freight on carriers with no tracking feed - anyone who's tired of chasing status by phone and wants a single trustworthy timeline per load.
You've got this - paste the first prompt and let the agent interview you.