Copilot prompts for project management: status, risks, delays

Eight Copilot Chat prompts for project management: task list, delay notice, risk register and end-of-project review, from Beginner to Expert level.

By QDNA · Published on September 10, 2026 · Updated on September 10, 2026

In brief. A project manager splits work up, informs, scores risks and reports. These eight prompts range from the task list to the end-of-project review, with two prompts per level of the course. They share one rule: Copilot names no owner and no due date that is not in your notes, and writes "to be specified" when the information is missing. The figures of a review are confronted with the attached documents, never taken for granted.

When to use it

Without a paid licence, Copilot Chat does not read your tracking tool: export, prepare a clean sheet and attach the file at the end of the prompt. A Copilot Page keeps a deliverable, a Notebook gathers the sources of a recurring file.

To adapt one of these prompts, open the composer and choose the "Project manager" template in the list of job templates.

Beginner

1. Task list to organise a seminar (Beginner)

BeginnerContext. A 60-person seminar in three months, with a budget and external speakers, to be split into dated tasks.

Create a task list for organising a 60-person seminar. Context: date in three months, on [date], room to be booked, four external speakers, budget of [amount] euros, team of three people. Expectations: ten tasks, one per line, with a suggested owner among "logistics", "communication", "content", and the execution week counted back from the date. Format: table task, owner, week.

Expected result. Ten tasks dated backwards from the event, ready to import into the tracking tool.

Mistake to avoid. Forgetting the target date: the deadlines become inconsistent and the list is unusable.

Related lesson. Writing a good prompt: the four ingredients

2. Raw notes into a tracking table (Beginner)

BeginnerContext. Your workshop notes must become an action table, with no rewording that betrays the original.

Turn the notes below into a four-column table: Action, Owner, Due date, Status. One row per action. Keep the original wording for the Action column. If a piece of information is missing, write "to be specified" in the cell instead of guessing.
Notes: [pasted text]

Expected result. An action table faithful to the notes, with the gaps visible instead of filled in.

Mistake to avoid. Saying "tidy this up": Copilot rewords the actions and invents owners.

Intermediate

3. Delay email, then targeted follow-up (Intermediate)

IntermediateContext. A work package is delivered three weeks late; the first version is too long and you follow up precisely.

Write a delay notification email to the stakeholders. Context: work package three of the [name] project delivered three weeks late, cause: waiting on a supplier, impact: none on the final date, measure taken: [measure]. Expectations: 100 words, transparency about the cause, factual tone, a three-row table delay, cause, action. Then, if I reply "shorter", rewrite in 60 words keeping the table and the cause.

Expected result. A factual email with the cause named, and a second tightened version that keeps the table.

Mistake to avoid. Hiding the cause of the delay: stakeholders always find out, and the follow-up "it's too long" removes the table.

Related lesson. Iterating: the first answer is a draft

4. Weekly status report with a sample bullet (Intermediate)

IntermediateContext. A prompt template reused every week, whose format is fixed by a sample bullet.

Role: assistant to the project manager. Goal: write the weekly status report of [project name] for [recipients]. Format: three sections "Done this week", "Planned next week", "Risks and needs", five bullets at most per section, 150 words in total. Rule: one bullet = one action + one owner. Sample bullet: "Acceptance testing of the invoicing module completed (Karim)". If my notes do not name an owner, write "to be specified".
Source: my notes for the week below. Notes: [paste]

Expected result. A status report in the same format from one week to the next, reusable without modification.

Mistake to avoid. Rewriting the prompt on the fly every week: the format shifts, and the recipients lose their bearings.

Related lesson. Giving examples and a role to set the style

Advanced

5. Scored and justified risk register (Advanced)

AdvancedContext. The project sheet and the incident history are attached; every score must be justified by a fact.

From the attached files project_sheet.docx and incident_history.xlsx only, proceed in four steps and wait for my validation after each. Step 1: identify the ten main risks. Step 2: score each risk for probability and impact from one to four. Step 3: propose a mitigation for each risk scored three or more. Step 4: justify each score with a fact from the history, quoted with its date; write "no fact" if the history contains nothing. Format: table risk, probability, impact, mitigation, justification.

Expected result. A register of ten risks where every score points to a dated incident or to an acknowledged "no fact".

Mistake to avoid. Accepting scores without justification: the register becomes decorative and nobody challenges or updates it.

6. Presentation in three prompts, finalised in a Page (Advanced)

AdvancedContext. An attached report must become eight slides, in three validated prompts, then laid out in a Copilot Page.

Prompt A: From the attached report.pdf, propose a plan in eight slides: title and one-sentence key message per slide, for an executive committee that has 15 minutes. Wait for my validation.
Prompt B: For each slide of the validated plan, write three bullets of 12 words at most and give the figure or the quotation from the report that supports it, with the page.
Prompt C: Review the eight slides: flag every bullet without a reference page and every bullet over 12 words.

Expected result. Eight slides where every bullet points to a page of the report, laid out in a shared Page.

Mistake to avoid. Asking "make me a presentation of this report" in one prompt: the bullets are not sourced and the plan was never validated.

Expert

7. End-of-project review audited against the documents (Expert)

ExpertContext. The initial proposal, the actual schedule and the meeting minutes are attached; the review confronts promised and delivered.

Act as a programme director. From the attached files initial_proposal.pdf, actual_schedule.xlsx and meeting_minutes.docx only, proceed in five steps. Step 1: confront promised and delivered deliverables, with the page of the proposal for each deliverable. Step 2: calculate the schedule and workload overruns and show the calculation. Step 3: draw five transferable lessons, each tied to a fact from the minutes. Step 4: write the two-page summary for the committee: results, overruns, lessons, recommendations. Step 5: check every figure of the summary against the documents and list the unexplained discrepancies. Format: compliance table, then summary, then discrepancies.

Expected result. A defensible review, every figure checked against a document, with the unexplained discrepancies listed.

Mistake to avoid. A complacent review that does not confront the figures with the documents: Copilot smooths things over if the check is not imposed.

8. Have the status report prompt improved (Expert)

ExpertContext. You submit the team's status report template to have it rewritten block by block, then you arbitrate.

Improve the prompt below for Copilot Chat. Rewrite it according to the blocks Role, Goal, Context, Sources, Format, Constraints, Verification. For each modification, explain in one sentence the problem it fixes. Add a robustness rule: what the prompt must do if the week's notes are empty or if they concern two projects. End with the questions to ask me to complete the prompt.
Prompt: [current template pasted]

Expected result. A prompt rewritten block by block, robust to empty or mixed notes, with the changes justified.

Mistake to avoid. Adopting the rewrite wholesale: keep what fixes an observed problem and reject the rest in writing, with a reason.

Related lesson. Asking Copilot to improve your prompt

Frequently asked questions

Can Copilot Chat read my project tracking tool?

No: without a paid licence, it works on the web and on the files you attach. It does query your mailbox, your calendar and your meetings from Outlook, through lexical indexing. For the tracking tool, export the task list or the schedule, prepare a clean sheet and attach the file at the end of the prompt.

How do I keep a project's context from one week to the next?

A long conversation drifts. Write a prompt template with the fixed elements, paste the week's notes at the end, and gather sources and prompts in a Copilot Notebook, available for Copilot Chat since June 2026 according to Microsoft.