Structured capture
Give officers a clear way to record the facts, location, time, observations and supporting material required by your process.
WFCControl
Incident reporting
Capture, escalate and review security incidents in one digital occurrence book
When a report begins in a notebook, continues in a group chat and reaches the client through an attachment, it is hard to see who owns the next action. WFC Control brings incident capture, review and controlled reporting into one operational workflow.
Your site procedures, escalation matrix and record-retention policy remain essential. WFC Control helps teams organise the process, it does not replace emergency services, legal advice or a formal investigation.
Built for accountable operations
A workflow your team can explain, not another disconnected tool
Visible ownership
Route a report to the right supervisor, record the follow-up and make review status easier to see.
Controlled sharing
Prepare the right operational update for authorised client contacts without disconnected email chains.
A practical operating path
Create a clearer process from first action to review
1
Record what happened
Capture the operational event using the fields, categories and supporting information your team requires.
2
Escalate under your rules
Use a defined severity and escalation route so the right person can review and assign follow-up.
3
Review and close
Keep comments, actions and closure notes with the record so supervisors have a clearer history to review.
Replace paper handovers with a clear workflow
Digital occurrence-book processes work best when the team agrees what must be captured, who receives it and what closure means. WFC Control supports a consistent operational path from the first note to supervisor review.
- Use agreed incident categories
- Record site and contract context
- Assign a follow-up owner
- Separate review and closure states
Keep urgent escalation separate
A recorded incident is not an emergency response. Site instructions should continue to define when officers call emergency services, contact a client, activate safeguarding procedures or notify a duty manager.
- Document the escalation matrix
- Train officers on immediate action
- Use internal routing for follow-up
- Review serious incidents with management
Retain records for a reason
There is no universal retention period for every incident record. The right period depends on business need, contract and applicable responsibilities. Make retention, access and deletion part of implementation.
- Set a documented retention approach
- Limit access by role
- Review records regularly
- Keep sensitive information proportionate
Questions buyers ask
Frequently asked questions
Useful official guidance
These links provide context for the operational and data-handling decisions described on this page. Always check current guidance for your organisation.
WFCControl
Bring your real workflow to the conversation
Request a tailored product walkthrough and discuss the sites, records, escalation rules and reporting needs that matter to your security operation.