Skip to content

01 · Timekeeping

Book the day whole.

In development · TBD 2027

A compliant timesheet is not a stricter timesheet. It is one where every number has a reason attached at the moment it changed, so nobody reconstructs anything later.

SF 1408 areas 5 & 6 · quarter-hour increments · daily entry

Daily entry
Eight, or a reason

The day books whole. Anything other than a full day carries a written reason, entered the day it happens, not at the end of the period. Quarter-hour increments; the floor is the day, not the week.

timesheet.day · reason required below full day

Corrections
Never silent

A changed hour keeps its old value, its new value, who changed it, when, and why. The correction is a ledger row of its own, so a period with edits reads as a period with edits.

timesheet.amend · prior value retained

Approval
One person-week

Supervisors approve a named person for a named week. The requester is excluded from their own approval by the system, not by policy — there is no configuration in which you approve yourself.

timesheet.approve · requester excluded

Floor checks
On the record

Unannounced floor checks are scheduled, recorded and answered inside the platform. The auditor asks whether you do them; the answer is a query, not a memory.

floor_check.run · scheduled and answered in-platform

What an auditor actually asks

Two of the fourteen SF 1408 areas are timekeeping. Both are about whether labor can be traced to a cost objective and whether the people doing the tracing are the right people.

05Timekeeping identifies labor by cost objectivesettled
06Labor distribution charges direct and indirect laborsettled
settled attention · reason on record live · never finished, kept
Why area 05 reads settled
Every posted hour carries a charge code, and every charge code resolves to one cost objective.
query · labor.post where charge_code is null → 0 rows · 90 days

The uncomfortable part

Timekeeping is where most small contractors fail a pre-award survey, and it is almost never because people lied. It is because the record was assembled after the fact, and an assembled record cannot answer "when did you know that".

Nothing counts until a named person reviews it.

Questions we get asked

The short answers.

Does CRATON support quarter-hour or tenth-hour increments?
Quarter-hour. Tenth-hour is a tenant setting in the data model but is not exercised by a customer yet, and we do not claim what we have not run. Request a walkthrough to see how it is configured.
Can a supervisor approve their own timesheet?
No. The requester is excluded from the approval set by the system. There is no role, tier or override that re-includes them.
What happens to an hour that is corrected after approval?
The approval is invalidated for that person-week, the prior value is retained, and the correction writes its own ledger row with the reason. The week returns to the approver rather than silently changing underneath them.
Does it work offline?
At launch, entry is queued locally and reconciled on reconnect, which matters in denied, disrupted, intermittent, and limited (DDIL) conditions. The ledger sequence is assigned on the server, so an offline entry is ordered by when it lands, and the entry timestamp is kept separately.

Keep reading

Next.

02 · Charge codes
No code, no booking

A charge code is not a label.

04 · Audit record
Fourteen questions. One binder

The SF 1408 asks fourteen things about your accounting system.

The record
AI-assisted. Every commit recorded

AI-assisted analysis. Every operator commit is recorded.

Request a walkthrough

Make your next audit the dullest hour of the year.

Forty minutes with the team building it. Bring your last SF 1408 or your first.

leadership@hypati.us

CRATON is in development; availability planned for 2027 (TBD). Walkthroughs by request.