Massachusetts Issues RFP for Bids for Long-Term Contracts

Massachusetts loves a good acronym. RFP, DPU, DOER, ISO-NEat this point, the state could power the grid with
leftover alphabet soup. But when Massachusetts issues an RFP for bids for long-term contracts,
it’s not just paperwork for paperwork’s sake. It’s a big, deliberate move that can shape what gets built, how it
gets financed, and how reliably the lights stay on when everyone cranks the heat (or AC) at the same time.

In plain English: an RFP (Request for Proposals) is Massachusetts saying, “We want specific resources, on a specific
timeline, under specific ruleswho can deliver the best value?” And “long-term contracts” are the part that makes
lenders, developers, and spreadsheet enthusiasts nod approvingly. A stable contract can turn a promising project
into a financeable project. Without that revenue certainty, many grid-scale projects remain stuck in the “great idea,
good luck funding it” phase.

This article breaks down what these RFPs are, why Massachusetts uses them, how the bidding process typically works,
and what the most recent waveespecially the state’s energy storage solicitationssignals for the future.
Expect real-world details, a few examples, and minimal legalese (because everyone deserves a break).

What “Long-Term Contracts” Mean (and Why Massachusetts Keeps Using Them)

In energy policy, “long-term” usually means long enough to outlast your phone contract, your average houseplant,
and at least one streaming service price hike. These contracts can run for many years, providing predictable revenue
tied to energy, environmental attributes, capacity, or other grid services.

Massachusetts relies on competitively bid long-term contracts because they can:

• Lower financing risk by giving projects a stable, bankable revenue stream.
• Drive competitiondevelopers sharpen pricing when they’re bidding head-to-head.
• Target specific needs like peak reliability, emissions reductions, or grid flexibility.
• Create accountability through milestones, security requirements, and regulatory review.

The basic logic is simple: Massachusetts sets the goal, designs the rules, and then lets the market compete to meet
themwhile regulators review the outcome to protect ratepayers. In practice, it’s a balancing act between speed,
cost, reliability, and fairness.

The Headline Example: Massachusetts’ Section 83E Energy Storage RFP

One of the most talked-about recent “Massachusetts issues RFP” moments involves grid-scale energy storage.
Under a framework commonly referred to as “Section 83E,” Massachusetts launched a competitive solicitation designed
to support large storage projects with long-term contractsstarting with a major first round sized around
1,500 MW of mid-duration energy storage.

Storage is a big deal because it turns the grid from a real-time juggling act into something closer to a well-managed
pantry. Instead of needing perfect timing between generation and demand, storage can shift electricitycharging
when supply is plentiful and discharging when demand is highest.

What counts as “mid-duration” storage?

In this Massachusetts procurement context, “mid-duration” doesn’t mean “kinda long” in a vague way. It’s defined by
the ability to dispatch at full rated capacity for at least 4 hours and up to 10 hours. That window
is designed to help cover peak periods and support reliability when renewables fluctuate.

Who issues the RFP?

In many Massachusetts clean energy procurements, the investor-owned electric distribution companies (the utilities
serving customers) play a central role, coordinating with state energy agencies. The RFP is typically structured
so bids are evaluated with oversight, including an independent evaluator and regulatory review steps.

What the RFP is actually buying: “Environmental attributes” (not necessarily the electrons)

Here’s where Massachusetts gets wonderfully specific. In the first major round of this storage solicitation, bids
centered on environmental attributesespecially Clean Peak Energy Certificates (CPECs).
Think of CPECs as a policy tool designed to reward clean energy that shows up (or reduces demand) during peak periods,
when the grid is typically most stressed and fossil generation is more likely to be on the margin.

Structuring a long-term contract around environmental attributes can create a bankable “floor” for a project while
still allowing the storage resource to participate in wholesale markets (energy, ancillary services, andwhere
applicablecapacity) for additional revenue. It’s a policy approach that tries to combine reliability goals with
market incentives instead of picking a single tool and hoping for the best.

Key Rules and Requirements Bidders Need to Know

Massachusetts RFPs are not “send us a brochure and we’ll call you.” They’re rigorous, standardized, and designed to
test whether a project is real, financeable, and deliverable. For storage RFPs tied to long-term contracts, the most
important requirements often fall into a few buckets:

1) Eligibility and project sizing

Eligible projects must meet technical and interconnection-related requirements. In the Section 83E storage example,
projects were expected to be large (think utility scale), with minimum and maximum size thresholds, and connected at
transmission-level voltages rather than purely distribution-level interconnections.

2) A real schedule, with real deadlines

