Short answer
AI site issue triage uses a language model to read reports from cleaners and client sites, classify each one by type and urgency, and route it to the person who owns it. For New Zealand cleaning companies the rule that matters most is that any report suggesting a notifiable event under the Health and Safety at Work Act 2015 bypasses the queue and goes straight to a duty manager.
- Each site report becomes a ticket with site, shift, category, urgency and owner.
- Possible notifiable events trigger a phone alert to a duty manager, never just a queue entry.
- Building faults belong to the client’s PCBU; triage drafts the handover to them.
- Measure time to first owner action, and audit for missed safety reports.
- HSWA changes from 1 April 2027 add critical risks; update triage rules before then.
What site issue triage does
Site issue triage reads every report that arrives from a cleaner’s app note, a client email or an after-hours text, and turns it into a structured ticket: what happened, at which site, how urgent, and who owns it. It does not fix anything or decide legal questions. It gets the issue to the right person quickly, with facts and photos in one place.
Reports in commercial cleaning fall into a predictable set: rework, consumables, building faults, access and security, extra-clean requests, and safety events. Safety events are rare and matter most. Extra-clean requests are the ones most often lost, and they are revenue.
The workflow at a glance
- Inputs
- Cleaner app notes and photos, client emails, after-hours texts and voicemail transcripts, site records (induction notes, building manager contact) and open tickets.
- Systems
- The rostering and task platform holding sites, shifts and checklists, the shared inbox in Microsoft 365 or Google Workspace, an SMS gateway, and the existing job system.
- Steps
- Ingest the message, match it to a site and rostered shift, extract the facts, classify type and urgency against written rules, merge duplicates, route to an owner, and draft an acknowledgement.
- Human review
- Anything safety-related triggers an immediate phone alert to the duty manager. Supervisors confirm routing on everything else daily and approve every reply to a client.
- Outputs
- A ticket with site, shift, category, urgency, owner and evidence; a drafted reply; a drafted handover when the fault is the building’s; a daily exceptions list.
- Measures
- Minutes from report to first owner action, share of tickets re-routed by a person, safety reports missed in monthly audit (target zero), and repeat issues per site.
- Risks
- A serious injury described casually and scored low, photos showing tenants or students, a drafted reply that admits liability, and alert fatigue from over-flagging.
Illustrative worked example
Illustrative example: a Wellington commercial cleaning company with 140 cleaners across 85 office, retail and school sites receives about 420 site reports a month. The figures are synthetic and the assumptions are stated below.
| Category | Reports a month | Default owner | Response target |
|---|---|---|---|
| Quality complaints and rework | 150 | Area supervisor | Same or next shift |
| Consumables and equipment | 110 | Stores coordinator | 2 working days |
| Building faults | 70 | Client building manager, via account manager | Handover within 1 hour |
| Access and security | 45 | After-hours supervisor | 30 minutes |
| Extra cleans and scope changes | 30 | Account manager | Quote in 1 working day |
| Safety and injury | 15 | Duty manager | Immediate phone call |
Assume a supervisor spends 6 minutes reading, looking up the site and forwarding each report today, and 2 minutes checking a prepared ticket afterwards. That saves 420 × 4 = 1,680 minutes, or 28 hours a month: about NZ$1,260 at an assumed loaded cost of NZ$45 an hour. Model fees are small: at roughly 3,000 tokens per report and an assumed US$5 per million tokens, under US$10 a month. Success is decided by a different number: whether all 15 safety reports reached the duty manager within minutes.
What New Zealand health and safety law expects
Under the Health and Safety at Work Act 2015, a business must notify WorkSafe “as soon as possible” after becoming aware of a notifiable event, by the fastest means available (section 56). Section 23 notifiable injuries include serious burns, serious eye injuries, hospital admission for immediate treatment, and medical treatment within 48 hours of exposure to a substance, which covers many cleaning chemical incidents. Section 24 incidents include a spillage of a substance and an electric shock. The site must be preserved (section 55) and records kept for 5 years (section 57). WorkSafe asks for deaths to be reported immediately on 0800 030 040.
Cleaners work in buildings someone else controls, so section 34 matters: where two businesses have a duty on the same matter, such as a broken stair nosing, each must consult, co-operate and co-ordinate. From 1 April 2027 the Health and Safety at Work Amendment Act 2026 replaces section 34 with a co-operation duty that depends on whether each business is small (fewer than 20 workers) or large, and introduces critical risks.
What stays with a human
- Deciding whether an event is notifiable, and making the notification.
- Anything said to an injured person or their whānau.
- Replies to formal complaints, and any wording that touches fault or refunds.
- Whether a cleaner keeps working at a site where they feel unsafe.
- Quotes for extra cleans and scope changes.
Where triage goes wrong
- Casual wording. “Slipped near the sink, all good now” gets scored as a quality note. Control: any mention of injury, chemical contact, blood, sharps, a fall or a threat forces the safety category whatever the model says, and every past safety report in the test set must be caught before go-live.
- Wrong site. Cleaners cover several sites. Control: match the sender to their rostered shift; ask when unclear.
- Duplicate storms. Five cleaners report one leak. Control: merge by site and category within a time window.
- Photos of people. Images can show tenants or students. Privacy principle 1 limits collection to what is necessary, so crop or blur before sharing with a client.
- Alert fatigue. If half the tickets are urgent, none are. Review urgency rates weekly.
Log every miss in an AI incident log and route ambiguous cases through a human review queue.
How to start and what drives the cost
Run a two-week shadow trial: the model triages, supervisors work as normal, and you compare. Cost sits in integrations (inbox, SMS, rostering platform), the rule set, the review screen and monitoring, not model fees. If sites and rosters already live in an operations platform such as the freshOps project in our portfolio, each report attaches to the right shift automatically. Our AI workflow automation service builds this routing with approvals in place.
Triage feeds the rest of the operation: a flooded site becomes a roster change message, and resolved tickets become evidence in contract performance reports. The cleaning industry guide maps the wider workflow.
Sources
- Health and Safety at Work Act 2015, New Zealand Legislation, Version as at 5 April 2025
- Health and Safety at Work Amendment Act 2026, New Zealand Legislation, 9 July 2026
- Notify WorkSafe, WorkSafe New Zealand, Updated 9 December 2024
- Principle 1: Purpose for collection of personal information, Office of the Privacy Commissioner, Accessed 19 October 2026
Written by the Levy Street team in Wellington. Last updated 19 October 2026.