Copilot for Planner prompts let you create, organize and prioritize tasks on a planner board without leaving Microsoft Teams. This page has 16 to copy, and the Founderz Copilot productivity course teaches you to apply them with a method.
What you’ll take from this
This library of Copilot for Planner prompts is built so you can set up and order a plan in minutes. Here is what you will find:
- 16 Copilot for Planner prompts ready to copy: create tasks, prioritize, project status, RAID risks and a weekly routine.
- What you need to access Copilot in Planner with your work account: license, Planner in Teams and preview status.
- The structure of a good prompt (role, context, task, constraints and format), with a before and after example.
- How the prompt changes in ChatGPT, Gemini and Claude, and what to always check before applying a suggestion.
Many project managers spend the first hour of Monday building tasks by hand: writing each one, assigning someone, deciding what goes first. Copilot for Planner prompts cut that work down to a few minutes. Copilot reads your current plan, proposes the missing tasks and suggests a priority order. You review, adjust and move on. The brackets mark what to swap: change what is inside them and keep the rest. Library reviewed in November 2026.
What is Copilot in Planner and who is it for in project management?
Copilot in Planner is the Microsoft AI assistant built into Microsoft Planner that helps create tasks, summarize project status and spot risks using natural language. It is part of Microsoft 365 Copilot and works inside the new Planner in Microsoft Teams. Instead of filling in fields one by one, you describe what you need and Copilot drafts a proposal. It is most useful for three profiles:
- A project manager builds plans fast, tracks status and anticipates risks without spending hours on admin.
- Operational teams see assigned tasks clearly and understand what goes first.
- Task owners get a prioritized list instead of a messy board.
According to the official Microsoft Support documentation, Copilot in Planner suggests tasks and generates status summaries from the existing plan. That frees the project manager from the mechanical part and leaves the judgment: how important each item is and who is the right person for each task.
How Copilot works on your project data
Copilot in Planner (preview) uses the data in your current project plan to generate its suggestions. It does not invent context: it reads the tasks, goals and dates that already exist in your plan. The flow is straightforward:
- Copilot reads the current plan and its tasks.
- It analyzes goals, deadlines and workload.
- It suggests new tasks, status summaries or risk alerts.
Copilot in Planner helps, but it does not decide for you. Every suggestion goes through your review: if a task is unnecessary, you delete it; if a priority does not fit, you change it.
With Microsoft Planner Copilot you can ask for three things about your project plan: create and organize tasks on the planner board, check project health and list the project risks. For project management, those three uses cover most of the repetitive work with Microsoft 365 Copilot, and each one appears below as a Copilot prompt ready to copy.
What you need to access Copilot in Planner with your work account
To access Copilot in Planner you need a Copilot for Microsoft 365 license and the new Planner inside Microsoft Teams. Without that license, the AI features do not appear on the board. Copilot in Planner runs on the Microsoft 365 environment, not as a standalone app.
| Requirement | Detail |
|---|---|
| License | Active Copilot for Microsoft 365 license |
| Environment | New Microsoft Planner in Microsoft Teams |
| Status | Copilot in Planner is in preview |
| Access | Through the Planner app in Teams |
Important
Because it is in preview, availability can vary by organization and by your Microsoft 365 administrator’s settings. If you do not see the Copilot features in your Planner, the license is probably missing or the rollout has not reached your tenant yet. Talk to whoever manages Microsoft 365 at your company before assuming something is broken.
How to create and prioritize tasks step by step with Copilot in Planner
Creating and prioritizing tasks with Copilot in Planner follows a four-step flow. What matters is that you review each suggestion before applying it to the board.
- Open the plan in Microsoft Teams. Go into the new Planner inside Teams and select the plan you want to work on.
- Run the prompt. Write what you need: create tasks, summarize status or spot risks. Copilot generates the proposal from your data.
- Review the suggestions. Read each proposed task. Delete what is unnecessary, edit what does not fit.
- Adjust priorities on the planner board. Reorder, assign owners and confirm deadlines.
This cycle works the same for one planner board or several. For a broader guide, see how to organize team tasks with Microsoft Planner from start to finish. The prompts below are grouped by what you want to achieve.
Copilot for Planner prompts: create tasks and plans
A project manager preparing an onboarding plan can use Copilot to plan all the tasks for the first two weeks, grouped by area. What used to take half an hour of manual typing can often be done in a couple of minutes of generating and reviewing.
Create the tasks for a launch
Act as a project manager.
Context: I am launching [a new website] and the Planner plan is called [plan name].
Task: create the tasks needed to launch it in [3 weeks], grouped by [design, content and development].
Constraints: one due date per group, concrete tasks that can be finished in one or two days, and no duplicates of tasks already in the plan.
Format: list by group with task, estimated duration and due date.
Onboarding plan for the first two weeks
Act as a Learning and Development lead in Human Resources.
Context: [name] joins the [team] team on [date] and I need an onboarding plan.
Task: generate the tasks for their first two weeks, grouped by area: access and equipment, training, team meetings and first goals.
Constraints: assign each task to [the new hire, their manager or the IT team], with a due day and a maximum of [20] tasks.
Format: table with task, owner, day and group.
Plan a marketing campaign
Act as the marketing lead of a team of [three] people.
Context: we launch the campaign [campaign name] on [date] for [audience].
Task: create the preparation, launch and wrap-up tasks, spread across weeks.
Constraints: flag the milestones that depend on other tasks, leave a week of buffer before launch and do not suggest channels we do not use: [campaign channels].
Format: list by week with task, suggested owner and dependency.
Split a big task into subtasks
Act as a project manager.
Context: the plan has one task that is too big: [task name], due [date].
Task: split it into subtasks that one person can finish in less than [two days].
Constraints: order them so each one can start when the previous one ends, and mark which ones can run in parallel.
Format: numbered list of subtasks with estimated duration.
Tip
Split a big project into several prompts, one per phase. Asking for too much in a single prompt gives generic tasks that are hard to review.
Copilot for Planner prompts: prioritize tasks and balance workload
With due dates on your tasks, Copilot can sort what is pending and spot who is getting overloaded. Without a deadline it cannot prioritize, so always add a time horizon.
Sort pending tasks by urgency
Act as a project manager preparing the week.
Context: the plan [plan name] has pending tasks with different due dates.
Task: sort the pending tasks by urgency based on their due date and flag the three most critical.
Constraints: overdue tasks and tasks with dependencies go first, and explain in one sentence why each of the three is critical.
Format: numbered list with task, due date and reason.
Prioritize by impact and effort
Act as a project management consultant.
Context: the team has more tasks than time in [the next two weeks] and the project goal is [goal].
Task: classify the open tasks by their impact on the goal and the effort they require.
Constraints: use only the information in the plan, mark tasks without a description as [to confirm] and do not remove any without telling me.
Format: table with task, impact (high, medium, low), effort (high, medium, low) and recommendation (do now, schedule or postpone).
Team workload distribution
Act as a team lead assigning work.
Context: it is the week of [date] and the [team] team has tasks in the plan [plan name].
Task: show me which people have the most tasks assigned this week and suggest how to rebalance the load.
Constraints: do not reassign tasks on your own, take into account that [person] is on vacation on [date] and suggest at most [three] changes.
Format: table with person, tasks this week and suggested change.
Overdue and blocked tasks
Act as a PMO reviewing a plan.
Context: the plan [plan name] has been running for [number] weeks.
Task: list the overdue tasks, the blocked ones and those with no owner.
Constraints: do not change dates or owners, and for each task suggest a question I should ask the right person.
Format: three lists with task, due date and suggested question.
Copilot for Planner prompts: project status and RAID risks
Status and risk prompts save a project manager the most time. Each one generates a proposal that you validate. For more context, there are practical examples of Copilot in project management to adapt to your case.
Project status in one headline
Act as a project manager reporting to leadership.
Context: the project [project name] is in the [phase] phase.
Task: summarize the current project status: completed, in-progress and blocked tasks, with a one-line headline on overall health.
Constraints: use only the data in the plan, maximum [100] words and no adjectives you cannot back with a number.
Format: headline, three bullets with numbers and a closing sentence with what you need from leadership.
Plan risks in RAID format
Act as a project manager experienced in risk management.
Context: the plan [plan name] is due on [date].
Task: identify the main risks in the current project plan and classify them as risk, assumption, issue or dependency (RAID).
Constraints: base each item on a specific task or date in the plan, do not invent generic risks and mark probability as high, medium or low.
Format: table with type, description, affected task, probability and suggested action.
Friday progress summary
Act as a project coordinator closing the week.
Context: it is Friday and the plan [plan name] has tasks completed this week.
Task: summarize what was completed, what slipped and what should start next week.
Constraints: maximum [120] words, mention people only for specific tasks and leave out tasks with no progress.
Format: three sections, "Done", "Slipped" and "Next week", with bullets.
Progress report for the client
Act as an account manager reporting to a client.
Context: the project [name] for [client] has a Planner plan with internal tasks and client-visible tasks.
Task: write a progress report based on the plan status.
Constraints: do not mention internal tasks, delays attributed to individuals or anything confidential, and keep a clear, honest tone about deadlines.
Format: email with three short paragraphs: progress, next milestones and what we need from the client.
Important
Copilot works on your plan data inside your organization’s environment, but review your internal policies on what information goes into prompts, especially if the project includes sensitive client or contract data.
Copilot prompts in Teams for your weekly routine
Copilot prompts in Microsoft Teams work best when they become a routine. A simple one: Monday to prepare the week, Wednesday to see what is blocked and Friday to wrap up and plan the next one. A marketing team of three can use this cycle to cut down on follow-up meetings.
Prepare the week on Monday
Act as a planning assistant for the team [team name].
Context: it is Monday morning and we work in the plans [plan names].
Task: prepare the week: tasks that are due, tasks I should start and tasks that depend on other people.
Constraints: order them by priority, do not add new tasks and flag any date conflicts.
Format: list by day of the week with task and priority.
Mid-week check-in meeting
Act as a meeting facilitator.
Context: it is Wednesday and the [team] team meets for [15] minutes to review the plan [plan name].
Task: prepare the meeting script from the plan status: what is blocked, what is slipping and what decision is needed.
Constraints: maximum [four] items, one per topic, with the question to resolve in each.
Format: table with item, question, owner and minutes.
From meeting notes to tasks
Act as a project coordinator.
Context: we just closed the meeting on [topic] and these are the notes: [paste your notes here].
Task: turn the notes into tasks for the plan [plan name].
Constraints: include only tasks someone accepted, write [to confirm] if the owner or date is missing and do not make any up.
Format: table with task, owner, due date and plan group.
Message to the team with the priorities
Act as the lead of the team [team name].
Context: we reordered the priorities of the plan [plan name] because of [reason for the change].
Task: write a message for the Teams channel that explains the new priorities and what changes for each person.
Constraints: friendly tone, maximum [100] words and no blaming anyone for the changes.
Format: an opening sentence, a list with "[person]: task, date" and a closing sentence inviting people to flag conflicts.
When the whole team uses the same prompts, boards look and read the same, and nobody wastes time decoding someone else’s format. The relationship between people and the project gets clearer when every task has context, an owner and a deadline.
How I built these prompts: the fields for writing Copilot prompts for Planner
A good prompt has context, goal, deadline and output format. The more specific you are, the better the answer on the planner board. These are the fields I always use, in this order, and what each one decides:
| Field | What it decides | Example in the prompt |
|---|---|---|
| Role | The voice and point of view | project manager reporting to leadership |
| Context | Which plan we are talking about and what phase it is in | plan [plan name], design phase |
| Task | What Copilot does (a clear verb) | create, sort, summarize, identify |
| Constraints | Deadline, limits and what it must not do | three weeks, do not reassign tasks on your own |
| Output format | How the result is delivered | table with task, owner and due date |
Five tips for writing your own Copilot prompts
- Talk to it like a new colleague. Copilot understands full sentences better than loose keywords; you do not need technical commands.
- Always state the deadline. Without a date, Copilot cannot prioritize.
- Add a negative rule. “Do not invent owners” or “use only the plan data” prevents the most common failures.
- Fix the format. If you want a table or a list by group, say so.
- Rephrase instead of accepting the first version. Each iteration improves on the last, and the prompts that work best are worth saving for reuse.
Example: from a weak prompt to a strong one
| Weak prompt | Strong prompt |
|---|---|
| “Add tasks to the project” | “Act as a project manager. Create the tasks needed to launch the website in 3 weeks, grouped by design, content and development, with one due date per group and no duplicates of existing tasks.” |
| “Tell me how the project is going” | “Summarize the current plan status: completed, in-progress and blocked tasks, with a one-line headline. Use only the plan data and a maximum of 100 words.” |
| “Sort the tasks” | “Sort the pending tasks by urgency based on their due date and flag the three most critical, with the reason in one sentence.” |
The weak prompt returns generic tasks with no deadline or owner. The strong one lands close to what you need and cuts the rounds of correction.
Common mistakes when asking Copilot in Planner for tasks
- Not stating a deadline. Without a date, Copilot cannot prioritize.
- Asking for too much in one prompt. Split the project by phase.
- Not reviewing the output. Copilot proposes, you validate. Accepting without reading creates noisy boards.
Copilot in Planner limits and where the person decides
Copilot in Planner speeds up tasks, but it does not replace your judgment. Its suggestions are a starting point, not a final decision. These are the limits to keep in mind:
- Preview status. Features can change. Check the Microsoft Support documentation for current availability.
- Human oversight. Copilot proposes tasks and priorities from your project data, but you decide what gets applied.
- Verification. An automatic priority may not reflect the real context of the project.
- Data privacy. Copilot works on your plan data inside your organization’s environment. Review internal policies on what information goes into prompts.
Judgment about what is urgent, who is the right person and which risk really matters stays human. Copilot removes the mechanical part. The responsibility stays with you.
How the prompt changes by AI tool
The prompts on this page are written for Copilot inside Planner, but the method (role, context, task, constraints and format) works in any assistant. Here is what changes:
Copilot
It works on your Planner plan, so you do not have to paste the tasks. It is the only one on the list that reads the plan directly and can propose changes to it, as long as you have the license and the feature has rolled out in your organization.
ChatGPT
It cannot see your Planner plan. Paste the task list with its dates, or attach an export, and ask for the result in the same format. It works for sorting and prioritizing if you work from a list.
Gemini
If your team uses Google Workspace, use it with a spreadsheet or a document that holds the tasks. The prompts that mention Planner need adapting to the text you paste.
Claude
It is useful with long meeting notes or lengthy scope documents: give it the full text and ask for the task list with owner and deadline. It does not access Planner, so you copy the result to the board.
Frequently asked questions about Copilot for Planner prompts
These are the most common questions about writing prompts and using Copilot in Planner, with the answer first.
How can I access Copilot in Planner?
You need an active Copilot for Microsoft 365 license and the new Planner inside Microsoft Teams. Because it is in preview, availability depends on your organization’s settings. If you do not see the features, ask whoever administers Microsoft 365 to confirm the license and the rollout in your tenant.
Do I need a Copilot for Microsoft 365 license to use Copilot in Planner?
Yes. Without an active Copilot for Microsoft 365 license, the AI features do not appear on the planner board. You also need the new Planner in Teams and the rollout must have reached your organization.
Where does Copilot in Planner get my project data?
From your current plan: the tasks, goals, owners and dates that already exist. It does not invent outside context and it works inside your organization’s Microsoft 365 environment, respecting the data policies your company has set.
What prompts can I use in Copilot to prioritize tasks?
Ask it to sort pending tasks by urgency based on their due date and flag the three most critical. If you add the project goal, it can also classify them by impact and effort. Both prompts are in the library.
Which Copilot prompts help a project manager?
The ones for project status, RAID risks, workload distribution and the weekly summary. They save the most time because they turn plan data into a report you review instead of writing from scratch.
How is Copilot in Planner different from Copilot for Microsoft 365?
Copilot for Microsoft 365 is the general assistant that works in apps like Word, Excel, Outlook and Teams. Copilot in Planner applies those capabilities inside Planner, focused on creating tasks, summarizing status and spotting risks, under the same license.
How do Copilot prompts help manage risks and RAID items?
You can ask Copilot to identify the plan’s risks and classify them as risk, assumption, issue or dependency. It analyzes the existing tasks and deadlines and points out possible blockers. You validate which risks are real and decide how to handle them.
Can I use Copilot in Planner for Learning and Development in Human Resources?
Yes. A Learning and Development team can organize onboarding plans, training paths or internal learning campaigns, with tasks grouped by phase and with deadlines. You decide which content, deadlines and owners fit.
Can I use ChatGPT, Gemini or Claude instead of Copilot for Planner?
As support, yes, but they cannot see your plan: you have to paste the tasks. Copilot is the one that works inside Planner with the plan data.
Your next step with Copilot for Planner prompts
Pick a task you do every week, change what is in the brackets of the matching prompt and try it on your plan. Then change a single field, such as the format, and compare. That teaches you what each field controls much faster than reading theory.
If you want to learn to write these prompts with a method and apply them to your own projects, the Copilot productivity course at Founderz guides you step by step. Founderz is an online AI business school, in collaboration with Microsoft, and a practical approach built around real work.