Runsheet · presenter reference
Cowork: from a launch decision to work done
One industry-neutral story. Turn a brief into launch assets, build an interactive readiness dashboard, handle a late change and prepare a request in another app.
≈25 min planned 25 min of core sections 8 sections 6 anchors Any team introducing a new employee service verified 2026-09-25
Employee Help is fictional. Inputs are prepared; Cowork output generation and browser execution still need rehearsal. The new portal form is a local preview until deployed.
↯Pivot map — read the room, not the script
Start here
Read the six-step route and prepare the exact attachment set.
They ask whether Copilot can make a deck too
Yes. Show the native PowerPoint agent, with the same initial sources.
They want something they can click and use
Build the readiness dashboard, then filter and open a task.
They ask what happens when things change
Reveal the training-delay update. Watch the dashboard and launch pack change together.
They want the action-focused Cowork finish
Fill a reviewed request in a signed-in app, without saving it.
They ask about email or meeting context
Use delivered fictional mail, or the genuine recording once created. Do not pass notes off as a recording.
AWhat you need open
1
Four source files only. Extract before attaching; do not upload the ZIP because the later update would spoil the reveal.
Also placed in Colin's OneDrive > Employee Help Demo > Inputs. No sharing permissions were added.
2
21 September proposal: six teams, 330 users. This is the old plan.
Attach first, with Planning Meeting Notes.docx. Both are one page.
3
23 September decision: two-team pilot, 100 users, launch gates and one unresolved retention question.
Attach with Project Brief.docx. Authored fictional notes, not a real meeting transcript.
4
24 September snapshot: 24 tasks across six teams. Eight pilot tasks, 16 later-phase tasks. Read me, Teams and Tasks sheets.
Add for the dashboard. The workbook is an input, not the demo's analytical centrepiece.
5
25 September change: accessibility fixed, training moved past the launch target.
Keep out of the first attachment set. Reveal in section 4.
6
A short role-play for Colin, Kadji and Karin if you want a genuine recorded-meeting version.
Presenter-only material. Do not attach this script as though it were an actual transcript.
7
Expected scope, counts, date traps and portal fields. These are authored-data controls, not recorded model results.
Presenter screen only. Never give this to Cowork or Copilot.
BPre-flight
- Use Colin in the agreed Caldova demo profile. All business content is fictional and industry-neutral; the lab account name is just the hosting environment.
- Confirm Cowork opens, licensed Copilot's PowerPoint agent is available, and the source files open as Colin.
- Prepare three tabs: Cowork, Copilot's PowerPoint agent and the blank Employee Help readiness review form. Keep this runsheet on a separate presenter screen.
- For browser automation use Cowork on the web in Edge, signed into the same work profile as the target app. A web-page sign-in alone does not prove the Edge profile requirement is met. InPrivate is not suitable.
- Confirm the tenant's Cowork Browsing setting and required Edge policy are already enabled. Do not change policies in front of the audience.
- The new portal scenario must be deployed before using its production URL. For now the blank-form preview is http://127.0.0.1:4417/?view=form&scenario=employee-help-readiness.
- Rehearse the real prompts below. Save actual completed Cowork outputs and their task link as a dated fallback. No prebuilt presentation or dashboard is supplied in this pack.
- Do not attach Latest Update.docx until section 4. Do not let broad enterprise search pull in the update or earlier demo outputs during the baseline run.
- Keep originals unchanged. Every generated deliverable is a new output file. Stop browser work before Save draft or Submit for review.
- Use 25 September 2026 as the review date and 12 October 2026 as the target inside this fictional exercise, even when presenting later.
!Things that will bite you
Make the story about work, not model scoring
Lead with an employee service that needs a launch pack, a useful dashboard and a review request. Only compare the PowerPoint task; do not spend the session running identical analyses twice.
The current scope is two teams, not six
The meeting overrides the earlier brief: IT Support and Workplace Services, 100 users. The later-phase teams stay visible in the tracker but outside pilot readiness counts.
More tasks complete can still mean a launch hold
After the update the pilot rises from 3/8 to 4/8 complete. But training is now two days after the target, so the overall decision remains on hold. This is the dashboard's useful moment.
An interactive snapshot is not a live system
The dashboard should show a source date and explain that changes require a new reconciliation. Do not claim automatic refresh, multi-user persistence or system integration unless you separately build and prove it.
No blank field gets an invented answer
Confirmed launch date and approved retention period remain blank. A target date and a training date are not launch approval.
Fictional email is optional and not sent yet
The prepared email fixtures have markers EH-01, EH-02 and EH-03. Until delivery is confirmed, use the equivalent source documents. Do not tell the audience those messages already exist.
A prompt is a request, not proof
The portal opening as Colin proves manual access. It does not prove Cowork can drive that browser. If browser use is unavailable, show the form yourself and say that the automated step was not demonstrated.
0 The story and the order
We are introducing one place for employees to ask for help. The original plan was too broad. I need a launch pack that reflects what was actually agreed, a dashboard I can use, and a request ready for review.
| Order | Do | Copy | What the room sees |
|---|---|---|---|
| 1 | Attach Project Brief + Planning Meeting Notes in a new Cowork task | P01, then P02 | A six-slide presentation, announcement draft and action plan |
| 2 | Use the same two files in Copilot's PowerPoint agent | P03 | Copilot can create the deck too |
| 3 | Return to Cowork; attach Launch Readiness Tracker | P04, then P05 | A working readiness dashboard |
| 4 | Reveal Latest Update in the same Cowork task | P06 | The dashboard and assets reflect a new launch blocker |
| 5 | Review the source-to-form mapping | P07 | Dates, owners and blanks before browser action |
| 6 | Open the blank portal form through Cowork | P08 | The app gets filled, then Cowork stops for review |
What you are preparing, and what Cowork must produce
Inputs and portal form are prepared. Cowork must generate the deck, announcement, action plan and dashboard. A saved backup must come from a genuine rehearsal, never a hand-built imitation.
1 Create the launch pack
Do this
- Attach Project Brief.docx and Planning Meeting Notes.docx from Employee Help Demo / Inputs. Wait for both attachment chips to load.
- Do not attach the tracker or Latest Update yet. Keep enterprise-wide discovery out of this task.
- Send P01. Look at the scope and date distinction before spending time making assets.
- If the interpretation is correct, send P02. Leave it running and move to the Copilot comparison if it needs time.
P01. Establish the current briefcopies as one block
Use only the attached Project Brief.docx and Planning Meeting Notes.docx for this fictional Employee Help service rollout. Do not search my mailbox, meetings, other files or the web. Tell me the latest agreed scope, user count, target date, launch gates, named owners and unresolved decisions. Explain where the 23 September meeting supersedes the 21 September proposal. Cite the source headings and decision IDs. Treat a target as a target, not approval. Do not create files or take actions yet.
Stop if this is wrong
Two teams, 100 users, target 12 October, all eight pilot gates required. The other four teams are unapproved later work. OQ01 retention is unresolved.
P02. Create three usable assetscopies as one block
Now create a launch pack using the same two sources and the scope we just checked. Produce Employee Help - Leadership briefing.pptx with exactly six slides including the title: purpose, approved pilot scope, employee journey, readiness gates, ownership and next decisions. Use a restrained professional design with editable text and shapes, clear diagrams instead of text walls, and source references in speaker notes. Also create Employee Help - Announcement draft.docx, under 200 words and clearly marked DRAFT - DO NOT SEND, and Employee Help - Action plan.xlsx listing action IDs, owners, due dates, dependencies and unresolved questions. Keep the pilot at 100 users across IT Support and Workplace Services. Describe 12 October as conditional. Do not invent readiness results, retention settings or approvals. Create new output files only; do not modify sources, send, publish or share anything. Show your work plan and report any missing output.
Open these outputs
Open the actual PPTX, not its filename in chat. Show two slides, an editable shape and the source note. Open the announcement to show DRAFT and the action plan to show named owners. Keep the action plan as a supporting output, not another finance demo.
2 Show that Copilot can make the PowerPoint too
If I just need a presentation, Copilot can do that too. Let me show it, rather than claim that making slides is unique to Cowork.
- Open the PowerPoint agent under Agents or Tools in licensed Copilot.
- Attach the same Project Brief and Planning Meeting Notes. Do not give it Cowork's finished deck or Latest Update.
- Send P03. Open the real PPTX when it completes. If the agent is unavailable, say so; that is an access issue, not a capability verdict.
- Return to Cowork. The next step is to continue the wider job in the existing task.
P03. Copilot PowerPoint comparisoncopies as one block
Use only the attached Project Brief.docx and Planning Meeting Notes.docx. Create Employee Help - Leadership briefing.pptx with exactly six slides including the title: purpose, approved pilot scope, employee journey, readiness gates, ownership and next decisions. Use a restrained professional design with editable text and shapes, clear diagrams instead of text walls, and source references in speaker notes. The 23 September decisions override the earlier proposal. Keep the pilot at 100 users across IT Support and Workplace Services. Describe 12 October as conditional. Do not invent readiness results, retention settings or approvals. Create a new presentation only; do not change sources, send, publish or share anything.
3 Build something the room can click
Now give me one screen I can use to run the pilot. I want to see what is ready, what is holding it up, and who needs to act.
- Attach Launch Readiness Tracker.xlsx in the same Cowork task. Keep Latest Update out for one more step.
- Send P04. Open the resulting HTML preview, rather than accepting a textual dashboard description.
- Select Workplace Services, choose a status, then clear the filters. Open T06 and inspect the owner, due date and reason it is blocked.
- Send P05 as the live refinement. Click the new launch-blocker view and check it does not count later-phase tasks.
P04. Build the interactive dashboardcopies as one block
Using the attached Launch Readiness Tracker.xlsx plus the two Employee Help source documents already in this task, build Employee Help - Readiness dashboard.html as a self-contained interactive dashboard. Use 25 September 2026 as the fixed review date. Default to the approved two-team pilot, not all six teams. Show user scope, completed pilot tasks out of eight, explicit Blocked status, overdue incomplete tasks, and incomplete launch gates as separate measures. Include working team and status filters, a task list and click-to-open details with task ID, owner, due date, dependencies and source evidence. Keep the four later-phase teams accessible in a separate view without mixing them into pilot KPIs. Use a clean accessible layout, text labels alongside colours, keyboard-operable controls, and a visible source snapshot date. Embed the data and scripts in the file; no external libraries, network calls, tracking or automatic refresh claims. Do not invent training completion percentages or a confirmed launch date. Keep original files unchanged. Return a real HTML file I can preview and use.
P05. Refine it livecopies as one block
Add a 'What could stop launch?' view to the dashboard. Show only incomplete pilot gates, their owners and any unfinished prerequisites, with the clearest next action. Keep tasks that have explicit Blocked status distinct from tasks that are merely incomplete or dependency-held. Include OQ01 retention as an unresolved review question, not a made-up task completion. Do not count the blocked Finance Operations or Sales Operations later-phase tasks as pilot blockers. Keep the full-task view and a clear-filters control.
Baseline controls before the update
| Measure | Expected |
|---|---|
| Pilot population | 100 users / two teams |
| Pilot tasks | 8; 3 complete; 37.5% |
| Explicit Blocked status | T06 only |
| Overdue pilot tasks | T02 and T06 |
| Later phase | 16 tasks / four teams / 230 users; excluded from pilot KPIs |
4 Reveal the change and keep the outputs aligned
A new update just arrived. One problem is fixed, but training now falls after the target launch. Update the work we already prepared and tell me what needs a decision.
P06. Apply the later evidencecopies as one block
Read the newly attached Latest Update.docx dated 25 September. Apply only its explicit changes to the dashboard and generated launch pack; preserve the original inputs. Record a before-and-after change log by task ID and source update ID. Refresh the dashboard, leadership deck, announcement draft and action plan so dates, scope, status and open questions agree. Keep the original tracker snapshot distinguishable from the reconciled state. Show whether the existing target can proceed and which decision is needed. Do not invent a new launch date or assume the training date is one. Keep the announcement unsent and clearly on hold. List each changed output and any part you could not update.
Point at these changes, not just a new summary
| Before | After | Why it matters |
|---|---|---|
| T06 Blocked | T06 Complete on 25 September; original due date retained | Completion evidence fixes one problem without rewriting history |
| T07 In progress; due 7 October | T07 Blocked; due/training 14 October | Training is two days after the unchanged 12 October target |
| 3 of 8 complete | 4 of 8 complete; still on hold | A percentage is not a go-live decision |
| 2 overdue pilot tasks | 1: T02 | Completed T06 is no longer overdue |
| Six-team proposal | Still only two pilot teams / 100 users | The update does not authorise expansion |
The moment to pause
Open the dashboard, then the deck's next-decisions slide and the announcement. All three should say the target is at risk/on hold, never 'new launch: 14 October'. Show OQ01 still open.
5 Carry the decision into an ordinary application
Deployment gate
The form is prepared locally at http://127.0.0.1:4417/?view=form&scenario=employee-help-readiness. P08 uses the production portal URL and must not run until that new scenario has been deployed. Local form QA is not a Cowork browser rehearsal.
P07. Inspect the mapping before any browser actioncopies as one block
Using the four original Employee Help files and their dated decisions, prepare a field mapping for an Employee Help readiness review request. Include service name, request owner, requested reviewer, approved scope, pilot teams, pilot users, target launch date, confirmed training date, readiness decision, outstanding gates, accessibility status, confirmed launch date and approved audit-log retention days. Cite the source for every populated field. Leave unstated or unapproved values blank and put open questions in notes. Do not open or change the portal yet.
Check before proceeding
| Field | Expected value |
|---|---|
| Owner / requested reviewer | Colin Ballinger / Kadji Bell |
| Scope / teams / users | Two-team pilot / IT Support and Workplace Services / 100 |
| Target / training | 12 October 2026 / 14 October 2026 |
| Readiness | On hold - launch gates incomplete |
| Outstanding gates | T02, T04, T07, T08 |
| Accessibility | Complete |
| Confirmed launch / retention days | Both blank |
- Once deployed, open the blank Employee Help form as Colin in the same signed-in Edge profile. Do not open the presenter answer key.
- Return to Cowork on the web and send P08. Handle first-run consent or sign-in yourself if requested.
- Watch actual browser progress. Use the visible switch-to-tab control if offered; inspect the populated form.
- Confirm that the target and training dates occupy different fields, the scope is 100 users, and the two unknown fields are blank.
- Stop without saving or submitting. The request is ready for human review, not an approved launch.
P08. Run only after the new production form is deployedcopies as one block
Use the browser to open https://app-caldova-cowork-browser-demo-437371.azurewebsites.net/?view=form&scenario=employee-help-readiness and fill the Employee Help readiness review form from the source-backed mapping we just reviewed. Use only the four approved Employee Help files and the mapping, not other records, the portal's demo kit, answer key or page source data. Use ordinary labelled controls. If existing unsaved entries are present, stop rather than clearing them. Leave Confirmed launch date and Approved audit-log retention period blank. Put OQ01 and the training-versus-target conflict in Follow-up notes. Stop before Save draft, Submit for review or any other persistence or approval action. Do not send a message, change another system or bypass a permission restriction. Show me the populated form and wait.
The work has reached another application, with the uncertainty kept intact. I can now review the request rather than copy the same facts into it myself.
Bound the claim
This is a browser-execution demo, not a claim that every possible integration is exclusive to Cowork. The app is an ordinary demo form and does not call a model. Only call it a Cowork success after Cowork actually populated it.
6 Optional email and recorded-meeting versions
Email version
Three fictional messages are prepared for Colin, Kadji and Karin with markers EH-01, EH-02 and EH-03. They are not yet sent. EH-01 repeats the two-team decision, EH-02 reports the training delay and accessibility completion, and EH-03 asks for readiness review. They do not grant access to the OneDrive folder.
E01. Discover only delivered demo messagescopies as one block
Find only messages whose subject contains [DEMO EH-01], [DEMO EH-02] or [DEMO EH-03] about Employee Help. List the subject, sender and actual received time so I can confirm the exact messages. Treat the scenario dates stated in the body separately from message delivery dates. Do not use unrelated mail, create files or send anything. If the messages are absent, say so and stop.
E02. Use the selected update email instead of attaching Latest Updatecopies as one block
Use only the EH-02 and EH-03 demo messages I selected, alongside the Employee Help sources already in this task. Apply their explicitly stated updates to the dashboard and generated assets. Keep the target distinct from the training date, preserve the two-team scope, keep OQ01 unresolved and leave the announcement unsent. Show the source message for every change. Do not use unrelated email.
Recorded-meeting version
Use Optional recording script.txt to record a short fictional planning meeting with consent. Keep its actual recording date. Once the real transcript is available, attach that exact meeting using Add work context instead of Planning Meeting Notes.docx. Run P01's questions against it first. Do not claim that the authored script or notes are a genuine transcript.
Rehearse before using meeting context
- Confirm the saved meeting and transcript are accessible as Colin.
- Check that the transcript actually contains the two-team decision, the 100-user count, the launch gates and OQ01.
- Keep the later update out of the initial meeting so the change reveal remains clear.
- If transcription or discovery fails, use the attached notes and say that you are showing the file-based version.
7 Reset and keep honest backups
- Keep original Inputs unchanged. Start a new Cowork task and a new Copilot conversation for each fresh demonstration.
- Attach only the two initial documents. Add the tracker and update at their numbered steps.
- Store genuine rehearsal outputs separately with product, date and model. Never rename prepared inputs as Cowork outputs.
- Do not leave a portal request saved or submitted. If a later approved rehearsal saves one, identify that exact record for cleanup rather than clearing all requests.
- The earlier finance/handover runsheet remains available as Optional practice. It is no longer the lead Cowork demo.
RIf something goes wrong
The generation takes longer than the audience slot
Start the Cowork task, show its actual plan and progress, then show the Copilot deck comparison while it runs. If needed, open a dated prior Cowork result and clearly identify it as a previous run.
The dashboard is just a screenshot or nonworking mock-up
Use P05 to ask for working filters and task details. Check it in the actual preview surface. Do not describe static pictures as an interactive dashboard.
A portal approval asks to save, submit or post
Cancel the action. This demonstration stops at populated fields. A separately approved later test can save a draft; no blanket approval is part of this runsheet.
The form shows old entries
Stop. Do not overwrite or clear another draft. Open the new blank Employee Help form after confirming that any unsaved work can be discarded.
The browser-control prerequisite is missing
Demonstrate the approved source-to-field mapping manually and name the missing prerequisite. Do not spoof a Cowork run or silently change tenant policy.
Email search returns unrelated lab material
Use the exact EH-01/EH-02/EH-03 markers and attach only the selected messages. Fall back to the four source files.
✓Truth ledger
- All scenario content was newly authored as fictional input. It is not adapted from the earlier recorded launch meeting, real customer information or internal product documents.
- Source dates, task IDs and control answers were checked on 25 September 2026. Product output generation remains to be rehearsed.
- Cowork documents file creation, preview, progress and multiple output files.
- Licensed Copilot's PowerPoint agent also creates editable presentation files.
- Cowork browser actions require supported Edge, the same signed-in profile and tenant/browser policy. They are device-dependent.
- The dashboard requested here is a self-contained interactive snapshot, not an automatically refreshed live data product.
Public sources
- https://learn.microsoft.com/en-us/microsoft-365/copilot/cowork/use-cowork
- https://learn.microsoft.com/en-us/microsoft-365/copilot/cowork/cowork-local-browser
- https://support.microsoft.com/en-us/office/365-copilot-app/get-started-with-word-excel-and-powerpoint-agents-in-microsoft-365-copilot
Last verified 2026-09-25 · re-check by 2026-10-25 · Sush