Washington Clean Energy Fund Research, Development and Demonstration Grants 2026: Approximately $10 Million for Emerging Clean Energy Technologies, Closing 3 September 2026

Washington Clean Energy Fund Research, Development and Demonstration Grants 2026: Approximately $10 Million for Emerging Clean Energy Technologies, Closing 3 September 2026

Washington State Department of Commerce is accepting applications for a new round of the Clean Energy Fund Research, Development and Demonstration (RDD) Program. The program is aimed at strategic research and development for new and emerging clean-energy technologies that can help Washington meet its climate goals. The public program page lists approximately $10 million in Climate Commitment Act funding and an application deadline of September 3, 2026, at 4 p.m.

This is a project-funding opportunity for organizations that can move a technology beyond the earliest research stage and toward demonstration or practical deployment. The program page identifies a technology readiness level (TRL) range of 4–7 upon award. That range generally points to work with a meaningful technical foundation, rather than an idea that exists only as a concept or a fully commercial product seeking ordinary expansion money. Applicants should use the official Request for Applications (RFA) for the controlling definitions, budget rules, award terms, and submission instructions.

Key details

The public summary does not state a maximum or standard amount for an individual award. Do not assume that the approximately $10 million will be divided evenly among applicants. Read the RFA before setting a request or building a multi-year budget.

What the RDD program is designed to support

Commerce describes this round as funding for strategic research and development of new and emerging clean-energy technologies. The emphasis matters. A proposal should connect technical work to a credible Washington need and explain what the requested grant would make possible that the applicant could not accomplish as effectively with existing resources.

The program page says funded projects should align with Washington’s 2021 State Energy Strategy. That gives applicants a policy reference for framing the public value of the work. A strong narrative can connect the technology to measurable climate progress, energy-system resilience, economic development, job creation, public health, or another outcome supported by the strategy. Those connections should be specific to the project rather than broad statements about climate change.

The funding comes from Washington’s Climate Commitment Act. Commerce says the act puts cap-and-invest dollars toward reducing climate pollution, creating jobs, and improving public health. Applicants should therefore explain both the technical case and the public benefit. A technically interesting project may still be a weak fit if its Washington relevance, emissions pathway, demonstration context, or route to use is unclear.

The RDD label also suggests a stage between basic research and routine commercial activity. The official page does not provide a full TRL glossary, so applicants should use the RFA and the Department of Energy’s linked TRL resource to describe their starting point honestly. Include evidence for the claimed stage: prototype test results, relevant bench or field data, validated components, a pilot environment, or other documentation appropriate to the technology. Avoid selecting a TRL only because it sounds favorable.

Who may be eligible

The listed applicant types are Washington-based for-profit organizations, nonprofits, local governments, research institutions, federally recognized tribes, higher education institutions, national laboratories, and state agencies. This is a broad institutional list, but it is not a guarantee that every organization can submit independently. The RFA controls details such as organizational status, partnerships, project roles, cost treatment, and any required registrations or certifications.

Organizations based outside Washington may still be eligible when they benefit the state and have a significant presence in Washington through investments or research. That language is important for companies, universities, laboratories, and other entities headquartered elsewhere. An out-of-state applicant should document the Washington connection instead of treating it as self-evident. Useful evidence might include an in-state facility, research collaboration, deployment site, investment, workforce activity, or a clear Washington-hosted demonstration, provided the evidence fits the RFA’s requirements.

For a company, eligibility should be tested against more than incorporation. The proposal needs to show why public funds support a Washington clean-energy objective and how the project creates value in the state. For a university or research institution, identify the Washington investigators, facilities, partners, and users who make the work relevant locally. For a tribe, local government, or state agency, describe the community or service context and how the project can translate into public benefit.

Technology areas and project fit

Commerce names four eligible technology categories:

• Advanced bioenergy, biofuels, and biorefining.
• Advanced energy storage, battery recycling, and battery technologies.
• Greenhouse-gas removal technologies and carbon capture.
• Flexible-load integration or grid modernization technologies.

The categories are specific enough that a general sustainability project may not qualify. Start by identifying the primary category and then explain the technical problem, proposed work, and intended demonstration. If a project crosses categories, make the relationship clear rather than listing every category as a keyword.

An applicant should be able to answer four fit questions. What clean-energy technology is being advanced? What technical barrier is the project addressing? Why is the work at an appropriate TRL for RDD support? Why does Washington benefit from this particular research or demonstration? If any answer depends on an assumption, resolve it by checking the RFA or asking Commerce before submission.

The program page says projects should be at TRL 4–7 upon award. That means the project plan should match the proposed maturity. A TRL 4 project may need component or subsystem validation; a more mature project may need an integrated demonstration, operational testing, or performance evidence. These examples are practical interpretation, not a substitute for the official RFA definitions. Use the source’s terminology in the final application and make the evidence traceable.

Application process and official materials

Begin on the Department of Commerce opportunity page and open the linked Request for Applications Box folder. The RFA is the document to consult for the complete application package. The public summary confirms the program purpose, applicant categories, TRL range, technology categories, date, and contact route, but it does not reproduce every required form or evaluation instruction.

Before drafting, download or review the RFA and build a compliance checklist from its sections. Confirm the required narrative, budget, work plan, milestones, attachments, signatures, file formats, page limits, and submission location. Because the summary does not state those details, this guide does not infer them. Missing a format rule can make a technically strong proposal ineligible or difficult to review.

The applicant conference was scheduled for July 13, 2026, at 2 p.m. The date has passed as of this page’s August 11 update. Commerce says questions and responses will be published in the Q&A folder in the RFA Box folder. Check that folder for clarifications before finalizing the proposal. If an important issue is not answered there, send a written question to [email protected] with the subject line “RD&D RFA 25/27.” Do not wait until the final afternoon to ask a question that could affect eligibility or budget structure.

