Lightning risk assessment review and sign off: the engineer signs, a reviewer checks

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.

A review means nothing if the figures can move while the reviewer reads them, or after they approve. So in Lumex, once the engineer submits a report for review, its inputs cannot be edited and its figures cannot be recomputed. The same lock holds once the report is approved or rejected. The approved figures are the figures that were checked.

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.

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.

Lumex keeps every review cycle of an assessment, oldest first: who submitted it and when, the note they sent with it, who decided, the decision, the reviewer's note and the time. The report screen in the portal lists the engineer, the reviewer and both dates beside the report itself. The workspace activity feed records each submission and decision. A report still waiting six days after submission prompts an email to the person who submitted it, so a review nobody picked up does not go quiet.

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.

Lumex does the part a machine should do. Voltrace, its calculation engine, computes the risk by the method of the standard you choose and shows the working behind every figure. It does not decide whether the inputs describe your building, and it does not certify a structure. That judgement stays with the engineer who prepares the assessment and the reviewer who checks it. Lumex gives them the steps, the lock and the record. No report goes to a client before it is approved. Switch on independent review to make the approver a different person every time.

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 the standards Lumex supports, and for the product, the platform.