Verified against ChatGPT · 2026-08-10
Build a weekly plan that leaves real buffer instead of scheduling every hour back to back
Turns a week's worth of commitments and goals into a day-by-day plan that deliberately reserves slack for the inevitable fire drill, instead of optimistically packing every hour.
The prompt
Ready to copy — highlighted parts are example details you can swap.
You are building my plan for the upcoming week. My past plans have all failed the same way: they schedule every available hour back to back, so the first unplanned interruption — which always happens — blows up the entire week and I end up behind on everything by Wednesday. GOALS FOR THE WEEK Ship the Q3 report draft, finish two vendor evaluations, clear the backlog of approval requests. FIXED COMMITMENTS (meetings, recurring blocks) Monday and Thursday leadership syncs (1 hr each), daily standup (15 min). TYPICAL INTERRUPTION LOAD Usually 1-2 hours a day of unplanned urgent requests, worse on Tuesdays. DAYS AVAILABLE Monday through Friday, with Friday afternoon reserved for a personal commitment. Build a day-by-day plan, but before assigning any actual work, reserve a buffer block on each day sized to my typical interruption pattern — do not schedule that buffer time with anything, and do not let it silently shrink because the goals list is long. Assign the weekly goals to specific days based on real dependencies (what has to happen before what) and natural deadline pressure within the week, not evenly spread for the sake of looking balanced. If the goals, once realistically time-estimated, don't fit into the days available after buffer and fixed commitments are subtracted, say so explicitly and tell me which goal should be cut or pushed to next week rather than compressing everyone's daily plan to a false density that ignores the interruption pattern I gave you. For each day, name the one thing that must happen that day even if everything else about the day goes wrong — this is the anchor task the day is built around, not just the first item on the list. At the end, note which single day has the least slack and is therefore most at risk if this week's typical interruption lands there. WHAT NOT TO DO Do not produce an hour-by-hour calendar grid — a day-level plan with named blocks is more honest about what's actually controllable a week out. Do not treat the buffer block as available capacity if the goals don't fit; the buffer stays protected even under pressure. OUTPUT FORMAT A day-by-day list (Monday through the available days): anchor task, other assigned work, buffer block (unscheduled). End with a one-line note on the most at-risk day and, if applicable, what to cut.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
A model asked to "plan my week" from a goals list and a calendar will, by default, produce the most visually complete-looking artifact it can — which in practice means filling every open hour, because an empty block reads as an unsolved part of the task rather than a deliberate feature; explicitly instructing it to reserve and protect a buffer block before assigning any work inverts that default, treating unscheduled time as a required output rather than leftover space to be filled. This matters specifically because GPT-5.1's tendency toward thoroughness works against realistic planning here — a longer, denser-looking plan reads as more helpful in isolation, even though a real week with zero slack is structurally guaranteed to fail on first contact with any interruption, which is precisely the failure the person asking for this prompt is trying to escape. The anchor-task framing for each day forces a genuinely different kind of prioritization than a simple task list: naming the one thing that survives even if the day goes sideways requires the model to reason about what's load-bearing versus what's merely scheduled, which produces a plan that degrades gracefully under real-world disruption instead of one where every item has equal, undifferentiated importance. Explicitly instructing the model to say the goals don't fit and to name what should be cut, rather than silently compressing the daily plan to make everything appear to fit, closes off the most common way these plans quietly become fiction — an assistant under implicit pressure to be maximally helpful will compress estimates until the math works on paper, and stating this rule up front removes the incentive to do that.
What you get back
Monday — Anchor: draft outline for Q3 report. Other: start vendor evaluation #1. Buffer: 1.5 hrs reserved, unscheduled. Tuesday — Anchor: clear approval backlog (highest interruption-risk day). Buffer: 2 hrs reserved. ... Most at-risk day: Tuesday, given your historically heavier interruption load and only one anchor task with no fallback if it slips.
Verified against
ChatGPT GPT-5.1 · 2026-08-10
Changelog
- 2026-08-10 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — custom software, built and maintained for you — that's Scult's day job.
EXPLORE CUSTOM SOFTWARE
