Why purchase requests flood the inbox
A purchase request arrives as a forwarded email with a quote, a deadline, and an implicit question. The executive sees it between meetings, forwards it to finance, and later learns that the quote expired. The problem is not the purchase; it is the absence of a lane that tells the requester what information to provide and who decides. Naming the lane and its owner is the first step toward reducing that traffic.
When every request goes to the principal, the desk loses the chance to screen routine purchases. Small renewals and standard supplies compete with decisions that genuinely need executive judgment. A purchase lane separates the two so attention goes to the commitments that carry real risk. The desk can then route the routine requests without asking the principal to interpret each one.
Start by counting the requests that reached the principal in the last quarter. Group them by amount, vendor status, and whether they were routine. The pattern will show where the lane should begin and which requests can move to the desk. Use the count to set the threshold, not a guess.
Define the threshold that sends a request to the desk
Set a threshold below which the desk can process a request under an approved budget. The threshold should name the amount, the category, and the evidence required. A request for office supplies is different from a request for a new data platform, even if the amounts are similar. Write the distinction down so the desk does not negotiate it each time.
Above the threshold, the request should still go through the desk rather than directly to the executive. The desk adds the budget line, the vendor status, and the decision the principal needs to make. This preparation turns a forwarded email into a usable decision item. It also gives finance a consistent record.
Build a one-page request record
The record should include the business reason, the vendor, the amount, the term, the budget owner, and the decision date. Add the quote or contract link and a note on whether the vendor is already approved. One page is enough for most purchases and forces the requester to be specific. The desk can reject an incomplete record without guessing.
Include the consequence of waiting. A request tied to a regulatory deadline or a project start date needs that context visible. If there is no consequence, the request can wait for the weekly window. This single field helps the principal prioritise without reading the whole thread.
Route by cost, risk, and renewal status
Cost is only one dimension. A low-cost tool that touches sensitive data may need a security review, while a larger purchase from an approved vendor may be routine. Route requests by the combination of spend, data access, and contractual commitment. The lane should state which reviews are required for each combination.
Renewals need their notice date checked before anything else. A request that arrives after the notice window is a different decision from one that arrives with time to negotiate. The desk should flag the date and the auto-renew terms at intake. That prevents a routine approval from becoming an urgent problem.
Set a weekly approval window
A weekly window gives the principal a predictable moment to review requests and gives the desk time to prepare them. Collect requests by a cut-off, assemble the record, and send one short list before the window. Urgent items can still move outside the window, but they should be rare and explained. The cadence reduces interruptions without slowing routine work.
Keep the list ordered by decision date rather than by amount. A small request with a hard deadline may matter more than a large one that can wait a month. Add a one-line recommendation to each item so the principal can approve, reject, or ask a question. The desk should record the outcome in the same place.
Handle urgent purchases without bypassing control
Urgent does not mean uncontrolled. Define a small set of situations that justify same-day approval, such as a failed system, a safety issue, or a contractual deadline. Require the requester to state the urgency and the cost of delay. The desk can then escalate with a clear recommendation rather than a forwarded panic.
After an urgent purchase, complete the normal record within one business day. The retrospective paperwork should note who approved it, what was bought, and why the normal window was not used. Review urgent purchases monthly to see whether the threshold or the lane needs adjustment. A pattern of emergencies usually points to a planning gap.
Audit the lane for leakage and delay
Track requests that bypassed the lane, the time from request to decision, and the number returned for missing information. These three measures show whether the process is working or merely existing. A rise in bypasses may mean the threshold is too low or the window is too slow. A rise in returns may mean the intake record is unclear.
Share the results with finance and the executive once a quarter. For related guidance, see our article on running a monthly vendor renewal watchlist and our executive support services. The GAO Green Book describes control activities and documentation that help a purchase lane stay auditable. The review should produce one change to the lane, not a longer report.
Key takeaways
- Set a written threshold that names amount, category, and required evidence.
- Use a one-page request record with the business reason, budget owner, and decision date.
- Route by spend, data access, and contractual commitment rather than by cost alone.
- Run a weekly approval window and reserve same-day approval for a short exception list.
- Measure bypasses, decision time, and returned requests every quarter.