Count the work around the meeting
A 30-minute meeting may also need ten minutes of preparation and fifteen minutes to capture decisions afterward. Those activities need space even though the invitation does not show them.
Review the purpose of each meeting. Write down what you need to bring and what you expect to leave with: a decision, feedback, a handoff, or a clearer question. Then reserve the necessary preparation and follow-through.
Do the same for travel and equipment setup. A call that starts at 2 is not compatible with a task that ends at 2 if you need to move rooms or collect materials first.
Match the task to the opening
A 20-minute gap can be useful for a short review, sending a prepared reply, or clarifying tomorrow’s next action. It may be a poor fit for writing a complex first draft that needs uninterrupted thought.
Choose a task with an achievable checkpoint. “Read the feedback and list the requested changes” can fit where “finish the redesign” cannot.
If the day contains only short gaps, acknowledge that limit. You can still make progress, but the plan should not imply that a long task has been handled merely because you distributed its title across several tiny blocks.
A worked example with three meetings
Suppose you work 9–5, with meetings at 10–10:30, 12–1, and 3–3:30. Your main outcome is a reviewed proposal outline. One possible plan is:
- 9–9:45: draft the outline.
- 9:45–10: prepare for the first meeting.
- 10–10:30: meeting.
- 10:30–10:45: capture decisions and take a break.
- 10:45–11:30: revise the outline.
- 11:30–12: messages and preparation for the next meeting.
- 12–1: meeting.
- 1–2: lunch.
- 2–2:45: review and share the outline.
- 2:45–3: prepare for the last meeting.
- 3–3:30: meeting.
- 3:30–4: follow-through and a break.
- 4–4:30: overflow or a small supporting task.
- 4:30–5: close loose ends and prepare tomorrow’s starting point.
This example protects one outcome and leaves room around conversations. It does not promise the output of a meeting-free day.
Replan from the current time when a meeting moves
If a call runs over, update what remains rather than trying to recover every missed block. Ask whether the main outcome still fits. You may need to reduce its scope from a polished document to an outline ready for discussion.
Check dependencies before moving work. Preparation must remain before the meeting; follow-through should not be scheduled before you know what was decided.
In Calendo, view your connected calendar alongside tasks and their start times. Calendar subscriptions are read-only, so changes to those source events belong in the original calendar. Use the visible commitments to choose realistic task placements.
A prompt for reviewing a crowded calendar
Use this with your connected AI assistant:
My workday is [hours], with these meetings: [times and purpose]. Preparation and follow-through need [estimates]. My main outcome is [result], requiring [estimated work]. Identify the usable openings and suggest tasks that fit them. Preserve lunch, breaks, and my stopping time. Tell me if the main outcome needs a smaller scope or a different day.
Review the result yourself before applying it. For more templates, see AI prompts for daily planning. If a task is too large for the available opening, use timeboxing to define a smaller checkpoint.
These guides use illustrative examples. AI helped draft the content; product descriptions are grounded in Calendo’s current features. No example is a promise of a particular result.
How we write these guides