Meeting operations

Building a Standing Agenda for the Executive's Weekly Chief of Staff Sync

A standing agenda for the weekly chief of staff sync, covering the purpose, the attendee list, the exception items, and the decision record.

4 min readHireExecutiveTeam editorial
Building a Standing Agenda for the Executive's Weekly Chief of Staff Sync article illustration
Table of contents
  1. Fix the purpose and the attendees before the first meeting
  2. Build a standing agenda that changes by exception
  3. Keep a decision and follow-up record in the same place
  4. Review the cadence every quarter
  5. Related resources
  6. Frequently asked questions

Fix the purpose and the attendees before the first meeting

Write one sentence that states what the weekly sync exists to decide, and test every agenda item against it. A meeting that tries to cover status, triage, and relationship building at once produces a long discussion with no clear output. Record the purpose in the meeting invitation. The purpose should be narrow enough that a new attendee understands it in a single reading.

Limit the standing attendee list to the people who can commit work or change a priority. A weekly sync that includes every project contributor becomes a reporting forum rather than a decision forum. Record the role of each attendee and the reason they are there. Optional attendees should receive the notes rather than a calendar invitation.

Agree who chairs the meeting and who owns the agenda, and keep those two roles explicit. A sync chaired by whoever speaks first drifts toward the loudest topic rather than the most important one. Record the chair and the agenda owner in the meeting notes. The chair should be able to end an item when the decision is clear.

Set the default length and the hard stop, and protect the executive's next commitment. A meeting that regularly overruns teaches attendees that the stated end time is not real. Record the start, the end, and the buffer before the next meeting. The chair should close the meeting at the stated time even when an item is unresolved.

Build a standing agenda that changes by exception

Keep a fixed order of sections so attendees can prepare for the same sequence each week. A different agenda every week forces the executive to relearn the meeting and makes omissions harder to spot. Record the order in a template and reuse it. Changes to the order should be proposed between meetings rather than during one.

Reserve the first section for decisions that are due that week and the second for risks that could change a decision. A sync that begins with status updates spends its best attention on information that could have been read. Record the decision and the risk in the agenda before the meeting. The status items should be written and circulated in advance.

Put a time box on each item and mark whether it is for decision, discussion, or information. An item without a label expands to fill the time available and often ends without a clear outcome. Record the label and the owner beside each item. The chair should move an information item to the notes when the meeting is running late.

Leave one short section for items raised on the day and cap the number that can be added. A sync with no room for the unexpected forces urgent issues into side conversations, but an unlimited open section lets any topic displace the agenda. Record the added items and who raised them. Items that recur should be promoted into the standing agenda rather than added each week.

Keep a decision and follow-up record in the same place

Record each decision in one line with the owner, the date, and the next checkpoint. A decision that is discussed but not written down is reopened the following week by someone who remembers it differently. Record the decision in the shared notes before the meeting ends. The note should state what was decided, not only what was discussed.

Capture follow-ups with a single accountable owner rather than a team name. A follow-up assigned to a function is a follow-up that no individual feels responsible for completing. Record the owner, the action, and the due date. The owner should confirm the wording of the action during the meeting.

Review the previous week's follow-ups at the start of every sync and close or re-date each one. A follow-up list that is never reviewed becomes a record of intentions rather than a working tool. Record the status and the new date for anything that slipped. The review should take less than five minutes when the list is current.

Keep the notes in the same system as the executive's decision log so the sync does not create a parallel record. Two logs with different wording force the assistant to reconcile them before an audit or a handover. Record the link between the sync notes and the decision log. The sync should add to the existing record rather than replace it.

Review the cadence every quarter

Ask each standing attendee whether the sync helped them make or change a decision in the last quarter. A meeting that everyone attends but no one uses for decisions has become a habit rather than a tool. Record the answers and the date of the review. The review should be short and should not become another meeting about meetings.

Check whether the same topics keep appearing without a decision and move them to a different forum. A recurring topic that never closes may belong in a project review or a one-to-one rather than the weekly sync. Record the topic and the forum it moved to. The agenda should shrink when a topic finds a better home.

Compare the meeting length with the number of decisions recorded and adjust the format rather than adding time. A meeting that needs more time often needs fewer information items, not a longer slot. Record the decision count and the actual duration. The chair should propose the change at the quarterly review.

Update the purpose statement and the attendee list when the executive's priorities change, and reissue the invitation. A sync designed for last year's operating model quietly becomes irrelevant after a reorganization. Record the new purpose and the date it takes effect. The change should be communicated before the next meeting rather than discovered at it.

Read also: decision log the team reuses and one-on-one reschedule measurement.

Frequently asked questions

Should one assistant support the whole executive team?

Sometimes. It works when priorities are clear and executives share one operating rhythm.

What should happen before a consult?

List the meetings, inbox rules, recurring reports, and decisions that need support.

Ready to define the role?

Use a recent leadership week to scope the support that would make the biggest difference. The consultation is a working conversation, not a generic pitch.

Book a consultation