The biggest single difference between blanket POs that function as healthy procurement instruments and blankets that drift into control problems is governance. Specifically: who owns the blanket, who can release against it, who approves each release, and who is accountable when something goes wrong.
Most companies have these roles in theory. The roles exist in policy documents, ERP configurations, and procurement procedure guides. In practice, the roles are often ambiguous, with multiple people sharing responsibilities or with no one clearly owning the outcome.
Clarifying the governance roles is mostly a definition exercise. Three roles, each with clear scope, cover almost every situation.
The Three Core Roles
Every active blanket should have three identifiable roles, named individuals, with clear accountability.
Blanket owner
The named individual accountable for the blanket as a whole. Typically a procurement category manager, a department head, or a designated business unit lead.
The blanket owner is responsible for the supplier relationship, the limit sizing, the consumption monitoring, the renewal decision, and the resolution of any issues that arise during the validity period. If the blanket becomes a problem, the blanket owner is the accountable party.
Release requestors
The named individuals authorized to initiate releases against the blanket. Typically a small group within the requesting business unit who have day to day knowledge of demand and are positioned to make timely release decisions.
Release requestors are not the same as release approvers. They initiate the call off, but the approval step is separate.
Release approvers
The individuals authorized to approve releases initiated by requestors. The approval tier depends on the release value, with larger releases requiring higher approval authority.
For routine, low value releases, the approver may be the requestor's direct manager or a procurement coordinator. For larger releases, the approver may be a department head, a procurement category manager, or finance, depending on size.
Why Role Clarity Matters
When the roles are clear, governance operates smoothly. When they are ambiguous, three patterns of failure show up.
No one feels accountable
The blanket has issues (overrun, scope creep, supplier performance problems) and no one feels personally accountable for resolving them. Procurement says it was a business unit blanket; the business unit says procurement should have caught the issue. The blanket continues with the issues unresolved.
Anyone can release
Without explicit release requestors, anyone in the business unit who knows the blanket exists can attempt to call off against it. The lack of constraint means small releases proliferate without anyone tracking the cumulative impact.
Approvals become routine
Without tiered approval responsibility, every release gets the same treatment, which usually means a routine sign off by whoever is in the approval path. Substantive review of larger releases gets lost in the volume.
Release Authority by Value
Tiered approval limits should be defined at the blanket setup and documented as part of the blanket record. The specific thresholds depend on company size and risk tolerance, but the structure is consistent.
Automated approval tier
Below a low threshold (often $1K to $5K for indirect blankets, lower for high control categories), releases auto approve provided they pass basic checks. No manual approval action required.
This tier handles the high volume of small transactions that would otherwise consume manager time disproportionate to the value.
Manager approval tier
Mid range releases route to the requestor's manager. Quick review focused on whether this specific call off is intended and consistent with department plans.
This tier captures most of the routine release flow with appropriate visibility but minimal friction.
Department head or procurement approval tier
Larger releases route to department head or procurement category manager. The review at this tier should be more substantive, confirming that the release size and purpose align with category strategy.
This is the tier where blanket health issues should surface: if a single release is large enough to warrant department head approval, the question of whether the blanket structure is still the right instrument for this kind of spend is worth asking.
Finance or executive approval tier
Very large releases (often above 10% to 20% of the blanket limit, or above absolute dollar thresholds) escalate to finance or executive approval. By the time releases reach this tier, the question is not just about this specific release but about the overall blanket trajectory.
Segregation of Duties
Standard segregation of duties principles apply to blanket POs and releases. Key separations:
- The blanket owner should not also be the release requestor for routine releases, to maintain independent oversight
- The release requestor should not be the release approver for the same release
- The person who receives the goods or accepts the services should not be the same person who approves the invoice
- The person who maintains the supplier master record should not be the same person who approves releases against that supplier
These separations are not always practical in small teams. Where they cannot be enforced through role assignment, compensating controls (post hoc reviews, audit sampling) need to provide equivalent assurance.
The Blanket Owner's Specific Responsibilities
Beyond accountability in the abstract, the blanket owner has concrete monthly responsibilities.
- Review consumption against the limit. Flag if pace is materially ahead or behind expected.
- Review release patterns for unusual activity: large releases, off pattern items, releases approaching scope boundaries.
- Coordinate with the supplier on any issues: delivery problems, billing disputes, performance concerns.
- Address any release approvals that are stuck in queue and update the renewal forecast based on current consumption trajectory.
- Document any blanket level decisions: amendments, scope clarifications, supplier escalations.
This is not a heavy responsibility for a single blanket, but across a portfolio of blankets, the cumulative attention adds up. Companies with many blankets often need a procurement coordinator dedicated to this kind of portfolio management.
Audit Considerations
External auditors testing procurement controls will look for clear evidence of governance discipline on blanket POs. The areas they probe:
- Whether named owners and approvers exist for active blankets, and whether the roles have been kept current as people change positions
- Whether release approvals follow the documented thresholds and whether exceptions are properly documented
- Whether segregation of duties is enforced in the release and approval workflow
- Whether blanket consumption is tracked and reviewed, with documentation of the review
- Whether amendments to blankets (limit increases, scope changes) follow a defined approval process
Going into the audit with documented governance roles, current ownership assignments, and a consistent approval trail shortens the audit work substantially compared to reconstructing the governance from emails and verbal explanations.
Start Here
Pull the list of active blankets and document the three governance roles for each one. The exercise itself will surface the gaps: blankets with no clear owner, blankets where the release requestor list has not been updated since the blanket was created, blankets where approval tiers are not documented.
Closing those gaps is mostly a documentation and notification exercise. Once the roles are clear, the ongoing discipline becomes much easier to maintain.
