Oxaide
Credit checklist

Lender BESS due diligence checklist for project finance teams that need a harder downside read

Use this checklist when the battery story has to survive lender, adviser, and credit-committee scrutiny. The goal is not more paperwork. It is to test whether usable capacity, degradation, telemetry quality, and operating history actually support the financing case.

The checklist

1Request raw or near-raw BMS, SCADA, and historian exports, not only presentation-layer dashboards
2Test usable capacity against the health number being used in the financing case
3Review degradation mode, not just the headline SoH figure
4Check whether derating, thermal stress, or rack divergence is already visible in the operating history
5Assess telemetry completeness, timestamp integrity, and missing windows before relying on any conclusion
6Reconcile dispatch and cycling history against the downside assumptions embedded in the credit case
7Confirm whether warranty position, remediation history, and augmentation needs have been represented cleanly
8Translate the technical read into lender-grade language: proceed, reprice, reserve, tighten covenants, or monitor
BESS Refinancing ReviewUsable Capacity vs BMS SoHBESS Telemetry Quality Checklist
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.