Copilot Cowork usage charges start 1 July for frontier-enrolled organisations. Here’s how to prepare

Download our value guide for Frontier-enrolled organisations

Create a practical Copilot Cowork testing toolkit for our organisation and generate it as actual downloadable files — not as text in the chat. I want real, finished outputs: a working Excel tracker, Word documents, a PowerPoint template, and a combined PDF. Save everything so I can download it.

Context:
We are a Frontier-enrolled organisation and Copilot Cowork usage charges start from 1 July. We want to use the current testing window to understand where Cowork creates value, what different tasks cost, how much review effort is needed, and where other Copilot experiences may be a better fit.

The purpose of this toolkit is to help our champions and Copilot power users test Cowork with real work, capture useful evidence, and build a practical business case for where Cowork should be used after usage charges begin.

Files to generate:
These are the actual outputs I want.

1. A Word (.docx) file for the champion launch message — Artefact 1
2. A Word (.docx) file for the testing plan — Artefact 2
3. A working Excel (.xlsx) tracker with real column headers, live formulas, and a populated example row — Artefacts 3 and 4
4. A Word (.docx) file for the tool comparison checklist — Artefact 5
5. A Word (.docx) file for the output review questions — Artefact 6
6. A PowerPoint (.pptx) one-page leader summary template — Artefact 7
7. A Word (.docx) file for the next steps checklist — Artefact 8
8. A combined PDF pack of all the document-based artefacts — Artefacts 1, 2, 5, 6, 7 and 8 — for easy sharing, in addition to the editable source files. Keep the Excel tracker as its own .xlsx.

Artefact 1 — Champion launch message
Format: Word .docx, ready to paste into Teams or Viva Engage.

Create a short, friendly post for Copilot champions and power users that:
- explains why we are testing Cowork now
- explains this is a short testing window before usage charges begin
- encourages people to test real work, not made-up examples
- asks people to capture cost, value and review effort
- tells people to share useful examples, misses and learnings
- feels clear, human and practical

Artefact 2 — Testing plan
Format: Word .docx, one page.

Include:
- purpose of the testing period
- who should be involved
- what types of work should be tested
- what should not be tested
- what evidence needs to be captured
- how examples and learnings should be shared
- how findings should be reviewed

Artefact 3 — Excel testing tracker
Format: Excel .xlsx, working file.

Create a usable Excel tracker with these columns as real headers:
- Test ID
- Date
- Tester name
- Team or business area
- Task name
- Task description
- What Cowork was asked to do
- Output created
- Model used, if visible
- /cost shown
- Usual time taken
- Time taken with Cowork
- Time saved
- Review or editing effort required
- Output quality rating
- Confidence in the output
- Was the task repeatable?
- Was Cowork the right tool?
- Would another Copilot experience have been better?
- Suggested next step
- Notes or lessons learned

Build live formulas into calculated columns for:
- Time saved
- Value score
- Repeatability score
- Recommended action

Include short notes explaining the rating scales, for example 1–5, so the formulas make sense.

Artefact 4 — Example completed tracker row
Format: Inside the same Excel .xlsx file.

Add one realistic, fully completed example row. It must show a Cowork-suitable task: a larger piece of work with multiple steps, more context and a substantial output to review. Do not use a quick question, a simple summary, or a basic content-drafting task.

Artefact 5 — Tool comparison checklist
Format: Word .docx.

Create a short checklist to help testers decide whether Cowork was the right place to do the work, comparing Cowork with:
- Copilot Chat
- Researcher
- PowerPoint
- agents
- skills or plugins

Artefact 6 — Output review questions
Format: Word .docx.

Create a short set of reflection questions to answer after each Cowork task, covering:
- accuracy
- usefulness
- missing information
- assumptions
- review effort
- time saved
- cost
- whether the task was worth the credits

Artefact 7 — Leader summary template
Format: PowerPoint .pptx, one page.

Create a one-page summary template to brief leaders after the testing period, including:
- what we tested
- who was involved
- where Cowork showed value
- where Cowork was not the best fit
- early cost patterns
- examples worth scaling
- training or guardrail needs
- recommendations for access, limits and next steps

Artefact 8 — Next steps checklist
Format: Word .docx.

Create a short checklist for what to do after testing, including:
- credit allocation considerations
- usage limits
- guardrails
- training needs
- champion support
- possible skills, plugins or future agents
- what needs leader approval

Tone:
Clear, practical and easy for non-technical business users to follow. Avoid hype. Make it feel like something a change team could share with champions, power users and leaders.

Formatting:
Use clear headings within each file. The Excel tracker must have usable headers and working formulas. The launch message must be ready to paste into Teams or Viva Engage. The leader summary must fit on one page. Generate all files and confirm they are saved and ready to download.