CloudWinks · Foundation apps

TimeTrackerTechnical brief

TimeTracker records who worked, when and on what. It keeps an attendance ledger and the classifications and timesheets that follow from it, without holding pay or rates.

Read the business brief · PDF

1. Architecture in brief

TimeTracker is a Foundation app with personal and company tenancy. It holds an append-only punch ledger, derived time segments, exceptions, and the company workforce model of shifts, pay periods, timesheets and versioned rule sets. CloudWinks supplies the application runtime and Crux the shared identity. Personal mode is a simple work timer; company mode adds workforce policy. No pay or rates are stored here.

2. Service boundary and intake

A punch is written once and is not updated. Corrections are recorded as adjustments alongside the punch. Segments are rebuilt from punches and approved corrections. A time entry must reference a subject or a cost code; a task pointer is optional. Geofence checks are a soft flag by default; a hard block is opt-in and applies only when online. Location is taken at the punch instant.

3. Data handled

The model stores punches and punch context, adjustments, derived segments, exceptions, labels, timesheets and approvals, shifts, pay periods, versioned rule sets, worker policies and registered devices. TimeTracker owns the punch, the derived time and the approved hours. It does not own the task, the place, the evidence photo, the secret or the paycheck.

4. Integrations and ownership

TaskMaster is an optional pointer. Roady can verify a geofence. MediaMogul can hold a punch photo. KeyKook holds device credentials. Conductor can time shift patterns. TjingTjing reads the approved-hours view (approved and locked rows only) and the hour classification used for overtime pay; BeanCounter supplies cost codes and applies cost and bill rates. TheReporter can present those views. TimeTracker owns attendance, not those other records.

5. Security and access

Raw punches are immutable; corrections are append-only. A kiosk PIN is stored as a salted hash, never in the clear, and biometrics are not used. Geofence policy is explicit, with a soft flag as the default. Employee location tracking belongs with the clocked-in or on-route window in Roady. Personal mode does not include payroll features. Device secrets are resolved through KeyKook.

Competitive context

AlternativeIts focusCloudWinks product focus
QuickBooks TimePunches, timesheet approval, overtime rules and optional geofencing.An append-only CloudWinks attendance ledger with approved hours offered to payroll and costing apps, and no money stored here.
ClockifyTimers, timesheets and approval that can lock submitted time.Time that can stand alone or point at a CloudWinks task, with crew and kiosk punching in the workforce model.

Read the business brief →

← More Foundation apps apps · All application briefs · How the framework works