Cisco True Forward Explained in Plain English

Cisco True Forward lets you add licenses at any point in your contract without paying until the next true-forward event. It never removes licenses mid-term—only your renewal date can reduce the count. The real risk is not the mechanism itself; it is arriving at renewal unprepared and locking in a seat count higher than you actually need.

Cisco True Forward, Explained

Cisco True Forward is the billing mechanism built into Enterprise Agreements and Flex subscriptions. If you have seen the term on a quote and gotten a vague answer, here is the plain version: you can add licenses at any point during your contract term, and the cost adjustment waits until your next true-forward event—typically your annual renewal date. You are never billed retroactively for the months you were already over your contracted baseline.

That protection has a tradeoff. The mechanism only moves in one direction mid-term. Understanding which direction, and when the rules change, is what determines whether True Forward works in your favor or quietly inflates your bill year after year.

How a True-Forward Event Works

When you sign a Cisco agreement you commit to a baseline seat count for the term. During the year, you can provision additional users immediately without placing a change order. Cisco's platform records the highest usage level reached during the term.

At your true-forward event, Cisco compares that peak against your contracted baseline. If peak usage exceeded the baseline at any point, your quantity steps up to that peak number, and you pay the higher price going forward into the next term. You are not charged for the prior months when you were already over.

Two rules catch people off guard:

• No mid-term reductions. If employees leave in month six, the contracted seat count does not change. You continue paying for those seats until renewal.
• Renewal is the only window to step down. That is the one moment in the contract cycle when you can reduce your seat count to match your real current headcount.

Most agreements have a true-forward event once per year on the agreement anniversary. Multi-year agreements may have different schedules—your contract language will define the exact timing.

Why Most Businesses Carry Too Many Licenses

Because True Forward never removes seats mid-term, licenses accumulate over the life of a multi-year agreement. Someone leaves the company; no one removes the provisioned seat. A project team disbands; the licenses stay active. A second location closes; the phones go dark but the agreement still bills for the seats.

Most organizations end up carrying somewhere between 10 and 25 percent more licenses than active users. On a deployment of any real size, that gap represents recurring cost that compounds across every renewal. The problem is structural: the mechanism is designed to make adding capacity frictionless, while removing it requires deliberate action at a specific, narrow point in time.

The fix is straightforward but requires doing the work before you sign. Pull your active user data from the Cisco portal—logins, call records, or active device registrations—and compare that number against the quantity in your current agreement. Come to the renewal conversation with documented numbers. Cisco will start from their recorded peak; you need to show your current reality to negotiate the count down.

For a structured process to run this audit before your agreement renews, Perdigon's renewal review service covers active user verification, contract quantity comparison, and SKU checks so you are not signing a new term blind.

True Forward vs. Standard Overage Billing

The practical difference between True Forward and a traditional overage model is clearest when headcount changes mid-year.

True Forward is clearly better during a growth phase—no in-year invoice surprises. It becomes a liability if headcount shrinks and you do not audit, because the stepped-up count rolls into the next term automatically if you do not catch it at renewal.

What to Check Before Your Next Renewal

Renewal is your one opportunity to adjust the count. Before agreeing to the next term, verify these four items:

1. Active users vs. provisioned seats. Provisioned does not mean active. Use login records, call history, or device registration data to find who is genuinely using the service versus simply occupying a seat in the system.
2. Cisco's recorded peak for the term. This is the number Cisco will propose as your new baseline. If your current headcount is materially lower, you need documented evidence to negotiate it down—Cisco will not volunteer the reduction.
3. SKU status. Cisco's Collaboration Flex Plan v2.0—sold as A-FLEX and A-FLEX-CC—reached end of sale on 2026-08-01. The last day to renew or add users on those SKUs is 2027-07-31, and support ends 2028-07-31. The current replacement SKUs are A-FLEX-3 and the E3 family. Renewing without checking your SKU means you could lock in another full term on a product line with a known end date.
4. Your carrier picture. If your SIP trunking or hosted voice runs through Lumen—also invoiced as CenturyLink, Qwest, Level 3, Embarq, or US West—know that Lumen stopped selling and renewing business voice products on 2026-08-01. Existing service continues month-to-month with no announced shutoff date, but you cannot add capacity or commit to a new term. If a move to Cisco Webex Calling is on your roadmap, your upcoming Cisco renewal is the natural consolidation point rather than indefinitely sustaining two separate voice platforms.

The mechanics of True Forward are simple once you have seen them once. The discipline is in the preparation—knowing your numbers before you negotiate, not after the contract is signed.