Features
Everything a billable hour needs
From the moment someone works a Tuesday morning to the moment it survives an audit question, the record lives in TackTime: entry, daily close, submission, and a complete history of every change.
Every workspace begins with a 60-day trial of the full product. You will sign in with your work identity first, then name the company and the address the workspace answers on.
The weekly grid
One clean grid for the week: the clients and projects you are assigned to, with their tasks, down the side, the seven days across the top, and totals that update as you type. Your assignments decide what you can book to, so nothing lands on the wrong project, and a week is the seven local dates of your own time zone rather than a server clock.
Week of 31 August 2026
Sample data
| Assignment | Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|---|
| Ledger migrationNorthwind Traders | 8h | 4h | 8h | 4h 45m | |||
| Q3 audit supportFabrikam | 4h | 3h | 6h | ||||
| Onboarding portalTailspin | 45m | ||||||
| Day total | 8h | 8h | 8h | 7h 45m | 6h 45m | ||
| Day status | Closed | Closed | Closed | Closed | Open | Open | Open |
Daily close and the late-entry policy
Closing a day is a deliberate act, not a timer left running over lunch. Your workspace policy decides how strict the clock is: require each day that holds entries to be closed for a DCAA-oriented posture, or allow flexibility with justifications. When an entry arrives late or a closed day is corrected, the policy asks for a reason and keeps it on the record.
Submit a week you have reviewed
When the week is closed, the person who worked it submits it. A submission captures exactly the entries as they stood, so what was submitted can never drift from what was reviewed; a correction afterwards is submitted again, as a new submission that supersedes the old one rather than editing it in place.
Roles, grants, and client access
People see exactly what they are granted: employees see their assignments, managers see the clients and projects they are granted, clients see their own engagements, and viewers see what they are given. 5 viewer accounts are included in every workspace. Assignments have real start and end dates, and time can be booked only on dates inside them, so a contractor cannot record hours past the contract's end.
Financial visibility
Billing rates and internal labor costs are separate permissions, granted apart from the work itself. Someone not cleared to see a rate is never sent one: the server withholds the field on every request, so it is an access rule, not a hidden column.
Hours by client, project, and person
Choose a date range and the hours in it are totalled for you: by client, then by project, then by the person who recorded them, with billable and non-billable time side by side, a count of the entries behind each figure, and a subtotal at every level. Owners and administrators read the whole workspace this way; everybody else reads the time they recorded themselves. The report is a page, read on screen, downloaded as a CSV or an XLSX workbook, or printed as it stands.
History on every entry
Every time entry keeps its complete revision history. A correction appends a new version and never erases what it corrects, and the reason for the change travels with it. Every change to an entry, a project, a rate, or a membership after the workspace is created is also written to an append-only audit log, and the compliance page says exactly what that log establishes and what it does not.
See it with your own projects.
TackTime supports a DCAA-oriented timekeeping process and is not a certification, an attestation, or a guarantee of compliance; how your organization configures and uses it decides the outcome.
Every workspace begins with a 60-day trial of the full product. You will sign in with your work identity first, then name the company and the address the workspace answers on.