Turn a task list into a realistic weekly plan

Work through a ten-hour example with deadlines, dependencies and a visible buffer for interruptions.

A plan can look tidy and still be impossible. The common problem is counting every free-looking hour as focused work, then scheduling tasks before their inputs are ready. Start with capacity and dependencies; let the wording come later.

The example below is a fictional five-day workweek. It is a planning exercise, not a report of someone's measured productivity. Change the times to match your own commitments before using it.

Count the time you can actually use

Suppose you have two hours of project time each weekday after meetings and routine work. That is ten hours for the week. Keep 30 minutes of each day free for interruptions. Your scheduled task budget is therefore 90 minutes a day, or seven and a half hours for the week.

Do not subtract the buffer twice. The example starts with two usable hours, not an eight-hour working day. Meetings have already been accounted for.

Give the tasks deadlines and dependencies

A: Review the landing-page copy, 90 minutes, due Wednesday. No dependency.
B: Prepare three product descriptions, 120 minutes. The owner's notes arrive Tuesday afternoon; due Friday.
C: Test the contact form, 45 minutes, after A is complete; due Thursday.
D: Choose and export a cover image, 60 minutes, due Thursday. No dependency.
E: Send the weekly project update, 30 minutes, Friday.
F: Explore a new colour palette, 90 minutes, optional and without a deadline.

Required tasks A to E total 345 minutes: five hours and 45 minutes. Adding optional F brings the total to 435 minutes, or seven hours and 15 minutes. It fits the weekly task budget on paper, but the order still matters.

Try this scheduling prompt

EXAMPLE PROMPT

Plan the tasks below across Monday to Friday. I have two hours of project time each day, and 30 minutes of that time must stay unscheduled. Respect the supplied deadlines and dependencies. Split a task only if its output can be reviewed in parts. List each day's tasks and scheduled minutes. Keep optional work visibly optional. If a dependency arrives late, show what should move rather than shortening the task estimates. Do not schedule product descriptions before Tuesday afternoon. Use the supplied task list A to F.

Paste the six task lines with that brief. Do the arithmetic yourself even if the response includes totals.

Examine one workable schedule

Monday: A, copy review, 90 minutes. Tuesday: C, form test, 45 minutes; D, cover selection, 45 minutes. Wednesday: finish D, 15 minutes; first part of B, 60 minutes. Thursday: finish B, 60 minutes. Friday: E, update, 30 minutes; optional F, first 60 minutes.

That schedules 405 minutes. The remaining 30 minutes of F can go in Thursday's unused task time if it is still worth doing. Every day also retains its separate 30-minute interruption buffer. Choosing not to fill the remaining space is a valid decision.

The schedule deliberately completes the copy before the form test and starts descriptions after the owner's notes arrive. If descriptions cannot sensibly be split, the 120-minute task does not fit a 90-minute daily task budget. You must reserve a longer block on one day and move other work, or renegotiate the task. A prettier table cannot resolve that conflict.

Replan when an input arrives late

If the notes arrive Thursday afternoon, B can no longer follow the Wednesday and Thursday plan. First remove F. Then decide whether Friday has a real 120-minute block available and what that means for the buffer and update. If not, ask for a revised deadline. Record the trade-off instead of hiding it inside a smaller estimate.

At the end of the week, compare estimated and actual time for A to E. If form testing took 90 minutes because of fixes, use that evidence next time. Save a plan you can adjust, not a full calendar you feel obliged to obey.