Tasks · build · professional-services
Consultancy time tracking with rate cards, rounding, monthly invoicing, and locked entries
time-tracking-invoicing · 3600 s per turn · source
The ask
We're a 12-person management consultancy and I need one place for our consultants' time and our client billing. I've attached our client list, our rate card (every client pays its own hourly rate for partners, seniors, and associates), and the July and August timesheets; we bill each entry in quarter hours, always rounding up, and once time has been invoiced nobody should be able to change it. I want to generate one invoice per client per month from that month's billable time, and see at any moment how much work is still unbilled on a dashboard. Each consultant should have a login that shows only their own time, our bookkeeper needs a read-only login, and I want an admin login for me and a login for Nadia Okafor, one of our senior consultants.
Seed files the agent must import: clients.csv</code>, <code>rates.csv</code>, <code>time_entries.csv. The agent must leave a RESULT.json with a reachable URL, an admin login, and the named restricted login.
Acceptance checklist
26 binary items. The first 14 are the enterprise baseline shared by every build task (delivery, invitations, roles, server-side authorization, scoped live dashboard, exact lists and exports, audit metadata, validation, persistence); the rest are application-specific. Core items, which together define "first usable": 1, 3, 5, 6, 8, 14, 19, 21, 23.
| Tag | Items |
|---|---|
| Exact | 9 |
| Rule | 4 |
| Permission | 3 |
| Dashboard | 2 |
| Delivery | 2 |
| Sharing | 2 |
| API | 1 |
| Audit | 1 |
| Automation | 1 |
| Persistence | 1 |
The full checklist with per-item "how to check" instructions and expected figures is in checklist.md. Testers see it; the agent never does.
Change requests
Each change is a new one-shot turn on the carried-forward workspace. Only the owner's text below is sent; the tester items are withheld. After each change the full checklist is rerun, so regressions count.
Change 1 · 3 new checklist items
I'd like a monthly report of each consultant's billed hours and billed amount so I can see who is carrying the load. Consultants can see their own line on it, nobody else's.
Change 2 · 3 new checklist items
Any client whose monthly invoice comes to more than $10,000 gets 10% off that invoice. Apply it automatically when the invoice is generated, as its own line.
Change 3 · 3 new checklist items
Invoices should start as drafts: I review and approve each one before it goes out, and only then is the time locked. If I delete a draft, its time goes back to unbilled. Consultants must never be able to approve an invoice.
No published score. Build runs need a human acceptance pass on a live URL, and no arm has completed one for the full set. Automated probes generate a tester sheet; they do not substitute for it. Results will be published as a separately labeled release when an arm completes.