Built for dispatch centers and patrol divisions
From the first ring to the signed report.
One record of the whole incident.
Dispatch and Field Reporting connects call intake, incident creation, and unit dispatch to the report that closes the incident. The call-taker sees where the caller is and what has happened at that address before. After the call, the officer records a voice note in the car, and it becomes a structured draft report that the officer reviews, corrects, and signs. Nothing is filed without that signature.
- Connected to the phone line
- Live unit status board
- Voice note to draft report
- The officer signs every report
What it changes for your office
An incident is one event. Today it lives in four places.
In most centers, the call is taken in one system, the incident is created in another, unit status is tracked on a third screen, and the report is typed hours later from memory and handwritten notes. Dispatch and Field Reporting keeps the call, the incident, the units, and the report in one record, so each person works from what the person before them already captured.
For the call-taker
When the line rings, the caller's location and the history of that address and phone number are already on screen. A live transcription runs alongside the call and suggests the incident type and the questions your protocol requires next. The call-taker stays in control of every field, and the transcription only assists.
For the dispatcher
The unit board shows every unit, its status, its location, and how long it has been on its current assignment. When an incident is created, the system recommends units based on proximity, availability, and the capabilities the call requires. The dispatcher accepts, changes, or overrides the recommendation, and the choice is recorded.
For the patrol officer
After a call, the officer speaks a voice note in the car or on a phone instead of typing a narrative at the end of a shift. The note becomes a structured draft with the narrative, persons, vehicles, times, and property filled in. The officer reviews it, corrects it, and signs it, and remains the author of record.
The product
Autessa Dispatch and Field Reporting, what your team works in.
Call Intake
Call intake is connected to the phone line. When a call arrives, the caller's location from the carrier and the history of the number and the address appear before the call-taker speaks. A live transcription follows the conversation, highlights details such as weapons, injuries, and vehicle descriptions, and suggests the next question your protocol requires. The call-taker decides what goes into the incident, and the recording and transcript are kept with it.
Incidents and Priority
An incident is created from the intake in one step, with the type, location, priority, and caller details already filled in. Priority follows the protocol and response plans your agency has adopted, and the call-taker or a supervisor can raise or lower it with a stated reason. Every change to an incident, from its type to its location, is kept in order, so the record shows how the picture developed as the call went on.
Unit Status and Recommendations
Every unit on the board shows its status, its location, and how long it has been in that status. When an incident needs units, the system recommends the closest available units with the capabilities the response plan calls for and explains each recommendation. The dispatcher assigns the units, and an override is recorded with its reason. Status timers flag a unit that has been on scene longer than your agency sets as a check-in interval.
Voice Note to Report
After the incident, the officer records a voice note in the car or on a phone. The note is transcribed and organized into a draft report in your agency's format: the narrative, the persons involved and their roles, the vehicles, the times from the incident record, and any property. Anything the system could not place is flagged for the officer instead of guessed. The officer reviews each section, corrects it, and signs, and only then does the report go to a supervisor. The original audio and the transcript are retained with the signed report.
In practice
The details that decide whether a dispatch record and a report hold up.
Three of them, handled the way a public safety agency already handles them: who decides at intake and dispatch, who authors the report, and what is kept from the moment the line rings.
On intake and dispatch
The call-taker and the dispatcher decide
Transcription, suggested questions, priority, and unit recommendations are assistance shown on screen. The call-taker confirms what goes into the incident, and the dispatcher chooses the units. When a person changes a suggestion, the change and the reason are recorded with the incident.
On authorship
The officer is the author of record
A draft built from a voice note is a draft until the officer signs it. The officer reviews each section, corrects anything that is wrong, and fills anything the system flagged as missing. The signed report carries the name of the officer, and the system is never listed as its author.
On the original record
The audio and the transcript are kept
The call recording, the call transcript, the officer's voice note, and its transcript are all retained with the incident. Anyone reviewing the report later can compare the signed text with what was actually said, and the corrections the officer made are visible as corrections.
Below: a draft report waiting for the officer, with the items the system would not fill on its own.
Defensibility
When a report is challenged, the original is still there.
Incident records and reports are read long after they are written: by prosecutors, defense counsel, internal review, and the public. The question is rarely whether the system was fast. It is whether the record shows what was reported, who decided what, and whether the signed report matches what the officer observed and said at the time.
Dispatch and Field Reporting keeps that record as the incident unfolds. Every incident change, unit assignment, and override records the actor and the time. Every report keeps the voice note, the transcript, the draft, each correction the officer made, and the signature. The log is append-only, and it runs in your own Autessa Private Cloud, an environment your agency controls, with keys your agency holds.
One incident, from the call to the approved report, with every hand-off recorded.
The same record across a shift, ready for the supervisor and the records unit.
See a voice note become a draft report.
Bring your report format and a few sample incidents. We will walk your dispatch supervisors and patrol sergeants through intake, the unit board, and a draft report built from a recorded voice note, with every step the officer reviews before signing.
FAQ
Questions we are glad to answer.
Does the system write or file reports on its own?+
No. It prepares a draft from the officer voice note. The officer reviews every section, corrects it, and signs it, and the report is filed only after that signature. The officer is the author of record.
Does the system dispatch units on its own?+
No. It recommends units and explains why. The dispatcher assigns units, and when the dispatcher chooses differently, the choice and the reason are recorded with the incident.
What happens to the audio after a report is drafted?+
The call recording, the officer voice note, and both transcripts are retained with the incident under your retention schedule. The signed report can always be compared with what was actually said.
Can officers record voice notes away from the car?+
Yes. A voice note can be recorded from the mobile data terminal in the car or from an agency-issued phone. Either way, it is attached to the incident the officer selects.
Where does our data go?+
Dispatch and Field Reporting runs in your own Autessa Private Cloud, an environment your agency controls, with keys your agency holds. Your calls, notes, and reports are not used to train models for anyone else.