Project timesheets that live where your people records live

Services companies that bill or account for time: agencies, consultancies, studios, engineering teams working across client projects, and internal teams that need to know where effort actually went. The buyer is usually a delivery lead or finance. It is worth having once "which project was that on?" is a question somebody asks more than once a month. A company where everyone works on one thing does not need it, and neither does a company that already logs time in a project tool it is happy with, because this module accounts for time rather than planning work.

A paid plan first, because paid modules cannot be enabled on the free plan. Then the configuration is short and mostly a set of decisions: your submission cadence, meaning weekly with a start day, fortnightly with an anchor date, or monthly; whether rates are enabled at all; whether contractor time can be logged, which is only offered while Contractor Management is enabled; a cap on hours logged per day if you want one; which approval workflow a submission binds to; and whether the submission reminder is on, which it is not by default. After that you create your projects and tasks. A workspace that never touches rates or client fields gets clean internal effort tracking rather than a half-configured billing system.

It is not a project management tool: no boards, no dependencies, no Gantt chart and no capacity forecasting. It accounts for time, it does not plan work. It does not invoice your clients, because Capstan is not your billing system; the reports export into the tool that is. There is no timer and no activity monitoring of any kind: entries are declarative and approval is the control. It does not enforce agreement with attendance, so a report can compare logged hours against attendance worked minutes but it never blocks a submission. And rates are single-currency in this version, with no per-task rates.

It reads the core rather than duplicating it: people and their employment records come from the core directory, approvals run on the core workflow engine, and the period view reads the core holiday calendars and leave ledger so non-working days and approved leave are marked and nobody quietly books eight hours on a public holiday. Reporting registers with the core report registry, so a manager sees the slice their permissions already allow. It needs no other paid module. Contractor time is the one cross-module feature: it can be logged the same way while Contractor Management is enabled, and the option is simply absent when that module is off rather than broken.

Projects, tasks, time entries, submissions and the utilisation reports stop being reachable, and billing stops at the end of the current period rather than on the day. The data is not deleted: it is retained on a schedule and restored if you re-enable within that window, including locked periods and their approval history. A full workspace export includes module data whether or not the module is currently enabled, so the record of who worked on what does not become hostage to a subscription. Attendance in the free core is unaffected, because logged project time and attendance are separate records that this module compares rather than merges.