Pay information visibility, completed shift tracking, timesheet review, attendance-based payment workflows and payout status for the clinician. On the operator's side, approved time becoming a pay figure, a bill figure and a margin, each calculated from rules resolved as at the work date, and each one explainable months later.
An hour becomes a figure in four moves: punches captured at the point of work, exceptions resolved by an approver, the calculation run under the rules that applied on the date the work happened, and three figures (pay, bill, margin), each carrying its explanation.
Time that never cleared a gate never reaches the calculation.
CareTech captures time at the point of work: clock-in and clock-out, geofenced punches, a timecard built from the punches that were actually captured, exceptions surfaced to the approver, and a route back for correction.
A punch taken outside the geofence is retained as evidence rather than discarded. Discarding it would delete the only record that the person was at the door at all; keeping it puts a question in front of an approver instead of a silence in front of an auditor.
A timecard cannot be approved over an unresolved meal-break violation. The approver is told exactly what to fix and the correction path stays open, so the exception is resolved rather than approved around. And the approval belongs to a role that did not build the schedule: a scheduler cannot approve a timecard.
Approved time is calculated into a pay figure, a bill figure and a margin. The figures are not the interesting part — the explanation behind them is, because that is what somebody has to defend in an audit two quarters from now.
Overtime follows the jurisdiction the work happened in. A tenant rule set below the federal 1.5× floor (or California's 2.0× for double time) is raised to the statutory floor, and the correction is written into the explanation an auditor reads. The floor is not something an organization can configure its way underneath.
A timecard corrected in September for July work is calculated under July's rules. Rate changes, jurisdiction rules and tenant configuration are all resolved as at the date the work happened, not the date somebody opened the record.
The database refuses the second claim. The constraint sits in the data layer rather than in application code, so it holds regardless of which service, screen or import made the request.
Pay information visibility, completed shift tracking, timesheet review, attendance-based payment workflows, payout status, account settings, profile updates and document visibility where applicable — and, for the operator, administrator payout dashboards over the same data.
Approved time · calculate pay, bill and margin · payout status · statement · invoice.
CareTech generates a provider import file for a payroll provider; the payment itself is made by that provider.
A figure is only as defensible as the gates the work passed through to reach it.
Where the hours come from. Approval-led confirmation, calendar visibility and time capture, with double-bookings refused at the gate rather than reconciled at month end.
02Where eligibility comes from. Credential requirements are checked at request, at confirmation and at clock-in, and both clearances and refusals are recorded.
03Where the query goes. A timecard exception and the support ticket about it route to the same place, and the history stays attached to the shift.
04Hospitals, clinics, home care, schools, behavioral health, rehabilitation, post-acute, senior living, correctional healthcare, diagnostic centers and longevity programs.
Money is where a workforce platform is finally tested. These are the mechanisms that decide whether a figure can be explained, and by whom.
Overtime follows the jurisdiction the work happened in, and a tenant rule below the statutory floor is raised to it, with the correction written into the explanation an auditor reads.
Rules resolve as at the work date, so a timecard corrected in September for July work is calculated under July's rules.
The same work cannot be billed twice: the database refuses the second claim, not a check in application code.
A timecard cannot be approved over an unresolved meal-break violation, and a scheduler cannot approve a timecard at all: approval belongs to a different role.
Finance cannot void an invoice, and an auditor can read payroll without being able to export it. Separation of duties is enforced at the boundary, not assumed.
CareTech calculates pay, bill and margin and generates a provider import file for a payroll provider. The payment itself is made by that provider.
How the governance chain works →Five questions that decide whether a pay figure is a number on a screen or a position somebody can defend.