Lesson 00.1: Welcome and Your First Safe Copilot Result

Module 00 · Lesson 00.1

Welcome: produce one safe result you can verify

Learn the course method in eight minutes. You will give Copilot fictional source material, ask for a precise work product, and check every important statement before accepting it.

LevelBeginner

Time8–12 minutes

AccessAny approved Copilot chat surface

DeliverableVerified decision-and-action brief

By the end of this lesson

You will have completed the smallest version of the workflow used throughout the course.

Name the source Copilot may use.
Specify the output and its non-negotiable constraints.
Trace decisions, owners, and dates back to the original notes.
Correct at least one weakness or confirm that no unsupported claim was added.

The job: turn rough notes into an action brief

A project coordinator needs a clean recap. The notes are incomplete on purpose. A good answer preserves those gaps instead of quietly filling them.

Source material · fictional meeting notes

- The team chose the smaller pilot group.
- Priya will prepare the onboarding email by Friday.
- The help-centre update needs an owner.
- Launch timing depends on security review.
- Mateo will send the pilot list; no date was agreed.
- The next check-in is Tuesday at 10:00 a.m. Pacific.

Work brief

Use only the meeting notes I provide.

Create a concise project brief with:
1. Decisions
2. Actions in a table with owner and due date
3. Dependencies
4. Open questions

Do not infer missing facts. Write “Not provided” when an owner or date is absent.
After the brief, add “Source check” and list anything you could not verify from the notes.

This brief contains Microsoft’s four useful prompt ingredients without turning them into a ritual:

Ingredient	Where it appears	Why it matters
Goal	Create a project brief.	Copilot knows the job, not merely the topic.
Context	The notes are the complete meeting record for this task.	The answer should not silently import outside assumptions.
Source	Use only the supplied notes.	You can trace every important claim.
Expectations	Four sections, an action table, explicit unknowns, and a source check.	The answer has a testable definition of done.

Inspect the output before revising it

Do not judge the answer by tone or formatting. Compare it with the six source lines.

Statements the answer may make

The smaller pilot group was chosen.
Priya owns the onboarding email; the notes say Friday.
Mateo owns the pilot list; no due date is provided.
Security review is a launch dependency.
The next check-in is Tuesday at 10:00 a.m. Pacific.

Statements the answer must not make

A specific calendar date for Friday or Tuesday.
An owner for the help-centre update.
Security approved the launch.
A pilot size or participant count.
A launch date.

If Copilot invented a fact, use a correction prompt.

Point to the unsupported statement and restate the evidence boundary. Do not merely ask for a “better” answer.

Correction prompt

Revise the brief.

You added this unsupported statement: “[paste the exact statement].”
The notes do not establish that fact.

Remove the claim, preserve the uncertainty, and check the revised brief line by line against the source notes. List every change you made.

Use the four-part validation pass

Microsoft’s current validation guidance asks whether the result is sourced, verified, contextual, and resilient. Use those checks before copying the brief into email, a Page, or a project record.

Source. Can you point to the exact note supporting each decision, action, date, and dependency?
Verified. Are names, owners, time zones, and dates copied correctly? Did Copilot invent a calendar date?
Context. Did the brief preserve the security dependency and the missing help-centre owner?
Resilient. If the security review slips or Friday means a different date, does the brief expose the dependency instead of hiding it?

Deliverable and scoring guide

Save the final brief in your course folder. If Copilot Pages is available, you may save it to a Page; otherwise a plain document or note is enough.

Check	Pass	Revise
Evidence	Every substantive statement is traceable to the notes.	The brief adds owners, dates, approvals, or quantities.
Unknowns	Missing owner and date fields say “Not provided.”	The answer hides gaps or assigns work.
Usefulness	A teammate could see decisions, actions, dependencies, and questions at a glance.	The output is a generic paragraph.
Review record	You noted what you checked and what you changed.	You saved only the final answer with no review trace.

Knowledge check

Why should “Friday” remain Friday instead of becoming a calendar date?

The notes do not identify the meeting date, so the corresponding calendar date cannot be verified. Converting it would add information that is not in the source.

What is wrong with asking “Summarize these notes”?

It states a broad goal but leaves the useful format, evidence boundary, missing-data behavior, and review requirement undefined. A summary could still be acceptable, but it would be harder to assess.

When is the lesson complete?

When you have a source-grounded brief, a line-by-line evidence check, and a saved note describing any correction—not when Copilot first produces polished text.

I produced the brief, checked it against the notes, and saved the verified version.

Official Microsoft sources

Verified July 30, 2026.