The schedule has an open slot. Is the person actually ready for the work?
This workflow makes a configured credential problem visible before assignment, routes any exception through a named decision, and shows the qualified recovery.
Dispatcher or safety owner · HVAC or electrical · a technician looks available but is not current for the configured job rule
What happens today
Today a credential date sits in a spreadsheet or a drawer until someone notices it after a customer has been promised a time.
Why it matters
The risk is an avoidable assignment problem, a hidden exception, and an owner discovering the issue too late.
Where this starts
A job requires a business-configured credential or readiness rule; one possible technician record is expired and another is current.
The workflow
- 1The dispatcher attempts assignment and sees the configured block, or the formal override requirement.
- 2The roster and credential record shows the expiry and readiness context, and the alert history.
- 3If policy permits, a manager reviews the scope and reason of an override; the system records the decision rather than hiding it.
- 4The dispatcher assigns the qualified alternative, or keeps the job visible as an exception.
- 5When a renewal document is reviewed and the roster is updated, readiness changes through a recorded human action.
Where a person decides
The business defines the rule, the approver, and the exception policy. CSS does not decide legal requirements.
If it does not go to plan
If no override is allowed and no qualified person exists, the job remains an owned exception. The appointment is not promised.
Where this ends
A correct assignment, or an auditable exception, is visible before dispatch proceeds.
What you can see
Seeded credential, readiness and assignment capture. No real employee name, document, or legal claim appears.
Why that is useful
The dispatcher can see readiness inside the assignment decision rather than reconstruct it later.
What this does not claim. This supports a record and a workflow. It does not certify compliance, licensing, insurance, or legal permission.
Workflow reviewed 2026-08-13