TackTime is built around these expectations rather than adapted to them afterward. What follows relates the product to each one, in the same order: what is built is stated as built, and the one capability that is still a design is stated as a design.
- Recorded daily, by the person
- A person records their own week on a grid of the seven days in their own time zone, and closes each workday as a deliberate act. When an entry arrives for an earlier date, the workspace policy decides what happens: allow it, require a written reason, or refuse it outside a window the policy sets. A late entry carries its justification with it, on the record, rather than being silently backdated.
- Charged to the work it belongs to
- A person can book time only to the clients and projects they are assigned to, inside the dates of the assignment, so nothing lands on a project the person is not on. Whether a catch-all project exists to be assigned is the workspace's own choice; the checklist above says not to keep one.
- All of the time, not only the billable part
- Indirect time is recorded the way direct time is, against a client and project set up to hold it, so the total for a day is on the record. TackTime does not reconcile to payroll; the record it holds is the one you reconcile from.
- Corrections that keep the original
- Changing a past entry never overwrites it. The original stays on the record, the change is a new version linked to the one before, and where the policy applies, the reason for the change travels with it.
- Reviewed by the supervisor who knows the work
- TackTime is designed so that each project's hours route to that project's manager, independently of every other project on the same timesheet. That routing is the design the product is built toward, and the compliance page says how the model works.
- A history an auditor can follow
- Every change to an entry, a project, a rate, or a membership after the workspace is created is written to an append-only audit log scoped to your workspace, and the compliance page says exactly what that log establishes and what it does not.
- Kept for the retention period
- Nothing in TackTime removes a time record, a version, or an audit event on a schedule; the record stays for as long as the workspace does. The retention period your contract sets is yours to meet, and the record is built to outlast the engagement.
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.