Curriculum
In this quick-win lesson, you will see how Microsoft 365 Copilot can transform a collection of rough notes into a structured action plan. You will also learn why the generated result must be reviewed and verified before it is used.
Copilot can help organize scattered ideas, reminders and discussion notes into a more useful format. A clear prompt can guide it to identify tasks, priorities, responsibilities, deadlines and missing information.
However, Copilot may misunderstand the notes or introduce details that were never provided. Compare the generated action plan with the original material and correct any unsupported assumptions.
Use the supplied practice material or your own non-sensitive notes to create an action plan. Review the first result, provide a follow-up instruction and save the verified version in your course workspace.
Complete the accompanying Action Plan—My Result download to record your original notes, prompts, corrections and final result.
A professional-looking action plan is not necessarily accurate. Always verify its tasks, owners, deadlines and priorities against the original notes before relying on it.
Here is our first practical result. These notes are incomplete, inconsistent and not ready to act on: “Friday webinar. Need slides. Ask Maya to approve title. Registration page maybe Wednesday. Jordan owns social? Check captions. Dry run Thursday. Need follow-up email.” Your job is to turn them into a plan you can review—not to let AI make unchecked decisions.
Use Microsoft Copilot or Copilot Chat available to you. The exact entry point may differ. A personal account, eligible work or school account, or another supported Microsoft Copilot experience can complete this text-based exercise. Do not use real confidential notes. Copy the supplied fictional notes from FB_S01L02_Rough_Notes_Starter.docx.
Enter: “Turn the notes below into an action plan for a small webinar team. Do not invent owners or dates. Use columns for Action, Proposed owner, Due date, Dependency, and Questions to confirm. Put unknown items as ‘Confirm’ and list assumptions separately.
Notes: [paste the supplied notes].” Pause and examine the result before accepting it.
The prompt names the deliverable, audience and format. More importantly, it forbids invented owners and dates. The word “Confirm” creates visible uncertainty rather than hiding it. The request for assumptions gives you a review target. This is not advanced prompt engineering; it is clear delegation with boundaries.
Check each action against the original notes. Is “Maya approves the title” represented? Is Jordan shown as confirmed or uncertain? Did Copilot invent a webinar platform, budget, speaker or exact time? Check that every date came from the notes. Mark unsupported additions in orange and verified facts in blue.
If the answer invented details, enter: “Revise the plan. Remove every owner, date or dependency that is not explicitly stated. Replace it with ‘Confirm’. Keep a separate Questions to confirm list.” If the answer is too broad, ask: “Split any action that contains more than one deliverable, but do not add new work.”
For a personal alternative, use the supplied weekend-event notes. Ask for an action plan with Task, Who, When, Needed information and Status. Do not include addresses, financial account information or private attendee details.
Use the starter file, run the first prompt, and complete the Verification Log. Save the response in S01L02_Action_Plan_My_Result.docx. Record at least one verified item, one uncertainty and one revision.
Use the second set of notes in the workbook. Write your own prompt that preserves unknowns. Your submission is the prompt, output and a three-line review: what was correct, what required confirmation, and what you changed.
If you cannot access Copilot, use the reference output and perform the verification exercise manually. If the response ignores the requested table, restate the output schema at the end of the prompt. If details are invented, quote the restrictive instruction again. If content is blocked by workplace policy, use the downloadable fictional file and do not bypass the policy.
You have completed a real workflow and, just as importantly, checked it. The next quick win adds grounding: you will summarize a source document and trace each important claim back to the source.
Not a member yet? Register now
Are you a member? Login now