AI can help turn a messy project idea into a draft plan. It can suggest tasks, identify missing information, and rearrange a list when something changes. It cannot know your team’s real availability or make commitments on somebody else’s behalf.
Your experience is especially useful here. If you have spent years handling projects, customers, households, or volunteer work, you may spot practical obstacles that a polished AI plan overlooks. Use that judgment to give the draft a reality check.
Guided practice · Beginner
Practise a plan you can check
Check whether a small project plan respects its scope, your time and the decisions nobody has made yet.
- Time: about 15–20 minutes for the practice.
- Device: a phone, tablet or computer.
- AI account: optional. Read the worked example, or paste the complete exercise into a text-chat tool you already use.
All practice material below is fictional. You do not need to upload a file, connect an account or use real work information.
Need help? Copy the exercise or Handle invented details.
Start with an outcome someone can recognize
“Improve onboarding” is too broad for a useful first plan. “Create an approved one-page welcome guide for new volunteers” has a visible result.
For this fictional example, the guide needs a contact list, instructions for the first visit, and a link to the existing handbook. It does not need a redesigned website, a new training course, or a database of volunteers.
Before opening an AI tool, write down:
- The finished item and who will use it.
- What must be included and what is outside the project.
- Available time, people, and any spending limit.
- Confirmed deadlines and dependencies.
- The decisions that still need an answer.
Use only information you are allowed to share with the chosen service. A made-up example is enough to learn the planning method.
Give the AI the gaps as well as the facts
An unanswered question belongs in the plan. It should not quietly become an invented fact. Here is a prompt you can adapt:
This is a fictional practice scenario. Help me draft a plan for a one-page welcome guide for new volunteers. It must include a contact list, first-visit instructions, and the existing handbook link. Website redesign and new training materials are outside scope. I have 90 minutes for my own preparation, drafting and revisions. A colleague has offered 30 minutes to check the content, but no review time is booked. The final approver and deadline are not yet confirmed. Propose a short task list. For each task, show what must happen first, the proposed owner, and the question that needs confirming. Label estimates as estimates. Do not invent names, approvals, dates, or agreements. Do not create tasks in other apps.
This produces planning material to review. It does not reserve your colleague’s time, establish a deadline, or assign responsibilities.
Check the order of work
A sensible starting sequence for this example could look like this:
| Task | Needs first | Confirm before proceeding |
|---|---|---|
| Collect the existing information | Access to the current handbook | Are the contacts and arrival instructions current? |
| Draft the one-page guide | Confirmed source information | Does it fit the agreed scope? |
| Check the draft | A complete draft | Who is available to review it, and when? |
| Approve and share the guide | Corrections completed | Who can approve it, and where should it be shared? |
You can arrange the review while collecting information. The review itself must wait for a draft. Asking AI to explain these dependencies can expose a schedule that merely looks tidy.
Also check whether “30 minutes of reviewing” has been confused with “a response within 30 minutes.” Working time and waiting time are different.
Worked example: check the time and the promises
This is an illustrative answer, not a recorded AI test. Your wording may differ; the constraints should survive.
- Collect and check the source information — 20 minutes estimated. Proposed owner: you. Confirm the contact details, arrival instructions and handbook link before using them.
- Draft the one-page guide — 50 minutes estimated. Proposed owner: you. Use the confirmed information and leave visible gaps for anything still missing.
- Review the draft — 30 minutes of a colleague’s time offered. Their review time is not booked. Ask when they can review and return it; do not put a promised return time in the plan.
- Revise after the review — 20 minutes estimated. Proposed owner: you. This follows the returned comments. If the changes need longer, revise the estimate or agree a smaller scope.
- Approve and share — unresolved. Confirm the approver, deadline and sharing permission. These have not been agreed.
Your estimated work: 20 + 50 + 20 = 90 minutes. The colleague’s 30 minutes is separate. Waiting for a review or approval is still unknown. This is not a promise that the project will finish in two hours, and the approval step has not been estimated.
Spot the mistake: “We will publish the approved guide on Friday”
The prompt supplies neither a Friday deadline nor approval. It also does not book the reviewer’s time.
Repair: “Draft, review and revision are proposed steps. Confirm the reviewer’s availability, final approver and deadline before setting a publication date.” Keep the estimates labelled and ask a person to confirm each commitment.
Keep responsibility visible
Replace vague labels such as “the team” with a confirmed owner, or leave the task unassigned until someone accepts it. Separate a person who contributes information from the person who approves the finished work.
The Project Management Institute’s framework for AI in project management considers both task complexity and the human involvement required. That is a useful distinction: arranging a draft task list is different from resolving a disagreement over priorities.
If you connect an AI tool to a project app, check whether it is allowed to create, change, or assign tasks. Start with a draft list you review before importing or sharing it.
Update the plan when reality changes
Suppose the handbook link is outdated. Tell the AI the confirmed change and ask for its consequences:
The handbook link does not work. We do not yet have a replacement. Identify which tasks this blocks, which can continue, and what decision we need. Keep the original scope. Do not invent a replacement link or mark the problem resolved.
Check the proposed revision yourself, then record the actual decision. A project record should distinguish confirmed changes from suggestions.
Finish with a usable result
Before calling the project done, check the guide’s links, contact details, approval, and intended audience. Save the finished version somewhere the right people can find it. Ask one new reader whether the first step is clear.
If your idea is still scattered, try organizing it with an AI-assisted mind map. For ongoing reviews after the plan is made, use one repeatable AI routine rather than generating a completely new plan each week.
Finish this practice
You have finished when: you can account for your 90 minutes, keep the colleague’s time separate, and name the review, approval and deadline decisions still to confirm.
Want to keep what you learned? Save a practice record (PDF or Word). Note whether you read the worked example or tried an AI response yourself.
Recommended next lesson
Now fit your part of the project into a week with realistic space.
Featured photograph by Alvaro Reyes on Unsplash. Photograph used for illustration.
Reviewed October 3, 2026.
Website check, October 14, 2026: see what was checked and its limits.
Practice updated October 14, 2026: copyable prompts, an illustrative time budget and a mistake-and-repair example. The example is teaching material, not a recorded tool test.
