True Forward vs Traditional True-Up: The Critical Distinction
Most enterprise software agreements use some form of annual licence reconciliation. The conventional model — a true-up — measures the gap between committed entitlements and actual consumption at the end of each measurement period, then invoices the buyer for the overage covering that past period only. If an organisation used 1,200 licences but committed to 1,000, a traditional true-up invoices for 200 licences for the 12 months of the measurement period. The charge is historical, limited to the consumption that occurred, and does not extend the billing obligation forward.
Cisco's True Forward works fundamentally differently. When an overage is detected at the annual True Forward milestone, Cisco does not invoice for the historical period of excess consumption. Instead, Cisco invoices for the additional licences at the new consumption level prospectively — for the entire remaining term of the EA. The formula is: (price per unit) × (units consumed beyond current entitlement) × (remaining months in the contract term).
The financial consequences of this difference are enormous. Consider an organisation that signed a three-year EA and in the first year exceeded its Collaboration entitlement by 300 seats, triggering a True Forward event at the year-one milestone. Under a traditional true-up, the invoice covers 300 seats for 12 months. Under Cisco True Forward, the invoice covers 300 seats for the remaining 24 months of the contract term — double the charge, invoiced immediately. In a five-year EA with an overage detected in year one, the prospective billing could cover four years of additional licence cost in a single invoice.
This prospective billing structure is not hidden in the fine print — it is a documented feature of the Cisco EA programme. But it is consistently underestimated by buyers who experience it for the first time, and it consistently produces budget surprises that would not occur under traditional true-up billing.
When True Forward Events Are Triggered
True Forward events can be triggered in two ways within the Cisco EA framework: through the standard annual milestone review, and through the exceptional growth mechanism that activates outside the normal annual cadence.
Annual True Forward Milestone
The standard True Forward review occurs annually at the anniversary of the EA start date. At this milestone, Cisco measures consumption across each suite in each portfolio and compares the recorded consumption against the current entitlement — which includes the original committed quantity plus any growth allowance applicable to that suite.
For the Collaboration and Security portfolios, the growth allowance is 15 percent of the committed suite quantity, applied once at inception. Consumption within this 15 percent buffer does not trigger a True Forward event. Consumption above the committed quantity plus the 15 percent buffer — even by a single user — triggers a True Forward invoice for the prospective remaining term at the new consumption level.
For the Networking Infrastructure portfolio, where licences are device-based rather than user-based, the review compares the committed device count against the deployed device count managed through Catalyst Centre or the Meraki dashboard. There is no equivalent percentage growth allowance for the networking portfolio in the standard EA structure, making accurate device count scoping at EA inception particularly important.
Exceptional Growth — The Semi-Annual Trigger
A less widely understood feature of the True Forward mechanism is the exceptional growth trigger. If consumption in any suite reaches or exceeds 115 percent of the total committed entitlement (including growth allowance) during the contract term — not just at the annual milestone — a semi-annual True Forward review can be triggered. This means that exceptionally rapid growth can result in two True Forward events in a single year rather than one.
The exceptional growth trigger is most relevant for organisations undergoing rapid headcount expansion, post-merger integration, or large-scale technology deployment programmes. An organisation that commits to 5,000 Webex seats with a 15 percent growth allowance (total buffer: 5,750 seats) and deploys 6,000 seats in the first six months exceeds the 115 percent exceptional growth threshold and will face a semi-annual True Forward event as well as the standard annual review.
Monitoring consumption against both the annual milestone and the exceptional growth threshold should be a continuous operational activity for any organisation running a Cisco EA — not a task completed only in the weeks before the annual measurement date.
Received a Cisco True Forward invoice or concerned about upcoming exposure?
We help enterprise buyers respond to, dispute, and prevent True Forward billing events.Calculating Your True Forward Exposure
Understanding your potential True Forward exposure requires four inputs: current consumption at the suite and product level, current entitlement (committed quantity plus growth allowance), remaining contract term in months, and the per-unit price for each suite in the EA.
Step 1 — Establish Current Consumption
For the Collaboration portfolio managed through Webex Control Hub, current consumption data is available via the Control Hub admin interface under Licences and Usage reporting. The report shows assigned licences by suite and product type. For the Security portfolio, consumption data is available through Cisco Secure Access and the relevant product admin consoles. For the Networking portfolio, device counts are available through Catalyst Centre or the Meraki dashboard depending on the management platform in use.
The key discipline is ensuring the consumption data reflects accurately provisioned and actively maintained licences rather than all historically provisioned licences. Licences assigned to users who have left the organisation, duplicate assignments resulting from provisioning errors, and licences assigned to inactive accounts all count against consumption at the True Forward measurement date. Cleaning up the licence estate before the measurement date is one of the most reliable ways to prevent an unnecessary True Forward event.
Step 2 — Compare to Entitlement
The current entitlement for each suite is the original committed quantity plus the applicable growth allowance. For Collaboration and Security portfolios with a 15 percent growth allowance, a 10,000-seat commitment has a total entitlement of 11,500 seats before any True Forward is triggered. If current consumption is 11,200 seats, the gap between consumption and the True Forward trigger point is 300 seats — a buffer that should be actively monitored as headcount continues to grow.
If the entitlement has already been adjusted upward by a prior True Forward event, the current entitlement reflects that higher level. The ratchet effect means that entitlements only move upward within an EA term — Cisco will not reduce the entitlement baseline during the contract period even if consumption subsequently falls below the adjusted level. This ratchet also becomes the renewal baseline, which is a separate but directly related cost concern addressed in the ELA Guide 2026.
Step 3 — Calculate the Invoice Amount
The True Forward invoice amount for a prospective event is calculated as follows: (units consumed above entitlement) × (per-unit price for that suite) × (remaining months in the EA term). Note that Cisco's invoice is for the full remaining term, not annualised. An overage of 200 seats at $25 per seat per month (annual rate $300 per seat) with 30 months remaining generates a True Forward invoice of $150,000, invoiced immediately as a single charge.
Most enterprise buyers find the prospective scale of this calculation surprising when they run it for the first time. The exercise of calculating potential True Forward exposure before the measurement date — rather than after receiving the invoice — is one of the highest-value activities a Cisco EA manager can perform in the months preceding the annual review.
The Value Shift Mitigation Mechanism
Cisco's EA terms include Value Shift provisions that can partially offset True Forward charges in certain circumstances. Understanding what Value Shift can and cannot achieve is important for buyers attempting to manage overage exposure.
Intra-Suite Value Shift
Intra-suite Value Shift allows unused residual value within a suite to be applied against True Forward charges for a different product within the same suite. In a Collaboration EA, unused Webex Meetings licence value can be applied against Webex Calling overages if the buyer has over-committed on Meetings and under-committed on Calling.
The practical applicability of intra-suite Value Shift depends on the coincidence of under-utilisation and over-utilisation within the same suite. Organisations that sized all products within a suite accurately at commitment have no surplus value to apply. Value Shift is most useful for buyers who over-committed on one product in anticipation of a deployment that did not fully materialise while simultaneously underestimating usage of another product in the same suite.
Cross-Suite Value Shift
In some EA configurations, cross-suite Value Shift is available, permitting unused value in one portfolio to offset True Forward charges in a different portfolio. Cross-suite Value Shift is not universally available and depends on the specific portfolio combination and EA contract version. Buyers who believe cross-suite Value Shift may be applicable should review their specific EA contract terms rather than assuming the provision applies.
Both forms of Value Shift require formal invocation through Cisco's EA management process. They do not apply automatically — the buyer must identify the surplus value, calculate the applicable offset, and formally request the adjustment before the True Forward invoice is finalised. Organisations that discover Value Shift eligibility after receiving the invoice are at a negotiating disadvantage compared to those who identify and invoke the provision before the measurement date.
Preventing True Forward Events — A Practical Checklist
True Forward prevention is primarily an operational discipline applied consistently across the EA lifecycle. The following controls, applied routinely, prevent the majority of avoidable True Forward events.
Monthly Licence Consumption Monitoring
Establish a monthly report that tracks current consumption against the True Forward trigger point (committed quantity plus growth allowance) for each suite in the EA. The report should show the current gap between consumption and the trigger, the trend rate of consumption growth over the prior three months, and the projected date at which consumption will reach the trigger based on current growth rates. This forward-looking view provides the lead time needed to act before a True Forward event occurs.
Timely De-Provisioning Controls
The single most common cause of preventable True Forward events is failure to de-provision licences from user accounts when employment ends or changes. Licences assigned to terminated employees, users on extended leave, and accounts that were created in error all count against consumption at the True Forward measurement date. Integrating licence de-provisioning with HR offboarding processes is a basic operational control that prevents licence count inflation over time.
In large organisations with multiple IT teams provisioning Cisco licences independently, establishing a centralised governance function that owns the licence estate and runs regular clean-up exercises is more effective than relying on distributed teams to self-manage de-provisioning. A quarterly licence audit — comparing current assignments against active HR records — typically recovers 5 to 15 percent of assigned licences in organisations that have not previously managed this process systematically.
Pre-Milestone Clean-Up
In the 60 to 90 days before the annual True Forward milestone, run a focused licence audit to identify and remove any assignments that are clearly inappropriate. This exercise should check for: users who departed since the last audit, duplicate assignments resulting from rebranding or provisioning errors, licences assigned to generic or shared accounts that do not require individual entitlement, and any provisional assignments made for temporary projects that have concluded.
The clean-up must complete before the True Forward measurement date, not after. Cisco measures consumption as of the milestone date. Licences removed the day after the measurement date have no effect on the current True Forward invoice but will reduce the consumption baseline for the next measurement period.
Buffer Management for Anticipated Growth
If headcount growth, a merger integration, or a technology deployment programme is expected to push consumption above the True Forward trigger point before the next annual measurement, proactive entitlement expansion is less costly than waiting for a True Forward event to generate the invoice. Cisco will amend an EA to increase committed entitlements at any point during the term, at the then-current rate per unit for the remaining term. While this increases the EA cost, it does so predictably and without the surprise of an unexpected True Forward invoice.
Want to establish robust True Forward monitoring for your Cisco EA?
We design licence governance frameworks that prevent overage events before they occur.Responding to a True Forward Invoice
When a True Forward invoice arrives — typically 60 days after the annual measurement milestone — the organisation has limited commercial options. The prospective billing obligation is contractual and Cisco will not waive a True Forward charge without a corresponding adjustment to the EA terms. However, how the organisation responds in the 60 to 90-day window between measurement and invoice receipt can materially affect the total cost of the True Forward event.
Verify the Consumption Measurement
Before accepting a True Forward invoice, verify that the consumption figures Cisco used in the calculation are accurate. Cisco measures consumption from the portal data as of the measurement date — if licence assignments were not cleaned up before the measurement date, the consumption figure may reflect inflated assignments rather than genuine user entitlement. If the licence audit reveals that a significant proportion of the measured consumption relates to accounts that should have been de-provisioned, this is a legitimate basis to dispute the invoice calculation.
Cisco's EA programme terms specify the measurement methodology. Where the buyer can demonstrate that assignments include clearly invalid accounts (terminated users, test accounts, duplicates), Cisco's account team can sometimes be engaged to agree an adjusted consumption figure that excludes demonstrably invalid assignments. This negotiation is most effective when supported by documentation from the HR system showing termination dates versus the True Forward measurement date.
Apply Value Shift Before Invoice Finalisation
If Value Shift eligibility exists — either intra-suite or cross-suite — the request must be submitted before the invoice is finalised. Once the True Forward invoice is formally issued, the ability to apply Value Shift against it is significantly diminished. Contact Cisco's account team or partner immediately upon learning that a True Forward event has been triggered and before the 60-day invoice delivery window closes.
Negotiate Instalment Payment Terms
Cisco's standard True Forward invoicing terms require payment within the normal accounts payable cycle (typically 30 days). For large True Forward invoices that represent a significant unplanned budget impact, Cisco will often negotiate instalment payment terms spread over two or three annual periods rather than a single upfront payment. This does not reduce the total obligation but it manages the cash flow impact and buys time to adjust the budget planning cycle. Instalment arrangements require formal agreement with Cisco or the partner and should be negotiated before the invoice due date.
Use the True Forward as a Renewal Negotiation Trigger
A True Forward event, particularly one that significantly increases the effective cost of the EA, often provides the most credible commercial signal an enterprise buyer can give Cisco that the agreement needs to be restructured. Organisations experiencing their first True Forward event have an opening to renegotiate the EA terms — not necessarily to reduce the current invoice, but to secure better terms for the renewal. This includes negotiating the renewal baseline methodology (average consumption versus peak consumption), securing a longer term at a lower rate that amortises the True Forward impact, and adding portfolio scope in exchange for pricing concessions on the inflated commitment.
True Forward and the Renewal Baseline Problem
The most significant long-term consequence of a True Forward event is not the invoice — it is the renewal baseline. As discussed in the Cisco ELA Guide 2026, True Forward adjustments become the new entitlement level for the remainder of the EA term, and that adjusted entitlement level then becomes the starting point for the renewal negotiation.
An organisation that started a three-year EA with a 10,000-seat Collaboration commitment, experienced a True Forward event at year one that adjusted the entitlement to 11,500 seats, and then stabilised consumption at 10,800 seats will face a renewal conversation that begins at 11,500 seats — the peak adjusted entitlement — not at 10,800 seats of actual ongoing consumption. The renewal proposal will be sized at 11,500 seats, and Cisco's account team will need a commercial reason to reduce the renewal commitment below that level.
Buyers in this position should document their actual consumption trend over the final 12 months of the contract as evidence for a reduced renewal commitment. The case for a renewal below the True Forward-adjusted baseline is strengthened by consumption stabilisation data, de-provisioning evidence, and a credible competitive alternative that demonstrates the buyer is not captive to the renewal at the inflated level.
Governance Framework for Ongoing True Forward Prevention
Enterprise organisations with large Cisco EAs should establish a formal governance framework for True Forward prevention that persists throughout the EA lifecycle. At minimum, this framework should include monthly consumption versus entitlement reporting for all portfolio suites, a quarterly licence audit integrated with HR termination processes, a pre-milestone audit completed 90 days before each annual True Forward review, a designated EA owner with authority to escalate consumption concerns to the account team and to initiate proactive entitlement adjustments, and an annual True Forward risk review that projects consumption growth against trigger thresholds for the coming 12-month period.
Organisations that invest in this governance framework typically avoid the pattern of reactive True Forward events that compound over the EA term and produce inflated renewal baselines. The administrative overhead of the framework is modest relative to the cost savings generated by preventing even a single mid-term True Forward event on a large EA.