Campaign handoff practice kit These documents are fictional. The expected response is an illustration prepared for this guide, not output from an executed Copilot test or a reported client result. B1 — Approved campaign brief, version 3 Approved · 28 September 2026 The B2B marketing-operations webinar is scheduled for 22 October 2026 at 14:00 UTC. The audience is in-house B2B marketing teams. Approved channels are email and organic LinkedIn. Paid media is not approved. The campaign manager prepares the invitation. No quantitative productivity promise has been approved. D1 — Invitation draft, version 1 Outdated draft · 24 September 2026 The invitation gives 20 October 2026 as the webinar date. It promises a 20% time saving without supporting evidence and suggests paid LinkedIn promotion. This draft does not override the approved brief B1. M1 — Campaign meeting notes Discussion and recorded actions · 29 September 2026 The team discusses moving the webinar to 29 October, subject to speaker availability. No decision is recorded. The creative lead will revise the headline by 5 October. Legal review is required before external publication. The notes record no owner or deadline for confirming speaker availability. A prompt you can adapt Prepare a short internal handoff note for the marketing team using only B1, D1 and M1. Treat B1 as the approved baseline, but log every conflict: a newer discussion does not automatically replace an approved decision. Separate confirmed facts, recorded actions, proposals and unknowns. Support each decision with a source ID and the relevant passage. Include dates, owners and deadlines only when recorded; mark missing fields as unknown. Flag the unsupported 20% claim and the unapproved paid channel. Recommend any next decision separately from actions already assigned. Do not send, publish or change the calendar. Produce a concise draft for human review. Illustrative expected note The links below point to the fictional source cards above. They are review references, not citations generated by Microsoft Copilot. Approved baseline The webinar remains scheduled for 22 October 2026 at 14:00 UTC for in-house B2B marketing teams. Email and organic LinkedIn are approved. B1 states the date and channels; the later discussion does not record a replacement decision. Sources: B1, M1 Date conflict requiring a decision D1 says 20 October; M1 proposes 29 October. Recommended next step: the campaign manager should obtain date confirmation before sending the invitation. This is a recommendation, not an action already assigned in the sources. Sources: B1, D1, M1 Recorded action The creative lead will revise the headline by 5 October, as recorded in M1. The owner and deadline for speaker confirmation are unknown. Sources: M1 Correct the invitation draft Remove the unsupported 20% time-saving claim and paid LinkedIn suggestion from draft D1 before reusing it. Do not introduce them into the approved plan: B1 approves neither the quantitative promise nor paid media. Sources: D1, B1 Still open Speaker availability, a decision on changing the date, and legal approval before external publication remain unresolved. M1 requires legal review; it does not say that review has passed. Sources: M1 Before anyone uses the note 1. Open each referenced passage and check the date, approval status and meaning, rather than just the presence of a link. 2. Confirm the event date with the appropriate decision-maker, clarify who will confirm speaker availability and by when and obtain legal approval before external publication. Check recipients and any restricted detail before sending. Judge the draft against five pass-or-fail checks Use the same approved examples for a manual draft and an AI-assisted draft. Record drafting, verification and correction time, missed errors and whether the reviewer accepts the result. A faster first draft alone is not evidence of return on investment. Source fidelity: Every material statement is supported by the right source and passage. An unavailable source is disclosed, not replaced by a guess. Conflicts and unknowns: The three dates remain distinguishable. The proposed 29 October date is never presented as approved. Actions, dates and ownership: The headline action is intact. No speaker-confirmation owner or deadline has been invented. Approved claims and channels: The unsupported 20% promise and unapproved paid promotion are excluded from usable campaign copy. Audience and data safety: The note is suitable for its recipients and contains no restricted detail or implied publication approval. Any critical error blocks reuse. Repeat the exercise with a missing source and conflicting versions. If permissions matter, an authorized colleague can run a separate test with appropriate test documents and their own access. Fix the source or review process before expanding the pilot. Product documentation checked on 2 October 2026 Copilot Chat overview and available information: https://learn.microsoft.com/en-us/copilot/overview Microsoft 365 Copilot licensing requirements: https://learn.microsoft.com/copilot/microsoft-365/microsoft-365-copilot-licensing Microsoft 365 Copilot data, privacy and security: https://learn.microsoft.com/en-us/microsoft-365/copilot/security-microsoft-365-copilot Data protection for work and school Copilot Chat accounts: https://support.microsoft.com/en-US/Privacy/data-protection-when-using-microsoft-365-copilot-chat-for-work-or-school Copilot Chat file uploads and frequently asked questions: https://learn.microsoft.com/en-us/copilot/faq Writing effective Copilot prompts: https://support.microsoft.com/en-us/microsoft-365-copilot/get-better-copilot-responses-with-great-prompting Copilot capabilities, references and limitations: https://learn.microsoft.com/en-us/microsoft-365/copilot/microsoft-365-copilot-application-card Web search, Bing queries and administrative controls: https://learn.microsoft.com/en-us/microsoft-365/copilot/manage-public-web-access