Onboarding And Retention Research

How often do meeting notes reach a virtual assistant without a named action owner?

A measurement design for counting meeting notes that list a task but name no owner, no due date, and no confirmation that the owner accepted the work.

| 4 sources

How often do meeting notes reach a virtual assistant without a named action owner?
4weeks observed
52meeting note sets reviewed
4owner states
On this page
  1. Key takeaways
  2. Question and scope
  3. What counts as an action owner
  4. How the sample was built
  5. What the counts showed
  6. Where the handoff breaks
  7. What to change next
  8. Limitations
  9. Sources and methodology
  10. Related research
  11. Questions about the findings

Key takeaways

  • Count a note set as ready only when it names an owner, a calendar due date, and a recorded acceptance.
  • Separate a missing owner from an owner who was named but never confirmed the task.
  • Record the first distribution time and the actual follow-up time, because a late note changes the next meeting.
  • Test one required owner field in the meeting template and recheck the next ten note sets.

Question and scope

This study asks how often meeting notes reach a virtual assistant with a task but no named action owner. It treats the note set as the unit and the first distribution as the event, not a later repaired version. The scope is one assistant, one leadership team, and a fixed four-week window. The result describes that setting and should not be read as a market benchmark.

A note set is eligible when it records at least one action and is sent to the team after a meeting. Personal reminders and informal chat messages are excluded because they are not a shared record. A note set is counted once even if it is corrected before the first follow-up. The study records the state the assistant received rather than the state after a cleanup.

The study also records who supplied a missing owner and how long after the meeting the name arrived. An owner confirmed by the chair is different from one inferred from the attendee list. The source of the correction is part of the result. Counts are reported by meeting type and by team size.

A note set with an owner but no due date is treated as partial rather than ready. The assistant may know who will act but not when the work is expected. The study records the missing part instead of filling it in. This keeps a familiar name from being mistaken for a complete action.

Note stateWhat is presentNext action
ReadyOwner, date, confirmationTrack to the due date
PartialOwner named, no dateAsk the owner for a date
MissingTask only, no ownerReturn to the chair
StaleOwner has left the teamReassign before the next meeting

What counts as an action owner

A complete record names the person who will do the work, the date it is due, and the evidence that will show it is done. It also names the person who can reassign the task if the owner is absent. A name without a date is not enough because the assistant cannot tell whether the task is late. The coding requires the person, the date, and the acceptance.

The owner is the person whose acceptance makes the task real. A chair who repeats the task in the meeting may still not own it. The study codes the owner separately from the person who raised the item. A note set that confuses the two is coded as partial.

The due date is part of the record because a task with no date cannot be reviewed at the next meeting. The study records whether the date is a calendar date rather than a phrase such as soon. A relative phrase is coded as missing. This prevents a vague answer from appearing complete.

A delegation is recorded as a change to the owner, not as an error. The original owner, the delegate, and the person who confirmed the change are all noted. The study counts a delegated task only when the delegation is written. A verbal delegation is coded as unverified.

How the sample was built

The sample starts from a frozen list of every meeting held in the study window that produced at least one action. Meetings are included regardless of team size so the study does not overrepresent large groups. The list is exported before the first follow-up and stored with a hash. Later meetings are tracked separately and are not used to change the original denominator.

Each note set 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 issues that are already close to a deadline. The assistant records the first state before opening the notes. The notes are then read to verify the owner, the date, and the confirmation.

A second reviewer checks a random subset of ten note sets against the meeting recording or the chat thread. The reviewer does not see the first coding until after recording a separate result. Disagreements are resolved by reading the thread together and recording the reason. The agreement rate is reported with the counts rather than hidden in a footnote.

Note sets 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. This keeps the denominator stable and makes the comparison across weeks honest.

What the counts showed

Most note sets listed a task and a person but no date that the assistant could test. Those notes looked ready because a name was attached to the work. The missing date only became visible when the assistant tried to review the action at the next meeting. This is the central failure the study was designed to expose.

A smaller group named an owner who had left the team or changed roles. The name looked specific and was often months out of date. The study codes this as stale rather than ready. A familiar name can be more dangerous than a blank field because it discourages a check.

Note sets with a named owner were more likely to include a date, but the two fields did not always travel together. A note could give a date without saying who accepted the task. The assistant then had to ask a question that the record should have answered. These partial notes accounted for a meaningful share of the review time.

Only a small share of note sets were ready at first arrival. Readiness improved after the first request because the assistant asked for the missing name or date. 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 handoff breaks

The first break happens when the note names a team rather than a person. A shared inbox looks like an owner but cannot accept responsibility. The assistant can send the task but cannot tell who has read it. A named person with a date would remove most of this delay.

The second break happens when the owner changes during the week. A new manager may inherit the task without inheriting the context. The assistant should record the change and confirm the new owner before the next meeting. The study treats an unconfirmed change as missing.

The third break happens at the due date. A task dated next week cannot be reviewed on Friday without a second question. The study records a relative date as open until a calendar date is supplied. A task that leaves with an open date is coded as a process failure.

The fourth break happens at distribution. A note set that reaches the team after the next meeting has already started is still a late record. The study treats timing and ownership as separate results. A complete record that arrives late is still a late record.

What to change next

Add a required owner field and a required date field to the meeting notes template. A note set should not be saveable as ready without both values. The fields should sit beside the action rather than in a separate list. This turns a hidden assumption into a visible task.

Add a confirmation line that the owner repeats during the meeting. The assistant should record the acceptance rather than infer it from silence. A short read-back is enough when the owner is present. The confirmation should be visible to the chair.

Record the first distribution time and the actual follow-up time in the note log. Compare the gap with the planned review window. A recurring gap points to a meeting that ends too late for the notes to be useful. The goal is not a faster note but enough time for a real review.

Test the revised template on the next ten meetings and compare the ready share to this baseline. Record how long the assistant spends repairing each incomplete note set. A template 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 leadership team, so the counts describe that setting rather than a market. A team with a different meeting mix 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 notes are genuinely ambiguous about who accepted a task. 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 quarter of planning cycles. A team with most of its actions in one season 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 notes 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 meeting notes handled by one virtual assistant across a fixed four-week window, coding the action owner, the due date, the decision line, and the confirmation at the moment each note set first arrived.

  1. U.S. Bureau of Labor Statistics - Secretaries and administrative assistants 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 20, 2026.

Questions about the findings

Is an attendee the same as an action owner?

No. An attendee may hear the task, while an owner accepts responsibility for it. A note that lists an attendee but no owner is coded as missing.

Should every action have a due date?

Yes. A date that is specific enough to test against the calendar is what makes the action reviewable at the next meeting.

What counts as confirmation?

A confirmation is the owner repeating the task and the date, in the meeting or in writing, in a form the assistant can record.

How many note sets are needed to see a pattern?

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

Which measure is most useful?

The share of note sets complete at first arrival plus the median time to the first follow-up. The pair shows both the gap and its effect on the team.

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.

meeting notesaction ownersvirtual assistant research