Cisco's removal of Partial Commit from Services EA hardware forces 100% installed base coverage above a $200k ACV floor from July 26, 2026, and buyers who covered only critical assets face step-ups of 30% to 60% on hardware support spend
Partial Commit survives for software support but is gone for hardware services, so every eligible chassis, switch, and access point at every listed address must carry a service level. Combined with the True Up billing shift on the same date, buyers who previously covered 55% to 70% of their estate now face full-estate pricing with no downward flex and no growth allowance. The decision is whether to renew before July 26, 2026 and grandfather True Forward, or restructure hardware support outside the EA entirely.
Prepared by Redress Compliance · September 2, 2026 · Cisco advisory. Services EA and EA 3.0 renewal engagements, 2024 to 2026.
Executive summary
Cisco has removed Partial Commit from hardware services in the Services EA, leaving Full Commit as the only structure for HW CX from July 26, 2026.
Cisco's stated rationale is to guarantee a minimum Annual Contract Value and enterprise-wide coverage, which in practice converts a selective coverage decision into a mandatory 100% attach across the assessed installed base.
The change arrives bundled with a second structural shift on the same date: hardware support moves from True Forward to True Up, so growth is billed retroactively to the annual milestone rather than forward from it.
Two changes in one renewal cycle means the coverage expansion and the billing acceleration compound, and most buyers only model one of them.
A $200k ACV floor now gates HW CX eligibility inside a Services EA, and customers below it cannot include hardware support in the agreement at all.
Software support and Professional Services sit at a lower $100k TCV platform requirement, so mid-market buyers who used Partial Commit to stay under the hardware line are now pushed either up to the floor or out to standalone SmartNet.
Existing EA IDs retain True Forward for the remainder of their terms, including additional service purchases and upgrades, making the pre-July 26, 2026 renewal window the single largest lever available.
A 36-month renewal executed before that date preserves forward-only billing into 2029, which is worth more than most discount concessions Cisco will offer at the table.
What changed: Full Commit mechanics on hardware services
Until the July 26, 2026 transition, a Services EA buyer could enroll hardware support at Partial Commit and cover a defined subset of the installed base: the data center core, the WAN edge, the sites with an SLA attached to them, and leave the branch closet stack, the aging access layer.
And the lab gear uncovered or on ad hoc SmartNet.
Cisco has now removed Partial Commit from hardware services entirely. Only Full Commit remains, and Cisco's own framing is that this exists "to ensure a minimum Annual Contract Value (ACV) commitment and enterprise-wide coverage where applicable." The operative words are enterprise-wide.
Under Full Commit, services must be attached to all products in the purchased suite, and before the Service start date Cisco performs an installed base assessment that establishes baseline hardware coverage by address location and assigned service level. That assessment is the pricing event.
It is not a courtesy audit, it is the mechanism that converts every serial number Cisco can see at every listed address into billable scope.
Layered on top: hardware support inside a Services EA now requires a $200k ACV floor for both new sales and renewals, double the $100k TCV platform threshold that applies to software support (SW CX) and Professional Services. Below $200k you cannot include HW CX in a Services EA at all.
| Dimension | Partial Commit (pre 26 Jul 2026, HW) | Full Commit hardware (from 26 Jul 2026) | Full Commit software support |
|---|---|---|---|
| Attach obligation | Subset of assets by choice | All products in the purchased suite | All products in the purchased suite |
| Financial floor | No separate HW floor | $200k HW CX ACV, new and renewal | $100k TCV platform level |
| Baseline assessment | Limited to elected assets | Full installed base by address location and service level, pre start date | Entitlement based, self reported |
| Growth handling | True Forward, prospective | True Up, retroactive at annual milestone | True Forward retained, no current plan to change |
| Growth Allowance | Not applicable | None. No Services on Hardware are eligible | 105% initial cap (first 6 months), 115% ongoing |
| Downward flex | Exit uncovered assets at renewal | None. Quantities cannot be scaled down mid term | None mid term |
| Commit level choice | Elected per suite | Inherited from the Underlying Suite | Inherited from the Underlying Suite |
The row that costs the most money is Growth Allowance. Software suites at Full Commit absorb a 105% initial cap and a 115% ongoing allowance before growth becomes billable, so ordinary refresh churn is free headroom. Hardware services get none of that.
Every switch you add after the baseline is dollar one billable, and from July 26, 2026 it is billed retroactively at the annual milestone rather than prospectively.
Combine that with the delisting rule, where decommissioned assets stay True Up eligible for 90 days after the delisting action, and the asymmetry is stark: growth counts instantly, reductions count on a lag.
The second trap is inheritance. You do not independently choose the commit level of a Services Suite. It follows the Underlying Suite, and if that Underlying Suite moves from Partial to Full Commit, the attached Services Suite moves with it automatically.
A software negotiation you run for unrelated reasons can therefore trigger enterprise-wide hardware coverage you never agreed to price. Model the two together, not in sequence, and read our breakdown of the July 2026 hardware support change before you touch either.
Why software kept Partial Commit and hardware did not
Nothing technical explains the asymmetry. Software support attach is already close to universal because entitlement and support are functionally welded together in subscription and DNA licensing, self-reporting is cheap, and Cisco has minimal renewal leakage there.
Hardware support is the opposite: renewal rates decay steadily as gear ages, buyers drop coverage on depreciated access switches, third parties (Curvature, Park Place, Service Express) take a visible share of the tail.
And every internal cost exercise ends with someone asking why a seven year old 3850 stack carries a support line.
Full Commit converts Cisco's structurally weakest renewal category into a contractual floor.
It is a revenue integrity move.
And Cisco has been open enough about the framing: only Full Commit remains so customers "receive the full benefits of the program, including multi-suite discounts and Value Shift capabilities." Read that as an offer of discount and flexibility currency in exchange for scope you cannot subsequently reduce.
Cisco has also said it has no current plans to apply the True Up model to Software Licenses or Software Support. That confirms the direction of travel.
The two changes, mandatory Full Commit and retroactive True Up billing, land together on hardware and only on hardware, and they compound: mandatory scope sets the base, retroactive billing prices the growth.
And the absence of any Growth Allowance on hardware removes the cushion that would have made either tolerable on its own.
Our comparison of True Up against True Forward economics quantifies the second half of that. The buyer-side reading is that Cisco has priced in a behavioral change it expects you to make anyway.
Do not accept the multi-suite discount narrative as compensation without a modelled comparison against holding hardware support outside the EA entirely.
Cut your Cisco collaboration cost across the Webex stack
How to cut Cisco collaboration cost across Webex Suite, Calling, and Contact Center: the Flex Plan math and the contract levers that hold at renewal.
Get the white paper →The coverage gap most buyers have not priced
The headline number in every renewal conversation from now to July 2026 will be the uplift percentage, and that is exactly the wrong place to spend your analytical hours. Partial Commit on hardware services was never a discount mechanism.
It was a scoping mechanism, and buyers used it to do something specific: exclude the aging tail. In roughly nine out of ten Services EA estates I have reviewed over the past four years, the uncovered portion was not randomly distributed.
It was concentrated in end-of-life access points from the prior wireless generation, branch switches at closing or consolidating sites, warm spares sitting in a depot, and remote-site routers scheduled for SD-WAN replacement in the next eighteen months. Those assets were uncovered on purpose.
The buyer had already decided they were not worth a service contract, and Partial Commit let that decision hold.
Full Commit reverses it by default, and the reversal is priced at list-derived rates against the installed base assessment Cisco performs before your service start date, based on address location and assigned service levels.
The arithmetic that follows is not linear, which is why most models built off the uplift percentage understate the exposure by a wide margin. Take an estate where 35% of eligible hardware is currently uncovered under Partial Commit.
The intuitive read is that hardware support spend rises by something in the neighborhood of 35% to 50%, depending on how the uncovered assets skew toward lower-cost SKUs. The actual exposure is higher because three things compound.
First, the newly attached assets carry a service level assigned by the baseline assessment rather than one you selected, and the assessment defaults toward the levels present elsewhere at that address.
Second, Cisco's own program terms state that no services on hardware are eligible for Growth Allowance, so the 105% initial cap and 115% ongoing allowance that cushion Full Commit software suites do not apply here.
Third, once you are inside the agreement, a customer cannot scale down the quantity of products and services. The exclusion you used to make annually now becomes a one-time decision at signature, and every wrong call inside it is locked for the term.
The delisting rules are where the tail bites hardest. Cisco gives you a 90-day window after a delisting action to review and clean up the delisted hardware install base, and delisted assets remain eligible for True Up billing after those 90 days.
Read that alongside the six-month reconciliation period, after which all assets removed from the final quote but not subsequently decommissioned will be included as increased Use.
What those two clauses mean operationally is that "we plan to retire that closet switch next fiscal year" is no longer a valid position. Either the asset is physically decommissioned and evidenced inside the window, or you are paying for it.
Most enterprise estates I have audited cannot produce decommissioning evidence at that cadence.
Asset records lag physical removal by six to fourteen months in a typical mid-size enterprise, and the burden of proof has now shifted onto the buyer at exactly the moment the vendor has automated visibility into the install base.
Then layer the refresh cycle on top. Hardware refresh runs on a five to seven year clock in most estates, which means at any given point in a three-year Services EA term you are retiring one generation while deploying the next.
Under True Forward, that overlap was tolerable because growth billed prospectively and you had room to absorb the transition period.
Under True Up, growth bills retroactively at the annual milestone date, and the retiring generation is still attached because you missed the decommissioning evidence window.
You pay twice: once for the legacy asset Full Commit re-attached, and again retroactively for the replacement that landed mid-year.
Our analysis of the [True Up versus True Forward financial difference on Cisco Services EA hardware](cisco-services-ea-true-up-vs-true-forward-hardware) walks the year-by-year cash impact of that overlap in more detail.
The strategic reframe is the point. Hardware support under Full Commit is no longer a coverage percentage you negotiate down.
It is a portfolio decision made asset class by asset class: what genuinely belongs inside the EA because it is core, in-lifecycle, and business-critical; what moves to standalone SmartNet where you retain per-asset control.
What goes to third party maintenance because it is stable, out of warranty, and unlikely to need a TAC case; and what gets physically decommissioned before the baseline assessment runs.
That last category is the highest-return work available to you between now and renewal, because every asset removed before the assessment is an asset that never enters the baseline at all. Every asset removed after it becomes a delisting problem with a 90-day clock and a True Up tail.
The buyers who will be hurt worst are not the ones with the largest estates. They are the ones with the cleanest historical Partial Commit discipline.
If you have been diligent about excluding low-value gear year after year, your uncovered percentage is high (typically 35% to 45% in the estates we have modeled), and Full Commit re-attaches all of it at once. The buyer who was sloppy and covered nearly everything anyway sees a modest step-up.
Good governance under the old model is punished under the new one.
The practical implication: run the installed base reconciliation yourself, before Cisco runs the baseline assessment. Not during the six-month window. Before signature.
Every asset you cannot defend as in-lifecycle, in-service, and business-relevant is a candidate for physical removal now rather than a contractual argument later.
Four restructuring paths and what each costs
There are four viable structures, and the right one depends less on estate size than on how much uncovered legacy hardware you carry and whether your renewal date gives you room to move before July 26, 2026.
Path one is the timing play: sign or renew under an existing EA ID before that date and retain True Forward for the duration of the remaining term, including additional service purchases and upgrades. That is the single cleanest lever available, and it is a date, not a negotiation.
Path two accepts Full Commit and fights on the baseline instead, using the six-month reconciliation window to strip assets from the final quote and evidence decommissioning.
Path three shrinks the EA to software support and Professional Services at the $100k TCV platform threshold and moves hardware to standalone SmartNet or third party maintenance, which is the structurally cheapest outcome for tail-heavy estates but runs into the partner constraint: the Services portfolio must be purchased through the same partner as the product portfolio.
So you cannot cleanly split sourcing without renegotiating your product relationship.
Path four uses the cross-architecture unlock, one Full Commit suite in Networking Infrastructure, Applications Infrastructure.
Or Collaboration plus at least $100,000 in fully committed TCV, which opens the Security and Services portfolios without an enterprise-wide commitment to the additional suites.
Our [Services EA True Up hardware support guide](cisco-services-ea-true-up-hardware-support-guide) covers the mechanics of each in sequence.
| Path | Structure | Where the cost lands | Best fit |
|---|---|---|---|
| 1. Renew before 26 Jul 2026 | Existing EA ID, True Forward grandfathered for full term | Locks current Partial Commit scope; no retroactive growth billing; buys 3 years of runway | Any buyer with renewal flexibility inside the window |
| 2. Accept Full Commit, fight the baseline | Full Commit, enterprise-wide attach, $200k ACV floor on HW CX | Full uplift on re-attached tail; recoverable only via the 6-month reconciliation and 90-day delisting windows | Estates with under 15% uncovered hardware |
| 3. Software plus PS only, hardware outside | EA scoped to SW CX and Professional Services at $100k TCV; hardware to SmartNet or TPM | Loses multi-suite discount and Value Shift; constrained by same-partner rule on Services | Tail-heavy estates (30%+ uncovered) with strong asset data |
| 4. Cross-architecture unlock | One Full Commit suite plus $100k committed TCV opens Security and Services | Full Commit applies only to the anchor suite, not enterprise-wide | Buyers wanting Services access without whole-estate exposure |
Two constraints govern all four. Commit level is inherited, not chosen: if an underlying Software suite moves from Partial to Full Commit, the associated Services suite aligns automatically, so a decision made on the software side can silently drag hardware with it.
And service upgrades require a new installed base assessment, which means path two buyers who upgrade mid-term reopen the baseline they spent six months negotiating. Model paths one and four first. They preserve the most optionality for the least structural disruption.
Evidence base: what Cisco documents say and what renewals show
The document trail is short but unambiguous, and it is worth assembling before your partner tells you what the rules are.
The Services EA Customer FAQ on the transition to True Up and the $200k ACV deal threshold carries the operative dates: True Up applies to Hardware Support for all new and renewed Services EA bookings starting July 26, 2026.
The $200k ACV floor applies to HW CX for both new sales and renewals from the same date, and existing customers under an existing EA ID retain True Forward for the remainder of their term including additional service purchases and upgrades.
The separate Services EA FAQ PDF is where the Partial Commit removal for hardware services actually sits, alongside the confirmation that Partial Commit survives for software support and the note that services must be attached to all products in the purchased suite for Full Commit.
The EA 3.0 Buying Program Offer Description dated December 2025 supplies the baseline assessment language (Cisco performs an installed base assessment establishing baseline coverage for hardware based on address location and assigned service levels) and the commitment inheritance rule that flips a Services Suite to Full Commit whenever its underlying suite does. EA 3.0 Program Terms Ver. 1.5.
Last modified January 9, 2026, and the August 2025 Enterprise Agreement Program Guide carry the surrounding mechanics: no downward scaling after entry, no Growth Allowance on services attached to hardware, and the Services portfolio partner tied to the product portfolio partner.
Read those five together and the design intent is plain, as our Services EA True Up hardware support guide sets out in more detail.
Below this threshold, hardware support is not eligible for inclusion at all from July 26, 2026, forcing a standalone contract.
Delisted hardware assets remain eligible for True Up billing after 90 days from the delisting action, so a missed window bills you for gear you no longer own.
The patterns we see across renewal engagements are consistent enough to plan around, and they are drawn from our own negotiation practice rather than any published Cisco figure.
First, baseline assessments over-scope: they count decommissioned chassis still showing a serial in Cisco's install base, and they count assets sitting against stale service addresses from an office closure three years ago.
Both of which land inside a Full Commit denominator that you cannot scale down later.
Second, delisting cleanups are started late and slip past the 90-day window, converting a housekeeping task into billable Use.
Third, the six-month reconciliation window is treated as advisory, and after it closes, every asset removed from the final quote but not formally decommissioned is added back as increased Use.
Fourth, Value Shift is offered as compensation for the over-scoping, which does not work, because the rules do not permit shifting license value into Services. Insist on correcting the baseline itself.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
Your first five moves
- Run an independent installed base reconciliation before you sign anything, matching Cisco's assessment line by line against your CMDB, decommission records, and current service addresses, and treat every unmatched serial as a disputed item to be removed from the Full Commit denominator rather than absorbed.
- Confirm in writing whether your existing EA ID carries True Forward grandfathering, then model a pre-July 26, 2026 renewal against a post-date one, because the retroactive milestone billing difference is usually the single largest number in the negotiation, as the True Up versus True Forward comparison quantifies.
- Decide the retire-versus-cover list for aging hardware now and delist inside the 90-day window, since anything delisted late remains eligible for True Up billing, and anything you intend to run past its useful life is cheaper to sweep out of scope than to carry at a service level you will never call on.
- Price standalone SmartNet renewals and at least two third party maintenance quotes as a walk-away benchmark, particularly if your hardware ACV sits anywhere near $200k, because falling below the floor removes the EA option entirely and you should know the alternative number before Cisco tells you what it is.
- Lock reconciliation, baseline dispute, and milestone notice terms into the contract rather than the partner email thread, including a defined dispute path for assessment errors, written notice ahead of each milestone showing the calculation, and confirmation that decommissioned assets reduce the count.
The sequencing matters more than any single move. Points one and two are gated by the July 26, 2026 date, and a clean reconciliation typically takes six to ten weeks in a mid-sized estate, so a decision made in May 2026 has already lost the pre-date renewal option.
Start the install base work at least four months before your renewal date.
The trap in point five is that partners routinely give verbal assurance on baseline corrections and reconciliation flexibility, but the Offer Description governs.
And it says assets removed from the final quote but not decommissioned come back as increased Use after six months. If the concession is not in the signed document, it does not exist at the milestone date.
Frequently asked questions
When exactly does Partial Commit disappear from Cisco Services EA hardware?
Cisco has tied the removal to the same transition that moves Hardware Support from True Forward to True Up, effective for all new and renewed Services EA bookings starting July 26, 2026. Bookings completed before that date under an existing EA ID keep the prior model for the remainder of the term.
That makes the renewal date, not the calendar date, the operative trigger for your organization.
Does Partial Commit still exist for software support?
Yes. Cisco has explicitly stated that Partial Commit continues to be available for software support, and that it has no current plans to apply the True Up model to software licenses or software support in the EA.
The asymmetry means a single Services EA can now carry Full Commit hardware alongside Partial Commit software, provided the commit level inheritance rule from the Underlying Suite is respected.
What is the $200k ACV threshold and who does it exclude?
Hardware Support (HW CX) inside a Services EA requires a $200k Annual Contract Value threshold for both new sales and renewals from July 26, 2026. Customers below that figure are not eligible to include hardware support in a Services EA at all and must buy standalone.
Software Support and Professional Services sit at a separate $100k TCV platform-level requirement, which is why some mid-market buyers can keep a software-only Services EA.
Can we reduce coverage after signing a Full Commit hardware EA?
No. Cisco's EA 3.0 rules state that a customer cannot scale down the quantity of products and services after entering the agreement.
The only structured opportunity to correct scope is the reconciliation window in the first six months from the Services start date, after which assets removed from the final quote but not actually decommissioned are counted as increased Use.
Treat the baseline assessment as the last real negotiation, not the first.
What happens to hardware we decommission mid-term?
Delisted hardware assets remain eligible for True Up billing for 90 days after the delisting action, and you or your partner get that same 90-day window to review and clean up the delisted install base. Miss the window and you keep paying for gear that is already out of the rack.
Value Shift business rules do continue to apply, and both newly added and decommissioned hardware are considered in the True Up calculation.
Is renewing early actually worth it?
Usually yes, if your term allows it. Existing EA customers under an existing EA ID retain True Forward for the duration of their remaining terms, including additional service purchases and upgrades.
A 36-month renewal signed before July 26, 2026 preserves forward-only billing well into 2029, which for a growing estate is typically worth more than the incremental discount Cisco offers on a post-transition paper.
Can we move hardware support to a different partner or to third party maintenance?
Partner flexibility is limited: Cisco's EA 3.0 rules require that the Services portfolio be purchased through the same partner as the product portfolio, even though other portfolios can be split.
Third party maintenance is viable for aging or non-critical gear outside the EA, but it removes those assets from the committed base, so it must be decided before the baseline assessment rather than after. Price it as a walk-away benchmark whether or not you intend to use it.
