Procurement teams that have run blanket POs for several years almost always have a stale blanket problem. Blankets that should have been closed years ago remain open in the system. Some have small residual limits that no one uses. Some are technically expired but never formally closed out. Some were superseded by newer blankets but never deactivated.
The accumulation is invisible until something forces a review: an audit finding, a system migration, a procurement leadership change. At that point the size of the cleanup project is often surprising.
Stale blankets are a low urgency, high accumulation problem. They do not cause acute operational issues, which is why they get deprioritized. But they create real costs: spend reporting accuracy, audit risk, and the cumulative administrative load of maintaining records that should not exist.
Why Blankets Do Not Get Closed
Four structural reasons explain why blankets accumulate without being formally closed.
No defined closure process
Most procurement systems have well defined processes for creating, amending, and renewing blankets. The closure step is often less explicit. When a blanket reaches its expiration date with residual headroom, the natural action is unclear: leave it dormant, formally close it, or extend it to use up the headroom.
Without a defined process, the default action is no action. The blanket sits in the system in an ambiguous state.
No clear ownership of closure
The blanket owner who set up the blanket may have left the role. The renewal got assigned to a new blanket with a new owner. The old blanket's closure was no one's specific responsibility. It stays open by inertia.
Residual limit feels useful
A blanket with $30K of remaining limit and a few months until expiration feels like a useful asset. The instinct is to leave it open in case it gets used. The instinct is rarely correct: the blanket usually does not get used, and at expiration the closure step still gets skipped.
Closure has no visible benefit
Closing a blanket does not produce a visible outcome. The procurement system has one fewer record. Nobody celebrates. The accumulated effect of disciplined closure is meaningful but not immediately apparent, which is why it gets deprioritized.
What Stale Blankets Actually Cost
The costs are real but indirect, which is why they accumulate without triggering action.
Inflated commitment reporting
Each open blanket appears in commitment reports as authorized spend potential. Stale blankets that no one intends to use still show up in the totals, inflating the commitment view. CFOs and finance leaders see overstated committed spend, which distorts capital planning and budget allocation decisions.
Audit findings and remediation work
External and internal auditors regularly flag stale blankets as a procurement control weakness. The blanket exists in the system, but the supplier relationship may be dormant, the original owner may have left, or the underlying contract may have expired. Each finding requires remediation work that could have been prevented by routine closure discipline.
Risk of unauthorized use
An open blanket is technically a usable authorization. If anyone with release authority spots the headroom and uses it for unintended purposes, the unauthorized release may go through without flagging because the blanket appears active. This risk is small but real.
Cumulative administrative load
Every open blanket consumes some administrative attention: system records, reporting cycles, periodic review. Across a portfolio of dozens or hundreds of stale blankets, the load adds up.
The Cleanup Project Methodology
A one time cleanup of stale blankets is straightforward but requires discipline. The approach has four steps.
Step 1: Inventory all open blankets
Pull every open blanket in the system, regardless of expiration date. The list should include the blanket reference, supplier, original limit, current consumption, validity period, original owner, and last activity date.
Step 2: Categorize by status
- Active and on track: current blanket, consumption tracking normally, no closure action needed
- Active but inactive: current blanket but no recent releases, possible candidate for early closure
- Expired but open: validity period has passed, blanket should have been closed
- Superseded: replaced by a newer blanket with the same supplier, old blanket should be closed
- Unknown status: insufficient information to categorize, requires investigation
Step 3: Resolve each non active blanket
For expired and superseded blankets, close formally with documentation of the closure date and the reason. For inactive blankets, contact the original owner or successor and either confirm continued need or close. For unknown status blankets, investigate enough to categorize, then resolve accordingly.
Step 4: Document the closures
Each closure should generate a record showing the reason for closure, the residual limit at closure (if any), and the responsible approver. This documentation supports the audit trail and prevents questions later about why blankets were closed without further activity.
Forced Expiration as Ongoing Discipline
After the cleanup, the ongoing discipline is preventing future accumulation. The most effective approach is forced expiration.
Time based forced closure
Every blanket has a defined validity period. At the end of the validity period, the blanket is closed automatically unless an explicit renewal decision has been made and a successor blanket created. The default action is closure, not extension.
Inactivity based closure
A blanket that has gone six months without any release activity gets flagged for review. If the inactivity is intentional (the spend pattern shifted), the blanket should be closed regardless of remaining validity. If unintentional, the situation gets investigated.
Annual portfolio review
At least annually, procurement leadership reviews the full blanket portfolio. The review covers supplier counts, blanket counts per supplier, total committed amounts, and stale candidates. The output is a closure list and any consolidation actions.
Quarterly Blanket Reviews
More frequent than annual, less frequent than monthly, quarterly reviews are the practical rhythm for ongoing portfolio management.
Each quarterly review covers:
- New blankets created in the quarter, with verification that each has proper governance setup
- Blankets approaching expiration in the next quarter, with renewal status confirmed
- Consumption patterns: blankets running ahead or behind expected pace, with explanations
- Stale candidates: blankets without recent activity, flagged for closure decision
- Exception reports: blankets with control issues (overruns, scope deviations, governance gaps) needing attention
The quarterly review takes 30 to 60 minutes for a small portfolio and a few hours for a large one. It is the single highest leverage governance practice for keeping the blanket portfolio healthy over time.
Closure Discipline as a Cultural Choice
Closing things deliberately is a discipline that does not come naturally to most teams. Opening new instruments is exciting; closing old ones is administrative. Companies that maintain healthy blanket portfolios treat closure with the same intentionality they treat creation.
This shows up in small ways. Closure decisions are documented in the same template as creation decisions. Closure events are reviewed at the same procurement leadership cadence as new blanket approvals. The blanket portfolio size is itself a metric, reviewed quarterly, with growth expected to be net positive only when the underlying business genuinely warrants additional instruments.
Start Here
Pull the inventory of all open blankets in your environment. If you do not currently have a single report that produces this list, that is itself the first finding: blanket portfolio visibility is not where it needs to be.
Once the list exists, run the four step cleanup methodology. Expect the first cleanup to take longer than future ones because the accumulated backlog is the largest you will face. Subsequent quarterly reviews are much lighter.
