The challenge
Lessons from incidents are shared by e-mail or chat, and nobody knows who actually read them. Contractors on site often never receive the alert at all.
Approve, publish and prove that every affected person read the safety alert.
Write a one-page alert about a hazard, near miss or lesson, review and approve it — with a director step for critical alerts — and publish it to projects, companies, organization nodes, roles or people resolved from the organization chart. Each recipient acknowledges, optionally with a note and photo, and the alert closes when everyone has acknowledged or it expires.
Capability map
12 capabilitiesOverview
The challenge
Lessons from incidents are shared by e-mail or chat, and nobody knows who actually read them. Contractors on site often never receive the alert at all.
How Green Codes Pro helps
Green Codes Pro turns the alert into a controlled publication: approved through the workflow engine, delivered to real people resolved from the project organization, and tracked from delivery to acknowledgement with overdue reminders.
How it works
The 6 stages a record moves through, from the first entry to a verified close.
Stage 1
Draft
Stage 2
HSE review
Stage 3
Approve
Stage 4
Publish
Stage 5
Acknowledge
Stage 6
Close
Capabilities
12 documented capabilities, each verified against the product.
12 capabilities
Write an alert with category, severity, instructions and photos, in English and Arabic.
HSE review and approval through the workflow engine, with an additional director approval for critical alerts and return or rejection with comments.
Holders of the urgent-publish permission can publish straight from draft with a mandatory comment kept on the timeline.
Target everyone, a project, a company, an organization node, a role type, a unit or a person; targets are resolved to real recipients at publication.
Track delivered, opened, acknowledged, pending and overdue recipients, with optional notes and evidence photos on acknowledgement.
Overdue recipients are reminded once a day, and the alert closes when everyone has acknowledged or it expires.
Published, acknowledgement-required, overdue and closed notices are sent in-app and by e-mail, and by WhatsApp or push where configured.
Raise an alert from an incident or observation page, linked back to its source; automation rules can also raise one.
Contractor users see and acknowledge the alerts addressed to them in the partner portal, and see only their own company's side.
AI-assisted
Where AI is configured, "Draft with AI" proposes the alert text for the author to edit; a template is used when no model is available.
AI suggestions support qualified people — they never replace professional review, and every decision stays with your team.
AI across the platform →Draft with AI
Where AI is configured, propose the alert text for the author to edit, with a template fallback.
Mobile & field
Recipients acknowledge from a phone, optionally with a note and an evidence photo.
Business advantages
Proof that each person received and acknowledged the alert.
Contractors receive alerts through the partner portal.
Critical alerts require an additional director approval.
Urgent alerts can be published immediately by authorised people, with the reason recorded.
Alerts are raised directly from incidents and observations.
Safety Alerts
Book a live demo with a product specialist, or request a quotation tailored to your users, projects and sites.