HazView is a live hazard map for mine and quarry sites. Every hazard, inspection, control and statutory report sits in one place, pinned exactly where it is on your operation.

The map is the record. Your crew sees the same picture on a phone in the pit, a tablet in the ute, and the screen at the front of the pre-start room.

The paper run-sheet. The whiteboard. The hazard spreadsheet on a shared drive that only one person maintains. And the statutory report written from memory at the end of a twelve-hour shift.

Most sites start by replacing one of those and expand once people see it working.

Everyone works off the same map, but they use it differently:

• Examiners and supervisors take handover, run inspections and submit the statutory report.
• Blast crews mark exclusion zones, check machine positions and confirm shots fired.
• Geotechs raise ground hazards, log inspections and attach controls and reports.
• Managers review trends, check controls are in place and sign off reports.

Surface operations: open cut coal, metalliferous mines, quarries and tailings storage facilities. HazView is in daily use across Queensland, New South Wales and Western Australia.

Every site is set up on its own instance, configured to how that operation actually runs, rather than a one-size-fits-all template.

Yes. HazView was built for pits where reception drops out, because that is where the work happens.

Keep logging inspections, adding photos and closing out your shift with no signal. It syncs as soon as you are back in range. Examiners tell us this is the difference between finishing a report in the pit and carrying it back to the office.

Computers, phones and tablets. Most people use a phone or tablet in the field and a computer for reporting and review. It runs on the devices your crew already carries, so there is no new hardware to buy.

Most people are working confidently after one session. We come to site and train each crew on the parts of HazView their role actually uses, and we track who has been trained on what so nobody is missed across swings.

It is the most common worry we hear, and the one that disappears fastest.

The map is the interface. If someone can find a spot on a map and take a photo, they can use HazView. Some of the heaviest users on our trial sites are the people who told us at the start they were not good with technology.

Yes. We build the report to match the format your site already uses, so it is recognisable to the people signing it and to anyone auditing it.

Because the inspections, photos and sign-offs are captured as you go, the report is largely written by the time you sit down. You review it, sign it and submit it without leaving HazView.

Those figures come from a site that moved its statutory reporting into HazView. Across a full year of shifts, that is time handed back to the people who should be out in the pit rather than at a keyboard.

Every inspection, comment, control change, photo and signature is timestamped and attributed to a named user, and the full history is kept.

You can search the archive for what a hazard looked like on a given shift, who inspected it and what controls were in place at the time. Nothing relies on somebody remembering.

No software can do that, and we will not tell you otherwise. Compliance rests with your site and the people running it.

What HazView gives you is the tooling and the evidence trail to demonstrate what was identified, what was done about it and when. It removes the “I’m fairly sure I mentioned that” problem.

Yes, and we would rather you did. We run a proper trial on your site, not a sandbox with sample data.

Trials run for two to four weeks, depending on what suits your site and how complex the operation is. We build your instance and populate it with your own site information first, then come to site to train your crews. The window is set so it covers both swings and gives everyone a fair run at it.

A handful of files and a list of people. Typically your site plan and boundary, recent aerial imagery, and the names and roles of the users you want set up.

We send a short request covering exactly what we need, and we do the building. Your team does not have to configure anything.

Your instance is built, populated and tested before we arrive on site. Training happens on day one and people are logging real hazards on their own site that same day.

There is no lengthy implementation project and nothing for your IT department to install.

You get a written report of what your site actually did with HazView: who used it, what was logged, what your people said about it in their own words, and where it made a measurable difference.

You also get a live dashboard through the trial so you can watch progress as it happens rather than waiting until the end. Then you decide.

You do. One hundred per cent of your site’s data belongs to your site. HazView does not retain it or use it for any purpose without your permission.

Each site runs on its own instance, so your data is not mixed in with anyone else’s. Traffic is encrypted, backups run regularly, and we hold documented recovery procedures.

Access is controlled per person, so you decide who can see and change what. If your IT or security team needs the detail, we will talk them through it directly.

Yes. HazView has a read API that covers effectively all of your site’s data, and sites already use it to pull hazard and inspection data straight into their own reporting dashboards.

If you have a particular system in mind, ask and we will tell you honestly whether it is straightforward.

Yes. Operations run multiple sites with HazView, each configured to suit how that site works, with its own hazard types, rating systems, inspection schedules and user permissions.

Licensing is arranged per site and scoped to the size and complexity of your operation, so a single quarry and a multi-pit mine are not treated the same way.

Get in touch and we will put together something specific to your site.

Direct access to the people who build HazView, by phone or email. Not a ticket queue.

We are on site with you during the trial, and we stay close afterwards because the sites using it are where we learn what to build next.

Constantly, and mostly because of the people using it. A good share of what is in HazView today started as a request from an examiner or a blast supervisor during a trial.

If your crew asks for something sensible, there is a real chance it gets built.

Get in touch through the contact form or email us. We will organise a short walkthrough with you and whoever else should see it, then talk through what a trial on your site would look like.