For Schools · Tier 3 Dynamic Risk Operations
Can your duty team log an incident and keep the full record in one place?
The integrated incident record, run by the school's own duty team inside the Duty Manager Dashboard.
An incident rarely stays one document. A first report becomes calls, messages, decisions, status changes, and follow-up items, spread across phones, notebooks, and inboxes. Afterward, someone reconstructs the sequence from whatever each person kept.
The duty team opens the incident, works it, and closes it as the situation runs. That working record — not a write-up assembled afterward — is the documentation the school keeps.
A Harborview trip in Seoul, day three of eight
Messages, calls, and check-ins enter the record as time-stamped entries, in sequence, beside the incident they concern.
The incident opens inside the trip view, not a separate module; every entry keeps its link to the trip, activity, location, and people the school recorded.
Updates are added as new entries; status moves through open, monitored, escalated, and resolved.
Follow-up items and the finished record move into the post-trip file.
ETI360 provides the system and the structured record — it does not monitor incidents, direct the response, decide escalations, or stand in for emergency services.
Incident reporting sits in Tier 3 Dynamic Risk Operations — the during-and-after tier.
Tier Three · During and after
Dynamic Risk Operations
Talk it through on your own trips.
A 20-minute conversation about the trips you run is enough to see whether the incident record fits how your team already operates.
Get in touch →We respond within two business days.