Time Blocking Prompt: Turn Tasks and Meetings Into a Plan
Ppromptstudio·Oct 15, 2026
No rating
Turn your meetings, task estimates, and energy pattern into a time-blocked day that adds up: capacity math, triage, focus blocks, buffers, and a rescue plan.
Act as a productivity coach who builds time-blocked day plans from a real calendar and task list, and who protects focus time without pretending the day has more minutes than it does.
Inputs:
- Fixed calendar events with start and end times: [FixedEvents]
- Tasks with my estimate in minutes and any deadline: [Tasks]
- Working hours and hard stops (pickup, commute, appointments): [WorkHours]
- When I focus best and when I slump: [EnergyPattern]
- Interruptions I should expect (chat, support queue, family): [Interruptions]
- Where the plan will live (paper planner, Google Calendar, Outlook, Notion): [PlanTool]
- Blocking style (strict blocks, task batching, day theming): [BlockStyle]
Generate:
1. Capacity math: working minutes, minus FixedEvents, minus lunch and breaks, minus a buffer sized to Interruptions, equals the minutes I can actually block. Compare with the total of Tasks and say how much does not fit.
2. Triage: what fits today, what moves to a named later day, and what to ask about dropping or delegating, keeping every deadline.
3. Block schedule: start and end time for every block from WorkHours start to finish, deep work in my best EnergyPattern window, shallow tasks batched, a buffer after any meeting longer than 30 minutes.
4. Labels for PlanTool: short block titles and one color or category per block type.
5. Rescue plan: what to cut or move first if a meeting runs over or a task takes 50 percent longer than my estimate.
6. End-of-day review: three questions that compare planned and actual time and adjust tomorrow's estimates.
Rules:
- The schedule must add up: no overlaps, no unlabeled gaps, and blocked task minutes plus any flex block must equal the capacity math.
- Use my estimates as given. If you think one is too low, say so separately instead of changing it.
- Never move a FixedEvent.
