Preparing a Chief of Staff Weekly Agenda from Open Decisions

Start from the decision log, not the inbox

A weekly agenda should begin with the decisions that are still open, not with the messages that arrived since Friday. Open the decision log and list every item that needs a choice, an owner, or a review. Then check the inbox for new information that changes one of those items. The agenda follows the work, not the noise. A visible draft also gives owners time to prepare the right evidence.

Group the items by the decision the team needs to make, not by the person who sent the last email. Two messages about the same hiring delay belong in one agenda item. A clear decision title helps the team prepare and prevents the meeting from becoming a status update. The title should say which choice is needed, not which topic will be discussed.

Leave out items that are already decided and have no open action. If an item is included only for awareness, mark it as a note and put it at the end. The meeting should spend its time on choices that need the group. A shorter agenda with real decisions is more useful than a complete list. A notes-only section can be read quickly and does not consume decision time.

Group items by the decision owner

For each item, name the person who will present the choice and the person who will decide. Those may be different. A finance lead may present a budget trade-off, while the CEO decides. Write both names beside the item so the meeting does not drift into a general discussion. If the presenter and the decider are the same, say so to avoid a second handoff.

Order the agenda by the owner's availability and the decision's deadline. Put the items that need the CEO first if the CEO can attend only part of the meeting. Group related decisions so the team can use the same context. Do not sequence items by the order they arrived in the inbox. A predictable order also helps participants know when their item will be heard.

Send the owner a short request for the pre-read, the options, and the recommendation. If the owner cannot provide a recommendation, record that the item is not ready. A meeting should not be used to discover that no one prepared the decision. The agenda can hold the item for the next cycle. The request should name the decision and the date the pre-read is due.

Leave room for urgent items without losing the queue

Reserve a short block for urgent items that arrived after the agenda was sent. Keep the block at the end so it does not crowd out the prepared decisions. If an urgent item needs more time, move a lower-priority item to the next meeting rather than extending the agenda indefinitely. Record the move. The note should say which item was moved and who approved the change.

Define what counts as urgent: a legal deadline, a safety issue, a customer commitment, or a decision that blocks another team. A request that is merely new is not automatically urgent. The definition helps the chief of staff protect the agenda without ignoring a real problem. Write the definition in the agenda template so the team applies it consistently. A shared definition reduces debates about priority.

If the urgent block is used every week, review the intake process. The team may be bringing decisions late because the agenda is not visible early enough. A simple change, such as publishing the draft agenda two days earlier, can reduce the number of surprises. Check whether the late items share an owner or a decision type. That pattern is easier to fix than a general reminder.

Send the pre-read with a clear ask

Send the agenda and the pre-read together, with a one-line ask for each item. The ask should say what the team needs to decide and what input the owner needs. Do not send a folder of documents without a recommendation. The pre-read should let a participant prepare in ten minutes. The pre-read should include the decision, not just the background.

Put the decision, the options, and the recommendation at the top of each item. Put the background below. If the team needs a specific person's input, name that person and the question. A clear ask reduces the chance that the meeting spends its first ten minutes reconstructing the issue. A reader should see the recommendation before the appendix and the decision date.

Ask participants to send corrections before the meeting, not during it. If a number changes, update the pre-read and mark the change. The meeting should start from a shared version. A pre-read that is revised silently creates the same problem as an unlabeled board packet. A silent revision should trigger a new version label, just like a board packet, and a note to the team.

Review whether the agenda changed the decisions

At the end of the meeting, record which decisions were made, which were deferred, and which were removed. Compare that list with the agenda. If an item stayed open without a new owner or date, the meeting did not finish the work. The gap is a signal for the next agenda. The comparison should be quick enough to complete before the next agenda is drafted.

Ask the owners whether the pre-read was sufficient. A repeated complaint about missing context points to a template problem, not a preparation problem. A repeated complaint about late materials points to the agenda timeline. Use the feedback to change one step. The feedback should be specific enough to change one field or one deadline next week or the week after.

Review the agenda over four weeks for items that never reach a decision. Some items may be too broad or may lack an accountable owner. Split them or remove them. A weekly agenda improves when it is measured by decisions closed, not by topics covered. A four-week view shows whether the agenda is improving or just getting longer over time.

Related resources

• Building a Decision Log the Executive Team Actually Reuses
• Measuring agenda preparation against open decision ownership
• Measuring decision log reuse across executive team meetings

Frequently asked questions