Job/Labor Time Clock
Let operators clock on and off a specific work order operation - start, stop, qty, scrap - so you capture true labor hours per job for costing, efficiency, and quoting instead of guessing.
Operators clock on an operation, record qty and scrap, clock off; the supervisor reviews and approves each shift's labor; then you export a clean labor-by-job CSV for costing and payroll.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account
- A list of open work orders and their operations (CSV or Google Sheet)
- Your operator list (CSV or Google Sheet)
The problem this kills
Right now you probably allocate labor to jobs by guess. Someone spreads payroll hours across work orders at month-end, or operators scribble times on a traveler that nobody can fully read, or you just assume "8 hours, evenly split." Then you quote the next job off numbers that were never real.
The damage is quiet but expensive: jobs that lose money look profitable, your standard times never get corrected, and your quotes drift further from reality every quarter. When a customer asks why a part costs what it does, you don't have a defensible answer - just an allocation formula.
What's missing is the simplest thing: a clean record of who worked on which operation of which job, from when to when, how many good parts they made, and how many they scrapped.
What you'll build
A shop-floor time clock your team actually uses. An operator picks their name, picks an open work order and the operation they're running, and hits Clock On. When they finish (or switch jobs) they enter good quantity and scrap and hit Clock Off. The tool stops one person from being clocked on two jobs at once, makes them log indirect or idle time explicitly, and flags anyone who forgot to clock out.
At the end of the shift the supervisor opens a review screen, fixes the messy stuff - missed clock-outs, overlaps, obvious mistakes - and approves the shift. Only approved labor flows into the export. That export is a clean labor-by-job CSV your costing and payroll systems can ingest.
What's inside the Implementation Plan
The plan is a complete runbook you paste into Claude Code (an AI coding agent). It builds the whole tool step by step, and it opens by interviewing you about your business - your operations, your work order and operation numbering, how your operators are identified, your shift rules, your indirect-time codes, and your messy edge cases - so the tool is tailored to how your shop actually runs, not a generic template. You confirm a short spec, then it builds from there.
Inside you get: the discovery interview, the data model, the operator clock-on/clock-off screens, the "you're already clocked on" guard, the missing-clock-out flagging, the supervisor approval gate, the labor-by-job CSV export, and a no-API fallback that imports your work orders and operators from a CSV or Google Sheet and exports labor as CSV - so it's fully buildable today even if you have no integration to your ERP.
The governance it includes (this is the point)
- Login so only your team can use the tool.
- Row-level security so each shop or organization only ever sees its own data.
- A complete audit trail - every clock event, edit, and approval recorded with who and when.
- A human-in-the-loop approval gate - the supervisor reviews and approves each shift's labor before anything is exported to costing or payroll.
- Duplicate guards - the same clock-on can't be recorded twice (dedupe key = operator + operation + clock-on timestamp), and one person can't be clocked on two jobs at once.
Who it's for
Operators who need a dead-simple way to clock on and off jobs. Supervisors who need to clean up and approve labor before it counts. Cost accountants who finally get true labor hours per job for costing, efficiency, and quoting.
You've got this - paste the first prompt and let the agent interview you.