Keep incident and prevention records reviewable
Welcome to Resgrid Academy. In this lesson, we will keep incident and prevention records reviewable. Incident information becomes harder to review and report when it is spread across calls, attachments, and separate files. We will explain the features, the setup decisions, and a practical way to check the result.
A department scenario
After each call, the officer completes an incident report from the call and a supervisor reviews it. Keep incident and activity records with the calls they came from, ready for review and reporting. The examples in this series use a fictional department and are teaching scenarios, not default settings.
Logs
Logs. Activity logs for calls, training and work. Choose the log types members complete. Availability also depends on Logs. Check access in the target department.
Records
Records. Incident and activity records. Turn on Records if it is available to you and review the record settings. Availability also depends on Logs. Check access in the target department.
Incident reports
Incident reports. Incident reports linked to calls. Decide who completes and who reviews each report.
Record definitions and templates
Record definitions and templates. The forms and fields records use. Start from the built-in forms and add only the fields you need.
Reports
Reports. Department reports on calls, personnel and activity. Run the reports you use for meetings or compliance. Availability also depends on Reports. Check access in the target department.
New Log
New Log. Record a run report, training log or work log. Know which reports your department completes and who reviews them. Records may need to be enabled for your department. Availability also depends on Logs. Check access in the target department.
Records Dashboard
Records Dashboard. Records that are due, awaiting review or ready to submit. Know which reports your department completes and who reviews them. Records may need to be enabled for your department. Availability also depends on Logs. Check access in the target department.
Records Settings
Records Settings. Numbering, retention, search and visibility rules for records. Know which reports your department completes and who reviews them. Records may need to be enabled for your department. Availability also depends on Logs. Check access in the target department.
Occupancies and preplans
Occupancies and preplans. Buildings and sites with their contacts, hazards and preplans. Know which reports your department completes and who reviews them. Records may need to be enabled for your department.
Inspections
Inspections. Schedule inspections and track violations and corrections. Know which reports your department completes and who reviews them. Records may need to be enabled for your department.
Hydrants and water sources
Hydrants and water sources. Hydrants and water sources with their inspection and flow history. Know which reports your department completes and who reviews them. Records may need to be enabled for your department.
Permits
Permits. Permits and their approval status. Know which reports your department completes and who reviews them. Records may need to be enabled for your department.
Investigations
Investigations. Restricted case records, such as fire investigations. Know which reports your department completes and who reviews them. Records may need to be enabled for your department.
Evidence capture and provenance
Evidence capture and provenance. Collect and track evidence attached to a record. Know which reports your department completes and who reviews them. Records may need to be enabled for your department.
Legal holds
Legal holds. Legal holds that stop records from being deleted. Know which reports your department completes and who reviews them. Records may need to be enabled for your department.
Reporting submissions
Reporting submissions. Submit incident reports to state or national reporting systems. Know which reports your department completes and who reviews them. Records may need to be enabled for your department.
Records analytics
Records analytics. Response, workload and readiness trends from your records. Know which reports your department completes and who reviews them. Records may need to be enabled for your department.
Saved record reports
Saved record reports. Saved record reports you can run again. Know which reports your department completes and who reviews them. Records may need to be enabled for your department.
Record exports and templates
Record exports and templates. Export records to files using templates. Know which reports your department completes and who reviews them. Records may need to be enabled for your department.
Disclosure requests
Disclosure requests. Requests to release records, with redaction and approval. Know which reports your department completes and who reviews them. Records may need to be enabled for your department.
Quality review and sampling
Post-finalization review uses rubrics, sampling, scores, and trends to identify reporting follow-up. Confirm rollout and reviewer access, configure an approved rubric, sample finalized records, and score a demo review. Review criteria, sample scope, notes, and amendment recommendations without treating a score as a rewritten incident report. Confirm availability in the demo department before recording the live workflow.
Records health and prevention attachments
Records health and prevention attachment screens make retained record support and issues visible to authorized users. Review the records health view and attach a synthetic support file to an appropriate prevention record. Verify parent-record access and the restricted-attachment behavior on the intended member account. Confirm availability in the demo department before recording the live workflow.
NERIS incident analysis lifecycle
Incident analysis is a separately validated and submitted artifact linked to an incident report. Start analysis from a demo incident, edit and validate it, then review finalization and submission readiness. Confirm the analysis lifecycle separately from the incident report. Submission waits for the required incident destination identity. Confirm availability in the demo department before recording the live workflow.
Community risk reduction activities
Community risk reduction records education and prevention activity with attendee counts. Confirm the community-risk feature and access, record a fictional activity, and review its summary and analytics scope. Check counts, dates, ownership, and the activity audience without placing attendee personal information into the example. Confirm availability in the demo department before recording the live workflow.
Record revisions and differences
Revision and difference views help reviewers understand how a record changed. Open two revisions of a synthetic record and review their differences and any permitted export. Confirm the selected revisions and access to the parent record before interpreting the difference. Confirm availability in the demo department before recording the live workflow.
Submission outcomes and reconciliation
Submission details and reconciliation keep a recorded report distinct from its external filing outcome. Review a test submission status and reconcile a known destination response through the owning workflow. Check the destination identity, accepted or failed outcome, and any corrections needed. Confirm availability in the demo department before recording the live workflow.
Inventory use attached to records
Record inventory workflows connect consumption and evidence to the incident or activity record. Link synthetic inventory use to a record, refresh its evidence, and review supported reversal handling. Reconcile the record, item, quantity, and corresponding stock movement. Confirm availability in the demo department before recording the live workflow.
Deployment connector administration
Deployment connector screens manage connector configuration, enablement, tokens, and runs. Review connector terms and ownership, configure a demo destination, and inspect a controlled run. Confirm the target integration, observed run, and token lifecycle. Mask credentials during capture. Confirm availability in the demo department before recording the live workflow.
Configure one useful workflow
For the training scenario, work in this order. Step 1. Review record settings, definitions, numbering, visibility, and retention. Step 2. Create a report linked to a training call and complete its required data. Step 3. Use review, evidence, exports, or submission workflows appropriate to the record.
Verify the result
Now verify the result. Check draft and review status, evidence provenance, restricted access, and the actual outcome of any test submission. A common problem to watch for: A queued submission is not acceptance by its destination. Legal holds and disclosure reviews require their owning workflows.
Try it with your department
Your practice task is simple. Prepare one complete training incident report and one incomplete draft. Use the work queue to assign corrections and compare analytics scope. Record the result, who owns the follow-up, and when it should be reviewed.