Reports where a supervisor has named you. Open one to write your own account of what happened and confirm the task you were doing.
File an incident report the same day something happens. Do not wait for a supervisor to be available.
Technician Accounts
Each technician named on this report writes their own account in their own words. Nothing here holds up filing or closing the report.
Your Account
You are named on this report. Write what happened in your own words and confirm the task you were doing at the time. This never changes anything a supervisor or the investigation team wrote, and you cannot see the investigation sections.
Section 1 · Report Identification
Section 2 · Event Details
Section 3 · Persons Involved
Tenure and task status are mandatory for every person listed. Every serious event in the 2022 to 2026 record where tenure is known involved someone at 13 months of service or less. Link a person to their PULSE account to notify them and let them give their own account of what happened.
Section 4 · Event Classification
Serious injury or fatality potential: answer this before anything else
Could this event, under slightly different circumstances, have resulted in a fatality or a life-altering injury? The actual outcome does not change this answer. A dropped object that hit nothing is still Yes if it fell where someone works.
Section 5 · Notification and Escalation
Complete on the day of the event. Customer notification runs in parallel and does not wait for the internal chain. Filing this report is never gated on completing this section.
Work resumption gate
Work on the affected tower, asset or task does not resume until this line is completed, within 2 hours of the event. PULSE cannot stop work physically -- this only records the confirmation. Once set, it cannot be changed.
Section 6 · Investigation Team and Evidence
Serious events require at least two investigators, one of whom is independent of the crew involved. The involved supervisor does not investigate alone.
Section 7 · Sequence of Events
Build the timeline before analysing anything. Facts only.
Section 8 · Condition and System Checks
Every line must be answered. These are the questions that turn an event into a lesson. Answer N/A rather than leaving a line blank.
Section 9 · Root Cause Analysis
Section 10 · Corrective and Preventive Actions
Training on its own is not a corrective action -- it may only be used paired with a control higher up the hierarchy and a defined way of checking it worked. A set of actions that is entirely administrative needs the Director of Operations to sign it off in writing with the reason.
Section 11 · Lessons Learned
Section 12 · Review, Approval and Closure
Six signature lines. The HSE Lead role is held on an interim basis by the Director of Operations, so one person may sign both, on two separate lines. The injured person's line is optional.
Answer each line. Every one of them is checked again on the server, against the record itself, before a report can close. Ticking a line does not close anything on its own. A comment that does not apply reads N/A.
Close this report
The server checks all seven closure lines against the record before it will close anything. If one of them is not true yet, it says which, and nothing moves.
File this report
Filing needs Sections 1, 2, 3 and 4 to be complete. It does not need Section 5 to be finished, and it does not need a supervisor to be available. Once filed, the 72-hour or 5-working-day investigation clock starts, counted from the event.