Research question and scope
This protocol measures how many purchase orders need a second approver before release. The unit is one purchase order submitted for approval during the period. A second approval means a reviewer beyond the first approver must approve before the order can be released. The measure describes the approval load, not the value of the purchase.
Set the scope to one procurement queue, one policy version, and a fixed period. Record the thresholds, the approver roles, and the system rules used at the time. If the policy changes during the period, split the sample at the effective date. A new threshold can change the share without changing the work.
Keep the measure separate from a judgment about spending. A second approval may be required by policy even when the purchase is routine. The purpose is to understand the demand and the wait. State that purpose in the report.
Population and unit of analysis
Define the population as every purchase order that entered the approval queue, including orders that were approved at the first step. The unit is the purchase order, not the approval message. One order may generate several messages and reminders. Count the order once and note the number of steps.
Include orders that were rejected, returned for changes, and withdrawn. A returned order is part of the approval load and may need a second review. Report the final status separately. Excluding returns would understate the work.
Exclude orders that were cancelled before any approval step. Report them separately as withdrawals. The approval queue never saw them, so they do not belong in the denominator. Keep the two groups distinct in the analysis.
Definitions that make the measure reproducible
Define a second approval as a recorded approval from a person other than the first approver after the first approval is complete. Define a policy-required second approval as one triggered by a written threshold or rule. Define a judgment second approval as one requested by a reviewer without a written trigger. Publish one example of each.
Define the release point as the timestamp when the order becomes available to the supplier or the buying system. Define the approval time as the period from the first submission to the final required approval. A measure that stops at the approval message may miss a system hold. Keep both timestamps in the same time zone.
Define the approver role by the permission in the system, not by the job title. A person with the title manager may not have the approval permission for a given amount. Record the role and the permission. The distinction prevents a false comparison between teams.
Sampling and data collection
Draw the sample from the procurement system rather than from a list of escalated orders. Record the export date, the filters, and the row count. Include every requester group and spend category in the period. A sample of high-value orders only will overstate the second-approval share.
Capture the order identifier, the amount, the category, the requester, the first approver, the second approver, the policy threshold, the timestamps, and the final status. Add the reason for any judgment approval. Store the record with the report. The policy threshold is needed to separate the two causes.
Check a small sample against the written policy. If an order was routed for a second approval without a matching rule, the system or the reviewer added a step. Record the reason. A policy that is not reflected in the system is a process risk, not only a measurement issue.
Record the time each approver had the order. A total approval time can hide a long wait at one step. Use the timestamps to split the wait. The step with the longest wait is the first place to review.
Measuring second-approval demand
Report the share of orders that needed a second approval, the share required by policy, and the share requested by judgment. Show the counts behind each share. A high judgment share may mean the policy is unclear or the first approver is avoiding a decision. A policy that produces most of the demand may need a simpler threshold.
Break the result down by amount band, category, requester group, and approver. A category with many second approvals may need a clearer threshold. A requester group with many returns may need a better intake form. Compare groups with similar spend and complexity.
Report the median and longest wait at the second step. A second approval that takes minutes is a different problem from one that takes days. Show the wait beside the share. The pair tells the reader whether the load is a volume issue or a bottleneck.
Limitations and next action
The measure cannot show an approval that happened in a private channel and was never recorded. It also cannot show the quality of the decision. Treat the result as a measure of the recorded approval path. Note the channels and order types that were not included.
Give the result to the procurement owner and the approvers with one change to test. The change might be a clearer threshold, a delegate for a busy approver, or a shorter review for a low-risk category. Record the effective date and repeat the measure with the same definitions. A controlled change is easier to judge.
Review the judgment approvals first because they are the least predictable. If they repeat for the same category, write a rule or remove the step. A second approval should protect a real risk, not compensate for an unclear first decision. A rule that is not enforced by the system will drift back.
