Add-on · Compliance

Catch the expired credential at assignment — not in the client audit.

Arcova Compliance keeps credential types, verification, scheduling checks, and renewals on one record so unqualified assignments stop before they confirm.

Operating record

Clears this link

  1. Shift cell

  2. Clock-in

  3. Time entry

  4. Invoice line

  5. Payout

Credential checks run before a shift can confirm, so an unqualified assignment never reaches the schedule.

See the whole chain

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. 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. 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. 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. 4

    Alert, renew, and update the record

    Expiration alerts fire on configured windows. Renewal workflows run from initiation through document submit to admin approval. Approved renewals update the parent credential.

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

Initiate, submit, review, approve in one workflow. Approved renewals update the parent credential. One active renewal per credential prevents 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

Configured 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.

See credential enforcement on your posts.

Test your credential rules against a real post and see how exceptions and renewals are handled.