Meeting cadence measurement

Measuring Direct Report One-on-One Reschedule Frequency in an Executive Office

A measurement protocol for one-on-one reschedules, covering the meeting inventory, the reschedule definition, the cause coding, and the quarterly review.

7 min readHireExecutiveTeam research

Key takeaway Measure one-on-one reschedules by who moved the meeting and how late, so a repeat pattern becomes a scheduling problem the office can fix rather than a personal complaint.

Measuring Direct Report One-on-One Reschedule Frequency in an Executive Office research illustration
Table of contents
  1. Key takeaways
  2. Question and scope
  3. What the sources establish
  4. Definitions and measures
  5. Sampling and collection
  6. Verification pathway
  7. Analysis and reporting
  8. Limits and next action
  9. Sources
  10. Related research
  11. Apply the research

Key takeaways

  • Measure one-on-one reschedules by initiator, notice in business hours, and final outcome, and count skips separately from moves.
  • Report the pattern by pair and by recurring conflict so the finding points to a scheduling decision rather than to an individual.
  • Record the protected slot, the notice rule, the owner, and a repeat date before the study is closed.

Question and scope

This study asks how often the executive's recurring one-on-one meetings are moved, by whom, and at what notice. The unit is one scheduled occurrence of one recurring one-on-one between the executive and a direct report. The review follows each occurrence from the original date to the date it was actually held, including cancellations that were never rebooked. It does not judge the quality of the conversation.

Set the scope to one executive, their direct reports, and a fixed period such as one quarter. Include the one-on-ones that were skipped entirely, because a cancelled meeting that is never rebooked is the most consequential outcome. Record the pair, the original date, and the outcome. The count should include meetings moved by the executive and by the direct report.

Include at least one direct report who joined during the period and one who was in a demanding role with frequent travel. A new report and a traveling report are likely to show different reschedule patterns, and the study should be able to describe both. Record the start date and the role context. The sample should include the weeks around a board meeting or quarter close.

What the sources establish

The BLS description of administrative support work establishes that calendar coordination is a core assistant task but does not define a reschedule standard. The PMI scheduling material describes schedule changes as changes that should be logged, assessed, and communicated rather than absorbed silently. ISO 9001 describes monitoring and measurement as part of process control. The sources do not establish an acceptable reschedule rate for one-on-one meetings.

The sources do not say whether the executive or the direct report should control the meeting, or how much notice is reasonable. They also do not establish a link between reschedule frequency and employee engagement. The study therefore measures the office's own cadence and the patterns it can observe. The report should keep that local scope visible and avoid causal claims.

The sources support treating a reschedule as a schedule change with a cause and an owner rather than as a neutral calendar event. A meeting that moves three times is not the same as a meeting that moves once. The study should test the number of moves, the notice, and the final outcome. A calendar with few visible cancellations can still hide a pattern of meetings that are never held.

Definitions and measures

Define a reschedule as any change to the start time or date of a scheduled occurrence, including a cancellation that is later rebooked. A cancellation without a new date is a skip and should be counted separately. Record the original date, the new date, and the number of moves. The definition should be applied before any rate is calculated.

Define notice as the time between the change and the original start time, measured in business hours rather than calendar days. A change made on Friday for a Monday meeting gives less useful notice than the day count suggests. Record the notice in hours and the day of the week. The measure should be consistent across time zones.

Attribute each move to the party who initiated it, using the calendar change record and a confirmation from the assistant when the record is ambiguous. A move initiated by the executive's office on the direct report's behalf should be attributed to the executive's side rather than to the report. Record the initiator and the evidence. The attribution should be reviewed before the pattern is reported.

Measure the held rate, the skip rate, and the median number of moves per occurrence separately. Combining them into a single reliability score hides whether the problem is frequent small moves or occasional lost meetings. Record each measure and its denominator. The report should show the raw counts alongside the rates.

Sampling and collection

Export the recurring one-on-one series for the full period with the original dates, the change history, and the final outcome. A current calendar view shows only the latest date and loses the number of moves. Record the export date and the system used. The export should be preserved with the study file so the analysis can be repeated.

Collect the calendar change records that show who moved each occurrence and when the change was made. A change made by an assistant on the executive's behalf should be visible in the audit trail. Record the actor and the timestamp. Where the trail is incomplete, mark the attribution as inferred rather than presenting it as confirmed.

