Missed workflow notifications for checklist submissions - July 2026

Summary

Between 8 and 15 July 2026, some form submissions did not send the notifications customers had configured through Workflows.

Only workflows triggered when a form or template was completed or updated were affected. Other workflow triggers continued to operate normally.

We’re sorry these notifications were not sent as expected.

What happened

On 8 July, an improvement to how form submissions reached Workflows exposed an issue where answers from completed forms were not correctly checked against workflow conditions.

In some cases, a submission that should have matched a configured workflow was incorrectly treated as not matching, so its notifications were not sent.

Because the affected workflows did not report errors, our existing monitoring did not alert us. We identified the issue on 15 July following a customer report.

Resolution

We corrected the matching issue on 15 July and confirmed that subsequent submissions were triggering workflows normally.

We then audited all workflows that may have been exposed and identified affected events. We resent missed notifications where it was safe to do so and contacted customers directly where a notification could not be resent.

We completed this review and customer follow-up by 17 July.

What we are improving

We have added targeted automated tests for this specific issue.

Further work includes:

• Additional monitoring to confirm that submissions matching workflow conditions result in the expected notifications.

• Broader automated testing of the complete submission-to-notification journey.

• A clearer escalation path for reports of missing notifications, so the right teams can investigate sooner.

Browser sign-on and Notice acknowledgements — July 2026

Summary

Between 7 and 14 July 2026, an issue affected some workers using browser-based sign-on when a required Notice needed to be acknowledged.

The issue was limited to browser-based sign-on. Workers signing on through the BuildPass mobile app, including automatic sign-on, were not affected.

What happened

The browser sign-on flow made a request that was not suitable for worker access. Under certain conditions involving an existing Notice and its sign-on records, the request failed.

From 7–13 July, this meant workers may have completed a web sign-on without acknowledging a required Notice. On 14 July, affected workers were instead prevented from completing sign-on.

Not every browser sign-on or Notice was affected.

Resolution

We restored the worker-safe process on 14 July and confirmed that browser sign-on was operating normally again.

We then audited the affected records, contacted relevant customers and provided reports showing the Notices and workers requiring review. We also released a self-service tool allowing customers to contact affected workers and collect their acknowledgement.

What we are improving

We are committing significant engineering time to improving how we build, test and release changes to critical workflows such as sign-on, safety Notices and compliance processes.

This work includes:
- Stronger risk assessments and review requirements for changes involving compliance, permissions or sensitive data.
- Broader automated and manual testing of complete worker journeys, including multiple workers and different sign-on methods.
- More structured quality assurance
- Clearer error reporting, monitoring and alerts so failures can be detected and investigated sooner.

We have already added targeted regression coverage for this Notice acknowledgement flow. We are also adjusting our delivery practices to allow more time for testing and quality assurance when changes affect critical customer workflows.