Alerts Report

The Alerts report lives at /admin/reports/alerts, in the Reports rail under Compliance. It answers one question that the Alerts & Bulletins screens cannot: which supervisors have, and have not, acknowledged each alert.

It covers every project you are a member of, so you pick the projects in the report itself.

For a one-project spreadsheet in the Lacroo Core layout, see Alerts Report (download) below.

The row grain

One row per alert × supervisor × prestart response.

• A supervisor who acknowledged an alert on three prestarts produces three rows. Each prestart is a distinct compliance event, so nothing is collapsed. The Prestart Date and Prestart ID columns tell those rows apart.
• A supervisor who never responded produces exactly one row, with every acknowledgement column blank.

That blank row is the point of the report. A screen that only lists responses can never show you the person who has not responded; here, the absence is a row you can sort, filter and export.

Row counts grow quickly (alerts × supervisors × projects). The XLSX export holds up to 100,000 rows.

Who counts as a supervisor

A supervisor is anyone whose role on the project is Supervisor or Senior Supervisor (a project role replaces their company role) and who is on the project team, or is the primary or an associated supervisor on a live prestart or diary there. The matrix is built from that set.

Two consequences worth knowing:

• Custom supervisor-like roles are not included. If your org creates its own role that supervises crews, its holders will not appear as rows. Give those users the Supervisor role.
• A response recorded against a prestart whose supervisor lacks that role does not appear. A response belongs to the prestart’s supervisor, and only people with the role have rows.

Membership is read as it stands today, not as at the alert’s issue date. Someone who joined a project last week gets blank rows for alerts issued before they arrived.

Filters

Every filter is written to the URL, so a filtered view is a link you can paste to someone else — and the Export button always produces exactly the rows on screen.

The three date bases

Filtering by Date acknowledged necessarily hides every un-acknowledged row — a row with no acknowledgement has no acknowledgement date to match against. This is inherent to the basis, not a defect. Use Issued on to see who still owes you a response; the report says so inline when the resulting table is empty.

Acknowledgement columns

Date-specified alerts acknowledge themselves

An alert issued with a specified date is treated as acknowledged for every supervisor: Acknowledged Yes/No reads Yes, Date/Time Acknowledged is left blank (nobody clicked anything, so there is no timestamp to show), and Acknowledgement Source reads Auto (date-specified).

Read the Source column before drawing conclusions from a compliance rate: Manual is a person confirming they read the notice; Auto (date-specified) is the system’s rule.

Acknowledged By, and why it is usually blank

In practice most acknowledgements are recorded by an administrator on the supervisor’s prestart, not by the supervisor themselves. The Supervisor column is always the person the alert was owed by; Acknowledged By names the person who actually recorded it, and is left blank when those are the same person. A populated Acknowledged By means somebody acknowledged on that supervisor’s behalf.

Unassigned org alerts

An org-scoped alert reaches projects through its associated-projects list. An org alert with an empty list reaches nobody.

Rather than let it vanish, the report surfaces it as a single row with Level = Organisation and blank Project, Supervisor and acknowledgement columns. It is informational: an alert issued to nobody is a misconfiguration you want to see. Turn Include unassigned org alerts off to hide them.

These rows disappear under Date acknowledged and under any acknowledgement filter that excludes Blank, for the same reason blank rows do. They also disappear the moment you pick a project or a supervisor: a row that belongs to no project cannot belong to the one you asked for. That is why the per-project export from HSEQ → Alerts (which is scoped to that project) never contains one.

Dates and timezones

Every date and time renders in the row’s own project timezone (falling back to Australia/Sydney). A Perth alert reads in Perth time no matter who runs the report or where they are, so a report spanning states never shifts a row onto the wrong day.

Export

Export XLSX exports the rows on screen, unpaginated, with the filters as they are when you click. It runs in the background:

• It appears under Exports, under the filters and above the table. You can leave the page while it is created.
• Each export has Download when it is ready, Run Again when it failed or expired, and Delete.
• You get an email when it is ready. The file is kept for 90 days.
• The file is named alerts-<date>-<time>.xlsx, for example alerts-2026-04-18-0930.xlsx.
• An export of more than 100,000 rows is refused. Narrow the dates, projects or supervisors and try again.

