Skip to content

Module 04

Timesheets and approvals

Approval you can defend six months later, when the dispute arrives and the chat thread has scrolled away.

What it does

An approval queue with pending weeks
An approval queue with pending weeks
A state machine, not an informal nod
Draft, submitted, approved, locked. Every transition records who did it and when, and the log is permanent.
Approved time is read-only
A correction is a new attributable event rather than an edit, so nobody rewrites history quietly and the trail of what changed stays intact.
Nobody approves their own timesheet
Including the person who owns the organization. The single and bulk paths run the same refusal, so there is no route that skips it.
Chasing is the system's job
Missing timesheets are found by comparing logged time against the working schedule, and the reminders arrive in the app. That is a manager's afternoon back, every week.

What it is not

Naming the ceiling is what makes everything above it credible. The roadmap says which of these are deferred and why.

  • Rate cards or invoices on this page. Money is its own module, priced from the approved hours this one produces.
  • Payroll export.
  • Email notification for work items. Reminders and mentions arrive in the app.

The rest of the product

Try it against your own week

Log a real week of your own hours and put it through approval. That is a better test than any feature list, and it takes an afternoon.