Tell AI what needs doing, what has a deadline, and what time is already spoken for. Ask it to group related tasks and show a suggested order, then make the plan fit your real workload.
“Help me organize my work for tomorrow.”
AI needs the tasks and any fixed commitments to make a useful draft.
“I have three tasks, a 10 o’clock meeting, and two hours of focused work available. Put urgent tasks first, leave time for breaks, and label any time estimates as guesses.”
You can change the order or remove anything that does not fit your day.
A practical way to plan
Make a plan that fits the day you have
A deadline says when work is due. A priority says what deserves attention first, based on impact, risk, or what another task depends on. They often overlap, but they are not the same: a high-impact task may need an early start even when its deadline is later, while a small urgent task may take only a few minutes.
- Mark fixed time first. Add appointments, travel, breaks, and other commitments. Count only the time that is actually available for tasks.
- Estimate in ranges. Break a task into visible steps. Use a similar task you have done before as a reference, then write a low and high estimate. Treat an AI estimate as a guess until you compare it with your experience.
- Allow for real life. Leave open space for interruptions and transitions. If the day is unpredictable, reserve a larger buffer and plan fewer tasks.
- Check dependencies and consequences. Put prerequisites first. Ask what can safely move if an estimate runs long, and what would be harmed by waiting.
Worked example: a three-hour morning
From 9:00 to 12:00 gives 180 minutes. A fixed meeting from 10:00 to 10:30, a 10-minute transition afterward, and 35 minutes kept open for interruptions and breaks leave 105 planned work minutes. Preparing for a 2:00 meeting may take 45–60 minutes; a report due tomorrow may take 60–90; routine messages take about 20. Even the low estimates total 125 minutes, so fitting everything would rely on luck.
- 9:00–9:45: prepare the 2:00 meeting; use the last 15 minutes before 10:00 as a buffer.
- 10:00–10:30: fixed meeting.
- 10:30–10:40: transition and capture follow-up actions.
- 10:40–11:40: make a first pass on the report.
- 11:40–12:00: buffer. Move routine messages to another window; if the report needs more than an hour, record the next step and renegotiate its timing.
This draft protects the nearer meeting need and admits that the report may take longer. Your own past timing and real deadlines should replace these example estimates.
Spot an unrealistic AI schedule
Add the minutes yourself after fixed commitments, breaks, transitions, and buffer. Be cautious if the plan fills every minute, treats guesses as facts, starts a task before its prerequisite, or ignores what must move when work runs late. Ask the assistant to show its assumptions, then correct them with what you know.
Guided practice · work at your own pace
Build a schedule that fits the time you really have
New to working between a lesson and an AI assistant? Read the beginner’s guide. It also explains a paper-only approach; no paid service is required.
Privacy: Use generic task labels or made-up examples. Follow workplace rules; do not share confidential employer, employee, or customer details with an unapproved AI service.
Worked example
From 9:00–12:00, a 30-minute fixed meeting, a 10-minute transition, and 35 minutes reserved for breaks and interruptions leave 105 work minutes. Meeting preparation (45–60 minutes), a report (60–90), and routine messages (20) need 125–170 minutes, so do not plan all three. Use 9:00–9:45 for preparation, 9:45–10:00 as buffer, 10:00–10:30 for the meeting, 10:30–10:40 to transition, 10:40–11:40 for a first report pass, and 11:40–12:00 as buffer. Move messages to another window; if the report needs longer, record the next step and revisit its timing.
Prompt to try
First write your goal and limits below. The prompt will use those notes.
Help me with this a practical schedule for a short work period. Ask a question if something important is missing. Do not invent facts. Tasks, deadlines, dependencies, fixed commitments, actual available time, and uncertainty in estimates: [add your goal and limits] Create a schedule only inside the time available. Show estimated duration as an estimate, include at least one buffer, preserve fixed appointments, and identify dependencies or deadlines that affect order. If tasks do not fit, say what should move rather than overfilling the schedule. Use only made-up, de-identified, or explicitly approved information. Follow my employer's rules; do not request confidential customer, employee, or business details.
Use generic work labels. State start/end time, fixed events, and any task that must happen before another. Mark estimates you are unsure about.
Paste the proposed schedule, including time ranges and buffers.
Add the low and high estimates. Do the tasks fit after fixed events, breaks, transitions, and a buffer? Is a priority being confused with a deadline? What depends on another task, and what can move?
Write a schedule using your real time window and ranges. Protect fixed events and a buffer, put prerequisites first, name the task that will move if work runs long, and state your first action.
Practice without AI
Use a paper calendar. Block fixed commitments first, then tasks using your own time estimates. Leave open space for interruptions and mark one task that can move if the day changes.
Your notes save in this browser as you type. They are included in the learning-work JSON export.
Save your capacity-checked schedule. When you are ready, mark this lesson complete.