A battery energy storage system procurement checklist should help make competing BESS RFP responses comparable before award. Start with one controlled matrix. Require every bidder to identify the offered configuration; the document revision and supporting evidence; every deviation or exclusion; the reviewer who owns the decision; and the award-gate status.
Use the matrix before you compare price
Fill in the buyer-input column, issue the same version to every bidder, and keep unresolved deviations open until a named project party closes them. The U.S. Department of Energy’s Federal Energy Management Program (FEMP) describes its checklist as a resource of tasks, questions, and reference points for federal agencies in the early stages of BESS project development. DOE states that its intended use is commercial-scale lithium-ion BESS procurement, although it may be used more generally for other BESS technologies; it is not a universal approval path. For a related containerized-solar RFQ structure, see our RFQ guide for containerized solar BESS.
This is a buyer-control tool, not a substitute for the signed contract, local engineering, utility or authority review, insurer requirements, or the project acceptance process.
Start with the response-control sheet, not a generic specification
A bid comparison breaks down when bidders answer different project versions. Before suppliers price a solution, establish the exact use case, operating duty, site inputs, interfaces, and boundary of supply that they are answering.
Use the BESS RFP checklist below, with one row for each decision area. Before issuing the RFP/RFQ, complete the Buyer requirement / project input column and define the allowed award-gate values—for example, complete, acceptable deviation, open buyer decision, or not comparable. Every bidder should complete the same response, evidence, and deviation fields and cite the applicable document revision.
| Procurement decision area | Buyer requirement / project input | Bidder must state or submit | Evidence / revision reference | Deviation, assumption, or exclusion | Buyer/EPC reviewer | Award-gate status |
|---|---|---|---|---|---|---|
| Use case and operating duty | ||||||
| Delivered configuration and boundary of supply | ||||||
| Site conditions, interfaces, and constraints | ||||||
| Functional and controls boundary | ||||||
| Project-requested safety, standards, and compliance evidence | ||||||
| Factory test, witness, and open-item approach | ||||||
| Transport, receipt, preservation, and document interface | ||||||
| Site acceptance and handoff prerequisites | ||||||
| Contract-proposed warranty, service, and spares terms |
A narrative statement that a bidder is “compliant” is not enough to compare offers. Ask for the specific configuration; the applicable drawing, BOM, firmware, or other document revision; the evidence scope; and the exception that supports the response. Different revisions, components, interfaces, or responsibilities should not be treated as interchangeable without a controlled project decision.
Ask for evidence that belongs to this project
A useful BESS procurement checklist does not prescribe a supposedly universal list of standards, certificates, or test steps. It gives the buyer a consistent way to request the evidence that the applicable jurisdiction, authority, utility, insurer, owner specification, and contract require.
For each project-specific requirement, ask the bidder or responsible project party to record:
- the country, jurisdiction, and decision stage;
- the authority, utility, insurer, owner, or contract party that requires it;
- the named requirement or edition, where applicable;
- the offered configuration and revision to which the evidence applies;
- the issuer, date, sample or test scope, conditions, and exclusions; and
- the reviewer, open item, dependency, and proposed resolution route.
This separates a declared document, a factory activity, a site task, and an approval decision. Equipment-side documentation does not by itself establish local design acceptance, permit approval, utility interconnection, insurer acceptance, or final contractual acceptance.
Carry open evidence through four decision gates
Do not wait until shipment or commissioning to discover that a bid comparison contains missing evidence or an unassigned interface. Use the same controlled register through the subsequent project decisions.
| Gate | Buyer decision | Examples of fields to control—not pre-filled proof | Accountable project role | Exit condition |
|---|---|---|---|---|
| Pre-RFQ | Is the project boundary sufficiently defined for comparable proposals? | Use case; configuration baseline; site and interface input; response format; deviation rules | Owner / procurement lead | RFP/RFQ issue authorized |
| Pre-award | Are proposals comparable, and are deviations and ownership visible? | Compliance/deviation matrix; document and test matrix; proposed responsibilities; assumptions and exclusions | Owner with EPC/technical reviewer | Commercial and technical award decision |
| Pre-shipment | Has the contract-defined factory-scope evidence and open-item process been controlled? | Agreed procedure where applicable; controlled records; open-item log; packing/document interface; handoff index | Contract-defined supplier and buyer acceptance authority | Contract-defined release decision |
| Pre-commissioning | Is the site handoff ready for its separate scope? | Site prerequisites; site responsibilities; handover index; punch-list ownership | Contract-defined site-handoff decision authority | Contract-defined site-handoff decision recorded |
These are decision controls, not mandatory milestones. The signed scope should define the actual deliverables, witness or hold points, review rights, acceptance criteria, remedies, and sign-off authority.
Keep factory evidence, site acceptance, and authority decisions separate
A factory acceptance test, shipment release, delivery receipt, site acceptance test, commissioning record, and energization event may all be relevant evidence when the project defines them. They do not automatically mean the same thing.
Before award, assign five questions:
- Which configuration and revision must the evidence cover?
- Which factory procedure, record, witness point, deviation process, and open-item process does the contract require?
- Which site inputs, commissioning activities, and acceptance evidence belong to the site scope?
- Who reviews each record, and who can make the relevant release or acceptance decision?
- Which authority, utility, insurer, owner, or contractual requirement has a separate submission or approval path?
Use the following mini-RACI as a project prompt. Replace every blank with named parties and the signed scope.
| Activity | Responsible party (R) | Accountable project party (A) | Consulted parties (C) | Informed parties (I) |
|---|---|---|---|---|
| Freeze offered configuration and revision | ||||
| Approve the bid-response and evidence format | ||||
| Log assumptions, deviations, and open items | ||||
| Make the contract-defined release decision | ||||
| Transfer controlled evidence and handover index | ||||
| Confirm site-readiness inputs | ||||
| Perform separately defined EPC, supplier, and site/O&M tasks | ||||
| Close assigned handover items |
Key: R = responsible; A = accountable project party; C = consulted; I = informed. This illustration does not allocate legal liability, regulatory authority approval, or contractual acceptance. The project scope must separately assign utility, authority having jurisdiction (AHJ), insurer, legal, and contractual responsibilities.
Add the spares and cross-border exception questions before award
Spares and after-sales questions are easier to resolve before a component issue occurs. Their purpose is to establish the configuration, documentation, and decision owner that an exception would require—not to imply stock, lead time, warranty acceptance, local service, customs clearance, or carrier acceptance.
| RFQ field / decision | Ask the bidder to state or confirm | Buyer / owner must decide | Do not pre-fill or imply |
|---|---|---|---|
| System identity | Model; serial/BOM/drawing revision; firmware or configuration baseline; part-number convention | Record owner and controlled-document location | That all revisions are interchangeable |
| Parts schedule | Part identity; equipment location/interface; project-defined written substitution and approval workflow; documented preservation/storage information | Criticality method; quantity; holding location; budget | Universal quantities or a standard critical-spares kit |
| Consumables schedule | Item identity; approved specification; documented storage/handling information and replacement trigger | Stocking owner; local procurement route; storage conditions | Consumable life or replacement interval |
| Service and authorization | Required diagnostic evidence; authorization/escalation contact; safe-work and return-approval route | Local authorized person/EPC/O&M role; escalation contact | Warranty acceptance, remote support, repair permission, or SLA |
| Packing and dispatch | Package dimensions/weight; handling marks; packing-list line-item data; preservation needs; transport classification/status and related documentation within the contracted scope, where applicable | Destination address; receipt constraints; unloading; broker/carrier contact | Universal packing method or dangerous-goods status |
| Commercial documents | Documents available within scope; proposed delivery term/place; origin/classification information only when contractually and legally confirmed | Importer/declarant; broker; tax/duty treatment; permits/licenses; carrier document requirements | Customs clearance or duty outcome |
| Receipt and returns | Receipt inspection record; serial/batch capture; discrepancy/photo protocol; return instructions when issued | Receiving party; quarantine/storage point; contractual return cost/arrangement | Return acceptance or replacement timing |
Where an item may be regulated for transport, require the responsible project party to determine the item’s transport classification and applicable requirements for the actual condition, quantity, mode, and route before release. Carrier acceptance remains an operational check. For sea carriage, the IMO explains that the IMDG Code governs relevant dangerous-goods carriage in packaged form; other modes require their separately applicable rules. Contract delivery allocation is different: the contract should state the selected Incoterms® rule, named place or port, and applicable edition—for example, Incoterms® 2020—together with any project-specific terms not allocated by that rule. The ICC overview explains that Incoterms® rules clarify delivery tasks, costs, and risks between sellers and buyers.
Compare deviations before comparing prices
A lower commercial total is not a comparable offer if the bidder omitted an interface, supplied evidence for a different configuration, or left an acceptance assumption unstated.
Before award, hold a single deviation review using the response-control sheet. Ask:
- Does the offer answer the controlled configuration and boundary of supply?
- Which requested documents are submitted, proposed, unavailable, or outside scope?
- Which factory, site, authority, utility, and acceptance activities are assigned—and which remain unassigned?
- Are the exclusions, document revisions, conditions, and dependencies visible to both commercial and technical reviewers?
- Does the contract record who decides release, handoff, final acceptance, return, or exception resolution?
Do not convert an unresolved line item into an implied supplier commitment. Resolve it with project-specific evidence and contractual language, or retain it as an explicit exception with an accountable decision owner.
Request a project-specific BESS RFQ discussion
Send the following inputs through the project RFQ enquiry form: use case; required or offered configuration/BOM revision; country and site; operating model; delivery boundary; decision stage; requested evidence; and known interfaces or exclusions. We can then discuss a project-specific RFQ response using those inputs. Final requirements, approvals, acceptance criteria, and commercial commitments remain subject to the applicable project review and contract.
