Skip to content
Feature

Offline safety reporting that sends when signal returns

Short answer

Haznote saves each report on the phone before it is sent, and sends it from a queue. With no signal the report waits, and it goes out when the connection returns. The queue belongs to the signed-in user. If notifications are already allowed, the app can schedule a reminder for a report that hasn’t gone yet.

Tap record, say what you saw, send. No signal? It waits on the phone.

The problem it solves

Hazards are often where there’s no signal. Basements, tunnels, rural sites, the middle of a big slab. A tool that needs a connection to accept a report loses it exactly where it matters. Haznote saves the report on the phone and treats the network as something that turns up later.

How the queue behaves

  • The report is saved on the phone when the worker finishes
  • It is sent from a queue when the phone can connect
  • A failed send doesn’t discard the report
  • The queue is tied to the signed-in user

When the connection comes back, the queue sends. If a send fails, the report stays on the phone. If the server refuses a report, it’s kept whole and the app says why, and whether sending it again will help. A report won’t loop forever on a problem a retry can’t fix.

Reminders without nagging

If notification permission was already granted, the app can schedule a reminder that a report hasn’t gone out yet. It never asks for the permission at that moment. Right after someone saves a hazard is the wrong time for a permission prompt.

Limits, stated plainly

A report that hasn’t left the phone is invisible to a manager. If a worker saves a serious hazard and then loses the phone, the report is on that phone and nowhere else. For anything urgent, tell someone in person. Offline capture protects the record. It doesn’t replace speaking up, and it doesn’t replace a phone call.

01 / How it works

How it works.

  1. 01 / Save

    Saved on the phone

    The report is stored locally the moment the worker finishes.

    • Local save
  2. 02 / Queue

    Sent from a queue

    Reports go out from the queue, and a failure doesn’t drop them.

    • Queue
    • Retry
  3. 03 / Arrive

    Visible when it lands

    The manager sees it as soon as it reaches the server.

    • Manager queue
Questions

Plain answers.

What if the phone is off for days?

The report stays on the phone and goes out when the app can connect.

Are photos and audio queued too?

Yes. They travel with the report as one submission.

Can someone else send my queued reports?

No. Each queued item records the user who owns it.

Sources

Where this comes from.

This page describes how Haznote works. It makes no claims about the law, so it cites no regulator.

Try it on one real site.

Run it on one site and see the first report land in the manager’s list.