Explore our Prompt Library to see real‑world examples of how to use Copilot effectively. These ready‑to‑use prompts are designed to help you get better results faster, using the GCSE method to keep requests clear, focused, and practical.

Create a clear step‑by‑step process from the information provided. I’m documenting how this should be done consistently, so use the details here and format it as an SOP with headings and numbered steps.

Rewrite this process so it’s easier for someone new to follow. Use the existing instructions and keep the wording simple, clear, and practical.

Summarise this process into a quick checklist. I need something easy to follow day‑to‑day, so use the full process and output short tick‑box steps.

Review this process and highlight any gaps or unclear steps. Use the current document and list what needs clarification in bullet points.

Turn this information into an action plan. I need to organise work across tasks, so use the details provided and present clear steps, owners (if mentioned), and next actions.

Create a prioritised task list from these updates. I’m planning the next workload, so use the information provided and order tasks by urgency and impact.

Identify dependencies or blockers in this plan. Use the details included and list what could slow progress, with suggested ways to remove the blockers.

Create a simple timeline or sequence of work from this information. Use the source content and present the output as ordered stages or phases. 

Summarise these updates into a short status report. I’m sharing progress with others, so use the content provided and format it as “What’s done, what’s next, risks/issues”.

Create a weekly operations update based on this information. Use the details here and keep it clear, professional, and easy to scan.

Turn this data into key operational highlights. I need quick talking points, so use the source provided and output 5–7 bullet points.

Rewrite this update so it’s clearer and more structured. Use the existing text and keep it concise without losing important information.

Summarise these meeting notes into clear outcomes. I need a quick record, so use the notes provided and format it as decisions, actions, and open questions.

Create a handover note from this information. Someone else may pick this up, so use the content provided and keep it clear, factual, and structured.

Pull out action items from these notes and turn them into a checklist. Use the source content and include any deadlines or owners if mentioned.

Write a short recap I can share with the team. Use the meeting or chat notes provided and keep the tone professional and easy to understand.

Identify risks mentioned in this information and summarise them clearly. I’m reviewing operational health, so use the source provided and output risks with a brief impact description.

Highlight recurring issues in these updates. Use the information provided and group issues into themes so we can address root causes.

Suggest improvements to this workflow. I want to reduce effort and delays, so use the process details provided and recommend practical changes.

Review this operational plan and point out where efficiency could be improved. Use the source content and list suggestions with quick reasoning.

Create a reusable template based on this format. I want to standardise future work, so use the structure shown and output a clean template with placeholders.

Rewrite this document to match a consistent operations style. Use the existing content and apply clear headings, concise language, and a logical flow.

Turn this repeated task into a standard checklist we can reuse. Use the source content and format it as a simple, consistent tick list.

Summarise the key points I need to make a decision here. Use the information provided and present the output as a short list of options, pros/cons, and a recommendation if possible.

Explain this operational situation in plain language so I can brief someone else. Use the source content and keep it short, clear, and non‑technical.