From a finance seat, a True Forward is a one-way ratchet on the cost base: it can move the committed number up but not back down, so whatever AI usage is on the meter when it triggers becomes a permanent line. With AI now metered in assists, the risk is no longer a few extra named users; it is consumption that scales with every automated action. The cluster context is in our 2026 guide to agentic AI ITSM pricing and negotiation; this article is the audit you run before the meter is read.
Book an AI cost control review →What is a True Forward and why does AI usage matter?
A True Forward trues up usage that has grown above your contracted entitlement, billing the increase forward into the remaining term rather than retroactively. As of 2026 pricing, ServiceNow meters AI in assists, roughly 25 for a small action and about 150 for a large agentic action, with overage top-ups, and from April 2026 bundles AI into its Foundation, Advanced and Prime tiers. An unaudited pilot can push assist consumption far above the baseline, so the True Forward captures that peak and makes it your floor for the rest of the term. The governance surface for this is the AI Control Tower, covered in paying only for what you use.
How do you audit AI agent usage before the True Forward?
Run a structured audit that produces a defensible forward number, not the vendor's measured peak. The steps below are deliberately evidence-first because a board number must be built on data the vendor cannot dispute.
- Pull assist consumption by month, agent and use case. Get at least three to six months of data so trend, not a single peak, drives the number.
- Strip out pilot and test spikes. Proof-of-concept runs, training, and re-tries inflate consumption without representing steady demand. Isolate and remove them.
- Classify each automation by value. Rank use cases by deflection or hours saved against assists consumed. Low-value, high-consumption automations are candidates to switch off before the meter is read.
- Separate durable from discretionary demand. Durable demand is what you commit to; discretionary demand should sit on overage top-ups, not the committed baseline.
- Model the forward number at a defensible run rate. Use the cleaned trend, add modest headroom, and bring that figure to the table instead of accepting the measured spike.
What does the audit output look like?
| Demand type | What it is | Where it belongs |
|---|---|---|
| Durable, high-value | Automations with steady use and clear payback | Committed baseline |
| Durable, low-value | Steady use, weak payback per assist | Review or switch off before True Forward |
| Pilot / test spikes | One-off proof-of-concept consumption | Exclude from the baseline |
| Discretionary | Occasional or seasonal automation | Overage top-ups, not committed |
Our gated ServiceNow Now Assist Cost Control Guide includes the assist-audit worksheet and the consumption-classification template behind this method.
How do you turn the audit into a lower committed number?
The audit is the evidence; the negotiation is what converts it to budget. Bring the cleaned forward number and ask that the committed baseline reflect steady-state durable demand only, with discretionary and seasonal usage carried on top-ups. Pair this with a consumption cap so a future spike cannot trigger another uncapped True Forward, the mechanics of which are in how to cap agentic AI consumption in ITSM contracts. The earlier mechanics of modelling assists before you commit are in how to cap ServiceNow assist consumption before you sign.
What to do next
Start the audit three to six months before the True Forward date, switch off low-value high-consumption automations before the meter is read, and bring a defensible forward number to the table backed by cleaned data. When you want it run end to end, including the consumption cap that protects the next cycle, the engagement goes through our AI cost control service on fixed fee or gainshare.
Book an AI cost control review.
We audit assist consumption, strip out the spikes, and bring a defensible forward number to the table before the True Forward locks the wrong one in. Fixed fee or gainshare.
Book an AI cost control review →Frequently asked questions
- What is a True Forward and why does AI usage matter to it?
- It trues up usage above entitlement and bills the increase forward for the rest of the term. An unaudited AI pilot can push assist consumption above the baseline, so the True Forward locks the spike into your run rate.
- How is ServiceNow AI usage measured?
- In assists, roughly 25 for a small action and about 150 for a large agentic action, with overage top-ups. AI is bundled into the Foundation, Advanced and Prime tiers from April 2026. Confirm rates against your order form.
- How far ahead should you audit?
- At least three to six months before the True Forward, so you have enough consumption data to strip out spikes and model a defensible forward number rather than accept the measured peak.