Gate Check-In/Out Log
Capture every gate-in and gate-out event at the guard shack, start a dwell timer the moment a trailer arrives, verify the seal at departure, and require a coordinator to approve each close - so your yard stops being a security and timing blind spot.
A simple gate log where guards capture check-in and check-out events (driver, carrier, trailer, seal, loaded/empty), a live dwell timer for every trailer in the yard, a seal-mismatch flag with a required photo, and a coordinator approval gate that closes the record - plus a clean CSV export of the whole log.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account
- A computer or tablet at the guard shack with a browser
The problem this kills
Right now, your yard is a blind spot. A driver pulls up to the guard shack, a name and trailer number get scribbled on a clipboard or typed into a spreadsheet that nobody else can see in real time. When did that trailer actually arrive? Has it been sitting for six hours racking up detention charges? Did anyone check the seal before it rolled out the gate? When the carrier disputes a detention bill, or security asks who was on the lot last Tuesday night, you're flipping through paper or guessing.
The cost is real: detention and demurrage charges you can't prove or dispute, trailers that go missing for a shift because no one noticed they never left, security gaps where a sealed load leaves with a broken or swapped seal, and a yard coordinator who spends half the day on the radio asking "is trailer 4471 still here?"
A gate log fixes the blind spot. Every arrival and departure is timestamped, every trailer in the yard has a running dwell timer, every seal is checked at the gate, and nothing closes without a human signing off.
What you'll build
A clean, fast web tool the guard uses at the shack and the coordinator uses from their desk:
- Gate-in capture - the guard records driver name, carrier, trailer number, seal number, loaded or empty, and the system stamps the exact arrival time and opens a yard record.
- A live in-yard board - every trailer currently on the lot, each with a dwell timer counting up so long-dwelling trailers jump out at you.
- Gate-out capture - at departure the guard re-reads the seal; if it doesn't match the seal logged at check-in, the tool flags a mismatch and requires a photo before it will continue.
- A coordinator approval gate - check-out events don't close the trailer's record until the yard coordinator reviews the seal verification and approves the close. The guard captures; a person confirms.
- A complete, exportable gate log - searchable, audit-ready, and downloadable as a CSV in the exact columns your yard management or TMS expects.
What's inside the Implementation Plan
A step-by-step runbook you paste straight into an AI coding agent (Claude Code). You don't write code - you describe your yard and answer questions, and the agent builds the tool with you.
It opens by interviewing you about your actual yard - your carriers, how you name trailers and seals, your typical and peak gate volumes, who guards the gate and who coordinates the yard, and your real edge cases (drop trailers, bobtails, swaps, after-hours arrivals). It reflects a short tailored spec back to you and waits for your thumbs-up before it builds anything, so you get a tool shaped around your yard - not a generic template you have to bend to fit.
From there it walks you through standing up the database, the guard capture screens, the dwell timer and in-yard board, the seal-mismatch flag with photo capture, the coordinator approval gate, login and audit trail, and finally the CSV export and a full end-to-end test.
The governance it includes (this is the point)
This isn't a toy spreadsheet replacement. The plan bakes in the controls a real yard needs:
- Login so only your guards and coordinators can use the tool.
- Row-level security so you only ever see your own organization's yard data.
- A complete audit trail - who logged each gate event, who approved each close, and exactly when.
- A hard human-in-the-loop approval gate - the guard captures the check-out and the seal read, but the trailer record only closes after the coordinator reviews and approves it.
- Duplicate guards - the same trailer arrival can't be logged twice (the dedupe key is trailer number + gate-in timestamp), so a double-tap or a re-radioed event won't create a phantom record.
- Seal integrity - a seal that doesn't match forces a flag and a photo, so a compromised load can't quietly leave the yard.
Who it's for
Gate guards who need a fast, idiot-proof capture screen at the shack, and yard coordinators who need a live view of what's on the lot, who's been sitting too long, and a clean sign-off before anything leaves. If you run a DC, a plant gate, a cross-dock, or any yard where trailers come and go and detention and security matter, this is for you.
You've got this - paste the first prompt and let the agent interview you about your yard.