Key takeaways
- Count a packet as ready only when the agenda names a decision or outcome, not just a topic.
- Separate a missing agenda from one the owner expected the assistant to infer from the meeting title.
- Record who supplied the clarification and how long before the meeting it arrived.
- Revise one owner template with a required decision field and test it on the next twenty packets.
Question and scope
This study asks how often a meeting preparation packet reaches a virtual assistant without a stated agenda or decision. It treats the packet as the unit and the first delivery as the event, not the later revision. The scope is one assistant, one executive calendar, and a fixed four-week window. The result describes that role and should not be read as a benchmark for every team.
A packet is eligible when it is assembled for a scheduled external meeting and contains at least one document. Invitations without attachments are excluded because there is nothing to assess. A packet is counted once even if it is revised before the meeting starts. The study records the state the assistant received rather than the state after a reminder.
The study also records who supplied the missing agenda and how long before the meeting it arrived. An agenda supplied by the meeting owner is different from one inferred by the assistant. The source is part of the result, not an anecdote. Report the counts by meeting type and by owner.
A packet that contains an agenda with no decision request is treated as partial rather than complete. The executive may know the topics but not what the client expects to settle. The study records the missing part instead of filling it in. This keeps a topic list from being mistaken for a decision agenda.
| Agenda state | Evidence | Follow-up |
|---|---|---|
| Complete | Topics plus a stated decision | Prepare a position |
| Partial | Topics but no decision | Ask for the outcome |
| Topic list only | Headings with no order | Clarify the priority |
| No agenda | Packet has no topic field | Ask before preparing |
Definitions and evidence standard
Define a usable agenda as a short list of topics with a stated decision or outcome for at least one topic. A list of headings without an outcome is not usable because the executive cannot prepare a position. A packet with a decision but no topic order is recorded as partial. The distinction matters because the repairs are different.
Use the invitation, the attached packet, and the assistant's task note as evidence. An agenda that appears only in a hallway conversation can be recorded if the assistant wrote it down at the time. Do not reconstruct an agenda from memory after the review begins. The reason should be visible to a reader who was not in the conversation.
Separate a missing agenda from an agenda the owner expected the assistant to infer from the meeting title. An inference may be reasonable for a recurring review that always covers the same items. It is not reasonable when the client has a new request in mind. Code the two conditions separately so the result does not blame the assistant for an unstated assumption.
Use the same definition of a usable agenda for every meeting owner, including senior executives. A rule that is relaxed for a senior person will hide the defect in the group that sends the most meetings. 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 packet in the window and freeze the list before coding. Include meetings with more than one client contact and more than one document type. If the window contains a conference or a holiday, report it separately. Record the number of packets, the number of owners, and the number of meeting types.
Measure the share with a complete agenda, a partial agenda, a topic list only, and no agenda. Add the time between packet delivery and the meeting start. Report the median rather than only an average. A few very late packets can distort an average and hide the common case.
If a packet was revised for a reason unrelated to the agenda, such as a missing file, record it separately. A packet that waited for a document is not an agenda defect. Report the unrelated waits beside the agenda results. The separation keeps the rate meaningful.
Have two reviewers code the first ten packets 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 agenda states before suggesting a cause. A large no-agenda group may mean the owners believe the meeting title is self-explanatory. A large partial group may mean the packet template has a topic field but no outcome field. Read the actual packets behind the biggest group before naming a reason.
Compare the result with the number of new meeting types introduced in the same week. A week with several new types may produce more missing agendas because the owner is also learning. Report the new-type count with the result. The comparison keeps a learning curve from being read as carelessness.
Check whether the missing agendas were clarified before the executive had to prepare. 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 agenda states across meeting types before combining them into one rate. A recurring review may carry a clear agenda while a one-off pitch does not. Report the rates separately when the difference is large. The split shows where a template change would have the most effect.
What the record shows
The record should show the agenda state at the moment the packet arrived, not the state after a reminder. A packet fixed within an hour is still a packet 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 owner is a template problem, while a pattern across many owners is a team habit. Compare the counts by owner 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 packets needed a decision and which only needed a status update. A missing agenda on a low-stakes update may be tolerable, while the same gap on a renewal call is not. Rank the cases by consequence rather than by count alone. That ranking should guide the first repair.
Limitations
The study measures agendas that were recorded, not every agenda that was spoken. An owner may have given the topics in a call that nobody wrote down. The result therefore describes the written packet, not the full communication. It also cannot show whether the executive was actually unprepared.
The calendar may change during the window, which can make an early packet look late by the later schedule. Freeze the meeting list and report any change. The sample may also be biased toward meetings that produced a document. State both limits beside the counts.
Deciding whether a topic is a decision requires judgment. Two reviewers may disagree at the margin. Record the disagreements and resolve them with examples before reporting. A calibration set of ten packets improves consistency.
Practical next step
Choose the owner group with the largest partial-agenda cluster and revise its packet template. Add a required field for the decision and one example of a usable answer. Explain that a topic list is not a decision agenda. Test the change on the next twenty packets.
Add a short field to the assistant's task note that records the clarification source. The field can be a list such as owner, executive, calendar, 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 agenda states with the baseline. Keep the revision if it reduces partial packets without increasing the delivery time. If the pattern does not move, the cause may be the invitation process rather than the template. Read the test with the people who own the meetings.
Sources and methodology
The study follows eligible external meeting packets through one assistant and one executive calendar for four weeks, coding the first agenda state, the clarification source, the time to clarification, and the time before the meeting against a frozen packet template.
- U.S. Small Business Administration - Manage your business current.
- U.S. Office of Personnel Management - Training and development current.
- U.S. Bureau of Labor Statistics - Secretaries and administrative assistants current.
- U.S. Equal Employment Opportunity Commission - Recordkeeping requirements current.
Source count: 4. Last verification date: November 17, 2026.
Questions about the findings
Is a topic list always a defect?
No. A topic list can work when the meeting is a routine update and the decision is already known. Count it as a defect when the executive cannot tell what the client expects to settle.
Should the assistant draft an agenda?
Only when a written pattern or a repeated meeting type supports it. Mark the draft as a proposal and ask the owner to confirm it before the executive relies on it.
How long should the observation window be?
Four weeks is enough to see recurring meeting types in many roles. A role with monthly client reviews may need a longer window to include those meetings.
What if the meeting owner is the executive?
Include executive-owned packets but report them separately. An executive may rely on context that is not written down, which is itself a finding.
Which measure is most useful?
The share of packets with a decision agenda plus the median time to clarification. The pair shows both the size of the gap and what it costs the executive.
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.
