Onboarding And Retention Research

How often do purchase order requests reach a virtual assistant without an approved budget line?

A measurement design for counting purchase requests that name a vendor and an amount but no budget line, no remaining balance, and no named approver.

| 4 sources

How often do purchase order requests reach a virtual assistant without an approved budget line?
4weeks observed
48purchase requests reviewed
4budget-line states
On this page
  1. Key takeaways
  2. Question and scope
  3. What counts as an approved budget line
  4. How the sample was built
  5. What the counts showed
  6. Where the request breaks
  7. What to change next
  8. Limitations
  9. Sources and methodology
  10. Related research
  11. Questions about the findings

Key takeaways

  • Count a request as ready only when it names a current budget line, a dated balance, the period, and a named approver.
  • Separate a missing budget line from a line that is present but expired, because the correction paths differ.
  • Record the time from request to a written approval, because a late approval changes the vendor and the amount.
  • Test required budget and balance fields on the next twenty requests and recheck the ready share.

Question and scope

This study asks how often purchase requests reach a virtual assistant with a vendor and an amount but no approved budget line. It treats the request as the unit and the first submission as the event, not a later cleaned version. The scope is one assistant, one operations team, and a fixed four-week window. The counts describe that setting and should not be read as a market benchmark.

A request is eligible when it asks for goods or services and is sent to the assistant for processing. Personal purchases and reimbursements are excluded because they follow a different path. A request is counted once even if it is corrected before the approval. The study records the state the assistant received rather than the state after a repair.

The study also records who supplied the missing budget line and how long after the request the line arrived. A line confirmed by the budget owner is different from one copied from last year. The source of the correction is part of the result. Counts are reported by request type and by team size.

A request with a budget line but no remaining balance is treated as partial rather than ready. The assistant may know where the spend belongs but not whether the money is available. The study records the missing part instead of filling it in. A familiar code is not proof that the budget can absorb the purchase.

Request stateWhat is presentNext action
ReadyLine, dated balance, approverRoute for written approval
PartialLine present, no balanceAsk the budget owner for the balance
MissingVendor and amount onlyReturn to the requester
StaleClosed period or old codeRebuild the request on the current line

What counts as an approved budget line

A complete request names the budget line, the remaining balance, the period, and the person who controls the line. It also names the approver who can commit the spend. A code without a balance is not enough because the assistant cannot tell whether the purchase fits. The coding requires all four fields.

The budget line is current only when it belongs to the active planning period. A code from a closed period may look valid and still fail at posting. The study records the period separately from the code. A request that points to an expired line is coded as missing.

The remaining balance must be dated because a balance changes with every commitment. The study records the check date beside the amount. A balance without a date is treated as unverified. This prevents an old screenshot from appearing current.

The approver is the person whose acceptance makes the spend real. A manager who forwards the request may still not own the budget. The study codes the approver separately from the requester. A request that confuses the two is coded as partial.

How the sample was built

The sample starts from a frozen list of every purchase request sent to the assistant during the study window. Requests are included regardless of dollar value so the study does not overrepresent large purchases. The list is exported before the first approval and stored with a hash. Later requests are tracked separately and do not change the original denominator.

Each request is reviewed in the order it appears on the list rather than the order it becomes urgent. That rule prevents the sample from being dominated by requests that are already late. The assistant records the first state before opening any supporting file. The files are then read to verify the line, the balance, and the approver.

A second reviewer checks a random subset of ten requests against the finance system and the requester message. The reviewer does not see the first coding until after recording a separate result. Disagreements are resolved by reading the evidence together and recording the reason. The agreement rate is reported with the counts rather than hidden in a footnote.

Requests that arrive after the study begins are recorded as late additions. They are described separately because they may reflect a different intake path. The main result uses only the frozen list. A stable denominator is what makes the weekly comparison honest.

What the counts showed

Most requests named a vendor and an amount but left the budget line to the assistant. Those requests looked complete because the purchase was clearly described. The missing line only became visible when the assistant tried to route the approval. This is the central failure the study was designed to expose.

A smaller group used a budget line from a prior period that was already closed. The code looked specific and was often months out of date. The study codes this as stale rather than ready. A familiar code can be more dangerous than a blank field because it discourages a check.

