Timekeeping that stands up to an audit

The controls

• Time is recorded when it happens

  Employees close 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 your policy sets. A late entry carries its justification with it, on the record, rather than being silently backdated.

• Corrections explain themselves

  Changing a past entry never overwrites it. The original stays on the record and the change is a new version linked to the one before it. Where the controls apply, a correction requires a written reason and the reason for the change travels with it. The record holds what changed, when, and by whom for every entry, and why for every controlled correction, for as long as the workspace holds it.

• Supervisors approve what they supervise

  By design, hours route to the manager responsible for each project, not to whoever happens to administer the software. When a week spans three projects, three managers review their own portion independently, and where the controls apply a supervisory review is required before anything else. Accountability follows responsibility.

• A policy a client cannot weaken

  Your workspace either mandates the DCAA-oriented controls for every client or lets each client enable them. A client may strengthen an optional setting and can never disable a workspace-wide mandate. Settings resolve down the workspace, client, and employee chain by taking the strictest value stated at any level, so the shortest late-entry window and the earliest cutoff win.

• History is appended, never rewritten in place

  Every record keeps its complete revision history in an append-only log scoped to your workspace. There is no edit-in-place anywhere in the system: what happened stays on the record, and a correction is an addition, never an erasure.