The workbook has three sheets:

1. Alerts Detail — the 17 columns exactly as shown on screen.
2. Summary by Alert — Title, Type, Issued On, Issued By, Level, Mandatory, Total Supervisors, Distinct Supervisors, Acknowledged, Not Acknowledged, No Response, Response Rate %.
3. Summary by Supervisor — Supervisor, Total Alerts, Distinct Alerts, Acknowledged, Not Acknowledged, No Response, Response Rate %.

Because each prestart response is its own row, the summary denominators count rows. The Distinct Alerts and Distinct Supervisors columns sit beside them so a supervisor who acknowledged one alert on five prestarts cannot be misread as five alerts. Distinct Supervisors counts people, so an unassigned org alert row counts as none.

Response Rate % is answered (Yes or No) ÷ total, rounded half up: 5 of 8 is 63%.

Two people with the same name stay two rows in Summary by Supervisor; their numbers are never added together.

The Export button on the project Alerts screen (HSEQ) exports the same file for that project, by the same rules: the alerts you ticked, or else the dates you choose (leave them blank for every alert). The dialog shows Download XLSX when the file is ready, and you get an email too. You need Alerts › Manage/respond to alerts on the project. The dialog links across to this report.

On the mobile app, Export on the Alerts screens exports every alert on the project. You get an email when it is ready, and the share sheet opens if you are still on the screen. You need Alerts › Manage/respond to alerts on the project.

Permissions and visibility

Viewing the report needs Reports › View admin reports.

It only ever shows projects you are a member of. Someone who is a member of no projects sees “No projects visible”.

Alerts Report (download)

A spreadsheet of who acknowledged each alert and bulletin on one project over a date range: every alert against every supervisor, with totals by alert and by supervisor. It keeps the Lacroo Core layout.

The file is named <Project> Alerts Report <From> - <To>.xlsx, for example Riverside Road Upgrade Alerts Report 1 Oct 2025 - 31 July 2026.xlsx.

Who can run it

Anyone with Prestarts › Export prestarts on the project. By default: master admin, organisational manager, project admin, engineer, senior supervisor and supervisor.

Running it

1. Open Reports › Compliance › Alerts Report.
2. Pick From and To. These are whole days in the project’s calendar, up to 732 days apart.
3. Click Generate.

You get an email when it is ready. The file is kept for 90 days. If nothing matches, you are told “No alerts or supervisors for these dates.”

The three sheets

Alerts Detail has one row per alert per supervisor:

Summary by Alert: Alert Title, Type, Issued On, Issued By, Level, Mandatory, Total Supervisors, Acknowledged, Not Acknowledged, No Response, Response Rate %.

Summary by Supervisor: Supervisor, Total Alerts, Acknowledged, Not Acknowledged, No Response, Response Rate %. Two people with the same name stay two rows.

Response Rate % is answered (Yes or No) ÷ total, rounded half up.

Yes, No and blank

• An alert with a specified date shows Yes for everyone, with no time.
• Otherwise Yes means acknowledged, No means not applicable, and blank means no answer.
• The time is when the latest answer was saved.

Which alerts

Live alerts and bulletins for the project, and organisation alerts sent to it, whose specified date falls in the range. An alert with no specified date uses the day it was issued. Archived alerts are left out.

Who counts as a supervisor

Anyone whose role on the project is Supervisor or Senior Supervisor (a project role replaces their company role) and who is on the project team, or has been the primary or an associated supervisor on a live prestart or diary there.

Whose answer counts

The latest answer on that supervisor’s prestarts on this project, whoever pressed the button. When a prestart is duplicated, the answers copied onto the new prestart are not counted until someone changes them.

Differences from Lacroo Core

• Alerts with no specified date are included, on the day they were issued.
• An organisation alert appears on every project it was sent to, not only its home project.
• Supervisors who worked on the project stay in past periods after they leave the team.
• Senior supervisors are included.
• An answer counts for the supervisor whose prestart it is on, even when an admin ticked it.
• Two supervisors with the same name are never merged in Summary by Supervisor.
• Supervisors are sorted by name.
• A reversed or too-long date range is refused before the report starts.
• You are emailed if the report fails.
• The file downloads only for you, and is kept for 90 days.