Question and scope
This review asks what a calendar can reveal about who owns a meeting and whether that ownership is real. The unit is one recurring or one-off meeting that appears on an assistant's calendar. The scope covers the invitation, the attendee list, the agenda, the preparation time, and the follow-up note. The review measures ownership signals, not meeting quality in general.
A meeting can have a named organizer and no decision owner. The organizer sends the invitation, while the decision owner is the person who can change the outcome or approve the next step. The review records both roles because a calendar often shows only the first. A meeting without a decision owner tends to produce updates rather than outcomes.
The review also separates a meeting the assistant attends from one the assistant prepares or schedules. Each role consumes different time and creates different access needs. A calendar that treats all three as attendance will hide the preparation work. The review records the role beside every event.
The evidence standard should state whether the review covers one assistant, one client, or a team. A team calendar may show a meeting that one person owns and another attends as backup. The unit should follow the decision rather than the invitation list. A pooled count across roles can make ownership look clearer than it is.
Definitions and unit
A meeting owner is the person accountable for the agenda, the decision, and the follow-up. A meeting organizer is the person who created the invitation and manages the logistics. A facilitator is the person who runs the discussion but may not own the outcome. The review codes these roles separately and records the evidence for each.
A decision is a choice that changes a commitment, a resource, or a next action. A status update is information that does not require a choice. The review codes the meeting output as a decision, an update, or unclear. A recurring meeting that only produces updates may not need the same cadence or the same attendees.
The unit is one event on one calendar. A recurring series counts as one event, but each occurrence can be sampled for output. The review records the series owner and the occurrence output because a series can drift after the original owner leaves. The distinction prevents the calendar from looking healthy because the invitation still exists.
Evidence collection
Export the calendar events for a four-week window, including the organizer, attendees, recurrence, and description. Pair the export with the agenda and the follow-up note for a sample of meetings. Where no agenda or note exists, record the absence rather than inferring the content. The evidence should let a second reviewer see the same ownership signals.
Read the invitation description for a stated purpose and a required output. A description that only repeats the meeting title is a weak ownership signal. Check whether the invitation names a decision or a preparer. A meeting with a clear purpose is easier to review than one that exists because it always has.
Ask the assistant which meetings they prepare for and which they only attend. Their answer may reveal hidden work that the calendar does not show. Add the preparation and follow-up time to the event record. A meeting that takes thirty minutes but requires two hours of preparation is not a thirty-minute commitment.
Patterns to measure
Measure the share of meetings with a named decision owner, a stated output, and a follow-up note. Keep the three measures separate because they fail in different ways. A meeting can have an owner and no note, or a note and no decision. The pattern shows where the calendar is only a scheduling record.
Measure the number of recurring meetings that have not changed their attendee list or agenda in several months. A stale series is a candidate for a shorter cadence or a written update. Compare the series with the decisions it produced in the sample. A series that produces no decision is a cost without a clear return.
Measure the preparation and follow-up time as a share of the meeting time. A meeting that requires more preparation than the meeting itself may be worth keeping, but the calendar should show the work. An assistant who is booked back-to-back has no room to prepare or to write the note. The calendar should reflect the real cost of the meeting.
Comparing ownership models
Compare a model where the assistant owns the logistics with one where the assistant also owns the follow-up note. The first keeps the calendar accurate, while the second creates a record of decisions and actions. Hold the meeting type constant as the data allow. A note-owning model may reduce repeated questions, but it also adds work.
Compare a model with a named backup against one where the organizer is the only contact. A backup can keep the meeting useful when the owner is away, but the backup needs the context and the authority to act. The review should record whether the backup attended or only received the invitation. An invitation without context is not a backup plan.
Record the cost of a meeting that lacks an owner. The cost may appear as a repeated question, a missed action, or a second meeting to decide what the first meeting did not. A comparison that only counts attendance misses the rework. The ownership model should be judged by the decisions it produces.
Limits and confounders
A calendar is a plan, not a record of what happened. A meeting may have produced a decision in a chat after the event, and the note may live somewhere else. The review should pair the calendar with the actual follow-up record. A missing note is a documentation gap, not proof that no decision occurred.
The sample may be too small to represent a quarter or a busy season. A calendar reviewed during a quiet month may look cleaner than the same calendar during a launch. Record the period and the volume beside the result. Do not publish a rate that the sample cannot support.
The reviewer may know the team and fill in an owner from memory. That knowledge is useful for explanation but dangerous for measurement. Require a written name or a recorded decision before coding a meeting as owned. The stricter rule keeps the finding reproducible by someone outside the team.
Reporting the finding
Report the share of meetings with a decision owner, a stated output, and a follow-up note. Show two anonymized examples that illustrate the difference between a well-owned meeting and a meeting that only exists. Recommend one calendar change, such as a required output field or a shorter cadence. Name the owner and the next review date.
Separate a meeting that lacks an owner from a meeting whose owner is on leave. The first needs a structural fix, while the second needs a backup. A report that merges them will recommend a new process for a temporary absence. The distinction keeps the remedy proportionate.
Recheck the calendar after one cycle and compare the same measures. If the number of meetings falls but the decisions do not, the change may have removed the wrong events. If the notes improve but attendance grows, the meeting may need a clearer purpose. The finding is complete when the calendar and the decision record agree.
Practical checklist
List the recurring meetings and name the decision owner for each one. Mark the meetings that only produce updates. Check whether the invitation states a purpose and an output. Add preparation and follow-up time to the calendar.
Test one shorter cadence or one written update in place of a meeting. Compare the decisions and the questions that follow. Keep the change if the output holds and the cost falls. Restore the meeting if a decision disappears.
Review the calendar again in a month and read the follow-up notes. Ask the assistant which meeting felt unnecessary and which one needed more preparation. Fix one item before adding another rule. The calendar should show the work that matters, not every hour that can be booked.
Sources
Open the original publisher and confirm the current version, definition, and scope before using a source for a business decision.
Turn the reading into a role brief
Bring the recurring tasks, tools, schedule, access limits, and owner-only decisions. Start with one work sample and one clear review path.
Plan a Philippines-based role
