Design System

Patterns / Email

Five compositions. One voice.

Operator emails are short, factual, one-action. The recipient is a busy supervisor reading on their phone between rounds; if the email needs a scroll, it has failed.

1. Hazard report submitted

Subject: Acknowledge required: SR-1042 — Scaffolding fault, Site AHigh-severity report needs your acknowledgement

SR-1042 needs your eyes.

Field team flagged a scaffolding stability issue at Site A on 26 Apr at 14:32. Initial classification: High.

Please acknowledge so triage can proceed.

Acknowledge SR-1042 →

2. Action assigned

Subject: Action assigned: A-204 — Replace scaffolding cross-bracingDue 2026-04-28 · site: Site A

You have a corrective action.

From SR-1042 — Replace cross-bracing on engine room scaffolding, install grounding clips.

Due: 28 April 2026, 17:00. Upload evidence photos before submitting for verification.

Open A-204 →

3. Verification request

Subject: Verify required: A-204 marked completeEvidence + photos attached for your sign-off

Verify A-204.

Site team marked the corrective action complete on 28 April at 16:18. Three evidence photos attached. Please review and sign off — or reject with a reason.

Review evidence →

4. Closed report — closeout summary

Subject: Closed: SR-1042 — Scaffolding stabilityResolved 2026-04-29 · Lessons learned attached

SR-1042 is closed.

Final classification: High · resolved 29 April 2026 at 11:42. One action issued, one verified, management review complete.

Lessons learned: Cross-bracing inspection cadence increased from quarterly to monthly across all scaffolds at this site. Standard operating procedure updated.

View full closeout →
Subject: Sign in to your operations dashboardLink expires in 15 minutes

Sign in.

Click the link below. It expires in 15 minutes. If you didn't request this, you can ignore the message.

Sign in →

If the email needs a scroll, it has failed. One subject. One paragraph. One CTA.