Onboarding And Retention Research

How often do virtual assistant purchase requests miss a budget owner?

A spend-control study for counting purchase requests that reach approval without a named budget owner and for separating a missing code from a code the requester expected finance to assign.

| 4 sources

How often do virtual assistant purchase requests miss a budget owner?
60days observed
110requests reviewed
4budget states
On this page
  1. Key takeaways
  2. Question and scope
  3. Definitions and evidence standard
  4. Sampling and measurement
  5. Findings and interpretation
  6. What the record shows
  7. Limitations
  8. Practical next step
  9. Sources and methodology
  10. Related research
  11. Questions about the findings

Key takeaways

  • Count a request as ready only when it names both a budget owner and a budget line.
  • Separate a missing owner from one the requester expected finance to assign at payment.
  • Record who supplied the clarification and how long the request waited before the code appeared.
  • Add a required budget-owner field to one request form and test it on the next twenty submissions.

Question and scope

This study asks how often a purchase request reaches approval without a named budget owner or budget line. It treats the request as the unit and the first submission as the event. The scope is one assistant, one team, and a fixed sixty-day window that includes a month-end close. The result describes that team and should not be read as a finance benchmark.

A request is eligible when it names an item or service and an amount to be spent. Requests for reimbursement of a personal purchase are excluded because the spend has already happened. A request is counted once even if it is revised after a question. The study records the budget state the assistant submitted rather than the state after finance intervened.

The study also records who supplied the missing budget owner and how long the request waited before the code appeared. A code supplied by the requester is different from one assigned by finance at payment time. The source is part of the result, not an anecdote. Report the counts by team and by spend range.

A request with a team name but no named budget owner is treated as partial rather than complete. The team may share a cost centre, but nobody is accountable for the remaining balance. The study records the missing part instead of filling it in. This keeps a general label from being mistaken for ownership.

Budget stateEvidenceFollow-up
CompleteNamed owner and codeApprove inside the balance
Owner onlyPerson named, no codeAsk for the code
Code onlyCode named, no ownerFind the owner
NeitherTeam label onlyStop and clarify

Definitions and evidence standard

Define a usable budget owner as a named person or role that can confirm the code and the remaining balance. A department name alone is not usable because it does not identify who can answer a question. A code without an owner is recorded as partial. The distinction matters because the repairs are different.

Use the request form, the approval message, and the finance record as evidence. A budget owner named in a meeting can be recorded if the assistant wrote it down at the time. Do not reconstruct an owner from the payment approver after the invoice arrives. The reason should be visible to a reader who was not in the conversation.

Separate a missing budget owner from an owner the requester expected finance to identify. An expectation may be reasonable when a written policy assigns every team a named finance partner. It is not reasonable when the policy only names a general mailbox. Code the two conditions separately so the result does not blame the assistant.

Use the same definition of a usable owner for every spend range, including small purchases. A rule that is relaxed for a small amount will hide the defect in the group that sends the most requests. The study should state any exception before coding begins. An exception added later should be reported as a change to the method.

Sampling and measurement

Collect every eligible request in the window and freeze the list before coding. Include requests from more than one requester and more than one spend range. If the window contains a quarter close or a holiday, report it separately. Record the number of requests, the number of requesters, and the number of categories.

Measure the share with a complete owner and code, an owner without a code, a code without an owner, and neither. Add the time from submission to the first finance response. Report the median rather than only an average. A few very large requests can distort an average and hide the common case.

If a request was delayed for a reason unrelated to the budget, such as a missing quote, record it separately. A request that waited for a supplier is not a budget defect. Report the unrelated waits beside the budget results. The separation keeps the rate meaningful.

Have two reviewers code the first fifteen requests and compare their results before continuing. Discuss every disagreement and write the agreed rule in one sentence. Repeat the comparison at the midpoint of the window. A short calibration note makes the final counts easier to defend.

Findings and interpretation

Present the budget states before suggesting a cause. A large code-without-owner group may mean the form asks for a code but not for the person who guards the balance. A large no-owner group may mean the requester is new to the team. Read the actual requests behind the biggest group before naming a reason.

Compare the result with the number of new requesters in the same window. A new requester may produce more missing owners because the intake process is also new. Report the new-requester count with the result. The comparison keeps a learning curve from being read as carelessness.

Check whether the missing owners were supplied before the purchase was made. A clarification found early is cheaper and may show that the assistant is already compensating. Report the clarification source with the result. The source tells the team where to invest next.

Compare the budget states across spend ranges before combining them into one rate. A small supply order may carry a clear owner while a service contract does not. Report the rates separately when the difference is large. The split shows where a form change would have the most effect.

What the record shows

The record should show the budget owner at the moment of submission, not the owner assigned after finance reviewed the invoice. A request fixed during payment is still a request that arrived incomplete. Report both the initial state and the time to correction. The pair separates a small habit from a costly gap.

A pattern across one requester is a form problem, while a pattern across many requesters is a team habit. Compare the counts by requester before writing a general recommendation. The narrow repair is usually faster and easier to test. A broad campaign can follow if the pattern holds.

The record also shows which requests stayed inside the remaining balance and which needed a new approval. A missing owner on a small purchase may be tolerable, while the same gap on a recurring service is not. Rank the cases by exposure rather than by count alone. That ranking should guide the first repair.

Limitations

The study measures owners that were recorded, not every owner that was spoken. A requester may have named the owner in a call that nobody wrote down. The result therefore describes the written request, not the full communication. It also cannot show whether the purchase was necessary.

The finance system may assign a code automatically at payment, which can make an early request look complete in hindsight. Freeze the submission snapshot and report any later assignment. The sample may also be biased toward requests that were easy to retrieve. State both limits beside the counts.

Deciding whether a role name is specific enough requires judgment. Two reviewers may disagree about a shared mailbox that is monitored by one person. Record the disagreements and resolve them with examples before reporting. A calibration set of fifteen requests improves consistency.

Practical next step

Choose the requester group with the largest missing-owner cluster and revise its request form. Add a required field for the budget owner and one example of a usable answer. Explain that a team name is not an owner. Test the change on the next twenty requests.

Add a short field to the request record that captures the clarification source. The field can be a list such as requester, manager, finance, or policy. A small list is faster than free text and easier to count. The note should take less than a minute to complete.

Review the change after two weeks and compare the budget states with the baseline. Keep the revision if it reduces missing owners without slowing the approval. If the pattern does not move, the cause may be the intake channel rather than the form. Read the test with the people who approve the spend.

Sources and methodology

The study follows eligible purchase requests through one assistant and one team for sixty days, coding the first budget state, the clarification source, the time to the first finance response, and the final approval against a frozen request form.

  1. U.S. Small Business Administration - Manage your business current.
  2. U.S. Office of Personnel Management - Training and development current.
  3. U.S. Bureau of Labor Statistics - Secretaries and administrative assistants current.
  4. U.S. Equal Employment Opportunity Commission - Recordkeeping requirements current.

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

Questions about the findings

Is a team name a budget owner?

No. A team name does not identify who can confirm the remaining balance. Ask for the person or role that guards the code.

Should finance assign every code?

Finance can assign a code, but the request should still name the owner who knows the balance. A code without an owner hides an overspend until payment.

How long should the window be?

Sixty days is enough to include a month-end close in many teams. A team with quarterly purchasing may need a full quarter.

What if the owner changes during the request?

Record the change and the date it took effect. A request that waits for a departed owner is a process finding, not a requester error.

Which measure is most useful?

The share of requests with both an owner and a code plus the median time to a finance response. The pair shows the gap and its cost.

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 requestsbudget ownershipvirtual assistant research