Lightning risk assessment review and sign off: the engineer signs, a reviewer checks
In a sound lightning risk assessment review and sign off, the engineer who prepares the figures owns them, and a second competent person checks them before anyone relies on them.
A risk assessment under IEC 62305-2:2024, the Annex L method of NFPA 780-2026 or AS 1768:2021 ends in a verdict: protection is needed, or it is not, and if it is, which measures bring the risk down far enough. That verdict decides money, design and liability. It is only as good as the inputs behind it, and the person least able to see a wrong input is the person who typed it.
So the work splits in two. The engineer prepares the assessment and puts their name to the figures. A reviewer checks it and records a decision. Neither job replaces the other. This piece sets out what each person does, what a reviewer should look at, what must stay fixed while they look, and what the record of the decision has to hold. It sits beside a companion principle, that every figure must be traceable and reproducible, because a reviewer can only check a number that can be followed back to its inputs.
Why the person who prepares a risk figure should not be the only one to check it
The risk methods are long chains. A structure's dimensions become a collection area, the collection area and the lightning density become a count of dangerous events, and that count meets a probability and a loss to give each risk component. One wrong input travels the whole chain and lands in the verdict looking exactly like a right one. The arithmetic will be perfect. The answer will still be wrong.
The engineer who entered that input reads it the way they meant it, not the way they typed it. A second person reads it cold. They compare the length on the screen with the length on the drawing, the occupancy with the brief, the service lines with the site. That is the whole value of review: a fresh reader at the point where errors enter, before the figures leave the firm.
Signing and checking are different acts. The engineer signs to say the figures are theirs and they stand behind them. The reviewer checks to say a second competent person looked and agreed. A report that has only one of the two has half the assurance a client thinks it has.
Who does what in a Lumex™ workspace
| Role | What it can do with an assessment |
|---|---|
| Engineer | Creates and edits assessments, opens the calculation working behind every figure, submits a report for review, generates it and, once it is approved, sends it to a client |
| Reviewer | Works the approvals queue: takes a report into review, then approves it, requests changes or rejects it. Generates reports. Cannot edit an assessment |
| Admin | Everything an Engineer and a Reviewer can do, plus running the workspace and its team |
| Surveyor | Records site data on location. Cannot submit or decide |
| Viewer | Reads projects, assessments and reports. Cannot change an assessment or decide on a report |
A Reviewer is assigned to a project, and their queue shows the reports for the projects they review. A Reviewer cannot change the inputs they are judging, which keeps the two jobs apart: if something is wrong, they send it back with a note, and the engineer fixes it.
What a reviewer should look at before approving
A reviewer is not there to redo the arithmetic. The method does that the same way every time. They are there to check what went into it.
The structure is the real one
Dimensions, height, location and the services that enter the building match the drawings and the site. The lightning density used and where it came from are stated. Most wrong verdicts start here.
The right standard and edition
The project specification names a standard. The report must apply that one, in the edition it names. Under NFPA 780-2026 Annex L the owner or the authority having jurisdiction may set other tolerable values (L.6.2), so any change has a source.
The verdict follows
The occupancy, the loss values and the protection already in place reflect the brief. The engineer's written assumptions are reasonable. The verdict and any proposed measures follow from the figures, and nothing is claimed that the figures do not show.
What is locked while a report is reviewed and after it is decided
Decisions can still be corrected, but in the open. A reviewer can undo an approval, a rejection or a request for changes. That reopens the review as a new cycle, and the earlier decision stays in the history rather than being erased. A rejected report cannot simply be submitted again. The one thing that stays editable is the next review date, because it is a reminder about the record, not a change to what the record says.
A reviewer never approves their own work
A reviewer cannot approve their own report
A Reviewer cannot approve or reject a report they created or submitted. When a decision is undone, the original submitter is carried onto the new review cycle, so reversing a decision does not let a reviewer who submitted the report decide on it.
A setting for a strict two-person rule
By default an Admin can decide any report, their own included, which suits a one-person practice, and the PDF then says one person prepared and approved it. A workspace that switches on independent review blocks every role, Admin included, from approving, rejecting or requesting changes on a report they created or submitted. It needs at least two members to switch on.
What the record of a sign off should hold
When a verdict is questioned months later, the first questions are who prepared it, who checked it, what they said and when. A record that answers all four, for every round, is what turns a review from a habit into evidence.
The downloaded PDF names the standard and edition on its cover. Its sign off page names who prepared the report and who approved it, with the approval date, or says it is not yet approved. Blank lines for the date, place, signature and stamp follow, to be completed by hand. The full history of every cycle lives in the portal record.
The method computes, people decide
Read more on the companion principles:
why every figure must be traceable and reproducible,
why every figure names the edition it was computed on,
why the activity record is only added to and
why the assessment is independent of protection products.
For what a finished report should contain, see
audit-ready lightning risk reports.
For the methods themselves, see
Questions answered
Who should sign off a lightning risk assessment?
What does a reviewer check in a lightning risk assessment?
Can an engineer approve their own risk assessment in Lumex™?
Can a lightning risk assessment be changed after it is approved?
What happens when a reviewer requests changes?
Does the report itself show who reviewed it?
Can a report go to a client before it is approved?
The tolerable risk in IEC 62305-2 is not a fixed constant.
Clause 7.3 NOTE 1 gives RT = 1 × 10⁻⁵ per year as a
representative value of tolerable risk and adds that another value may be set once
the case has been investigated in detail. The standard's introduction then lets national or local regulations fix
RT, the tolerable frequency of damage FT
Get started today