In this article
- Before trying these Copilot prompts
- 1. Turn a task list into prioritisation questions
- 2. Prepare for a meeting from approved notes
- 3. Make a message easier to act on
- 4. Compare options without inventing a winner
- 5. Close a meeting with a draft action register
- What to do when a prompt returns a weak answer
- Keep the prompt that survives review
These are original practice prompts, not copied product demonstrations or claims of hands-on testing. Their usefulness depends on the task, the quality of the input and your review.
Before trying these Copilot prompts
Check which Copilot experience your organisation provides. Microsoft's official overview describes differences in grounding and licensing; do not assume every chat can access your work files.
Microsoft's WorkLab prompt article offers another starting point. The prompts below focus on visible source boundaries and practical checks for an ordinary workday.
Use the relevant approved app or chat, supply information you are permitted to share and adapt the instructions to your job. Where access is absent, do not compensate by uploading restricted material.
1. Turn a task list into prioritisation questions
Ask Copilot to reveal what you need to decide rather than letting it silently determine your priorities.
Review this fictional task list. Group items by stated deadline, dependency and unresolved decision. Do not invent urgency or importance. Identify three questions I should answer before setting today's priorities.
This is useful when a list mixes routine actions with blocked decisions. The output should help you see the structure, while you retain responsibility for priorities.
Check that actual deadlines remain accurate and that a vague task has not become an urgent commitment. If the list omits consequences, add that context yourself before deciding.
2. Prepare for a meeting from approved notes
Ask for questions that expose missing information and support the decision you need to make.
Using only these approved notes, prepare questions for a project review. Separate questions about confirmed progress, unresolved risks and decisions required. Do not infer individual motives or add facts outside the notes.
For a hypothetical launch discussion, the tool might help distinguish a delivery question from a scope decision. You must still check whether the questions are relevant to the participants and the meeting's authority.
Remove questions already answered in the material. Add any important operating context the tool could not know.
3. Make a message easier to act on
Use Copilot to restructure a draft while preserving its factual and commercial meaning.
Rewrite this fictional update for a busy colleague. Put the requested action first, then the necessary context and any unresolved issue. Preserve dates, owners and qualifications exactly. Flag anything unclear instead of resolving it.
Compare the original and revised versions before sending. Pay particular attention to words such as “may,” “approved,” “proposed” and “confirmed”; changing them can alter the commitment.
If the rewrite sounds more confident than the evidence permits, restore the qualification. Clear writing should make uncertainty easier to understand, not erase it.
4. Compare options without inventing a winner
Use a common set of criteria to make trade-offs visible.
Compare the two options in these fictional notes using cost information supplied, operational effort, reversibility and unanswered questions. Mark missing information as unknown. Do not recommend an option unless the provided evidence supports that recommendation.
This is useful when stakeholders discuss different advantages without agreeing on criteria. Check that the table treats both options consistently and does not convert missing information into a favourable score.
Keep the final decision with the authorised person. A table can organise evidence without establishing which trade-off your organisation should accept.
5. Close a meeting with a draft action register
Ask the tool to distinguish decisions, proposals and unresolved work.
Turn these approved meeting notes into a draft register with action, explicitly named owner, stated deadline and unresolved question. Leave owner or deadline blank if not supplied. Separate agreed actions from suggestions. Do not mark an item complete.
Check the register with the participants through your normal process. A name mentioned during discussion is not necessarily the owner of an action, and a suggested date is not necessarily a commitment.
If the meeting involved sensitive employment or personal information, use only an authorised workflow. A useful prompt does not override information-handling rules.
What to do when a prompt returns a weak answer
First identify the kind of failure. Missing information calls for clarification. An unsupported fact calls for checking and correction. A formatting problem calls for a specific revision. Treating every issue as “make it better” hides the cause.
For the action-register prompt, suppose the tool lists a person as owner because they discussed the item. Return to the notes and ask for explicit evidence that the person accepted responsibility. If that evidence is absent, leave the field blank and resolve it through the normal meeting process.
For the comparison prompt, watch for a favourable score assigned to an option with missing information. Ask for the unknown to remain visible rather than substituting a neutral or optimistic estimate.
If the tool cannot perform the requested task in your account, stop and confirm the available features. Do not keep submitting the same instruction or granting additional access without understanding the limitation.
The useful question is whether the prompt helps you complete a checked task. A polished response that requires extensive repair is a reason to narrow the task or use your existing method.
Keep the prompt that survives review
Try one prompt first. Record the useful result, correction needed and whether the complete task became easier.
Save a prompt only after it works on a second relevant example. Include the check that caught the most important error, so future use does not depend on memory.
Visit PiOfAI, the personal AI workflow guide and clear manager communication to connect a good prompt with better work.
AI-assisted researched guidance from PeakBelt. Hypothetical examples are labelled in the text. See our editorial approach.