Massachusetts RFPs publish a schedule: bidder conference, Q&A deadlines, proposal due dates, selection windows,
and contract execution targets. That schedule matters because it shapes development pacing and signals how quickly
the state expects capacity to come online.

As a practical example of how “real” these timelines get: the solicitation schedule included a firm proposal deadline,
then a project selection window, then a contract execution period, and then a planned timeline for submission to the
Department of Public Utilities for approval. For developers, that’s not just a calendarit’s a financing and staffing plan.

3) Pricing rules that limit surprises

One reason Massachusetts uses an RFP structure is to create apples-to-apples comparisons. In the storage RFP example,
bids for CPECs used an annual fixed pricing approach (a predictable $/certificate structure) with guardrails designed to
keep bids within program parameters.

4) Interconnection and deliverability

A storage project isn’t valuable if it’s stuck in an interconnection queue forever. Massachusetts RFPs place heavy
emphasis on interconnection status, upgrade plans, and deliverability. This is where developers have to prove their
homework is done: studies, milestones, and credible pathways to commercial operation.

5) Oversight, transparency, and an independent evaluator

Competitive solicitations can raise fairness concernsespecially when utilities have affiliates, lots of market power,
or just too much opportunity for “oops, we accidentally saw your bid.” That’s why these processes often include
independent oversight and structured “standards of conduct” to protect integrity.

How the Bid Evaluation Process Usually Works

While details vary by solicitation, Massachusetts long-term contract RFPs generally follow a familiar pathway:

1. Stage 1: Eligibility and completeness. Did you follow instructions? Did you include required forms?
   Do you meet minimum technical and legal requirements?
2. Stage 2: Price and value analysis. How does the bid compare on cost-effectiveness, risk allocation,
   and benefits to Massachusetts customers?
3. Stage 3: Viability and deliverability. Can this actually be financed and built? Is the interconnection
   realistic? Are permits plausible? Is the schedule credible?

The best bid isn’t always the cheapest. Massachusetts evaluators typically look for a portfolio that balances price with
execution risk. A slightly higher-priced project with strong interconnection readiness and clean permitting may beat a
lower-priced bid that looks like it’s built on optimism and a single screenshot of a concept drawing.

Regulatory Approval: Why Winning Isn’t the Same as “Done”

Massachusetts long-term energy contracts generally don’t become fully effective until they survive a regulatory review
process. That review is where ratepayer protection shows up in a concrete way: regulators examine contract terms,
cost recovery structures, and whether the solicitation complied with legal requirements.

For bidders, this means two important things:

• Contract language mattersyou may win, negotiate, and still face conditions that require adjustments.
• Time mattersregulatory review adds a step that must be planned into financing and construction schedules.

This is also why Massachusetts RFPs spend so much time on process, recordkeeping, and oversight. A clean procurement
record can make approvals smoother; a messy one can become a headache with footnotes.

Why Massachusetts Is Betting Big on Energy Storage

Massachusetts has ambitious climate and reliability goals, and storage has become a “Swiss Army knife” resource:
it can shift energy, reduce peak demand, support renewable integration, and provide grid services. The state’s storage
procurements are also designed to create a pipeline of projects rather than a one-and-done announcement.

In the Section 83E framework, the state’s procurement plan spans multiple years and multiple tranchesreflecting a
broader strategy to scale storage over time rather than assuming the industry can instantly deliver everything at once.

What Happens After the RFP: Selections, Portfolios, and Real Projects

Once bids are received and evaluated, Massachusetts can select individual projects or a portfolio. In the storage case,
public reporting indicated that Massachusetts ultimately selected a set of large projects totaling roughly
1.268 GW in the first major storage procurement roundillustrating that “up to 1,500 MW” doesn’t always mean
“exactly 1,500 MW,” especially when cost-effectiveness and viability screens do their job.

It’s also common for RFPs to attract multiple bids but only a subset to move forward. Competitive solicitations are
designed to do exactly that: filter projects until the state ends up with a shortlist that is both economical and buildable.

Practical Takeaways for Developers, Communities, and Curious Ratepayers

If you’re a developer or investor

• Read the definitions like your financing depends on itbecause it does.
• Interconnection readiness is not optional; it’s a central scoring factor in practice.
• Model downside scenarios (delays, upgrade costs, market price shifts) and show you can survive them.

If you’re a city or town hosting a project

• Expect outreach to cover siting, safety, design, and local benefits.
• Ask about construction timelines, traffic, noise, emergency response planning, and ongoing operations.
• Request clarity on how the project interacts with local zoning and permitting requirements.

If you’re a ratepayer

• Long-term contracts can help bring new infrastructure online that supports reliability and emissions goals.
• Regulatory review exists to keep the “good idea” from becoming an “expensive surprise.”
• Storage can reduce peak costs over timebut outcomes depend on execution, market conditions, and contract structure.