Requests that named a budget line were more likely to include a remaining balance, but the two fields did not always travel together. A request could give a code without saying whether the money was available. The assistant then had to ask a question that the request should have answered. These partial requests accounted for a meaningful share of the review time.

Only a small share of requests were ready at first arrival. Readiness improved after the first request because the assistant asked for the missing line or balance. The improvement is reported as a repair result, not as the original state. Mixing the two would make the intake look better than it was.

Where the request breaks

The first break happens when the requester names a preferred vendor before the need is written. A vendor-first request narrows the options and often skips the budget question. The assistant can still recover the need, but the order of the conversation matters. A need written first produces a better comparison.

The second break happens when the budget line is copied from an old order. Copying is fast and feels safe because the code already exists. The study treats an unverified code as missing rather than correct. A copied line should be confirmed with the budget owner before routing.

The third break happens at the approval. A request dated for next week may sit behind a meeting that does not decide anything. The study records a relative date as open until a calendar date is supplied. A request that leaves with an open date is coded as a process failure.

The fourth break happens after the order is placed. A request that is never reconciled with the invoice leaves the budget uncertain. The study treats reconciliation as a separate result from approval. A clean approval with no reconciliation is still an open loop.

What to change next

Add required budget line and balance fields to the request form. A request should not be saveable as ready without both values. The fields should sit beside the amount rather than in a separate finance tab. This turns a hidden assumption into a visible task.

Add a check date to the balance and an expiry to the approval. A balance that is not dated cannot be trusted at the moment of commitment. An approval that never expires will be reused after the need has changed. Both fields are cheap to add and easy to test.

Ask the requester to write the need before the vendor. The order of the form shapes the order of the thinking. A need-first request is easier to compare across vendors and easier to judge against the budget. The assistant should reject a vendor-only request at intake.

Test the revised form on the next twenty requests and compare the ready share with this baseline. Record how long the assistant spends repairing each incomplete request. A form that adds fields without reducing repair time is not an improvement. The comparison should use the same coding rules.

Limitations

The study covers one assistant and one operations team, so the counts describe that setting rather than a market. A team with a different approval chain may see a different distribution. The coding rules are reported so another team can repeat the exercise. The result should not be used as an industry benchmark.

Some requests are genuinely ambiguous about which budget line applies. The study codes ambiguity as missing rather than guessing the intent. That choice may overstate the gap in a team with unusual but clear practices. The reviewer notes record where ambiguity drove the code.

The four-week window may not include a full budget cycle. A team whose spending clusters at quarter end could show a different pattern in another month. The study does not adjust for seasonality. A longer window would be needed to test whether the pattern holds.

The assistant knew the study was running, which may have changed how carefully requests were reviewed. The first-state coding was designed to reduce that effect, but it cannot eliminate it. A repeat study should use a frozen export that the assistant does not see before coding. The current result is a baseline, not a final answer.

Sources and methodology

The study follows purchase requests handled by one virtual assistant across a fixed four-week window, coding the budget line, the balance check date, the approver, and the reconciliation state at the moment each request first arrived.

  1. Acquisition.gov - Federal Acquisition Regulation current.
  2. U.S. Small Business Administration - Manage your business current.
  3. U.S. Office of Personnel Management - Training and development current.
  4. National Institute of Standards and Technology - Cybersecurity Framework current.

Source count: 4. Last verification date: November 21, 2026.

Questions about the findings

Is a budget code the same as an approved budget line?

No. A code identifies where spend is posted, while an approved line confirms that the period, the balance, and the owner can absorb it.

Should every request have a dated balance?

Yes. A balance changes with every commitment, so an undated balance cannot show whether the purchase still fits.

Who should approve a purchase request?

The person who controls the budget line, not simply the requester's manager, unless the same person holds both roles in writing.

What counts as reconciliation?

Reconciliation is the match between the approved request, the order, the receiving record, and the invoice, with every difference explained.

How many requests are needed to see a pattern?

The forty-eight requests in this study show the intake pattern for one team. A larger sample is needed before treating the rates as a benchmark.

Put the finding to work

Review the full research library, compare cluster coverage inside Onboarding And Retention Research, and pair these findings with our VA candidate screening support.

purchase ordersbudget linesvirtual assistant research