Key takeaways
- Code the request itself for owner, source, output, finish standard, and due date.
- Separate a missing element from a missing document or an unclear instruction.
- Repair the intake template before asking the assistant to fill gaps from experience.
Question and scope
The question is narrow: when a request reaches a virtual assistant during the first month, how often does it arrive with everything needed to finish the work? A complete brief is not a long message, because length does not guarantee clarity. It is a message with the owner, the source, the output, and the finish standard. The review counts requests, not hours, so a single complex task does not dominate the result. Include requests that arrived through a shared inbox only when the assistant can identify the original sender.
Scope the review to one role and one client over a fixed window, usually the first four weeks. Include requests from email, chat, and the task system if those channels feed the same queue. Exclude work the assistant initiates without a request. Write the boundary down before counting because a moving scope makes the result impossible to compare. Record the date range and the role name at the top of the coding sheet.
| Brief element | Evidence in the request | Common gap | Action |
|---|---|---|---|
| Owner | Named requester and recipient | Forwarded thread only | Ask for the recipient |
| Source | Named file or record | Folder link only | Request the version |
| Output | Exact deliverable | Topic only | Define the finish |
| Standard | Checkable finish line | No acceptance rule | Add a check |
What counts as a complete brief
A complete brief names the person who asked for the work and the person who will receive it. It identifies the source record, the exact output, and the standard the output must meet. It also states the due date and what to do if an input is missing. Those five elements are enough for most administrative requests. Write the definitions in the same order as the fields so a coder can move left to right.
Do not treat a link to a folder as a complete brief. A folder may contain several versions and no clear instruction about which one applies. Do not treat a ticket title as complete either, because a title rarely carries the finish standard. The review should code the presence of each element from the request itself, not from a conversation that happened later. If the request itself is missing, mark the row as incomplete rather than reconstructing the brief.
Method and evidence standard
Use a simple coding sheet with one row per request and one column per brief element. Mark present, absent, or unclear, and keep a short note for every unclear mark. A second reviewer codes a sample of the same rows to check that the definitions are being applied the same way. Report the disagreement rather than forcing a consensus that hides ambiguity. Report the unclear share separately because it points to a definition problem rather than a missing field.
Keep the original request text with the row so the coding can be reopened. Record the date, the channel, the task family, and whether the assistant had to ask a question before starting. Those fields let the analysis separate a missing element from a missing document. They also make the review useful to the person who owns the intake process. Keep the row identifier tied to the task, not to the requester's name.
Measures and findings
Report the share of requests with all five elements present, the share missing one element, and the share missing two or more. Then report the elements that fail most often and the task families where they fail. A single overall percentage is easy to quote but hard to act on, because it hides which part of the brief needs repair. A short note should say which field was absent and what the assistant had to ask.
Pair completeness with the number of follow-up questions. A request can look complete and still generate a question because the answer was ambiguous. Pair it also with the number of returns or corrections. The combination shows whether the brief is merely present or actually usable. Describe the pattern as local to the reviewed role and window. Do not merge the follow-up question into the completeness count; keep the two measures separate.
What drives incomplete briefs
Incomplete briefs often come from a request that was forwarded without context. The sender assumes the assistant can see the earlier thread or knows the client's standing instruction. A second common cause is a template that asks for a due date but not for a finish standard. The template teaches people what to include, so a weak template produces weak briefs. Describe the pattern by requester group only when the group has enough requests to compare.
Another cause is a requester who does not know what the assistant needs. That is an onboarding problem for the requester, not only for the assistant. A short intake guide with one good and one bad example can change the pattern faster than a reminder. Review the causes by requester group before writing a fix. A template that is too long will be bypassed, so test it on a real request before rolling it out.
Interpreting the pattern
A high completeness rate with a high question rate suggests the brief has the right fields but the wrong level of detail. A low completeness rate with a low question rate may mean the assistant is filling gaps from experience, which is a risk during the first month. Read the two measures together before drawing a conclusion. Ask one requester to complete the template while the reviewer watches and note where they pause.
Look for a change over the four weeks. Completeness that improves after the first week may reflect a learning requester, while completeness that falls may reflect a busier queue. Do not attribute the change to the assistant without checking the request source. The pattern is evidence for a process conversation, not a performance rating. If the same field is skipped by every requester, the template is the problem.
Limitations
The review covers one role, one client, and a short window, so it cannot support a claim about virtual assistants in general. Requester behavior may change because they know they are being observed. The coding of unclear elements depends on the reviewer's judgment even when the definitions are written down. Do not treat a single week of improvement as proof that the intake change worked.
The review also cannot show whether a complete brief produces better work. It measures the input, not the outcome. A separate quality sample is needed to connect the brief to the finished output. State those limits in the summary so the reader does not treat a local count as a universal benchmark. A brief that is complete but late should be coded separately from one that is missing fields.
Practical next step
Fix the intake template before asking the assistant to compensate. Add a field for the finish standard and one for the source record. Give requesters an example of a brief that was completed without a follow-up question. Keep the template short enough that people use it during a busy day. The review can be repeated with a different role if the coding sheet stays the same.
Assign an owner for the intake process and a date to recheck the sample. Share the first result with the requesters, not only with the assistant's manager. Ask which field is hardest to complete and why. The next sample should show whether the template change reduced the missing elements. Keep the sample size visible so a small count is not mistaken for a broad trend.
Logging the next twenty requests
Log the next twenty requests after the template change. Use the same coding sheet and the same definitions so the two samples can be compared. Include the channel and the requester group. Do not change the definitions in the middle of the sample, because that makes the comparison unreadable. Do not use the result to compare one assistant with another.
Review the log with one requester and one reviewer. Ask whether the coded elements match what they see in the work. Correct the definitions if needed, then start a fresh sample. The aim is a repeatable check that survives a change in staff. A quality sample of the same requests would show whether brief completeness changes the output. Use the same request identifiers so the two records can be joined.
What would change the conclusion
The conclusion would change if a complete brief still produced the same number of follow-up questions and returns. That would point to a different problem, such as an unclear task instruction or a missing system permission. It would also change if the missing elements clustered in one requester group rather than across the queue. Share the coding sheet with the requester so they can see what the review measures.
A larger sample across several roles would show whether the pattern is local or structural. A quality sample linked to the same requests would show whether completeness affects the output. Until then, report the finding as a description of this intake process and use it to test one repair. Write the second sample result beside the first so the change is visible. Keep both samples in the same folder.
Sources and methodology
A bounded documentary review of requests handled by one virtual assistant role during a fixed first-month window. Each request is coded against five brief elements, with a second reviewer checking a sample. The review reports local completeness and follow-up questions only; it does not estimate performance or compare the role with an external benchmark.
- U.S. Small Business Administration — Hire and manage employees current.
- U.S. Office of Personnel Management — Training and Development current.
- U.S. Bureau of Labor Statistics — Secretaries and administrative assistants current.
- CISA Secure Our World current.
Source count: 4. Last verification date: November 7, 2026.
Questions about the findings
What counts as a complete brief?
A request that names the requester and recipient, identifies the source record, defines the exact output, states a checkable finish standard, and gives a due date.
Does a complete brief guarantee good work?
No. It improves the starting condition. The quality of the output still depends on the task instruction, the assistant's skill, and the review.
Can this review be used to rank requesters?
No. It describes where the intake process loses information. Use the result to repair the template and the requester guidance.
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.
