EARLY ACCESS Sinkaos is in early access. Apply to join →
INCIDENT LOGGING

Incident logging that survives the shift change.

Incident logging in Sinkaos turns every report into a record with a place, a severity, an owner and a history. When the night shift hands over at six in the morning, the incoming lead reads open incidents and their timelines, and does not have to reconstruct the night from a chat.

Request early access See how it works
THE LOG TODAY

The log is in three places, and the handover is in someone’s head.

During a long response the record is split. Some of it is in the paper log at the command post, some in a group chat, some on the whiteboard, and the rest in the memory of whoever was on the radio. At handover the outgoing lead talks for ten minutes, the incoming lead takes notes, and half the detail is lost by lunchtime.

Then the questions start. When exactly did the report about the cracked embankment arrive? Who was sent, and did they confirm? Which tasks are still open? If the answers depend on scrolling back through four hundred messages, the next shift is working from a guess.

A NIGHT AND A HANDOVER

One night of a flood response, and the handover at six.

  1. 22:40
    A report becomes a record
    A volunteer sends a photo of water over a footpath in the operation chat. The operator turns the message into an observation with one action. It keeps a link back to the message, its position and the photo.
    ObservationsFrom a message
  2. 23:15
    It escalates to an incident
    A second report of seepage at the embankment arrives. The operator opens an incident with severity, an owner and both observations as evidence, and assigns two tasks: check the embankment, close the footpath.
    IncidentsTasksEvidence
  3. 01:50
    A late report lands in the right place
    A patrol in a dead zone recorded a crack at 01:05. It arrives at 01:50 and goes onto the timeline at 01:05, marked as late, next to the river gauge reading from that moment.
    Two clocksSync
  4. 05:45
    The handover starts from the record
    The outgoing lead opens a saved view of open incidents and unacknowledged tasks in the area. She and the incoming lead go through each incident’s timeline together, and owners are reassigned to the day shift.
    Saved viewsOwnersTimeline
  5. 06:10
    Nothing depends on memory
    If the morning briefing needs a summary of the night, an optional AI summary of the time window is drafted from the record. A person checks it before it goes anywhere.
    Optional AISummary
Replay of a closed demo festival operation: the map at 19:36 with incident INC-0007 and the tracks of the teams, a playback bar from 18:00 to 22:00 and the timeline of the incident on the right.
Replaying an operation with an incident timeline. Demo data.
THE LOG

An incident log built from records, not scrollback.

Typed records

Every incident, task, place, person or vehicle has a stable identity, a history and links to related records.

Observations with confidence

Fast field reports with a photo, position, source and confidence, marked as verified or disputed.

Incidents from anywhere

Created by hand or from a message, report, alert or sensor, with severity, owner, workflow and evidence.

Tasks that get acknowledged

Assigned, prioritised and placed on the map, with checklists, sub-tasks and acknowledgement.

Your own forms

Conditional fields, validation, calculations, signatures and photos, so the log asks for what your procedures need.

Two clocks

When something happened and when it became known are kept apart.

Replay at any speed

See the picture at any moment, with gaps in the data shown honestly.

Export for the report

Records as GeoJSON, JSON or CSV, reports as PDF, and after-action packages with a checksum manifest.

AT HANDOVER

What the incoming shift can check, and where.

QUESTIONIN A CHAT OR PAPER LOGIN SINKAOS
What is still open?Read back and guessSaved view of open incidents and tasks
Who owns it?If someone wrote it downOwner on every incident and task
When did it actually happen?Time the message arrivedTime it happened and time it became known
Where exactly?A street name or a descriptionPosition on the map, with photos
What has changed since?Ask aroundHistory of every record
What did the sensors say then?Usually lostReplay with live data from that moment
WORTH KNOWING

What incident logging in Sinkaos does not do.

It is not a dispatch system
Sinkaos is not a certified emergency dispatch or public warning system. It sits alongside the systems your dispatch centre already runs.
Records are readable by the server
Incidents, tasks and map objects are encrypted in transit and at rest, and the server reads them to sync and raise alerts. Messages and files are end-to-end encrypted. Details on the Security page.
AI only suggests
Optional AI can draft summaries or propose records from text. A person confirms them, and your organisation can switch AI off.
Paper rules still apply
If your organisation must keep an official log in a set form, Sinkaos helps you build it from the record. Whether it satisfies your rules is for you to confirm.
WHERE IT IS USED

Where teams keep their log in Sinkaos.

Council emergency centresFlood and storm responseMulti-day searchesSecurity control roomsFestival operationsLarge exercisesInfrastructure outagesOn-call fire crew call-outs
QUESTIONS

Questions about the log and handovers.

Can we turn chat messages into log entries?
Yes. An observation, incident or task can be created from a message, and keeps a link back to where it came from. Places, incidents and tasks shared into a chat stay the same object, not a copy.
How does shift handover work?
Through the record itself: saved views of open incidents and tasks, owners you can reassign, and a timeline for every incident. An optional AI summary of a time window can help with the briefing.
Can we use our own incident forms?
Yes. Build forms with conditional fields, validation, calculations, signatures and photos, and add your own record types alongside the built-in ones.
What happens to reports written offline?
They are saved on the phone and sent when a link appears. Each one keeps the time it happened, so it lands in the right place on the timeline, marked as late.
Can we use the log for a debrief?
Yes. The after-action review starts from the record: messages, tasks, incidents, tracks, plan versions, alerts and media. Export an after-action package or a PDF report.
Who can change an entry?
People whose role allows it. Every change is kept in the record’s history, and admin actions and exports go into a tamper-evident audit trail.
RELATED

Try it on your next operation.

Early access is free. We set up the first operation with you and stay close while you use it.