Oxaide
Claims and underwriting checklist

BESS insurer review checklist for owners who need the technical position clean before the economics turn political

This checklist keeps insurer, broker, and owner conversations grounded in evidence. Use it when the battery story needs to survive claims, renewals, underwriting review, or dispute positioning without collapsing into screenshot theatre.

The checklist

1Establish the actual technical question: claim support, renewal, underwriting refresh, or dispute positioning
2Request raw or near-raw telemetry that supports the owner position rather than relying only on screenshots and summary PDFs
3Check whether reported SoH is commercially credible against usable-capacity reality
4Identify the likely degradation or stress mechanism, not just whether the site "looks off"
5Assess thermal stress, derating, rack divergence, and any precursor behaviour that changes insurer posture
6Document telemetry gaps and evidence boundaries so the insurer conversation does not overclaim certainty
7Translate findings into insurer-grade language that can survive broker, OEM, owner, and underwriter scrutiny
8Decide the next move clearly: support, narrow, retest, remediate, or escalate
Operating posture

Scope first

Defined review scope

Boundary, telemetry window, and mandate question are pinned down before conclusions move.

Encrypted handling

Protected review workflow

Review traffic and operating data are handled with encrypted transfer and controlled access.

Customer boundary

Customer-controlled deployment

Managed, private, and isolated deployment paths are available when the environment requires them.

Direct accountability

Principal sign-off

Technical accountability stays close to the method rather than disappearing into a generic workflow.