Project/Task Time-Entry Logger
Build your own internal time-tracking tool: pick a project and task, log time with a start/stop timer or paste in entries, roll it up into a reviewable daily and weekly total, confirm it, get manager approval, and export a clean CSV.
A logged-in time-tracking tool where people pick a project and task, log time by timer or manually, see a daily and weekly roll-up, confirm their day, get a manager to approve, and export approved entries as a CSV in the exact columns your system expects.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account (for approval and reminder emails)
- A projects/tasks/codes list as a CSV or Google Sheet
- A people list (names + emails) as a CSV or Google Sheet
The problem this kills
By Friday, nobody can remember what they actually worked on. Time gets reconstructed from memory, guessed against the wrong project code, or typed into a spreadsheet that three people overwrite. Billable hours leak. Project budgets drift because the numbers going in are soft. And when a manager finally signs off on a timesheet, they're approving a fuzzy total they have no real way to check.
The usual "fixes" make it worse: a shared spreadsheet with no validation, a clunky enterprise tool nobody opens, or sticky-note tallies that get entered in a panic at week's end. None of them stop a typo'd project code, a double-counted hour, or two timers running at once.
What you'll build
A small, focused web app your team logs into. Each person picks a project and a task from your real list of codes, then logs time two ways: a start/stop timer for live work, or a quick manual entry ("9:00–10:30 on PROJ-204 / design review"). The tool rolls everything up into a daily total and a weekly view, flags anything that looks off, and walks the entry through a confirm-then-approve flow before it ever becomes a submitted timesheet. At the end you get a clean CSV export in exactly the columns your payroll, billing, or project system expects.
What's inside the Implementation Plan
- It starts by interviewing you about your business. Before a single line is built, the plan makes the AI agent ask you about your real projects, task names, and code conventions, who logs time and who approves it, your typical and peak volumes, your rounding and daily-cap rules, and your messiest edge cases (split days, overnight shifts, PTO). It reads a short tailored spec back to you and waits for your thumbs-up. You get a tool shaped to how you work, not a generic template.
- A step-by-step build, each step ending in a ready-to-paste prompt.
- A data model tuned to your project/task/code conventions.
- Validation that checks every entry against your valid project codes, warns on overlapping timers, and warns on days over a sane cap you set.
- A duplicate guard so the same entry (same person + project + task + start time) can't be logged twice.
- The "No API yet?" fallback so you can build this today: pull projects and people from a sheet, push approved time out as CSV.
The governance it includes (this is the point)
- Login so only your team can use the tool.
- Row-level security so each person sees only their own entries (and managers see only their team's).
- A complete audit trail: who logged, edited, confirmed, and approved what, and when.
- A hard human-in-the-loop approval gate: the tool drafts the day's roll-up, the person confirms it, and a manager approves the submission. Nothing becomes an "approved" timesheet on its own.
- Duplicate guards so the same time entry can't slip in twice.
Who it's for
Individual contributors and billable staff who want logging to take ten seconds, not ten minutes. Project and team managers who need totals they can trust before they approve them. Anyone who reaches Friday and honestly can't remember what they did on Tuesday.
You've got this — paste the first prompt and let the interview tailor the rest.