Key takeaways
- Measure purchase approval from the first complete request to the final decision, and report the waiting time at each stage so delay is not mistaken for diligence.
- Keep the measurement definitions fixed across the review period so the next cycle can compare like with like.
- Record the correction owner and a repeat date before the file is closed.
Question and scope
This study asks how long an executive office purchase request takes from the first complete submission to the final approval or rejection. The unit is one request. The review follows the request through each approver and records where it waited. It does not judge whether the purchase itself was wise.
Set the scope to one executive office and one quarter and include requests for services, equipment, subscriptions, and travel. Record the request type and the amount band. A study that covers only large purchases will miss the repeat small requests that consume most of the administrative time. The study should note the mix so the result is not read as an average across unlike requests.
Include requests that were withdrawn, requests that were rejected, and requests that were split into smaller amounts. A withdrawn request still consumed approval time. Record the outcome and the stage reached. The sample should include at least one request that was returned for more information.
What the sources establish
The BLS description of administrative support work establishes that processing approvals and maintaining records are core assistant tasks but does not define an approval cycle standard. ISO 9001 describes quality management as a process with defined requirements and review points, which supports measuring each stage. The NIST cybersecurity framework describes access and authorization controls, which supports recording who approved what. The sources do not establish a target number of days for a purchase approval.
The sources do not set a delegation threshold or a required number of approvers. They also do not say whether a verbal approval counts. The study therefore measures the office's own policy and the evidence it keeps. The report should keep that local scope visible.
The sources support separating the time a request waits from the time an approver actually works on it. A long cycle can reflect a queue rather than a difficult decision. The study should record both the elapsed time and the number of stages. The distinction is the core of a useful result.
Definitions and measures
Define the start as the moment a complete request, with the required evidence, reaches the first approver. A request that is missing a quote has not started the approval clock. Keep the definition fixed across the sample. The report should show how many requests were incomplete at first submission.
Define the end as the moment the final approver records a decision in the system of record. An email that says the purchase looks fine is not a final approval. Record the decision and the timestamp. The definition should be agreed with finance before the study begins.
Measure the elapsed days, the business days, and the number of approvers who touched the request. Record the waiting time at each stage and the time spent in rework. The measures should be reported together. A short cycle with three reworks is not necessarily efficient.
Sampling and collection
Sample requests from the procurement system, the finance inbox, and the executive assistant's tracking sheet. Include a request made outside the system and a request that was approved by a delegate. Record the source and the route. A system-only sample will miss the requests that bypassed the process.
Collect the request form, the quotes, the approval messages, the delegation record, and the final decision. Mask the supplier pricing that is not needed for the timing review. If an approval was given in a meeting, record the note and the date. A verbal approval without a note cannot be timed reliably.
Include a request at the start of a quarter and one at the end of the quarter, when budgets and approver availability may differ. Record the period and the workload. The sample should test the process when the office is busiest, not only in a quiet month. The comparison should state which period dominated the sample.
Verification pathway
Check each stage timestamp against the system log rather than the date on the request form. A form dated at the start of the week can hide a submission that happened on Friday. Record the source and the timestamp. The study should use the same source for every request.
Confirm that the approver had the authority recorded in the delegation register at the time of the decision. An approval by someone without authority can restart the cycle later. Record the approver and the delegation. The check should be done for at least one request per approver.
Test one request by asking a colleague who did not process it to trace the route from submission to decision. A route that only its owner can explain is not a repeatable process. Record the test and the result. The test should use the same system the office uses.
Analysis and reporting
Report the median and the range of cycle time, the median waiting time per stage, and the share of requests that required rework. Break the results down by request type and amount band. Report the withdrawn and rejected requests separately. A single average can hide a small category with a very long cycle.
Inspect the delays for patterns. A cluster of waiting time at one approver may point to a delegation gap, while a cluster of rework may point to an unclear request form. Choose one change, such as a required quote or a named delegate. Do not rank approvers by cycle time when their request mix differs.
Report the share of requests that were split to avoid a threshold and the time those splits added. A split can be a legitimate budgeting choice or an attempt to bypass a control. Show the count and the pattern. The measure should be read with the finance contact rather than used as a accusation.
Limits and next action
The study cannot prove that a faster approval produced a better purchase or that every request was necessary. It also cannot capture the informal conversations that moved a request forward. The report should state those limits and avoid treating speed as the only goal. Keep the forms and the system logs with the study so the next reviewer can check the same record.
Set a repeat study date and keep the definitions stable. Assign the correction to the process owner and give the executive a one-page approval map. The next quarter should test whether the same stage or the same form field causes the delay. A useful result is a request that reaches a decision without a chase.
Sources
- Secretaries and Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Outlook Handbook.
- Executive Secretaries and Executive Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics.
- Executive Secretaries and Executive Administrative Assistants, O*NET OnLine.
- Business Formation Statistics, U.S. Census Bureau.
- Nonfarm Business Sector: Labor Productivity, Federal Reserve Economic Data.
- Productivity Statistics, OECD Data Explorer.
- World Development Indicators, World Bank DataBank.
- ILOSTAT Labour Statistics, International Labour Organization.
- 2024 Work Trend Index Annual Report, Microsoft and LinkedIn.
- The economic potential of generative AI, McKinsey Global Institute.
- Creating helpful, reliable, people first content, Google Search Central.
- Search Engine Optimization Starter Guide, Google Search Central.
- Dear Manager, You Are Holding Too Many Meetings, Harvard Business Review.
- BLS, Secretaries and Administrative Assistants.
- ISO 9001, Quality Management.
- NIST, Cybersecurity Framework.
Related research
Apply the research
Use the finding to frame one question for your own team: which support work is currently invisible, and who should own the next step? A scoped consultation can turn that question into a practical role. Write the question down before the meeting. Name the person who owns the next step.
Turn the finding into a support scope.
Bring the workflow that feels hardest to see. We will help define the role, the evidence it should maintain, and the decisions that stay with leadership.
Talk through the role