Health, Safety & Inclusion
Incident Management
Connect the report to the response and the learning.
Connect incident reports, immediate responses and follow-up responsibilities with the relevant people and locations.
Capture the people, location, time, and factual circumstances.
START WITH THE ACTUAL WORK
Why connect incident management?
An incident record is incomplete until immediate actions, responsible follow-up, and the outcome are clear.
WHAT THIS CAPABILITY BRINGS TOGETHER
Incident Management: records, decisions, and handovers.
Structured reporting
Capture the people, location, time, and factual circumstances.
Response coordination
Identify urgency and route actions to the appropriate staff.
Outcome and improvement
Record the resolution and any operational change needed to prevent recurrence.
FOLLOW THE WORK FROM START TO FINISH
Explore the incident management workflow.
This interactive illustration explains the operating model. It contains no live institutional records.
Structured reporting
Capture the people, location, time, and factual circumstances.
Incident types and severity reviewResponse coordination
Identify urgency and route actions to the appropriate staff.
Responsible teams and escalation routesOutcome and improvement
Record the resolution and any operational change needed to prevent recurrence.
Closure evidence and follow-up datesRecord an incident
Record the incident and any immediate action already taken.
A WORKED EXAMPLE · ILLUSTRATIVE SCENARIO
Recording what happened is different from deciding the response
A campus incident involves several observations and an unresolved repair. Combining assumptions with facts would make review and follow-up unreliable.
The decision and its context
Record the event, time, location and factual observations, then assign the appropriate review. Separate investigation, approved actions and the operational work required to resolve a related issue.
What a complete outcome looks like
The record should show who owns each action and why the incident is closed or remains open. Restricted details should not be copied into general maintenance tasks.
A CAPABILITY, NOT AN ISLAND
Connect incident management with the next workflow.
The same institutional context should support the next responsible team’s action. Explore the connected capabilities.
Bring asset records, reported faults, assigned work and maintenance history into campus operations.
Safeguarding & Child ProtectionStructure concern reporting, designated review and restricted case handling around institutional safeguarding procedures.
Emergency Response & Fire DrillsSupport emergency planning and drill records with responsibilities, participation checks and review actions.
YOUR INSTITUTION’S RULES
Set the rules for incident management.
- Incident types and severity review
- Responsible teams and escalation routes
- Closure evidence and follow-up dates
WHEN THE DAY DOESN’T FOLLOW THE DEFAULT
An incident involves sensitive student information
Restrict its details while sharing only the operational actions needed by other teams.
Incident ManagementStructured reporting → Outcome and improvementSEE HOW THE WORK CONNECTS
Incident Management
Authorized staff · Operations teams. Capture the people, location, time, and factual circumstances.
- 01
Structured reporting
Capture the people, location, time, and factual circumstances.
- 02
Response coordination
Identify urgency and route actions to the appropriate staff.
- 03
Outcome and improvement
Record the resolution and any operational change needed to prevent recurrence.
Illustrative workflow · Shape the details around your institution.
AUTOMATION WITH A PURPOSE
When a follow-up passes its due date.
Use an agreed trigger and response while keeping the responsible person in the decision.
A follow-up passes its due date
Bring the outstanding action to its responsible owner and designated reviewer.
APPROPRIATE CONTROL
Who can act on incident management?
Incident access must reflect sensitivity and responsibility; distinguish factual observation from subsequent professional assessment.
Explore security and institutional controlKNOW WHETHER THE CHANGE IS HELPING
Resolution and recurrence
Review overdue actions and repeated incidents by context without exposing unnecessary personal details.
Agree the baseline, reporting period, and owner before comparing results.Connect evidence to decisionsSEE IT IN YOUR CONTEXT
Different institutions. Specific responsibilities.
Institution perspectives
Special educationBoarding schoolsPeople doing the work
Student support teamsPrincipalsA practical introduction
Bring a representative workflow, one recurring exception, and the people who own the handoffs.
Plan your implementationBEFORE THE CONVERSATION
Useful questions about incident management.
Is recording an incident the same as responding to it?
No. Immediate assistance and institutional procedures come first; the record coordinates the subsequent accountable response and review.
How should sensitive workflows be introduced?
Agree the professional responsibilities, access boundaries, consent context, escalation routes, and retention rules. Test permissions and exceptional cases with the designated institutional leads.
PUT YOUR PROCESS IN THE PICTURE
Explore incident management in your institution.
Start with your current workflow, the decisions that take time, and the handoffs you want to improve.
This public page presents Qentak’s capability model and an illustrative workflow. Available modules, integrations, operating rules, and rollout scope are established in your implementation plan.
Explore all 69 capabilities