Documentation
ArkCloud Workforce
The staff roster and the schedule around it: shifts, declared availability, credential tracking with derived expiry, and onboarding tasks.
Credentials are recorded, not verified. Workforce stores the credential and expiry date someone entered and derives status from that date. It does not contact an issuing board, and an expiry status here is never evidence that a licence is currently in good standing.
The ArkCloud Workforce dashboard, summarising staffing, credential expiry and scheduled shifts. Workforce holds staff information and no patient data.
/workforce/dashboard
Why expiry status is derived and never stored
A stored status is a second copy of a fact the expiry date already carries, and the two drift the moment nobody runs the job that updates them. A credential that expired on Sunday would still read Valid on Monday - and it would read valid on a roster someone is using to decide who can treat a patient. Deriving the status when it is read makes that failure unrepresentable: the date is the only source, and a status disagreeing with it cannot exist.
What this is not
- Not payroll. No pay rates, no hours worked, no earnings.
- Not time and attendance. Shifts are what was scheduled, not a record of who clocked in.
- Not primary source verification. See the notice above.
Staff roster
The people who work for the organisation, held separately from platform user accounts - a staff member may exist without ever signing in, and often should.
Shifts and availability
Scheduled shifts alongside the availability a staff member has declared, so a rota can be checked against what someone actually said they could work.
Credentials, with derived status
A credential records its type, identifier and expiry date. Expiry status is DERIVED from that date on read, never stored - so a credential cannot be marked valid while its date says otherwise.
Staffing analytics
Aggregate views over the roster and the schedule - headcount, employment mix, upcoming shifts and credential exposure - computed from the same records the roster shows.
Built and working today
Read from the application's own capability registry, so this list cannot claim something the code has not built.
- Staff scheduling
- Shift management
- Provider scheduling
- Credential tracking
- License tracking
- Onboarding
- Productivity metrics
- Workload visibility
- Availability
- Team assignments
- Staff breakdown by job title
- Staffing analytics
Related: Users and roles covers platform accounts, which are a separate thing from staff records.