Timeline and deadline

The application deadline is September 3, 2026, at 4 p.m. Commerce lists the anticipated notification date for successful and unsuccessful applicants as October 23, 2026. The public page does not state a project start date, award duration, payment schedule, or contracting timetable. Those details should come from the RFA and any later award documents.

Treat 4 p.m. as a hard cutoff. Set an internal deadline at least one business day earlier so the team has time to resolve upload, signature, validation, or formatting problems. Confirm the applicable time zone and submission rules in the RFA. The page displays the deadline but does not spell out the time zone in the text shown here, so applicants should not rely on a local-time assumption.

If your team attended or registered for the July conference, consolidate its questions and compare the answers with the current RFA. If you did not attend, that alone does not indicate ineligibility; the official page directs applicants to the RFA folder and Q&A material. Keep a dated copy of the documents used for submission so the final proposal can be reconstructed if the page or folder is updated.

What to prepare before writing

The most useful early work is an evidence map. List each important claim in the proposal and pair it with the test result, citation, partner commitment, market or deployment evidence, or policy source that supports it. At minimum, prepare:

• A plain-language description of the technology and the problem it addresses.
• A defensible starting TRL and evidence for that assessment.
• A work plan that links tasks to technical milestones and a demonstration or validation outcome.
• A Washington benefit statement tied to the project’s location, partners, users, jobs, emissions impact, or public-service value.
• A realistic budget built from the RFA’s eligible-cost and matching-fund rules, if any.
• Roles for the applicant, researchers, vendors, deployment partners, and other collaborators.
• A risk register covering technical failure, permitting, supply chain, data, safety, schedule, and adoption issues relevant to the project.

Ask an independent reader to identify where the proposal jumps from laboratory promise to expected impact without showing the intermediate proof. Reviewers need to understand not only what the technology could do, but what this grant-funded period will test, measure, and decide.

How to make the proposal easier to evaluate

Organize the narrative around a short chain: need, technical barrier, proposed intervention, measurable test, Washington benefit, and next decision. Use the same names for work packages and milestones in the narrative, timeline, budget, and risk plan. Consistency lets a reviewer check whether the requested funds actually support the promised work.

Quantify outcomes where the project can support them. Examples include an efficiency target, durability threshold, cost-per-unit objective, emissions measurement, throughput, safety criterion, or field-performance result. Do not manufacture precision. A bounded target with a clear measurement method is more useful than an impressive number with no baseline or test protocol.

Make the project’s public value distinct from the applicant’s commercial upside. A company can explain its route to market, but the application should also show why the work advances Washington’s energy and climate objectives. Explain who will use the result, where validation will occur, what knowledge or infrastructure will remain available, and what follow-on investment or deployment decision the project could inform. These are preparation recommendations based on the program’s stated strategic R&D and Washington-benefit focus; the RFA remains the authority for scoring criteria.

Common mistakes to avoid

The first mistake is submitting a concept that is too early. If the project will not reach the stated TRL range upon award, explain the actual maturity and check whether the RFA permits it. The second is presenting a commercial expansion plan without a research, development, or demonstration question. The third is treating Washington location as a slogan rather than documenting partners, facilities, investment, deployment, or research benefit.

Other avoidable problems include an unsupported TRL claim, milestones that cannot be measured, a budget that does not map to tasks, and a proposal that ignores the Q&A folder. Do not assume the total program amount is an individual award ceiling. Do not copy a prior application without checking the 2026 RFA. Finally, do not leave file naming, signatures, registrations, or upload checks until the deadline day; the official summary does not list those mechanics, so they must be verified in the application materials.

Frequently asked questions

Is this funding available outside Washington?

Possibly. Commerce says out-of-state organizations may still be eligible if they benefit Washington and have a significant Washington presence through investments or research. The RFA should be used to confirm how that test is applied and what evidence is required.

How much can one applicant request?

The public opportunity summary confirms approximately $10 million in total funding but does not state an individual award maximum. Check the RFA before setting the request.

Must the project use a specific technology?

It must fall within at least one category named by Commerce: advanced bioenergy, biofuels and biorefining; storage and battery-related technologies; greenhouse-gas removal or carbon capture; or flexible-load integration or grid modernization.

What technology stage is expected?

Commerce says projects should be at TRL 4–7 upon award. Use the linked TRL resource and the RFA to classify the project and support the classification with evidence.

Can I still ask questions after the applicant conference?

The conference was listed for July 13, 2026. Commerce says questions and responses will be published in the RFA Q&A folder and provides [email protected] for written questions. Check the folder and contact Commerce promptly about unresolved material issues.

When will applicants hear back?

Successful and unsuccessful applicant notifications are anticipated October 23, 2026. The page does not promise that date as a final decision deadline or provide award contracting details.

Official links and next steps

Start with the Washington State Department of Commerce RDD opportunity page. From there, open the linked Request for Applications Box folder and review the current RFA, Q&A material, and any associated files. The official page identifies September 3, 2026, at 4 p.m. as the application deadline and lists [email protected] for written questions.

The immediate next step is a fit check: identify the eligible technology category, document the project’s TRL, and write a three-sentence explanation of the Washington benefit. If those three pieces are credible, move to the RFA checklist and budget. If one is missing, resolve it before spending time polishing the narrative. Because this is a competitive public-funding call with approximately $10 million available across the program, accuracy about eligibility, evidence, and submission instructions should take priority over making the proposal sound larger than it is.