Productivity Workflows

Time Blocking With AI: Plan a Realistic Week in 30 Minutes

Learn time blocking with AI: honest task estimates, fixed blocks for commutes, power cuts and prayers, and a calendar week you can keep, in 30 minutes.

Time to complete
30 minutes for the first week, then 5 minutes a day and 15 minutes on Friday
Difficulty
Beginner
Tools needed
An AI chatbot (ChatGPT, Claude or Gemini)Google Calendara notes app or paper

Time blocking means giving every important task its own slot in your calendar, instead of keeping a to-do list and hoping the day leaves room for it. With AI doing the sorting and arithmetic, you can build a realistic, time-blocked week in about 30 minutes.

The word that matters is realistic. Most time-blocked weeks fail by Tuesday because the plan ignored real life: the 90-minute drive from Ikorodu, the power cut at 4pm, the lecture that runs over. This workflow builds those things in first, then fits your work around them.

If you want the bigger picture of weekly planning, our guide to planning your week with AI covers the full routine from priorities to review. This workflow zooms in on the mechanics that guide only introduces: honest duration estimates, fixed blocks, buffers, calendar set-up and what to do when blocks collide. And if you only need to protect one deep-work session a day, start with protect your best hours first instead.

What You'll Need

  • An AI chatbot. The free version of ChatGPT, Claude or Gemini is enough.
  • Google Calendar (or any calendar you check daily).
  • Your list of commitments for the week. Work deadlines, classes, exam dates, family duties, church or mosque, gym, side hustle.
  • 30 minutes without interruptions, ideally on Sunday evening or Monday morning.

One rule: never paste confidential work data into a chatbot. Describe tasks in general terms, such as "monthly sales report for manager".

Step 1: Brain-Dump Everything for the Week

Spend five minutes writing every task, appointment and obligation, in any order. Include small things like "renew data plan", because unplanned small tasks steal time.

Then paste the list into your chatbot with this prompt:

