Evidence in Advance: The Standards Record Insurers and Indemnifiers Expect to See
Insurance claims and indemnity disputes rarely begin with a shortage of opinion. They begin with a shortage of evidence that can be followed. A product fails, a customer alleges loss, or an indemnity clause is invoked, and the questions arrive in a particular order: which standard applied, was it the correct revision, who approved the position, and what record shows that the control was working on the day? The answers are usually scattered across project files, email folders and the memories of staff who have since moved on. Standards evidence is therefore not merely an audit chore. It is a risk-transfer asset, and it is built long before anyone speaks of a claim.
The question behind the questionnaire
Insurers, loss adjusters and legal teams tend to probe the same territory. They want to know the specification that governed design, manufacture or installation. They want to know whether that specification was current and whether any deviation was authorised. They want to see the calibration and maintenance record that shows the control was live rather than merely written. And they want to identify the competent person who signed the work off.
For UK businesses, the frame is familiar. The Insurance Act 2015 places a duty on policyholders to make a fair presentation of risk, which includes disclosing material circumstances. Product liability exposure under the Consumer Protection Act 1987 can turn on whether a defect existed and whether reasonable steps were taken. Contractual indemnities often depend on proof that the supplier met the specified standard. In each case, the quality of the standards record shapes the conversation.
Build the evidence spine early
A useful evidence pack rests on four connected records. The first is the controlled specification: the standard, clause set and customer amendment that applied to the project. The second is the revision history: what changed, when, and why the project remained on the revision it did. The third is the calibration and maintenance record: proof that measurement and production controls were operating within their defined limits. The fourth is the sign-off trail: who approved the design, the deviation and the final conformity statement, and on what authority.
None of these records is exotic. The difficulty is that they are often held by different functions and are rarely assembled with a future claim in mind. A project standards register, maintained from kick-off, is the simplest remedy. It should name the standard, the revision, the date of application, any transition period relied upon, and the customer-specific clauses that sit alongside it.
Revision history is not administration
When a standard is revised or withdrawn, the manufacturer's exposure does not end with a shelf update. An insurer may ask why a project continued on an older revision, whether a transition period applied, and how the decision was recorded. A standards decision log is the appropriate home for that narrative. For each material decision, record the clause concerned, the revision in force, the reason for the chosen position, the approver and the documents affected. The log need not be elaborate, but it must be contemporaneous. Reconstructed rationales carry little weight.
Equivalence decisions deserve particular care. If a substitution was made on the basis that it was close enough, the file should say what equivalence meant, who defined it and what evidence supported it. A vague assertion is difficult to defend; a recorded rationale is not.
Calibration, maintenance and the lived standard
The presence of a calibration certificate is not, by itself, proof that a control was effective. Insurers tend to look for the schedule, the certificates, the out-of-tolerance procedure and the link between an instrument and the batches it affected. The same applies to maintenance records for plant and tooling. The question is not whether a file exists, but whether it demonstrates that the standard was operating in practice.
For SMEs, a simple annual reconciliation is often enough: compare the calibration schedule against the asset register, confirm that certificates are present, and record any gaps with an action owner. If an instrument was found out of tolerance, the file should show the containment decision and the customer notification, where required.
Sign-off, competence and the named person
A signature without a name and a date is a weak record. The evidence pack should identify the approver, their role and the basis of their competence. Training matrices, professional qualifications and delegated authority records all help. Where engineering judgement was exercised because the standard was silent, the record should state the judgement, the evidence considered and the reviewer. That is not a counsel of perfection; it is the minimum needed to explain a decision years later.
A practical pack for members
A workable standards evidence pack for an SME typically includes:
- A project standards register naming each standard, revision and customer amendment.
- A revision and transition log, including equivalence and deviation approvals.
- Calibration and maintenance schedules, certificates and out-of-tolerance records.
- Conformity declarations, test reports and supplier certificates of conformity.
- A competence and training matrix for approvers and key inspection staff.
- Purchase order flow-down evidence showing that supplier obligations were communicated and acknowledged.
- A claim notification folder, opened only when needed, that preserves the records in the state they were in at the time of the event.
Indemnity follows the paper trail
Contractual indemnities are only as robust as the evidence behind them. When a purchase order flows down a standard, the supplier should be able to show that it received the correct revision and understood the applicable clauses. Where a customer seeks indemnity from a manufacturer, the manufacturer's file should connect the specification, the production record and the conformity statement. Gaps in that chain are where disputes settle on unfavourable terms.
Ready, not perfect
The aim is not a perfect archive. It is a record that can be explained. Members preparing for 2026 reviews may find it useful to run an annual dry run: select a recent project, ask a colleague to answer the insurer's questions using only the file, and note where the trail breaks. BEMSC member resources and the helpline can support that peer review, and the Council's community of practice is a sensible place to test whether a record would withstand scrutiny.
Standards evidence is at its most valuable when no claim exists. Assembled in advance, it supports insurance placement, indemnity negotiations and customer assurance. Assembled after notification, it is often too late to be persuasive.