How It Works With ESO
ESO handles your department's incident submission, NERIS workflow, and records management. Station Draft produces a structured draft for the officer to review before they open the ESO record. The two tools operate independently — there is no API connection, no credential sharing, and no data flowing between them automatically.
The ESO Workflow
- 1
Officer writes a short narrative
A few sentences describing what happened — arrival conditions, actions taken, incident outcome.
- 2
Station Draft generates a draft
The narrative is mapped to NERIS incident fields with confidence flags (High / Review / Missing) for each field.
- 3
Officer reviews the draft
The officer checks each flagged field. Review and Missing flags require officer input. High confidence fields can be accepted as-is.
- 4
Officer transfers to ESO
The officer copies the structured output — or uses the PDF export — and enters the data into their ESO incident record.
- 5
Officer submits through ESO
The ESO NERIS submission workflow runs as it normally does. Station Draft is not involved in submission.
What Station Draft Does Not Do
- Connect to ESO through an API or data integration
- Log in to ESO on behalf of the officer
- Submit incidents to NERIS directly
- Store incident data after the draft session
- Replace ESO or your department's existing NERIS workflow
Station Draft Is Not Affiliated With ESO
Station Draft is an independent tool. It is not affiliated with ESO, endorsed by ESO, or a certified ESO integration. ESO is a trademark of its respective owner. The workflow described here reflects how Station Draft's export format can be used alongside ESO — it is not an official ESO feature or partnership.