FAQ: Massachusetts RFPs for Long-Term Contracts

Is an RFP the same as a law?

No. The law creates the authority and the goals; the RFP is the tool used to implement that authority through a
competitive process.

Do long-term contracts guarantee lower bills immediately?

Not automatically. Long-term contracts are about predictable pricing and enabling investment. The value proposition
typically includes reliability, emissions reductions, and longer-term system benefitsnot always a short-term discount.

Why not just let the market build storage without contracts?

Some storage gets built merchant (without long-term contracts). But if the state wants specific outcomeslike a certain
amount of storage by specific datescontracts can reduce risk and accelerate deployment.

What’s the difference between buying energy and buying “environmental attributes”?

Buying energy is purchasing electricity itself. Buying environmental attributes is purchasing the clean-energy “credit”
associated with production or performance, which helps meet policy goals like clean peak requirements.

Closing Thoughts: Why This RFP Moment Matters

When Massachusetts issues an RFP for bids for long-term contracts, it’s doing more than announcing a procurement.
It’s setting market rules, steering investment, and signaling prioritiesespecially around reliability and decarbonization.
The storage-focused long-term contract solicitations show how the state is trying to build a grid that can handle more
renewables without turning peak hours into a stress test.

The big picture is straightforward: Massachusetts is using long-term contracting to move from policy goals to physical
infrastructureprojects in the ground (or, in the case of batteries, projects on concrete pads with a lot of very serious
electrical cabinets). If you want to understand where New England’s grid is heading, follow the RFPs. They’re basically
the state’s “shopping list” for the next decade.

Experiences from the RFP Trenches (Because the Fine Print Has Fine Print)

If you’ve never lived through an RFP response cycle, imagine training for a marathon where the route changes mid-run,
you’re required to carry a binder, and someone periodically asks you to “please provide supporting documentation.”
That’s the vibeespecially for a high-stakes Massachusetts long-term contract solicitation.

First comes the RFP drop. Teams gather around the PDF like it’s a season finale. Someone says,
“It’s only 95 pages,” and another person laughs the way you laugh when you’ve already accepted your fate.
Engineers start searching for interconnection requirements. Finance people start building models. Legal folks start
highlighting defined terms with the intensity of a true-crime investigator.

Then comes the definition phase, which is where hopes and dreams go to be clarified. What does
“mid-duration” mean here? What exactly counts as “Full Rated Capacity”? What’s the contract buyingenergy,
certificates, or both? The team discovers that one small definition can change the entire revenue model. This is also
where the group chat fills up with messages like “Can someone confirm whether this is delivery into GIS accounts?”
and “Are we sure the schedule says noon EDT and not local time?” (Spoiler: the deadline is always real, and it is
always sooner than it feels.)

Next is the schedule sprint. The bidder conference goes on the calendar. The internal deadlines go on the
calendar. Then more internal deadlines go on the calendar because nobody trusts the first internal deadlines. A project
manager starts saying “we’re on track” in a tone that suggests they are using “track” as a motivational concept, not a
factual statement.

As the proposal comes together, teams often learn that RFPs are less like a single essay and more like a group project
where everyone has a different grading rubric. The technical team wants precision. Finance wants bankability. Legal wants
to avoid committing to anything that could be interpreted as “forever.” Meanwhile, someone is tracking the bid fee and
making sure it’s calculated correctly, because nothing says “please take us seriously” like forgetting a required payment.

The night before submission is its own category of human experience. There’s a final check that every form is included,
every file name is correct, and every attachment is the right version (because “Final_FINAL2_REALLYFINAL.pdf” is a classic,
but not a strategy). People triple-check that confidential and public versions are handled correctly. Someone reads the
submission instructions one more time, not because they expect new information, but because hope is a powerful drug.

And thensubmission. The team hits upload, watches progress bars crawl across the screen, and briefly forgets how to
breathe. Once it’s in, there’s a strange calm. Not peace, exactlymore like the quiet you feel after sprinting through
an airport and realizing your flight is delayed anyway. The project isn’t “done,” of course. If selected, it’s contract
negotiations, regulatory review, permitting milestones, interconnection steps, and construction planning. But in that
moment, the RFP is no longer a document. It’s a timestamp.

The main lesson from the trenches: Massachusetts RFPs for long-term contracts reward teams that treat the process like
an integrated disciplineengineering, finance, legal, permitting, and community engagement all pulling in the same direction.
The state isn’t just buying capacity. It’s buying confidence that the project can show up, perform, and deliver value for
years. That’s why the RFP reads like it does. It’s not trying to be poetic. It’s trying to be buildable.