Incident Reporting That Closes the Loop From Scene to Station
Emergency services incident reporting fails in two predictable ways: the report never gets completed, or it gets completed but the follow-up actions—corrective training, counseling, supervisor sign-off—happen somewhere else and never get linked back to the original event. When an audit happens six months later, the record shows the incident but not the resolution. That gap is a governance problem.
This template is built specifically for QAS operations in the Cardwell region, covering the full lifecycle of an incident from callout timestamp through to training completion and counseling date. The Incident complete boolean at the bottom is not decorative—it is the close-out flag that marks a record as fully resolved.
The Incident Profile: Time, Crew, and Attending Agencies
Incident date/time captures callout time; incident completed captures return to station. The interval between them is the total operational duration—relevant for both crew fatigue assessment and resource planning. The OIC field logs who was in command; QAS crew is a multi-select covering all attending personnel. Both fields are pre-populated choice lists, which prevents free-text variation causing the same name to appear under three different spellings in a filter.
Other agencies in attendance covers QPS Cardwell, QFES Cardwell, SES Cardwell, Rural Fire Service Kennedy Valley, and a catch-all for anything else. Multi-agency incidents in rural Queensland are routine, and recording which services attended with which crews is the operational detail that matters when an inter-agency debrief happens or a complaint is raised. The GPS Location field pins the geographic coordinate of the incident independently of the free-text location description—both fields exist because one is machine-readable and the other is human-readable.
Incident type distinguishes Emergency standby, Training, Public relations, Full turnout, and Other. The classification is not about statistics—it is about whether the record should trigger the clinical audit pathway or the training record pathway downstream.
Aid, Drugs, and Clinical Documentation
Aid administered is a boolean, and By whom expands on it—multi-select across Christopher, Martin, and Mick, the named crew. Nature of injury and Further treatment are free-text fields where clinical detail lives: description of the presentation, interventions in sequence, escalation decisions.
The Drugs administered field currently carries Aspirin and No drugs. The default is No drugs, which means the field is never left blank—an important audit trail decision. Any deviation from No drugs requires an affirmative selection, which keeps the clinical record honest even when entry happens under time pressure at scene.
QFES driver required and QFES driver name are operationally specific: when the QAS vehicle requires a QFES-licensed driver, this records who drove. Without this field, that information lives in someone's memory or a handwritten note that gets lost.
The Training section carries Corrective training required (text description of the gap), Training received (description of what was done), Training provided by, and Date training completed. The Counselling section is parallel: who provided it, and when it was received. These are not afterthought fields—they are the compliance documentation that proves an incident did not just get filed and forgotten.
Submitted by and Submitted by date record who completed the digital report and when. In a volunteer or part-time service environment, the person at the scene and the person completing the paperwork are sometimes different individuals. This field makes that explicit.
Photos attaches scene documentation directly to the incident record, keeping visual evidence permanently linked to the event rather than stored in a separate photo folder that gets reorganized by someone who was not on the call.