#time blocking
2 prompts found

Time Blocking Prompt: Turn Tasks and Meetings Into a Plan
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.
Calendar Time-Block Planner for a Chaotic Week
Turn a chaotic week of meetings, travel, and tasks into realistic time blocks with buffers, travel, and protected deep work. No fantasy 5am schedule.
Act as a calendar surgeon. Fit work into the week that already exists. Do not delete immovable meetings. Do not invent 5am magic. Name what will slip. Inputs: - Time zone and work hours: [TZ, earliest start, latest stop] - Week: [Dates] - Immovable: [Meetings, school, travel, care] - Tasks that need time: [List with rough minutes] - Deep work I want: [Project names] - Energy pattern: [Mornings / afternoons / known bad days] - Constraints: [Commute, lunch, no-meeting blocks I already own] - Tools: [Google / Outlook / paper] - What I am willing to drop: [List] - Sleep and personal: [Non-negotiables] Generate: 1. Load check: Sum of task minutes + meeting hours vs available hours. A sentence on whether this week is already over. What slips first from What I am willing to drop. 2. Principles for this week only: 5 rules (buffer, travel, meal, shutdown, one deep-work window). 3. Day-by-day blocks: For each day, a table-like list: start-end, label, type (immovable / deep / admin / buffer / personal / travel). Include 10-15 min buffers after hard meetings. Put Deep work I want in Energy pattern hours if those hours are free. 4. Travel and logistics: Door-to-door, not just the meeting start. 5. Task-to-block map: Every task from Inputs either sits in a block or is explicitly deferred with a date. 6. Overflow: A parking lot with the first day it can live. 7. Calendar paste: A plain list I can type into Tools, one line per block: Day, start-end, title. 8. Failure modes: If a meeting overruns 30 min, what gets eaten. A Thursday 4pm re-plan rule. Constraints: - If hours do not fit, cut. Do not shrink lunch to 5 minutes. - No em dashes. No 4am workout unless Inputs asked. - Honor Sleep and personal as immovable. - Do not add tasks I did not list. - Write times in the user's time zone, 24h or am/pm consistently.