Menu
|
Menu
The True Forward is one of the most misunderstood events in a Cisco Enterprise Agreement lifecycle. It’s not a renewal. It’s not a negotiation. It’s a reconciliation. And if you’re not prepared for it, the number that shows up on the reconciliation report can be genuinely surprising.
Here’s what actually happens during a True Forward, what drives the math, and how to avoid walking into your anniversary date blind.
A Cisco Enterprise Agreement bundles licensing across an entire product family, typically Meraki, Webex, or security products, into a single contract with a fixed annual payment. The EA covers all devices and users in scope at the time of signing, plus a growth buffer.
The True Forward is the annual reconciliation event, usually at your EA anniversary date, where Cisco compares what you’re actually consuming against what you contracted for.
The key rule: True Forwards only go up. If your consumption exceeds your contracted quantities, your annual payment increases to cover the delta. If your consumption is below your contracted quantities, your payment stays the same. You don’t get a credit for using less than you bought.
This is by design. EAs are structured as commit-based agreements. The discount you received at signing was based on a consumption commitment. The True Forward enforces that commitment.
The calculation is straightforward in theory:
Current consumption – Contracted quantity = Delta
If the delta is positive, you pay for the overage at your contracted rate. If the delta is zero or negative, nothing changes.
In practice, the math gets complicated for three reasons.
A Meraki EA might include switches, access points, security appliances, cameras, and sensors. Each product category has its own contracted quantity. You might be under on switches but over on access points. Each category is reconciled independently.
This means you can’t offset overages in one category with underages in another. Being 50 switches under and 30 APs over doesn’t net to 20 under. You pay for the 30 APs.
Enterprise customers rarely run a single Meraki org. We see environments with 3, 5, sometimes 15+ orgs. During True Forward, Cisco needs to count devices across all orgs covered by the EA.
The question that trips people up: which orgs are in scope? If you created a new org after the EA was signed, it may or may not be covered. If you merged orgs, device counts may have shifted. If you have lab or test orgs, are those devices counted?
Getting the org-to-EA mapping wrong means either overpaying (counting test devices as production) or undercounting (and facing a correction later).
True Forward consumption is typically measured at a point in time near your anniversary date. If you just deployed 200 devices for a new site rollout two weeks before your anniversary, those devices count in your True Forward even though they’ve only been active for 14 days.
Conversely, if you decommissioned 100 devices a month before your anniversary, they shouldn’t count, but only if the unclaim/reclaim process was completed and reflected in the licensing portal.
Timing your deployments and decommissions relative to your True Forward date is one of the simplest ways to manage EA costs. This isn’t gaming the system. It’s operational planning.
Based on managing EA environments across dozens of enterprise customers, here are the patterns that cause True Forward surprises.
The most common scenario. The EA gets signed, the annual payment is known, and nobody looks at consumption numbers until 30 days before the anniversary. By then, the overages are already baked in and there’s no time to optimize.
Fix: Track consumption monthly. You don’t need a complex system. A monthly count of licensed devices per category, compared against contracted quantities, takes 30 minutes and gives you 11 months of lead time to adjust.
New projects spin up new orgs. Acquisitions bring in inherited orgs. POCs create test orgs that never get cleaned up. Each org potentially adds devices to your True Forward count.
Fix: Maintain an org registry that maps every Meraki org to its EA coverage status. Review quarterly. Flag any org that isn’t clearly in or out of scope.
Even when the total EA cost is known, nobody can answer “what does Site X cost us?” or “how much is the Chicago office’s Meraki spend?” Without per-site or per-business-unit allocation, the EA becomes a lump-sum budget line that nobody can optimize because nobody can decompose it.
Fix: Implement cost allocation by location, business unit, or cost center. This requires mapping device counts per org/network to organizational structures. It’s tedious to do manually but essential for budget owners who need to justify their share of the EA spend.
Your channel partner (CDW, Insight, WWT, etc.) processes the EA transaction, but their level of proactive True Forward management varies significantly. Some partners send 90-day pre-anniversary reports. Some don’t engage until Cisco sends the reconciliation notice.
Fix: Don’t rely on your partner to flag overages. Own the data yourself. Share your consumption tracking with your partner 90 days before your anniversary so they can validate against Cisco’s numbers and negotiate if needed.
90 days before anniversary:
60 days before:
30 days before:
At anniversary:
True Forwards only go up, which means EAs are optimized for growth. If your environment is shrinking, consolidating, or staying flat, the EA model may no longer be the best licensing structure.
Signals that it’s time to evaluate alternatives:
In these cases, a conversation with your Cisco account team about EA restructuring, term adjustment, or a shift to per-device licensing may save more than staying in the current EA structure.
The checklist above works. It’s also manual, which means it depends on someone remembering to do it.
For organizations managing large EAs across multiple orgs and business units, automating consumption tracking and cost allocation eliminates the quarterly scramble. Smart Track was built for exactly this use case: continuous consumption monitoring, automated cost allocation by business unit or location, and True Forward-ready reporting without the spreadsheet.
It’s available through the Cisco Networking App Marketplace and on Cisco GPL. But even without tooling, the discipline of monthly consumption tracking and a 90-day prep cycle will prevent most True Forward surprises.
Noel-Edouard Chenu is the CEO of Boundless, a Cisco ecosystem software company. Boundless Smart Track provides automated EA consumption tracking and cost allocation for enterprise Meraki environments.
1207 Delaware Ave #552, Wilmington, Delaware 19806
Americas: +1 (347) 464 6510 - EMEA: +33 (0) 181 22 12 80
