Designing a Decision Calendar for a Busy Executive
Published August 14, 2026
Placing decisions and preparation ahead of deadlines is a small operating decision with an outsized effect on an executive's day. The goal is not to create another document that feels complete for a week and then disappears. The goal is to make the next useful action visible, give the assistant a clear boundary, and make it easy for the executive to correct the routine when circumstances change.
Start with the outcome
Write the desired outcome before writing a checklist. For this routine, the outcome is a reliable view of what deserves attention, what can wait, and what requires a decision. That sentence gives the assistant a test for relevance. If a proposed step does not improve the view or move an open loop, it probably belongs outside the routine.
The outcome should name a time horizon. A morning routine looks at today and the next few fixed commitments. A quarterly routine looks at priorities, dependencies, and capacity. A handoff note looks at the next owner and the next moment when an update is needed. Mixing all three horizons makes the record hard to use.
Gather only the right inputs
Begin with the systems that are authoritative for the work. Check the current calendar, the approved task record, the latest source document, and the last decision note. Treat chat messages and memory as prompts to verify, not as the final record. This simple distinction prevents a stale message from quietly becoming a commitment.
Create a short input list for the first pass: fixed commitments, deadlines, people waiting for an answer, unresolved decisions, and changes since the last review. Add the source link beside each item. A link is more useful than a copied paragraph because it lets the next reader inspect the current version without maintaining two competing records.
The Google Calendar Help guidance is a useful reference for the underlying practice. It does not prescribe an executive's exact routine, but it supports the discipline of keeping the source, owner, and next action clear. The McKinsey Decision Making guidance offers a second perspective on executive decision calendar, especially where context or access can change.
Run a decision-oriented first pass
Sort each item into four buckets: act, prepare, wait, or escalate. Act means the assistant has both the information and authority to move it. Prepare means a recommendation or draft is useful, but someone else must approve the result. Wait means an outside input is missing and the item needs a named follow-up date. Escalate means the rule does not cover the consequence, sensitivity, or urgency.
Do not let the first pass become a deep research session. Capture the question, the missing fact, and the person who can answer it. If the item is important enough to require more work, give that work a separate owner and due time. This preserves the rhythm of the routine while still protecting the issue from being forgotten.
Make context scannable
Every line in the working record should answer four questions: what is happening, why it matters, what happens next, and when the next update is due. Use concrete verbs. “Confirm attendees by Thursday” is stronger than “follow up on meeting.” “Draft two options for review” is stronger than “work on recommendation.”
Keep the executive view short. Put detail in the source material and use a link or reference to reach it. A useful brief can include a one-sentence recommendation, two supporting facts, one risk, and the decision deadline. If the executive needs the full history, it should be available without making the summary carry every detail.
Define authority and escalation
The assistant can organize information, prepare a draft, propose a sequence, and carry out an approved action. The assistant should pause when the work creates a new obligation, changes a sensitive relationship, exposes confidential information, or commits another person without clear authority. Those are not failures of initiative; they are the points where judgment needs an explicit owner.
Write the escalation rule into the routine. State who decides, what evidence to include, and how quickly the question needs an answer. A good escalation is easy to respond to: “Should we keep the Thursday meeting, move it to next week, or ask for a written update? The conflict affects the launch review, and an answer is needed by noon.”
Close the loop
At the end of the review, every item should have a status and a next action. Use a small vocabulary such as active, waiting, scheduled, delegated, approved, or closed. Add the owner and date when either one is known. Avoid a vague “in progress” label that hides whether someone is actually moving the work.
Review carried items with curiosity rather than blame. A task that repeats may need a clearer owner, a missing decision, a better reminder, or permission to stop. The point of the review is to improve the operating rule and protect attention, not to produce a longer list.
A practical checklist
- State the outcome and time horizon.
- Verify the current calendar, task record, and source documents.
- Sort items into act, prepare, wait, or escalate.
- Write the next action, owner, and update time.
- Keep sensitive details in the approved source system.
- Close completed items and review anything carried forward.
Common mistakes to avoid
The first mistake is recording activity instead of decisions. A list of calls made and messages sent does not tell an executive what changed. The second is treating every request as equally urgent. Priority should reflect consequence, timing, and dependency, not message volume. The third is allowing an exception to remain personal knowledge. If the same exception appears twice, turn it into a written rule or deliberately name it as an executive preference.
Another mistake is making the record too polished to maintain. A routine that requires an hour of formatting will be skipped when the day is busy. Favor plain headings, short sentences, stable labels, and links to the source. The durable record is the one someone can update accurately during a real week.
FAQ
How often should this routine run?
Use the shortest cadence that catches the risk. A daily review fits changing commitments; a weekly review fits priorities and recurring work; a monthly review fits patterns and stale items. Increase the cadence temporarily when the executive is traveling, hiring, launching, or handling a sensitive transition.
What should the executive receive?
Send the smallest useful view: decisions needed, deadlines at risk, meaningful changes, and items that are ready to move. Keep supporting context linked rather than pasted into the message. The executive should be able to respond quickly and still find the evidence behind the recommendation.
When should an assistant escalate?
Escalate when authority is unclear, the consequence is material, confidential information may be exposed, a relationship could be changed, or waiting would create a meaningful risk. Include what you know, what you recommend, and the time by which a decision matters.
How do we know the routine works?
Look for fewer repeated questions, fewer missed handoffs, and faster decisions with less re-reading. Ask which items were carried forward and why. The answers show whether the routine needs a clearer rule, a better source, or a different cadence.