You’ll practice: Prepare an update and action list; distinguish drafting, approval, and sending.
The idea
A smooth draft can be wrong. I check details that change what someone does: arrival time, room, remote access, and commitments. Tone comes after accuracy.
Check D4 against D1–D3, not its confidence or another assistant's agreement. Use the relevant notes, message, or policy. [S1]
I ask for an explanation before showing the answer. Studies involving coding and school mathematics distinguish task completion from understanding. They did not test this course. Our approach is to try first, compare the answer, and explain one correction in your own words. [S3, S4]
Worked example
Correct the claim, not just the wording
First attempt
Refreshments are approved, so everything is ready.
A more useful version
Refreshments are awaiting the budget owner's written approval. Noor will request the decision; no decision deadline has been agreed.
This preserves the open decision and follow-up owner without inventing a deadline.
Your turn
Try it yourself
Review D4. Mark the misleading claims, then write a corrected update and action list. Check missing information as well as incorrect sentences.
Read the fictional source documents
You are helping prepare an internal team update and action list for Noor, the workshop organizer. Everyone and everything in this packet is fictional. The exercise reference date is 19 September 2026. Use D1–D3 as sources. D4 is a deliberately flawed draft to review, not evidence of what happened.
Early planning meeting notes
The team wants a hybrid workshop on Thursday 8 October 2026 to agree three ways to make team projects easier to coordinate.
The initial suggestion is 10:00–11:00 Pacific time in the Cedar room. These are proposed arrangements, not a final booking.
Plan for 12 people onsite and 8 joining remotely: 20 people in total. These are planning numbers, not a confirmed attendance record.
Noor is organizing the workshop. Eli will prepare the agenda. Sam will collect accessibility requests. No deadline has been agreed for Eli's agenda or Sam's collection of requests.
Refreshments have been requested. No spending decision or quote is recorded.
Organizer's confirmed update
I have confirmed the workshop for Thursday 8 October 2026, 14:00–15:00 Pacific time, in the Maple room for onsite participants. This replaces the earlier suggested time and room.
We are still planning for 12 people onsite and 8 remotely. The workshop purpose and the assignments to Eli and Sam are unchanged.
The remote joining link is not available yet. I will add it by Tuesday 6 October 2026 at 16:00 Pacific time.
The agenda deadline has not been agreed. Refreshments are still awaiting the budget owner's written approval; I will ask for that decision. No deadline for that decision has been set.
Please prepare the team update and action list as a draft for me to review. I have not approved the final message for distribution. Do not send it yet.
Short team communications policy
For workshop logistics, the organizer's latest written confirmation replaces earlier proposed times and rooms. A later draft or an unattributed suggestion does not replace that confirmation.
Spending on refreshments requires the budget owner's written approval. A request, a pending decision, or a request to make an announcement is not that approval.
The organizer must review and approve the final team update before it is sent.
A hybrid-workshop update must include remote joining information or clearly state that the link is pending and identify who will provide it.
If a deadline has not been agreed, write 'not yet agreed' and ask the responsible person to confirm it. Do not choose a date and present it as a commitment.
A convincing draft that needs review
Subject: Team workshop: everything is ready
Our team workshop is confirmed for Thursday 8 October, 10:00–11:00 Pacific, in the Cedar room. All 20 people will attend onsite.
Refreshments have been approved. Eli will finish the agenda by Friday 25 September.
This update has been approved and sent, so there is nothing else to follow up.
Make: A draft for Noor's review, with source labels in your working notes and an explanation of one correction.
- Correct the time, room, and onsite/remote planning numbers.
- Remove invented approval, deadline, and sent-message claims.
- Include the pending remote link, its owner, and its stated due date.
- Keep all remaining actions visible without inventing deadlines.
Give me a hint
Your update should explain attendance and open decisions. Check every word that implies completion.
Compare with an example answer
Draft for Noor's review: Our hybrid team workshop is on Thursday 8 October, 14:00–15:00 Pacific, in the Maple room for onsite participants. We are planning for 12 people onsite and 8 remotely. We will agree three ways to make team projects easier to coordinate. The joining link is pending; Noor will add it by 6 October at 16:00 Pacific. Refreshments await the budget owner's written approval. Eli is preparing the agenda; its deadline is not yet agreed.
Actions: Noor: add the joining link by 6 October, 16:00 Pacific; ask the budget owner for a refreshments decision, deadline not yet agreed; review and approve the final update before sending. Eli: prepare the agenda and confirm its deadline. Sam: collect accessibility requests and confirm the deadline. No deadline is supplied for Noor's final review or for Eli and Sam's work.
Why D4 needs repair: it uses the replaced time and room, turns a 12/8 plan into 20 confirmed onsite attendees, invents refreshments approval and Eli's 25 September deadline, omits remote joining information, and falsely claims approval, sending, and no remaining work. D1–D3 support the corrected version. Nothing has been sent in this exercise.
Pause and reflect. Explain one correction without reading the model answer. Which source settles it, and what would go wrong if it stayed unchanged?
Check your reasoning
A new situation
Use the habit somewhere else
Now suppose the budget owner sends a written refreshments approval. No new deadline, joining link, or message approval is supplied. What changes?
Show answer guidance
Change only the refreshments status and close Noor's request-for-decision action. Keep the pending remote link and its due date, unagreed agenda/accessibility deadlines, and Noor's final-message review and approval. Refreshments approval does not approve or send the team update.
Research and source notes
Reviewed Sep 19, 2026. These sources inform the exercises; they do not establish results for this course.
S1 · Get started writing prompts in Microsoft Copilot
What it supports: Start with a clear goal, add useful context, expectations and sources, iterate, and verify responses against trusted material.
In this course: Lessons 1–3 use a bounded assignment, a labeled source packet, and claim-by-claim review.
Limits: Product guidance, not measured proof of productivity or this teaching method. The course needs no Copilot account; access to organizational work data in Copilot depends on the product entitlement.
Revisit when: Recheck when the guidance, intended tool, or organization's permitted data use changes.
S2 · Learn about prompts for Gemini in Docs, Sheets, Slides, Vids & Forms
What it supports: Use natural language, a specific task, relevant context and an appropriate format; review and refine. Not every suggested prompt component is mandatory.
In this course: Lessons 1–2 use ordinary wording and a compact context note rather than a required prompt formula.
Limits: Vendor recommendations for Google features, not evidence that one format works best everywhere. Product eligibility is separate; no Gemini account is required for the exercises.
Revisit when: Recheck if Google revises the guidance or if a lesson starts depending on a specific product feature.
S3 · How AI assistance impacts the formation of coding skills
What it supports: In a randomized study of 52 mostly junior Python developers learning Trio, the AI group averaged 50% on an immediate quiz versus 67% without AI; the completion-time difference was not statistically significant.
In this course: Ask learners to make an attempt, explain a correction, and distinguish task output from understanding.
Limits: Small coding study with an immediate assessment. Interaction patterns were qualitative associations, not randomized teaching methods. It does not establish lasting skill loss, results for everyday writing, or effectiveness of this course.
Revisit when: Revisit after relevant replications, longer follow-up, or evidence from comparable employee writing tasks.
S4 · Generative AI without guardrails can harm learning: Evidence from high school mathematics
What it supports: Assisted practice improved in both AI conditions. Ordinary answer-oriented assistance harmed later unassisted exam performance; the teacher-informed tutor largely avoided that harm without showing an unassisted advantage over the control.
In this course: Offer a first attempt, an optional hint, an answer explanation, and a changed-case question; keep assisted and independent observations distinct.
Limits: One high school in Turkey, mathematics, a Fall 2023 deployment, and short-term outcomes. This was not employee training or a test of static feedback. It does not demonstrate this course's learning effect.
Revisit when: Revisit when studies test comparable workplace tasks, longer-term outcomes, or different assistance designs.