In this guide
  1. Begin with a safe weekly inventory
  2. Choose outcomes before arranging time
  3. Estimate with ranges, not false precision
  4. Ask AI to expose collisions
  5. Turn the plan into visible commitments
  6. Use a short daily re-plan
  7. Review the plan as an experiment
01

Begin with a safe weekly inventory

Collect your fixed commitments, active projects, waiting items and deadlines. Do this in your approved calendar or task system. Before using an AI tool, remove or generalise information you are not permitted to share. A label such as ‘customer escalation’ may be enough for planning; names, account details and confidential context may not be.

Do not make the input larger than the decision. For a weekly plan, you usually need the task, deadline, estimated effort, dependencies and consequence of delay. You rarely need the full email chain or project file.

02

Choose outcomes before arranging time

Write the two or three outcomes that would make the week useful. An outcome is a result you can recognise: approve the store-opening checklist, submit the first budget draft, or resolve the ownership of a delayed handover. ‘Work on the budget’ is an activity; it does not define enough progress.

Ask which outcomes are truly yours to choose. If priorities conflict or deadlines exceed capacity, flag the decision for your manager or collaborators. AI can display the conflict, but it cannot accept the trade-off on behalf of the people involved.

03

Estimate with ranges, not false precision

Give each substantial task a rough range: thirty to forty-five minutes, two to three hours, or more than half a day. Include preparation, review and coordination—not only execution. Mark tasks with uncertain scope and work that depends on someone else.

A generated schedule can look authoritative because every block fits neatly. Real work does not. Preserve open space for routine interruptions, travel, customer issues and decisions that take longer than expected. The aim is a credible week, not a perfect calendar.

04

Ask AI to expose collisions

Provide the permitted inventory, outcome priorities, time ranges and fixed commitments. Ask the model to identify overload, dependencies, missing information and tasks that may need to move. Request questions before a proposed schedule. This makes uncertainty visible instead of letting the tool quietly assume.

Review each flagged collision yourself. Some short tasks carry high consequences; some apparent deadlines are flexible; some meetings cannot move because several people depend on them. Add the context only you can supply, then ask for a revised plan.

Practice prompt

Using only the fictional task list below, identify deadline conflicts, dependencies and missing estimates. My three weekly outcomes are listed first. Do not schedule yet. Ask up to five questions that would materially change the plan. After I answer, propose a plan with no more than two priority work blocks per day and at least 25 percent unscheduled capacity.

05

Turn the plan into visible commitments

Move the approved work blocks into the system you actually use. Add a first action to each priority block so you can begin without reopening the planning exercise. Record who is waiting, when you will follow up and which tasks you deliberately deferred.

If the plan depends on another person changing a deadline or providing information, have that conversation. A private plan does not resolve a shared conflict. State the trade-off plainly: ‘If the review remains Tuesday, the analysis will move to Thursday. Which outcome should take priority?’

06

Use a short daily re-plan

At the start or end of each day, compare reality with the plan. What finished, moved or changed? Update the remaining capacity and protect the most useful next action. You may ask AI to reorganise the permitted task list, but keep the revision small. Rebuilding the entire week every day creates planning work rather than progress.

When an urgent task arrives, name what it displaces. If nothing is allowed to move, you do not have a scheduling problem; you have a priority or capacity problem that needs a decision.

07

Review the plan as an experiment

At the weekly reset, compare planned and completed outcomes. Note where your estimates were wrong, where dependencies delayed work and which blocks protected useful progress. Do not treat every change as failure; the purpose of the review is to improve the next plan.

Adjust one planning assumption at a time. You might reduce daily priority blocks, increase buffer time or separate coordination from focused work. Keep a manual alternative available. AI earns a place in the routine only when the complete process improves clarity or follow-through.

Before you move on

  • Only permitted and necessary information enters the planning tool.
  • The week is organised around recognisable outcomes.
  • Time estimates include preparation, review and coordination.
  • The plan contains buffer time and makes uncertainty visible.
  • Conflicting commitments lead to a conversation or decision.
  • The weekly review changes one useful assumption for next time.

Sources and further reading

These official resources informed the guardrails and practical method in this guide.

  1. NIST AI Risk Management Framework Core ↗
  2. ICO: Artificial Intelligence and Data Protection ↗
  3. OpenAI Academy: Prompting ↗
Use the free Workweek Starter →

This preview uses fictional examples where indicated. Read our editorial approach.