Business Ops & Client Comms

Verified against ChatGPT · 2026-08-10

Build a weekly time-blocking plan around your actual meeting load, not an idealized week

Generates a realistic weekly time-block schedule that works around your fixed meetings and real energy patterns instead of assuming an empty calendar.

ChatGPT (GPT-5.1)5 fillable variables

The prompt

Ready to copy — highlighted parts are example details you can swap.

Build me a weekly time-blocking schedule that works around my actual week, not a fantasy version of it.

FIXED COMMITMENTS THIS WEEK
Daily 9:30-10am standup, Tuesday 2-4pm client review, Thursday 11am-12:30pm all-hands.

TOP PRIORITY THIS WEEK
Finishing the Q3 budget model before Friday's finance sync.

DEEP WORK HOURS I ACTUALLY NEED
About 8 hours total across the week, ideally in blocks of 90 minutes or more.

MY ENERGY PATTERN
Sharpest 8-11am, a hard crash after lunch until about 3pm, second wind late afternoon.

RECURRING TIME WASTERS
Checking Slack constantly between tasks, and unplanned 'quick calls' that run 30+ minutes.

Start from the fixed commitments as immovable and build everything else around the gaps they leave — do not propose a schedule that assumes any of them can move, and if the gaps left are genuinely too fragmented to fit the stated deep work hours, say so directly instead of squeezing an unrealistic block in anyway. Place deep work in the windows that match my stated energy pattern where a gap of the right size actually exists; if my highest-energy window is already occupied by fixed commitments, say that plainly rather than defaulting to the textbook advice of 'do deep work in the morning' regardless of what I told you. Give the top priority the first usable deep-work block of the week, not the last one — a priority scheduled for Friday afternoon after everything else has taken the good slots isn't actually prioritized. For each recurring time-waster listed, either block a fixed, minimal window for it (so it stops bleeding into everything else) or flag it as something to actually eliminate this week rather than schedule — decide which based on whether it sounds like a necessary recurring task or a habit.

Do not produce a generic Monday-through-Friday grid with identical daily structure — a real week has different shapes on different days because of the fixed commitments, and the schedule should visibly reflect that. Do not schedule back-to-back deep work blocks longer than what's realistic for sustained focus without at least a short buffer between them.

OUTPUT FORMAT
A day-by-day table (Mon-Fri) with time blocks labeled by type — Fixed / Deep Work / Time-Waster Containment / Buffer — followed by one line flagging any day where the top priority didn't get a real slot, and why.

Customize

Optional — swap in your own details for the highlighted parts above.

Why this works

Generic time-blocking templates fail in practice because they're built around an idealized week with no meetings, so the first real fixed commitment collides with the plan and the whole thing gets abandoned by Tuesday — anchoring the model to the actual fixed commitments as immovable, and instructing it to say plainly when the remaining gaps can't fit the requested deep work hours, forces an honest schedule instead of an aspirational one that looks good but doesn't survive contact with the real calendar. GPT-5.1's default advice on deep work timing leans heavily on generic 'mornings are best for focus' guidance from its training distribution; explicitly requiring the schedule to match the stated energy pattern, and to flag it directly when the high-energy window is already occupied by a fixed meeting, prevents the model from overriding your actual reported energy data with textbook productivity advice that doesn't apply to your week. Placing the top priority in the first usable slot rather than wherever fits addresses a subtle scheduling bias: without an explicit instruction, priority-ranking naturally gets treated as informational rather than structural, and the stated priority ends up in the least protected slot simply because it was mentioned last in the reasoning. Forcing a decision between 'contain' and 'eliminate' for each named time-waster is what separates a time-blocking plan from a wish list — scheduling around a bad habit without addressing it just reproduces the same lost time inside a nicer-looking grid.

What you get back

Monday: 8-9:30am Deep Work (budget model — top priority gets the first slot), 9:30-10am Fixed (standup), 10-10:15am Buffer, 10:15-11am Time-Waster Containment (batch Slack replies)... Flag: Wednesday's only open deep-work window is 1-2:30pm, which falls in your stated post-lunch energy crash — consider swapping a lower-focus task into that slot instead.

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
All Business Ops & Client Comms prompts

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY