Use it when you are

  • A Sunday evening or Monday morning review when the list is longer than the week
  • Replanning midweek after an urgent request has displaced everything else
  • Deciding what to push back on before agreeing to new work
  • Balancing client work, admin and one longer-term project as a freelancer

Why this prompt works

Arithmetic before ambition

Most weekly plans fail on Monday because the list contains more hours than the week does. Step 3 makes the model total the estimates, subtract a buffer and state the shortfall in plain numbers. Seeing that gap is what makes the cutting in step 4 feel necessary.

Four exits for every task

A list with only 'do' and 'later' lets everything drift into later. Defer with a date, delegate with a handover, and drop are distinct choices, and requiring one of them for each task means nothing stays on the list by default.

Estimates are labeled

The model cannot know how long your work takes. Marking each estimate as yours or a guess shows where the plan rests on soft ground, and after a couple of weeks of correcting the guesses you will have better numbers to feed in.

Limits on the day, not only the week

A plan that fits the week can still stack three heavy tasks on Tuesday. Capping demanding work at two items a day, placing it in your stated focus time and batching small admin tasks reflects how attention is actually spent.

How to use it

  1. Paste your whole task list without tidying it. Include the things you are avoiding.
  2. List fixed commitments with days and times, and any deadline that falls this week.
  3. Enter the hours you truly have, not the hours you wish you had.
  4. Read the capacity summary first. If the shortfall is large, review the Defer and Drop groups and overrule the model where you disagree.
  5. Correct any (guess) estimates that look wrong and ask for the schedule to be rebuilt.
  6. Copy the daily blocks into your calendar, and rerun the prompt midweek if the plan breaks.

AI model compatibility

ModelStatusNotes
ChatGPTExpected to workIf you replan during the week, continue in the same conversation and say what was completed and what changed, so the earlier estimates carry over.
ClaudeExpected to workNo model-specific adjustment needed. Paste the prompt as written.
GeminiExpected to workKeep the six numbered steps in order. Google's prompting guidance favors explicit sequencing, and the capacity check has to come before the schedule.

“Expected to work” means the prompt uses plain, model-independent structure and has been reviewed for that — not that it has been run on that model. A model is marked Tested only when a test record is published below.

Worked example

Scenario: A freelance consultant facing a proposal deadline in a week with a full-day workshop. Details are invented for illustration.

Example: filled-in prompt
# Role
You are a pragmatic planning partner. You assume the week will contain interruptions, and you would rather give me a plan I finish than one that looks impressive on Monday.

# My week
- Everything on my list:
Finish Harlow proposal (about 6h left), invoice March work, prepare workshop slides (3h), reply to supplier about new rates, book dentist, update portfolio page, read the two industry reports I saved, website
- Fixed commitments (meetings, appointments, deadlines with dates):
Mon 10:00-11:00 client call; Wed all-day workshop delivery; Fri 12:00 Harlow proposal deadline
- What matters most right now: Winning the Harlow proposal; getting invoices out on time
- Hours I can realistically work this week, outside fixed commitments: 24 hours outside fixed commitments
- When I do my best focused work: Mid-morning

# Work through this in order

1. Clarify the list. Rewrite any vague item as a concrete next action ('Website' becomes 'Draft homepage copy'). If you cannot tell what an item means, keep my wording and flag it.

2. Estimate. Give each task a time estimate in hours. Mark it (mine) if I supplied it and (guess) if you did. For anything over three hours, name the first piece that fits in one sitting.

3. Capacity check. Add up the estimates. Reserve 20 percent of my available hours as buffer. State plainly: total estimated hours, hours available after buffer, and the difference.

4. Choose. Select up to three outcomes that would make the week a success, judged against what matters most. Then sort every task into:
   - Do this week
   - Defer (say to when)
   - Delegate or ask for help (say what to hand over)
   - Drop
   The 'Do this week' group must fit inside the hours after buffer. If it does not, keep cutting and show what you cut.

5. Schedule. Place the 'Do this week' tasks across the days around my fixed commitments. Put the most demanding work in my best focus time. Put no more than two demanding tasks on one day, and group small administrative tasks into one block.

6. Risks. Name the task most likely to overrun and what I should drop first if it does.

# Rules
- Do not add tasks, habits or goals I did not mention.
- Do not move or shorten fixed commitments.
- Deadlines that fall this week outrank priorities; if the two conflict, tell me.
- No motivational commentary and no general productivity advice.

# Output format
A three-line capacity summary. The three outcomes. A table for the four-way sort (task | estimate | group | note). The schedule as a list by day with rough time blocks. The risk note last.

What a good response should contain

  • 'Website' flagged as too vague to estimate, kept in the original wording
  • A capacity summary showing estimated hours against roughly 19 hours after the 20 percent buffer
  • Three outcomes that include the submitted proposal, delivered workshop and sent invoices
  • The industry reports and portfolio update placed under Defer or Drop, with a reason
  • Workshop slides scheduled before Wednesday and proposal work in mid-morning blocks, finishing ahead of Friday noon

This is an illustrative scenario showing how to fill in the prompt and what to look for. It is not a recorded model output. Recorded outputs will be published here once this prompt has a test record.

Testing and editorial review

Status: Untested. Reviewed for structure and clarity by the editorial team. No recorded model test yet.

No test record has been published for this prompt yet. When it is tested, this section will show the model and version, the date, the inputs, the actual output and notes against our seven-point rubric. We do not publish numerical scores.

Editorial record
AuthorTheBestPromptFor Editorial Team — The editorial team writes, reviews and maintains the prompts and guides on TheBestPromptFor. Prompts are drafted with AI assistance and reviewed against published editorial standards.
PublishedNovember 15, 2026
Last reviewedNovember 15, 2026
Last testedNot yet tested
Version history
  • v1.0 — November 15, 2026 · Initial version

Limitations and things to check

  • Time estimates marked (guess) are rough. Only you know how long your work takes.
  • The model cannot see your calendar, inbox or colleagues' availability unless you paste the details in.
  • It can recommend deferring or delegating, but whether that is acceptable to a client or manager is your call.
  • A plan does not survive every week intact. Treat it as a default to return to, and replan when something big changes.

Alternative prompts

All Productivity prompts →

Frequently asked questions

Why does the plan keep 20 percent of my time unscheduled?

Because unplanned work arrives every week, and a plan with no slack breaks at the first interruption. The buffer is a starting point, not a rule. If your weeks are heavily reactive, edit the figure in the prompt upward; if they are predictable, lower it.

What if I disagree with what the model wants to drop?

Overrule it. Say which task must stay and ask it to rebalance, which means something else has to leave the 'Do this week' group. The value of the exercise is that the trade-off is made explicit instead of being discovered on Friday.

Can I use this for a team instead of one person?

It is designed for one person's week. For a team you need per-person capacity and dependencies between tasks, which this prompt does not model. You can run it per person, or use the OKR prompt for the team's goals for the quarter.

Sources and references

  1. Prompt design strategies — Google AI for Developers
  2. Prompt engineering guide — OpenAI

Was this prompt useful?

No account needed. Do not include personal information.