Module · Compliance
Know whose credentials need attention.
Track licenses and training, check post requirements, and see upcoming renewals before you assign a guard.
Where credential gaps surface too late
Armed licenses, CPR, background checks, and jurisdiction permits live across binders and spreadsheets. Misses show up in client audits — not when someone assigns the post.
Expired credentials found during audits
A license lapsed weeks ago. The spreadsheet was not updated. The client finds it in quarterly review — after the guard already worked the post.
Renewals depend on one person's memory
Supervisors know who needs renewals until they are out. No shared expiration window. No alert. Guards report to posts they are no longer qualified to hold.
Exceptions with no reviewable trail
A manager verbally clears one shift. Months later the same guard is still on the post with an expired credential — no approver, reason, or end date on record.
How it works
From credential upload to blocked assignment
One compliance loop: define requirements, verify credentials, check them at assignment, then renew before they lapse.
- 1
Define credential types and post requirements
Create types with renewal windows, grace periods, and verification rules. Attach them to posts, roles, or locations. Set block or warn per requirement.
- 2
Upload and verify credentials
Officers submit credentials with supporting documents. Admins verify issue date, expiration, and issuing authority. Bulk import covers existing workforce data.
- 3
Enforce at assignment time
When a scheduler assigns a guard, Arcova checks mandatory credentials for that post. Missing or expired credentials block confirmation — or warn when enforcement mode allows it.
- 4
Alert, renew, and update the record
Alerts go out at 90, 60, 30, and 7 days before a credential expires. Start the renewal, collect the documents, mark it complete — the credential updates itself.
Catch the expired credential before assignment
Credentials stay enforceable at the desk — not as a monthly report nobody opens.
Scheduling enforcement
Credentials are checked when someone assigns a post — not as a weekly dashboard. Unqualified placements stop before they reach the schedule.
Renewal lifecycle
Start the renewal, attach the documents, and close it out in one place. The credential updates itself, and only one renewal can be open per credential — no duplicate submissions.
Exception management
Temporary exceptions require an approver, business reason, and expiration. Scope to a post or apply globally. Every exception stays auditable.
Check the requirement before the shift.
What changes when credentials, exceptions, and renewals share one enforceable record.
Credential enforcement
Before
Schedulers check a spreadsheet before assigning — when they remember. The sheet is often weeks stale.
With Arcova
Every assignment runs credential checks. Missing or expired qualifications block confirmation before the shift goes live.
Expiration tracking
Before
Someone reviews expirations monthly. Guards with lapsed credentials work posts for weeks before anyone notices.
With Arcova
Staged expiration alerts and escalation keep renewals in motion. Expired credentials flag system-wide.
Exception handling
Before
Verbal approvals. No record of who authorized what. Temporary exceptions become permanent.
With Arcova
Every exception has an approver, reason, scope, and expiration. It auto-expires and leaves an audit trail.
Compliance feeds the rest of the platform
Verified credentials gate scheduling and stay visible on personnel and training records.
Included in your Arcova software plan
Standard modules are included in your software plan. Pricing follows active field team size.
- Credential type and expiration tracking
- Compliance-gated scheduling checks
- Audit-ready dashboards
Setup is quoted separately.
See plans and pricingSee how Arcova checks your post requirements.
Bring an example license or training requirement. We will show how it is tracked and checked.