Our Commitment
ClockAide is used by organizations whose attendance records are read back in audits, licence reviews, insurance claims, and disputes. A record is only worth as much as the system that produced it, so this page states what we guarantee, how each guarantee is enforced, and — below — what we do not claim.
Reliability
What happens every time, including when things fail.
One shift, one call
No member of your staff is called twice for the same shift, regardless of infrastructure conditions.
How it is enforcedReminders are claimed atomically — a single locking statement marks a reminder as in-flight and hands it back in one step — and only then is the call placed. Two schedulers running at once cannot both claim the same reminder. Telephony providers retry their callbacks, so every write that must happen once is conditional on the record still being in flight: a duplicate delivery finds nothing left to claim and changes nothing.
A voicemail never reports an arrival
A message left on an answering machine never states that a shift was confirmed.
How it is enforcedThe answering-machine message is a separate script from the one a person hears. It gives the reminder, says another attempt is coming, and stops there. Answering the call is what confirms the shift, so a machine that accepted a recording has confirmed nothing and the record continues to say so.
We tell you what this cannot do
Known limits are published before you pay, not discovered after.
How it is enforcedShifts must start and end on the same calendar day, so overnight care crossing midnight is unsupported — a schema constraint, not an interface gap, and not something a setting will unlock. Reminder calls are placed to US numbers. If either rules you out, we would rather you know now.
Confidentiality
What we hold, and what we have no way to hold.
Your records stay inside your organization
Staff, schedules, and call history belong to one organization and are never assembled across accounts.
How it is enforcedEvery request establishes which organization the signed-in user belongs to before it reads anything, and every query against a business table is bound to that organization. Requests that touch billing or team membership additionally require an owner. There is no shared view and no cross-account reporting surface.
We have nowhere to put client information
ClockAide holds a name, a mobile number, and shift times. Nothing about the people your staff are sent to.
How it is enforcedThis is a property of the schema, not a policy we ask you to trust. There is no client record, no matter or case number, no visit note, and no clinical field anywhere in the system — and reminder calls are never recorded. There is nothing of that kind here to disclose, subpoena, or breach. If you need to identify a shift, use a time and a person.
Compliance
What an auditor can establish from the record.
We call only the numbers you enter
ClockAide dials US numbers. A number carrying any other country code is rejected at entry rather than reshaped to fit.
How it is enforcedNumbers are normalized to a single canonical format on the way in and validated before they are stored. Reformatting a foreign number into a domestic one would produce a valid number belonging to someone who never consented to be called, so the number is refused instead and the person who entered it is told why.
A correction is recorded as a correction
A clock-in entered by a manager is always distinguishable from one confirmed by a phone call.
How it is enforcedEvery clock event stores its source. Phones die and staff are sometimes already with a client, so managers can record attendance by hand — and when they do, the entry keeps that origin permanently. An audit reads the same record you do: what the call confirmed, what a person asserted, and when.
Billing authority is separate from scheduling
The people running the schedule cannot change the plan, and the separation is enforced by the server.
How it is enforcedRoles are checked server-side on every request rather than by hiding controls in the interface. Schedule managers add staff, build schedules, and work the call log. Only an owner reaches the subscription, the payment method, or an invoice. You can add as many schedule managers as you need without adding cost.
The gaps, stated plainly.
Every vendor page lists strengths. These are the questions we would fail, published so you can rule us out in a meeting rather than a month into an implementation.
- No SOC 2 report
- We have not completed a SOC 2 Type I or Type II audit. If your procurement process requires one, we cannot satisfy it today.
- No HIPAA business associate agreement
- We do not sign BAAs. Our position is that ClockAide has no field for protected health information rather than that it protects it under contract — confirm that reasoning suits your compliance posture before relying on it.
- No contractual uptime guarantee
- We publish no SLA and offer no availability credits. Reminder calls depend on a third-party telephony carrier we do not control.
- Not a payroll system of record
- ClockAide records whether a shift was confirmed by phone. It is not a timekeeping product for wage calculation, and it does not compute hours, overtime, or pay.
Questions this page didn't answer?
Ask before you commit. We would rather lose a sale to a limitation than defend it after you have staff depending on us.