Setting Blanket PO Limits and Tracking Consumption Against Them

AP Automation
A blanket PO is only as useful as its limit is accurate. Most limits get set by guess and never reviewed. Here is the analytical approach that works.

A blanket PO with a poorly set limit fails in one of two ways. Set too low, it runs out before the validity period ends, leaving the requesting team scrambling to source through alternate channels. Set too high, it shows committed spend on the books that the company has no intention of fully using, distorting commitment reporting and tying up budget capacity unnecessarily.

Setting the right limit is not difficult, but it does require an analytical approach. So does tracking consumption against the limit in a way that surfaces issues early rather than at the last minute.

This article covers both: how to set the limit based on historical and forward looking data, and how to structure consumption tracking so that limit issues become visible before they become operational problems.

How to Set the Initial Limit

The right limit balances three considerations: historical actual spend, expected forward change, and an appropriate buffer for variability.

Start with twelve months of historical spend

Pull the trailing twelve months of actual spend with the supplier, in the categories the blanket will cover. This gives the baseline. If the blanket scope is narrower than the supplier's total spend, isolate the relevant categories.

If historical data is not available (new supplier, new category), use forecasted volume from the requesting department, validated against industry or peer benchmarks.

Adjust for expected forward change

Apply known changes for the upcoming period. Growth in operations that will increase demand. Strategic decisions to expand or reduce the category. Price changes negotiated in the underlying contract. Seasonal variation that the trailing twelve month average might smooth over.

The adjusted baseline becomes the expected spend during the blanket validity period.

Add an appropriate buffer

Add a buffer of 10% to 20% above the expected spend. The buffer absorbs normal variability and unanticipated needs without requiring blanket revisions. Larger buffers (above 20%) start to look like overcommitment and should be justified by a clear reason.

Why Limits Get Set Wrong

Three common patterns produce limits that are not analytically grounded.

Limit equals supplier's request

The supplier suggests a limit based on what they would like to bill, and procurement adopts that figure without independent validation. The supplier has every incentive to set a high limit; this is not the right input for sizing.

Limit copied from the prior period

The previous blanket had a $500K limit, so the new one gets $500K too. The underlying spend may have shifted significantly, but the limit gets carried forward without review.

Limit set to match the budget

The blanket limit gets set to the total budgeted spend for the category, with no buffer. This works only if the budget is itself analytically rigorous and includes its own buffer, which it often is not.

Tracking Consumption Through the Period

Once the blanket is active, consumption tracking has two purposes: surfacing limit risk early enough to take action, and producing the data that informs the next period's limit setting.

The minimum tracking includes:

  • Cumulative committed value (sum of releases) against the limit
  • Cumulative invoiced value against the limit
  • Percentage consumed as of the current date
  • Pace analysis: at the current consumption rate, when will the limit be reached?
  • Comparison against expected pace (linear over the period, or seasonal if the spend has known seasonality)

The pace analysis is the most useful piece. If consumption is tracking 20% ahead of where it should be at this point in the period, the limit is on pace to be exhausted before the validity end. That is a signal to investigate the cause and decide on action, not a reason to immediately raise the limit.

Threshold Triggers

Active tracking means triggering reviews at defined consumption thresholds, not at arbitrary calendar intervals.

50% consumed

Initial check in. Is consumption tracking close to the expected pace? Any patterns in releases that warrant attention? No action typically needed unless consumption is materially ahead of pace.

75% consumed

Substantive review. Project the remaining consumption to the validity period end. If the projection exceeds the limit, identify the cause: under sizing, demand increase, scope expansion, off pattern releases. Decide whether to manage usage down, increase the limit through formal amendment, or plan for a successor blanket.

90% consumed

Escalation. With 10% of the limit remaining, the operational window is short. Either an amendment is processed quickly or the requesting team needs to prepare alternative sourcing. The 90% threshold should not be hit by surprise; the 75% review should have set the direction.

100% consumed before validity end

Failure mode. The blanket is exhausted and the period is not over. The requesting team has no authorization to continue purchasing. Standard POs become the bridge, with all the administrative overhead the blanket was meant to avoid.

What the Consumption Data Tells You for Next Period

When the blanket expires or completes, the consumption data should drive the next period's limit setting. Three patterns are typical and each has a different implication.

Consumed at or near 100%

The limit was reasonably calibrated. The next period limit can be set similarly, with adjustments only for known forward changes. The buffer was appropriate.

Consumed at 70% to 90%

Mild overestimate. The next period limit can be set lower, closer to the actual consumption plus a smaller buffer. The savings show up as reduced committed spend on the books.

Consumed below 50%

Significant overestimate. Either the original limit was set far too high, or the spend pattern shifted during the period. Investigate the cause before sizing the next blanket. The next limit should be sized to the actual consumption pattern, not to the prior limit.

The discipline of reviewing actual versus limit at expiration is what prevents the long term drift where blanket limits grow without analytical basis.

Start Here

Pull the consumption data on your three largest active blankets. Calculate the actual pace against the original limit. Whatever the pattern shows is the diagnostic for whether your limit setting discipline is working.

If pace is consistently ahead or behind expectations, the limit setting methodology needs adjustment. Fix the methodology before the next round of renewals, not after another period of drift.

Krishna Srikanthan
Head of Growth

Table of contents

How efficient is your finance team?

Thank you! Please check your inbox.
Something went wrong while submitting the form. Please retry

See Finofo in Action

Please wait. Redirecting...
Oops! Something went wrong while submitting the form.
Watch a demo