Here is my brain dump for the week of [date]. Group it into:
1. Fixed commitments (things with a set time I can't move)
2. Deadline tasks (must be done by a specific day)
3. Flexible tasks (important but no fixed day)
4. Quick admin (under 15 minutes each)
5. Things that can wait until next week or be dropped

Ask me about anything that is unclear instead of guessing. Do not schedule anything yet.

My list:
[paste your brain dump]

The "ask me instead of guessing" line matters: a confidently wrong guess about a deadline will wreck the plan later.

Checkpoint: You have five grouped lists, and you have answered any questions the AI asked. Anything in group 5 is officially off this week's plate.

Step 2: Estimate Durations Honestly (and Pad Them)

This is where most time blocking goes wrong. People estimate for a perfect day. Real days have interruptions, slow internet and a colleague who "just needs two minutes".

Ask the AI to estimate each task, then to add padding based on how things actually go for you:

For each task in groups 2, 3 and 4, estimate how long it will realistically take me.

Context about how I work:
- I usually underestimate writing and analysis tasks by about [half / double]
- My internet is [stable / unreliable], and power is [stable / unreliable] during [hours]
- I get interrupted at work roughly every [X] minutes

Give two numbers for each task: the "ideal" time and a "realistic" time with padding. Explain the padding in one short phrase. Round to 15-minute units.

Use the realistic number, not the ideal one. As a rough rule of thumb, add a quarter to a half on top of any task you have not done before. If a task's realistic time is over three hours, ask the AI to split it into smaller blocks with a clear output for each, such as "draft sections 1 and 2" rather than "work on report".

Checkpoint: Every task has a realistic duration in 15-minute units, and nothing is a vague "work on X" block longer than three hours.

Step 3: Lock In Your Fixed Blocks First

Before any task goes into the calendar, place the things that will happen whether you plan for them or not. In Nigeria, that list is longer than most productivity advice assumes.

Typical fixed blocks:

  • Work hours and any recurring meetings
  • Commute and traffic. If the Third Mainland Bridge or the Lekki-Epe Expressway is part of your day, block the real time, not the Google Maps estimate at midnight.
  • Power windows. If you know NEPA usually takes light in the afternoon, or you only run the generator in the evening, block deep laptop work for when power is reliable and keep low-power tasks (reading, phone calls, planning) for the outage window.
  • Prayers, church, mosque and family time
  • Lectures, tutorials and study group sessions
  • Sleep and meals. A plan that only works if you skip lunch is not a plan.
Here are my fixed commitments for the week, with times:
[paste them]

Also note these patterns:
- Commute: leave home at [time], arrive at [time]; return trip usually [X] minutes
- Power is usually off between [times] on [days]
- Prayer / worship times: [times]
- I need at least [X] hours of sleep

Lay these out as a Monday-to-Sunday grid in 30-minute rows. Mark every free gap with its length. Do not add any tasks yet.

Checkpoint: You can see exactly how many free hours you have this week. If the total is smaller than the realistic total from Step 2, you now know before Monday, not on Thursday night.

Step 4: Build the Week With AI

Now let the AI fit your tasks into the gaps. Give it rules, because a chatbot left to itself will pack every minute.

Using my fixed grid and my task list with realistic durations, build a time-blocked plan for the week.

Rules:
- Put my hardest task of each day in my best focus window: [e.g. 6:30am to 8:30am]
- No more than [X] hours of deep work per day
- Leave a 30-minute buffer block every afternoon for overruns and surprises
- Batch quick admin into one or two 30-minute blocks a day
- Keep laptop-heavy tasks out of the power-cut windows
- Leave at least one evening completely free
- If everything does not fit, do not squeeze it in. List what does not fit and suggest what to drop, delegate or move to next week.

Show the plan as a table: Day | Time | Block | Output expected.

The last rule is the most valuable part of this workflow. Seeing "these three tasks do not fit" on Sunday lets you renegotiate a deadline or ask for help early. If the gap is about goals rather than tasks, run your list through SMART goals with AI to decide what actually matters this quarter.

Read the plan line by line and push back. If the AI put heavy analysis right after your commute, ask it to swap.

Checkpoint: You have a table where every block has an expected output, there is a daily buffer, and you have consciously decided what will not happen this week.

Step 5: Put It in Google Calendar

A plan in a chat window will be forgotten by Tuesday. You have two options:

  1. Type the blocks in manually. This takes about 10 minutes. Use one colour each for fixed blocks, deep work, admin and buffers.
  2. Import a file. Ask the AI for a calendar file, then import it via Google Calendar on a computer (Settings, then Import and export).
Convert this time-blocked plan into an .ics calendar file I can import into Google Calendar.
- Time zone: Africa/Lagos
- Use the block name as the event title and the expected output as the description
- Add a 10-minute reminder to deep-work blocks only
Output only the file contents in a code block.

Save the output as a file ending in .ics and import it into a separate calendar called "Time blocks", so you can hide or delete the whole week in one click if something goes wrong. Check the first two days against your table before trusting it, because AI-generated calendar files sometimes get a time zone or date wrong.

Make fixed blocks such as commute and prayers recurring events, so next week you only add tasks.

Checkpoint: Your week is visible in Google Calendar on your phone, colour-coded, with reminders only where they help.

Step 6: Do a 5-Minute Daily Reset

No week survives Monday unchanged. The daily reset is how you adjust without throwing the plan away.

Each evening, or first thing in the morning, open the chat where you built the plan and paste a quick update:

Daily reset for [day]. What happened today:
- Done: [list]
- Not done: [list, with a short reason]
- New things that came up: [list]

Adjust tomorrow's blocks only. Keep fixed blocks where they are. Use the buffer before moving anything to another day. If tomorrow is now overloaded, tell me what to push and suggest a one-line message I can send if it affects someone else.

Then move the blocks in your calendar. If this takes more than five minutes, your plan is too packed.

Checkpoint: Tomorrow's calendar matches reality, and anything you moved has a new home rather than floating on a list.

Step 7: Run a Friday Review

The Friday review turns one good week into a system. Its job is to improve your estimates and your rules, not to judge yourself.

Here is my plan for this week and what actually happened:
[paste the plan table and a short summary per day]

Review it:
1. Which types of task did I underestimate, and by roughly how much?
2. Which blocks kept getting moved or skipped, and why?
3. Did my power, commute or worship patterns differ from what I planned for?
4. Suggest three specific rule changes for next week's plan.
Keep it short and practical.

Save the three rule changes in a note called "Time blocking rules" and paste them into Step 4 next Sunday. After a few weeks your estimates get noticeably more accurate.

If you track your hours in a spreadsheet, you can go further and ask what the numbers show over a month. Our workflow on AI for data analysis walks through turning a simple sheet into clear answers.

Checkpoint: You have three written rule changes and a saved note you will reuse next week.

Worked Example: Ifeoluwa, a Junior Analyst Studying for a Professional Exam

Ifeoluwa (an invented example) is 25, a junior analyst at a logistics company in Ikeja. She lives in Ikorodu and studies for professional accounting exams on the side. Her study hours kept vanishing.

Brain dump. Her list had 23 items, including a weekly delivery report, two client data requests, four exam topics, a cousin's wedding on Saturday and choir rehearsal on Thursday. The AI asked whether the exam topics needed first-time reading or past-question practice, which changed the estimates.

Honest estimates. She told the AI she usually underestimates analysis tasks by half. The weekly report went from her guess of two hours to a realistic three and a half. Each exam topic became two 75-minute blocks: one for reading, one for past questions.

Fixed blocks. Her grid showed the real picture. She leaves home at 5:45am to beat traffic and gets back around 7:30pm. Light in her area usually goes off between 6pm and 10pm on weekdays, so evening laptop study was unrealistic. Thursday evening was choir, and Saturday was the wedding.

The plan. The AI placed exam study from 6:45am to 8:00am at a quiet café near her office, where power is steady, on Monday, Tuesday, Wednesday and Friday. Evenings became phone-friendly study: flashcards and recorded lectures. The weekly report was split across Monday and Tuesday afternoons. Sunday afternoon got a three-hour study block. Two items did not fit: a free online Excel course and reorganising her files. She moved both to next week.

Calendar and resets. She imported the plan into a "Time blocks" calendar. On Wednesday, a client request landed unexpectedly. Her daily reset used Wednesday's buffer and moved one past-question block to Sunday, and the AI drafted a short message to her manager confirming the new delivery time.

Friday review. She covered three of the four exam topics, not four. The review showed that morning study only worked on days she left home by 5:45am. Her new rule: if she leaves late, swap the morning study block for the evening phone block. For a fuller study system, see our AI study routine that improves grades.

Common Mistakes

Planning the ideal week. If your plan needs zero traffic and 24-hour power, it will fail.

Filling every slot. A week with no buffer collapses at the first surprise. Leave at least 30 minutes of unplanned time each day.

Vague blocks. "Study" or "work on project" invites drifting. Every block needs an expected output.

Trusting the AI's estimates without context. AI does not know you are slow at writing or that your manager interrupts often. Tell it, and ask for padded estimates.

Abandoning the plan after one bad day. That is what the daily reset is for.

Letting the AI book things automatically. Some assistants can now act on your calendar. That can help, as we explain in AI agents for everyday tasks, but review every block before it lands. You are the one who has to live in the week.

FAQ

What is time blocking in simple terms?

Time blocking is scheduling your tasks into specific calendar slots, so each important job has a time when it will happen. Instead of a list you hope to get through, you have a plan of when each thing gets done.

How is this different from a to-do list?

A to-do list tells you what to do. Time blocking tells you when, and shows whether everything actually fits. That second part is the main benefit: you see overload before the week starts.

Which AI tool is best for time blocking?

The free versions of ChatGPT, Claude and Gemini all work. Honest context about your commute, power and energy matters more than the tool.

How do I time block with an unpredictable job?

Block less. Plan only 50 to 60 per cent of your available hours and keep larger buffers. Put your one non-negotiable task early in the day, before requests start arriving.

Is it safe to paste my schedule into a chatbot?

Your routine is usually fine to share, but leave out confidential work details and client names.

Start This Sunday

Time blocking with AI is not about squeezing more into your week. It is about seeing honestly what fits and adjusting calmly when life happens. Block 30 minutes this Sunday, run the seven steps once and treat the first week as an experiment.

Once your weeks are under control, you will have more space for career moves too, such as sending a timely thank you email after an interview instead of forgetting it in a busy week.

More in Productivity Workflows.

More workflows