Customs Broker Handoff Tracker: Stop Chasing Import Docs by Email

The problem this kills

Every import entry is a little paper chase. The commercial invoice is in one email, the packing list is in another, the bill of lading came as a forwarded PDF, the ISF data is in a spreadsheet, and the broker keeps emailing back asking for the one thing nobody attached. Documents dribble out one at a time, the broker can't file until the set is complete, and the entry sits — sometimes long enough to blow past the ISF deadline (the importer-security filing that's due before the cargo even sails) or the entry filing window, which turns into holds, exams, and per-day storage fees at the port.

The worst part is that none of it is hard. It's just uncounted. Nobody can see, at a glance, which of the eight documents this entry needs are actually in hand, which are missing, and how many hours are left on the clock. So it gets managed in a reply-all thread and a coordinator's memory — and the day one slips is the day a container racks up demurrage.

You don't need a six-figure customs platform to fix this. You can build the tracker yourself, this afternoon.

What you'll build

An internal web tool your import team logs into. For each entry you create a record keyed to its entry or PO number, attach the documents as they arrive (commercial invoice, packing list, bill of lading, ISF data, certificates of origin, and whatever else your entry type needs), and the tool checks the set against your completeness rules — the exact document checklist for that entry type, mode, and country. Anything missing is listed in plain words; the ISF and entry deadlines sit on a countdown so a slipping entry turns red before it's late.

When the packet is complete, your coordinator reviews the whole set on one screen and approves the handoff — the human gate. Only then does the packet go to the correct broker (with a clean email and the files attached or a secure link), and the entry moves into a status board you track all the way to customs release: submitted, accepted, exam, released. It even handles the messy parts: an entry with no broker assigned yet, a document that arrived but is the wrong version, and a duplicate entry someone tried to create twice for the same PO.

What's inside the Implementation Plan

The downloadable plan is a single markdown file you paste into an AI coding agent. It opens by interviewing you about your own import process — your entry types and the exact document checklist each one needs, what your broker calls a "complete" packet, how you currently track ISF and entry deadlines, your broker contacts, your naming for entry and PO numbers, and your real edge cases — and then it reads a short spec back for your thumbs-up before it builds anything. That's the difference between a tracker shaped to your lanes and a generic template you have to fight.

From there it walks the agent through the data model (entries, documents, brokers, completeness rules, status history), the document uploader backed by file Storage, the completeness-check engine, the deadline countdown, the coordinator review-and-approve screen, the broker handoff email, and the status board to release. Every step ends with a ready-to-copy prompt. There's a full "No API yet?" path: import entries from a CSV/Google Sheet and export a clean entry-and-status CSV in the exact columns your system of record expects — so you never have to touch a broker API or an ABI connection to ship.

The governance it includes (this is the point)

In customs, who-signed-off and when is the compliance story. The plan builds it in: a login so only your team can use it; row-level security so each organization only ever sees its own entries; a complete audit trail of who attached, checked, approved, sent, and updated each entry, and when; a hard human-approval gate so no packet is sent to a broker until a coordinator reviews the complete set and approves the handoff; and a duplicate guard (on entry / PO number) so the same entry can't be created or handed off twice. An incomplete packet physically cannot be approved or sent — the missing-doc check blocks the handoff button until the rules pass or a coordinator approves a documented exception. That's the trail an auditor or a CBP request wants.

Who it's for

Import coordinators, logistics and trade-compliance teams, and broker clients who own the documents-to-release process and are tired of finding out an entry was incomplete only when the broker emails back. If you can explain to a new hire which documents an entry needs and what makes a packet ready to file, you can build this — no developer required.

You've got this — open the plan, paste the first prompt, answer a few questions about how your imports actually run, and you'll watch your first entry packet check itself and light up the deadline clock.