Submission outcomes and reconciliation

Submission details and reconciliation keep a recorded report distinct from its external filing outcome.

Why it helps
Submission details and reconciliation keep a recorded report distinct from its external filing outcome.

How to configure it
Review a test submission status and reconcile a known destination response through the owning workflow.

Before you begin
Check your department access and intended audience.

Examples for your department
Community paramedicine and mental health response: Submission outcomes and reconciliation: Use an approved operational record definition for visits or responses; select fields and access according to the service’s record policy.
Search and rescue: Submission outcomes and reconciliation: Record search activity, participants and outcomes; distinguish a saved draft from a reviewed or finalized record.
Security companies and departments: Submission outcomes and reconciliation: Record patrol or incident activity under an appropriate definition; review required fields and client/site access.
Wildland contractors: Submission outcomes and reconciliation: Record assignment activity and crew evidence; link the correct call or deployment and retain review status.
Industrial emergency response teams: Submission outcomes and reconciliation: Record drills and response activity; review the definition, participants and finalization requirements.

Documentation: https://docs.resgrid.com/