p>A policy announcement, funding page or tax-incentive summary is not yet a project benefit. Do not use it in an award recommendation, funding plan or diesel-displacement business case until the team has preserved the official record and established the program scope. The record should also assign an owner and state whether the project is only aware of the program, is reviewing eligibility, has applied, or has received a project-specific decision.
For example, the U.S. Environmental Protection Agency describes its Diesel Emissions Reduction Act (DERA) funding program as offering grants and rebates. That official program page cannot establish a stationary solar/BESS project’s eligibility. Program scope, applicant, equipment, location, timing and application conditions must be checked against the exact project.
Use policy awareness as an evidence task, not an approval
De-dieselization may appear in national policy, regional funding, utility initiatives, emissions programs, procurement rules, tax measures or development-finance requirements. These mechanisms have different administrators, legal bases, application cycles, evidence requirements and decision authorities. A project team should not combine them into one “incentive” line item.
The U.S. Department of Energy Federal Energy Management Program’s BESS procurement checklist is for federal agencies and is intended for procurement of commercial-scale lithium-ion BESS. It provides early-stage tasks, questions and reference points. It is useful as a scoped procurement reference; it does not confirm funding eligibility or recommend a particular diesel-displacement architecture.
Policy Evidence Register
Transfer this buyer-controlled register into the funding, procurement or investment-committee record. It is not legal, tax or grant advice, and it is not a fillable website record.
| Record field | What to capture | What it prevents | Accountable project owner |
|---|---|---|---|
| Jurisdiction and administrator | Country, state/province, local area where relevant, program administrator and official contact path | Treating a program in one jurisdiction as globally available | Owner / funding lead |
| Official source and check date | Official program page, notice, application document or governing text; version and date checked | Relying on a search snippet, reseller page or expired summary | Funding lead / counsel as appointed |
| Applicant and project scope | Eligible applicant type, location, technology, use case, delivery model and stated exclusions | Assuming that a diesel-reduction objective makes the proposed project eligible | Owner / project developer |
| Timing and status | Open/closed status, relevant deadline, award status and any stated budget or allocation condition | Placing an unconfirmed benefit in the approved project economics | Funding lead |
| Evidence and obligations | Baseline, equipment, procurement, commissioning, reporting, measurement or retention evidence explicitly required by the program | Discovering conditions after award or installation | EPC / owner’s representative |
| Reliance status | Awareness / eligibility review / application submitted / written award or determination / post-award compliance | Calling a possible program a secured project benefit | Project director |
Do not let a program change the technical decision too early
A project can investigate funding and still keep its technical and commercial decision separate. Power and energy boundary, duty cycle, site constraints, grid or off-grid operating mode, civil and electrical interfaces, transport, permitting, authority review, insurance, acceptance criteria and contract responsibilities remain project-specific. A program record may create an additional evidence requirement; it does not replace those decisions.
Our containerized BESS EPC interface review provides a route for assigning configuration, delivery, commissioning and handover responsibilities. Use the Policy Evidence Register alongside that project record rather than treating a funding application as a substitute for the project basis.
Award and reliance gate
| Stage | Permitted project statement | Evidence required before moving forward | Do not state |
|---|---|---|---|
| Awareness | A potentially relevant program has been identified. | Official source, jurisdiction and administrator recorded. | The project qualifies or funding exists for it. |
| Eligibility review | The team is checking fit against stated conditions. | Applicant, location, technology, timing and exclusion review; named owner. | Eligibility is confirmed. |
| Application planning or submission | The team is preparing or has submitted materials under the stated process. | Controlled submission record and any program-required evidence. | Submission equals award. |
| Written decision | A written project-specific determination has been received and recorded. | Decision document, stated conditions, responsible owner and change implications. | The decision replaces permitting, contract, utility or acceptance requirements. |
| Post-award implementation | The project is meeting the stated reporting or evidence obligations. | Obligation register, evidence owner, due dates and change-control path. | All project approvals or performance outcomes are automatic. |
A project should use a Hold when the program source is not official, the applicable geography or applicant is uncertain, a condition cannot be met from the proposed configuration, or a financial model depends on a benefit without a project-specific basis. The correct next action may be an official administrator inquiry, tax/legal review, a revised project basis, or removal of the assumed value from the decision record.
Questions for the project meeting
- Which exact public program is being discussed, and which official document governs it?
- Who is the eligible applicant, and does that entity match the project contracting structure?
- Does the program address the proposed location, technology and operating use case?
- What needs to happen before a possible benefit can be used in the project economics or award recommendation?
- Which documentation, reporting and change-control obligations survive into delivery and operation?
- Which project decisions remain outside the program administrator’s scope?
Request an EPC Interface Review
You may share the project jurisdiction, operating mode, proposed power and energy boundary, existing diesel baseline records, program documents and open delivery interfaces. Final eligibility, funding, tax treatment, design, permitting, authority decisions and acceptance remain subject to the program rules and responsible project parties.
Last Updated on 08/18/2026
