Save the Copilot prompts your team keeps retyping
Four people write their own version of the same Monday-update request, and one of them keeps getting an action list full of things nobody agreed. The good prompt exists somewhere in last week's chat.
What you'll make
one reusable Copilot prompt, saved under a title that says when to use it and shared with your Teams team, that a colleague can run correctly without you.
What you'll need
Microsoft 365 Copilot with a work or school account, one prompt you already know works, and about fifteen minutes plus a colleague to test it.
Example result.
Saved title: Weekly ops update — decisions, actions, open questions (won't assign unagreed owners)
Shared to: Operations team › Team prompts
Colleague's test result:
Decision: review the delivery schedule.
Accepted action: Jo to gather supplier dates; deadline to agree.
Open question: whether to accept the suggested Friday launch.1. Pick the prompt and make it work without you
Start with the single request your team retypes most often. A library of forty prompts that nobody searches is worse than three that people use, because it looks as though the problem has been solved.
The value in a saved prompt is rarely the main instruction; “summarise this” isn’t hard to remember. It’s the lines underneath about what not to do. Keep those, and replace dates, names and files with bracketed fields:
Summarise last week's [project] activity for a Monday update, from the notes below.
Use three sections: Decisions, Accepted actions and Open questions. Give a short quote or location for each decision. Only list an action if someone explicitly accepted it. If its owner or deadline wasn't agreed, keep the action and write "to agree"; do not invent either. Do not treat suggestions or silence as agreement. Keep conditions visible. List unaccepted proposals under Open questions. No opening paragraph about the week in general.
NOTES: [notes][project] is the project name; [notes] is this week’s notes. Saving a prompt doesn’t give the next person your files or your earlier chat, so say what input it expects.
Why this works: the constraints are what get dropped when people write from memory, and they’re what made the prompt work. Writing it out properly once matters: saving a hurried version just distributes the hurry.
What you should see: a prompt with no leftover specifics, which gives a checked result on a small example.
2. Save it with a title that says when to use it
Run the prompt, then hover over it, select the bookmark icon and choose Save prompt. You can edit the title as you save. Saved prompts are only visible to you; you’ll find them under Your prompts (some Microsoft pages say “Your saved prompts”).
The title is the step that decides whether anyone uses it again. In a shared library, a title does the job of documentation: it should answer “should I use this one?”, not just “what does this do?”.
- Weak: Meeting summary
- Better: Meeting notes to actions — keeps owners and dates unassigned if not agreed
Why this works: the better title tells a colleague what makes this prompt different from the three others with similar names, which is what they need while scanning a list.
What you should see: the prompt in your saved list under a title that names the job and its one distinguishing behaviour.
3. Share it with the team
Open the prompt gallery from Copilot Chat (the prompt pills or … below the input box), go to Your prompts, hover over the prompt, select Share prompt at the top of its card, then Share to team and choose the team. Colleagues find it under Team prompts. Ignore any advice to install the old standalone Prompt Lab app: it was discontinued in July 2025.
For a one-off, there’s a lighter route: after a prompt runs, hover over it and select Copy to copy a link, then paste it in the Teams channel where the work happens.
Two things to know before building a process on this. Microsoft documents no approval or review step for team prompts, so any member can share one; if you need a reviewed set, that review is a human habit. And Microsoft’s pages describe sharing as available with a Microsoft 365 Copilot (work or school) licence, so if you’re on Copilot Chat alone, check whether the control appears.
Why this works: a prompt in the channel where people work gets used more than an entry in a gallery nobody opens.
What you should see: the prompt under the team’s Team prompts tab, or a link pinned in the channel.
4. Check it with one colleague
Ask one person to find the prompt, fill in the fields and run it on their own notes. Check their result against those notes, especially owners and dates.
If it only works with your explanation alongside it, add that explanation to the prompt. If it needs a file they can’t open, give them a source they can use rather than pasting restricted material into the prompt.
Why this works: the only proof a shared prompt works is someone else running it.
What you should see: a colleague’s result that passes the same checks yours did, without borrowing your chat history.
Check the result
- The saved text still has every constraint line and every bracketed field.
- The title names the job and the behaviour that makes it different.
- A colleague found it, ran it and got a checkable result.
- Someone is named to tell when it stops working well.
The usual failure: the prompt shrinks as it travels. Someone saves or copies a shorter version without the lines about unagreed owners, and the action list fills up again. Spot it by comparing the shared text with your original, line by line, and by checking a colleague’s result for owners or dates that aren’t in the notes.
Review this reusable prompt against the failure below. Propose the smallest change that fixes the error while keeping the useful behaviour. Say which earlier examples should be rerun.
PROMPT: [prompt]
FAILURE AND EXPECTED BEHAVIOUR: [failure][prompt] is the saved text; [failure] is what went wrong and what should have happened.
Worked example: the Monday operations update
Fictional example. This week’s notes:
Team agreed to review the delivery schedule.
Jo agreed to gather supplier dates. No deadline was agreed.
Sam suggested a Friday launch. Nobody accepted it.A colleague used an older saved copy titled Weekly summary, which had lost two lines. It returned: “Actions: Jo to gather supplier dates by Friday. Launch confirmed for Friday.”
- The failure. The short copy had no rule against inferring agreement, so Sam’s suggestion became a launch date and gave Jo a deadline nobody set.
- The repair. The team deleted the old copy and shared the full prompt from step 1 under the descriptive title. Run on the same notes, it gave the result at the top of this page: Jo’s action kept, the deadline marked “to agree”, Friday left as an open question.
- What changed in practice. Not speed: typing a prompt was never the bottleneck. The constraints now travel with the request.
Task kit for this job: Download (ZIP) · Reusable instructions
Go deeper
Optional training: Ask IT to publish organisational prompts
Administrators can publish prompts for the whole organisation in the Microsoft 365 admin center: expand Copilot, select Prompts, create the prompt and select Publish. It needs the AI Administrator or Search Editor role. Published prompts can take about three hours to appear, and up to four can be pinned as suggestions in Copilot Chat, Edge and Teams.
Limits worth knowing: 1,000 prompts per tenant; imports up to 5 MB or 100 prompts at a time; title 35 characters, display prompt 132, prompt text 8,000. These apply to organisational prompts only. It’s the right route for something the organisation has decided, such as a required structure for client notes, and the wrong one for a prompt you’re still changing weekly.
Optional training: Write for someone who didn't write it
A prompt that works for you often fails for a colleague, for predictable reasons. Hard-coded specifics (a file, a quarter, a team name) should be bracketed fields. Assumed inputs should be stated: a colleague pasting a raw transcript into a prompt written for tidy notes will get a worse result and conclude the prompt is bad, so add “If the notes are a raw transcript, first list who said what.” And a line like “do not infer agreement from silence” looks like clutter to someone who hasn’t seen the failure it prevents, so keep it and, if needed, say why in the title.
For multi-step jobs with files and review decisions, a bookmark isn’t enough; see Save a useful AI task so you can reuse it.
Optional training: Keep a small library from going stale
Libraries decay quietly: nobody deletes anything, three prompts do similar jobs and new colleagues pick one at random. Three habits are enough.
- Cap the number, say at eight. The cap forces the conversation about which meeting prompt is actually better.
- Review when something changes, not on a schedule: a new format, a new system, a wrong answer.
- Name one person per prompt to tell when it misbehaves.
Saving prompts doesn’t make Copilot’s answers correct. It makes the request consistent, which makes the errors consistent too. That’s useful: a consistent error is one you can spot and fix.