Skip to content

Report an incident

Report an injury, near miss or other incident at any time, understand when it enters the register, and see what happens after you report it.

For office staff and crewLast reviewed
On this pageReport an incident

Anyone on the team can report an incident or near miss at any time. Reporting does not require clocking in. On Incidents, select Report an incident to open the report drawer on a wide screen or a full-screen sheet on a phone. The form writes directly to the HSWA incident register, and Save stays pinned while you scroll.

Report an incident

From the standalone form

  1. Select Report an incident on the Incidents page or field Home screen. The report opens in the register drawer or phone sheet and starts with Job.
  2. On the standalone form, optionally choose a visible, active job in Job. Leave Job set to No job or outside a job for a report that is not tied to a job.
  3. Where did it happen? is optional when you select a job. Where did it happen? is required when no job is selected.

From a job page

  1. On a job page, the job is already selected. Open the job, select the Safety tab, and select + Report incident under Incidents & near misses.
  2. Enter Exact location on site (optional), such as a roof area or loading bay.

Complete either form

  1. Choose the Type: Near miss, Injury, Illness, Property damage or Other.
  2. Choose the Severity: Low, Medium, High or Critical.
  3. Date and Time start at the current New Zealand date and time. Change them if it happened earlier.
  4. Describe What happened, and optionally what Action taken was done about it.
  5. Optionally add Photos. Select Take photo to use the app camera or Choose from library to attach an existing image. You can select several library photos in one visit.
  6. Tick WorkSafe-notifiable event if it is one.
  7. Select Save in the standalone drawer or sheet, or Log incident on the job page. After the incident is created, each photo attempts to upload or queues in the media outbox when the connection is unavailable. When no photo fails, the drawer closes and the register list shows the new incident, with an Incident logged message. On a job page the form starts again, empty.
  8. If a photo fails, the form stays open. A permanent error from a photo uploaded while online leaves Incident logged. in the form and shows a named failure notice with its reason. If a live upload fails, the notice names each failed filename and gives its reason. A photo that is still too large after shrinking needs a smaller copy or can be removed. Retry is shown only for temporary live upload failures. If a queued photo is permanently refused later, ONYX1 saves the refusal details before removing it from the queue and shows the person who took it a notice once. The notice explains the reason and links back to the incident when it still exists.

Fields you must fill in are marked Required, and most others Optional. If you select Save or Log incident with a required field empty, the form lists what is missing at the top, shows the message under each field, and moves you to the first one.

There's no sign-off and nothing to approve before the report is recorded. Evidence photos use the existing media outbox and can upload without a clock-in.

This queued-photo coverage applies to the incident form's Photos section. Image and signature fields inside a custom site-report form use that form's direct upload handling instead. A failed field file stays in the form with its own error and retry control and is out of scope for the queued-media refusal notice.

Incident site reports

If you submit a site report whose kind is Incident, ONYX1 creates and links the incident-register row when the report is signed and submitted. It maps the report's type, description, immediate actions, first-aid notes, area-made-safe answer, notifiable answer, register reference, job, location, reporter, date and photo references. The operation is idempotent, so submitting the same report again does not create a second register row.

An Incident site-report draft is not added to the register. A submitted report is the filing event. Existing submitted Incident reports can also be added by the controller's one-off backfill command.

The register

The owner, admins, dispatchers, office and site supervisors see the full register under Incidents. A user with the incidents page grant also sees the full register. The summary strip shows Open, Notifiable (WorkSafe), This month and Closed counts. Status is a segmented control for Open, Closed and All. On a phone, select Filter to choose Type and Severity in a sheet. Wide screens use register rows; phones use compact cards. Each row or card shows the NZ date, type and severity, one status, the description, job, location, reporter and status (Open, Waiting for sign-off, Signed off or Closed). Notifiable and Overdue markers remain visible when they apply. Overdue means the incident is signed off and one of its corrective actions is still open after its due date.

Techs and contractors without the incidents page grant see the incidents they reported themselves. They can open their own details and evidence photos but cannot browse someone else's incident.

Techs and contractors without the incidents page grant cannot export the register, and they do not see the Export button. People who can see the full register can select Export, choose a date range with the shared date fields, and optionally tick Notifiable only, then download the WorkSafe-ready PDF or CSV.

Select a row or card to open the incident record drawer. It shows the full description, location, action taken, people involved, the investigation report and any evidence photos. The same record is available at its incident route. A photo taken with no signal is queued and attempts to upload when you're back online. If the server permanently refuses it, ONYX1 saves the refusal details before removing it from the queue so later uploads can continue, then tells the person who took it why. The notice is shown once and can be dismissed. If the incident still exists, it includes a link to it. The image bytes are not kept after a permanent refusal, so take the photo again or attach a smaller copy when the notice asks you to.

Incident review widget

Owners, admins and site supervisors can add the ONYX1 incidents widget. It shows open incidents that need workflow review, the severity counts, the oldest or most overdue age and a few safe kind and stage labels. It does not show the report description, reporter contact details or other incident narrative. Tap it to open /incidents.

The widget is read-only and shows Updated h:mm am/pm in New Zealand time. If it is stale, open ONYX1 before relying on the count. Dispatchers and office staff can use the full register, but do not receive this workflow-review widget.

What happens after you report

The owner, an admin or a site supervisor investigates the incident: they fill in one short investigation report and submit it. The owner or an admin then signs it off, or declines it with a reason so the investigator can change it. The incident closes by itself when its last corrective action is done. If an action is assigned to you, you get a notification at sign-off and select Mark done on the incident when it is finished. The full steps are in Investigate and sign off incidents.

The details of the person involved and their injury are health information. Only the owner, admins and site supervisors see them, even on an incident you reported.

Dispatchers and office staff can see and export the full register but cannot investigate or sign off. Anyone else who opens an incident sees only the rows permitted by their role.

If something goes wrong

  • Describe what happened. The description is required before you can report an incident.
  • Say where it happened, or pick the job. Add a location or choose a visible, active job.
  • Enter the time it happened. Fill in Time as well as Date.
  • Enter the date it happened. Fill in Date as well as Time.
  • That job isn’t available. The job may be outside your visibility, archived or from another company. Pick a visible, active job or leave the report standalone and add a location.
  • The owner, an admin or a site supervisor fills in the investigation. Only the owner or an admin signs it off, and an incident closes only when every action is done.