An append-only audit log for lightning risk assessments, and its limits
An append-only audit log is evidence only when entries are added as the work happens and nobody can change them afterwards.
A lightning risk assessment passes through several hands before anyone relies on it. An engineer enters the building, a reviewer checks it, a report goes to an owner, an insurer or an authority. When a question comes later, the first thing anyone asks is who changed what, and when. A log that can be edited cannot answer that, because a quiet correction looks exactly like the original entry.
Why an audit trail must be append-only
An audit trail has one job: to let someone who was not there reconstruct what happened. It can only do that if each entry is written at the moment of the action and never touched again. Append-only means exactly that. New entries go on the end. Old entries are neither corrected nor removed, even when they record a mistake, because the mistake is part of the history.
The risk clauses themselves are about the comparison, not the records. IEC 62305-2:2024 clause 7.3 asks you to compare the risk with its tolerable value, and NFPA 780-2026 L.6.5 asks the same for each type of loss. Neither clause says how to prove later who entered the inputs or who approved the result. That falls to the tool and to the firm that signs the report.
Two records, each with its own audience
The workspace activity record
Each change your team saves to an assessment, a project or a project document, a new assessment draft starting or being removed, and each review step adds a line naming the person, the action, the assessment reference and the time. The line is written in the same database save as the change, so a change that fails to save leaves no line. Workspace admins read it on the activity page.
The staff audit log
When a Webority operator suspends or reactivates an account, changes a subscription or feature access, issues a refund or replays a payment notification, an entry records the operator and the outcome, and for some actions the values before and after. A bulk recompute of stored assessments writes one entry per assessment with the standard and edition it ran under, and records a failure as a failure.
A line in your workspace record names a signed in member of your workspace, or the Webority support team when it replies to or resolves one of your support tickets. A change saved with nobody signed in, such as a payment notification, is filed under the workspace owner with a note that it was recorded automatically. Any other change saved from the Webority admin portal writes no line in your workspace record, rather than invent an actor.
Nothing in Lumex™ edits or deletes an entry
Review decisions follow the same rule. Once a reviewer approves, rejects or sends back a report, that decision is fixed, and an attempt to change it is refused. Reopening a review starts a new round beside the old one, so the earlier decision, its note and its date stay on record. Removing the assessment removes its review rounds with it, while the activity lines for each step stay. The sign-off itself is described in the engineer signs, the reviewer checks.
What the audit log does not do
A principle page that claims more than the product does would break the principle it describes. These are the limits as they stand today.
| Question | Workspace activity record | Staff audit log |
|---|---|---|
| Who it covers | Members of your workspace, automatic events filed under the owner, and support replies to your tickets | |
| Who can read it | Workspace admins, on the activity page | Webority administrators, in the admin portal |
| What one entry holds | Who, what action, which record, when. Not the values that changed | Who, what action, outcome, and for some actions the values before and after |
| Never | Never | |
| Enforced by the database itself | No. The rule lives in the application | No. The rule lives in the application |
| Sealed against tampering, for example by hashing | No | No |
| If the entry cannot be written | For an assessment or project change, the change is not saved either | The action still stands and the failure is logged as an error |
More limits matter to an auditor. A draft autosave and a save that changed nothing add no line. The workspace record shows a person by their current name, so a renamed user appears under the new name on older lines. And the last updated by and last updated time on an assessment are a single stamp that each save overwrites, not a history; the activity record is the history.
An audit trail beside figures you can trace
Related principles:
why figures must be traceable and reproducible,
why the engineer signs and the reviewer checks,
why the current edition is held as data and
why the assessment is independent of protection products
Questions answered
What does the append-only audit log record about an assessment in Lumex™?
Can anyone edit or delete an entry in the Lumex™ audit log?
Does the audit log show what values changed in an assessment?
Are actions by Webority staff recorded?
What happens to the review history when a report is reopened?
Is downloading a report recorded as an edit?
Get started today