Ask each direct report for a short confirmation of whether the meeting was held and whether the new time worked. A calendar that shows a held meeting can still hide a ten-minute conversation that replaced the intended hour. Record the confirmation and the duration. The request should be brief and should not ask the report to evaluate the executive.

Interview the executive assistant about the rules for moving a one-on-one and the requests that trigger a move. A rule such as 'board travel always wins' explains a pattern that would otherwise look like avoidance. Record the rule and the request pattern. The interview should be summarized without attributing individual criticism.

Verification pathway

Match each occurrence to the calendar change record, the final meeting, and the direct report's confirmation before classifying it. An occurrence with no confirmation may have been held informally, and the report should say so. Record the match and the classification. An occurrence that cannot be verified should be listed as unverified rather than counted as skipped.

Ask the assistant to confirm any occurrence that the data classifies as a skip before the finding is published. A meeting that was replaced by a longer conversation in the corridor may be a skip on the calendar but not in practice. Record the confirmation and the explanation. The study should correct the classification when the explanation is credible.

Have a second reviewer recompute the held rate and the median notice for a sample of ten occurrences. A rate that cannot be reproduced from the same records is not ready for a management report. Record the reviewer and the difference found. The report should state the reconciliation method when the two calculations differ.

Check the time zone settings on the calendar series and the change records before calculating notice. A series that spans offices in different zones can produce a notice figure that is off by a day. Record the zone and the conversion. The report should state the assumption when the series crosses zones.

Analysis and reporting

Report the held rate and the notice pattern by direct report, by day of week, and by initiator rather than as a single executive-wide average. An average can look acceptable while one pair has not met for two months. Record each cut and the number of occurrences behind it. The report should show the counts so a reader can judge the reliability and avoid naming individuals unnecessarily.

Separate the moves caused by genuine emergencies from the moves caused by routine overbooking. The first is unavoidable, while the second is a capacity problem the office can plan around. Record the cause code and the evidence. The report should recommend a different action for each pattern.

Compare the reschedule pattern with the executive's stated priorities and the direct reports' own calendars. A one-on-one that is always moved for the same recurring meeting reveals a conflict that should be resolved at the source. Record the conflict and the owner. The report should present the pattern as a scheduling decision rather than as a performance judgment.

Recommend a protected slot, a minimum notice rule, and a monthly review of skipped meetings rather than a general instruction to reschedule less. A vague instruction is not enforceable and does not change the underlying conflict. Record the recommendation and the owner. The report should say what will be measured at the next review.

Limits and next action

The study cannot prove that reschedules affect a direct report's performance or engagement, and it cannot capture the conversations that happened outside the calendar. It also cannot see the meetings that were never scheduled because the pair was already overloaded. The report should state those limits and avoid treating a high held rate as proof of good management. The report should avoid linking the pattern to individual performance.

Set a repeat measurement date and keep the definitions of a reschedule, a skip, and notice stable. Assign the protected slot to the executive assistant and the minimum notice rule to the chief of staff. The next quarter should test whether the same pair or the same recurring conflict accounts for most of the moves. A useful result is a meeting that is either held or deliberately replaced, not one that quietly disappears.

Sources

  1. Secretaries and Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Outlook Handbook.
  2. Executive Secretaries and Executive Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics.
  3. Executive Secretaries and Executive Administrative Assistants, O*NET OnLine.
  4. Business Formation Statistics, U.S. Census Bureau.
  5. Nonfarm Business Sector: Labor Productivity, Federal Reserve Economic Data.
  6. Productivity Statistics, OECD Data Explorer.
  7. World Development Indicators, World Bank DataBank.
  8. ILOSTAT Labour Statistics, International Labour Organization.
  9. 2024 Work Trend Index Annual Report, Microsoft and LinkedIn.
  10. The economic potential of generative AI, McKinsey Global Institute.
  11. Creating helpful, reliable, people first content, Google Search Central.
  12. Search Engine Optimization Starter Guide, Google Search Central.
  13. Dear Manager, You Are Holding Too Many Meetings, Harvard Business Review.
  14. BLS, Secretaries and Administrative Assistants.
  15. Project Management Institute, PMBOK Guide.
  16. ISO 9001, Quality Management.

Apply the research

Use the finding to frame one question for your own team: which support work is currently invisible, and who should own the next step? A scoped consultation can turn that question into a practical role. Write the question down before the meeting. Name the person who owns the next step.

Turn the finding into a support scope.

Bring the workflow that feels hardest to see. We will help define the role, the evidence it should maintain, and the decisions that stay with leadership.

Talk through the role