Evaluation 1 of 5
Contract clauses to accountable obligations
A security contract is easier to manage when the team can connect each delivery obligation to an owner and a due date.
- Prepare
- Bring a fictional clause requiring a weekly site report, its deadline and the role responsible for approval.
- Check
- Create or review the obligation in the demo, attach its clause reference and follow the evidence submitted for review.
- Read the result
- Submitted evidence and accepted evidence are different states. Check the acceptance decision before treating an obligation as fulfilled.
Evaluation 2 of 5
Officer shifts and post coverage
A rota needs an explicit handover when one officer leaves and another takes responsibility for a post.
- Prepare
- Prepare two fictional shifts at one site, a short overlap and a vacant post that needs a manager's decision.
- Check
- Review officer readiness, assigned coverage and the handover in the Command demo. Check the vacant period separately from the staffed periods.
- Read the result
- A scheduled officer is not proof of attendance. Agree how the organisation verifies readiness and accepts the handover.
Evaluation 3 of 5
Patrol observations and follow-up
Patrol evidence should tell the reviewer what was observed, when it was recorded and what needs attention.
- Prepare
- Choose a fictional observation at a contract site and a follow-up action with a named owner.
- Check
- Open the patrol record and its supporting evidence. Follow the action to its deadline and check what the reviewer can verify.
- Read the result
- An observation record does not prove continuous presence or replace a physical inspection. Confirm any checkpoint or hardware requirement separately.
Evaluation 4 of 5
Incident deadlines and escalation records
An incident report is actionable when the next responsible person can see its urgency, deadline and unresolved work.
- Prepare
- Use a fictional incident with an acknowledgement deadline and one supporting photo without personal information.
- Check
- Follow the incident record through assignment, review and the next action. Check the deadline and what remains outstanding.
- Read the result
- The organisation owns its response and escalation procedure. A recorded incident is not a dispatch or emergency-service guarantee.
Evaluation 5 of 5
Reviewed client delivery reports
A client report should make it possible to distinguish completed work from open issues across the reporting period.
- Prepare
- Select one fictional site, a date range, an accepted obligation and an unresolved incident.
- Check
- Review the exported client report against those source records. Check whether submitted evidence is clearly separated from accepted delivery.
- Read the result
- Avoid treating a report as an invoice or proof of payment. Confirm report fields and client access as part of the agreed deployment.