Onboarding And Retention Research

Where does rework accumulate between a calendar conflict and the rescheduled meeting?

A measurement design for mapping the repeated steps between a detected conflict and a confirmed new meeting time, from the option set to the room and the invite.

| 4 sources

Where does rework accumulate between a calendar conflict and the rescheduled meeting?
5weeks observed
3executives tracked
6rework points
On this page
  1. Key takeaways
  2. Question and scope
  3. What counts as a repeated step
  4. How the sample was built
  5. Where the rework accumulates
  6. Where the sequence breaks
  7. What to change next
  8. Limitations
  9. Sources and methodology
  10. Related research
  11. Questions about the findings

Key takeaways

  • Count a sequence as complete only when it names the option set, the approval, the room, and the attendee confirmation.
  • Store the options with their cost and consequence so a second approver does not force a rewrite.
  • Check the room and the link with the new time, because a time without a place is not a resolved meeting.
  • Test one required option field in the reschedule form and recheck the next ten sequences.

Question and scope

This study asks where rework accumulates between a calendar conflict and the rescheduled meeting. It treats the rescheduling sequence as the unit and the first conflict signal as the event, not a later cleaned-up calendar. The scope is one assistant, three executive calendars, and a fixed five-week window. The result describes that setting and should not be read as a market benchmark.

A sequence is eligible when a meeting is moved, shortened, delegated, or cancelled because of a conflict. A meeting that is changed for a content reason is excluded because the cause is different. A sequence is counted once even if the meeting moves twice. The study records the steps the assistant actually performed rather than the ideal path.

The study also records who supplied a missing decision and how long after the conflict the decision arrived. A choice confirmed by the executive is different from one inferred from a reply. The source of the correction is part of the result. Counts are reported by meeting type and by calendar.

A sequence with a new time but no confirmed attendee is treated as partial rather than complete. The assistant may have moved the meeting without closing the loop. The study records the missing part instead of filling it in. This keeps a busy calendar from being mistaken for a resolved conflict.

Rework pointWhat repeatsNext action
Option setSame three options rewrittenStore the options once
ApprovalDecision asked twiceRecord the approver and time
RoomRoom rebooked after the moveCheck the room with the time
InviteInvite rebuilt from notesUpdate the original invite

What counts as a repeated step

A repeated step is any task the assistant performs more than once for the same sequence because an earlier record was incomplete. Rewriting the same option set for a second approver is a repeat. Rebuilding an invite that was already sent is a repeat. The coding requires the same purpose and the same sequence.

The study separates a repeat from a legitimate revision. A new time after a new constraint is a revision, not rework. The assistant records the reason for each change. A repeat without a new reason is coded as rework.

The option set is the most common place for a repeat because it is often written in a chat and then rewritten in a message. The study records whether the options were stored where the approver could see them. An option set that exists only in one thread is likely to be rebuilt. A stored set with the cost beside each option removes the second rewrite.

A room or a link is part of the sequence because a new time without a place is not a resolved meeting. The study records whether the room and the link moved with the time. A meeting that keeps the old room is coded as partial. The check is recorded before the change is sent to attendees.

How the sample was built

The sample starts from a frozen list of every conflict recorded in the study window across the three calendars. Sequences are included regardless of seniority so the study does not overrepresent one executive. The list is exported before the first reschedule and stored with a hash. Later conflicts are tracked separately and are not used to change the original denominator.

Each sequence 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 conflicts that are already late. The assistant records the first state before opening the calendar. The thread is then read to verify the options, the approval, and the confirmation.

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

Sequences 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.

Where the rework accumulates

Most rework happened at the option set. The assistant wrote two or three choices in a message, the approver asked for the cost, and the choices were rewritten in another message. The first set looked complete but did not carry the information the decision needed. This is the central failure the study was designed to expose.

A smaller group repeated the approval step because the decision was recorded in a chat that a second approver could not see. The name looked specific and was often out of date. The study codes this as a stale approval rather than a new decision. A familiar thread can be more dangerous than a blank field because it discourages a check.

Sequences with a stored option set were more likely to include the room, but the two did not always travel together. A new time could be approved without checking whether the room was free. The assistant then had to reopen the decision after the move. These partial sequences accounted for a meaningful share of the review time.

Only a small share of sequences were complete at first confirmation. Rework fell after the assistant began storing the options and the room together. 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 sequence breaks

The first break happens when the conflict is reported without the cost of moving each meeting. A message that only says there is a conflict sends the decision back to the busiest person. The assistant can describe the clash but cannot explain the trade-off. A written option set with the cost would remove most of this delay.

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

The third break happens at the room or the link. An approved time may still fail if the room is taken or the link was created for the old time. The study records the room check separately from the time approval. A sequence that leaves with an unconfirmed room is coded as a process failure.

The fourth break happens at the attendee confirmation. A meeting that is moved but not acknowledged is still a risk. The study treats confirmation and scheduling as separate results. A complete record that no one has seen is still incomplete.

What to change next

Add a required option-set field that names the cost and the consequence of each choice. A conflict should not be saveable as ready without at least two options. The field should be visible to the approver rather than buried in a thread. This turns a hidden assumption into a visible decision.

Add a room and link check to the same form as the new time. The assistant should record the confirmation for each resource before the move is sent. A time without a place should be flagged. The rule should be reviewed when the meeting platform changes.

Record the conflict time, the approval time, and the confirmation time in the sequence log. Compare the gaps with the planned response window. A recurring gap points to a decision that is asked too late. The goal is not a faster move but a complete one.

Test the revised form on the next ten sequences and compare the repeated-step count to this baseline. Record how long the assistant spends rebuilding each option set. A form that adds fields without reducing rework is not an improvement. The comparison should use the same coding rules.

Limitations

The study covers one assistant and three calendars, 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 sequences are genuinely ambiguous about whether a step was a repeat or a revision. The study codes ambiguity as a revision rather than guessing waste. That choice may understate the rework in a team with unclear threads. The reviewer notes record where ambiguity drove the code.

The five-week window may not include a full quarter of planning cycles. A team with most of its conflicts 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 sequences were recorded. 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 rescheduling sequences handled by one virtual assistant across a fixed five-week window, mapping each step from the first conflict signal to the confirmed meeting and coding every repeated task, missing decision, and rebuilt invite.

  1. U.S. Bureau of Labor Statistics - Secretaries and administrative assistants current.
  2. U.S. Small Business Administration - Manage your business current.
  3. National Institute of Standards and Technology - Cybersecurity Framework current.
  4. U.S. Office of Personnel Management - Training and development current.

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

Questions about the findings

What counts as rework?

Rework is a step that is repeated because the earlier record was incomplete or unclear, such as rewriting the same option set for a second approver.

Why track three executives?

Three calendars show whether the pattern belongs to one person or to the process. The study reports the sequences together and by calendar.

Should the room be checked before the move is approved?

Yes. A new time that has no room is not a resolved conflict, so the room check belongs in the option set.

How many sequences are needed to see a pattern?

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

Which measure is most useful?

The number of repeated steps per sequence plus the median time from conflict to confirmation. The pair shows both the waste 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.

calendar conflictsrescheduling reworkvirtual assistant research