Cowork scenarios

Review my week since Monday: the meetings in my calendar (including transcripts and recaps where available), my sent and received email, and the Teams conversations I am part of.

Create a one-page Word document called "Week in review – [date]" with:
1. Decisions made this week: who made them and where, with a link to the meeting, email or chat.
2. Commitments I made to others and commitments others made to me, with due dates. Highlight anything overdue.
3. Topics that keep coming up or are escalating.
4. Open questions nobody has answered yet.
5. My three priorities for next week, each with a one-line reason.

Then draft a short email to [my team / distribution list] covering points 1, 3 and 5. Show it to me before sending. If a source was unavailable or something is unclear, say so instead of guessing.

Run this every Friday at 15:00.

I was away from [start date] to [end date]. Go through the email and Teams messages I received in that time, including channels where I was @mentioned.

Sort everything into four groups and show them as a table in this session:
- Needs my decision or reply this week: who is waiting, what they need, the deadline.
- Can be delegated: suggest who to hand it to, based on who has handled similar topics.
- For information only: one line each.
- Already resolved by others while I was away: one line each, so I don't reopen it.

For the first group, draft short replies in my usual tone and save them as drafts in Outlook. Don't send anything. Finally, list the meetings in my calendar for the next five working days that I need to prepare for, and why.

I will be out of office from [start date] to [end date]. [Name] covers for me.

Using my email, Teams chats, calendar and the files I worked on in the last three weeks, create a Word handover document with:
1. Work in progress: status, next step, deadline and who else is involved.
2. Anything due while I am away, and who should handle it.
3. Meetings during my absence: which ones to cancel, which ones [Name] should attend, and a short brief for each of those.
4. Contacts who may reach out, and what each of them is likely to need.
5. What I should look at first when I am back.

Then draft: an out-of-office reply (Czech and English), an email to [Name] with the handover document attached, and a short note to my team. Show me all drafts before anything is sent or changed.

Use the transcript and chat of my meeting "[meeting name]" from [date].

1. Write a summary of no more than ten bullet points: decisions, key arguments, and anything that changed since the previous meeting in this series.
2. Create a table of action items: task, owner, due date. Where the meeting didn't name an owner or a date, mark it "to be agreed" instead of inventing one.
3. List open questions and risks raised.
4. Draft a follow-up email to all attendees with the summary and the action table.
5. If a next meeting was agreed, propose an invitation.

Show me the email and the invitation before sending.

Every working day at 7:30, prepare my briefing as an interactive HTML page.

Use my calendar for today and tomorrow, email and Teams messages from the last 24 hours, and the documents in [folder or SharePoint site].

At the top: at most three things that need my decision or reply today, each with one recommended next step.
Then three sections:
- Meetings: what each one is for, what I should prepare, conflicts and double bookings.
- Commitments: deadlines in the next five days, things waiting on me, and things I am waiting on.
- Signals: topics with unusually high activity, and important threads that have gone quiet for more than a week.

Link every item to the email, chat, meeting or file it comes from. Keep it short enough to read in three minutes. Focus on work and decisions, not on judging individual people.

Prepare the pre-read for the [leadership / board] meeting on [date].

Sources: [results file or report], the project status reports in [folder], and email and Teams discussions from the last [four] weeks about the topics on the agenda: [agenda or list of topics].

Use our template [template file] and create a Word document with:
1. Summary on one page: results against plan, main changes since the last meeting.
2. Projects: status, risks and what is needed from the board.
3. Decisions requested at this meeting, each with options, a recommendation and its impact.
4. Open actions from previous meetings and their status.

Cite the source of every figure. Where numbers differ between sources or something is missing, list it in a separate section "To be checked before sending". Don't share the document with anyone; I will review it first.

I lead [area] with these workstreams: [list of workstreams and their leads].

From the last two weeks of email, Teams channels [channel names], meeting recaps and the files in [SharePoint site], build an interactive dashboard with one card per workstream:
- Status (on track / at risk / off track) and the evidence for it.
- What moved forward, what is blocked and by whom or what.
- Dependencies on other workstreams.
- What the workstream needs from me.

Below the cards, list the three most important cross-team risks and a proposed action for each. If a workstream has had little recent activity, say so rather than assuming it is on track.

Run this every Monday at 8:00 and tell me what changed since the previous week.

I need to decide [the question, for example: whether to move our customer support to a new tool by Q2].

Research it using our internal documents in [folder or site], relevant email and Teams discussions, and reputable public sources on the web.

Create a Word decision brief of at most four pages:
1. The question and why it matters now.
2. Two to four options, each with benefits, costs, risks and what it would take.
3. A comparison table.
4. Your recommendation and the conditions under which it would change.
5. Sources: every claim linked to its internal or public source. Mark which claims rest on a single source.

Separate facts from assumptions. If the evidence is thin, say so clearly instead of filling the gap.

Turn my notes in [file or OneNote page] into a memo and a short deck for [audience] about [topic].

Use the data in [Excel file] and draw on my earlier materials on the same topic in [folder] for structure and tone.

1. Memo in Word, at most two pages: the key message in the first paragraph, then the supporting arguments with numbers, then what I am asking for.
2. A PowerPoint deck of at most eight slides based on the memo, using the template [template file], with one message per slide and charts made from the Excel data.
3. A list of gaps: claims without data, numbers that don't match, and questions the audience is likely to ask.

Write in my style; match my recent documents on this topic. Save both files to my OneDrive and don't share them yet.

I am meeting [customer] on [date] at [time].

Before the meeting: from my email, Teams, meeting history with this customer, files in [account folder] and [CRM: account and open opportunities], write a one-page brief:
- Where the relationship stands and what has changed in the last [three] months.
- Open opportunities, open issues and unanswered questions on both sides.
- Who is attending from the customer side and what each of them cares about.
- Two or three things I should be ready to address, with suggested talking points.

After the meeting: set up a task that runs one hour after the meeting ends. From the transcript, list decisions, actions with owners and dates, and risks, then draft (1) a follow-up email to the customer in my usual tone and (2) a short internal update for the account team.

Show me the brief, the summary and both drafts before anything is sent or shared. Cite your sources and name anything you could not find.

Attached is an RFP from [customer]: [RFP file]. The deadline is [date].

1. Extract every requirement and question into an Excel compliance matrix: ID, requirement, mandatory or optional, our answer, compliance (full / partial / no), source, confidence (high / medium / low), owner for review.
2. Answer each item using only our approved materials: [folder with previous RFP answers, product documentation, security and certification documents]. Cite the source document for every answer.
3. Where no approved source exists, leave the answer empty, set confidence to low and suggest who should answer (product, legal, security, pricing).
4. Write a summary in Word: overall fit, the riskiest requirements, and questions to clarify with the customer.
5. Draft emails to the owners of the open items with their questions and the deadline [internal date].

Show me the drafts before sending. Never invent capabilities, certifications or prices.

Every Monday at 7:00, prepare an account update for [customer].

Combine:
- Public news from the last week: results, leadership changes, acquisitions, strategy announcements, regulatory issues.
- Internal signals: email and Teams traffic with the customer, support issues raised, and [CRM: opportunity changes].

Write a one-page brief:
1. What changed, with links to sources.
2. What it may mean for us: risk, opportunity or nothing.
3. One to three recommended actions, each with a draft message I could send (to the customer or internally).

Mark which items come from public sources and which from internal ones. If nothing significant happened, say so in one sentence instead of filling the page.

I have a quarterly business review with [customer] on [date]; the contract renews on [renewal date].

From [usage or service reports], support cases, email and meeting history from the last quarter, the contract in [contract file] and [CRM data]:
1. Summarise usage and adoption trends, support issues and how they were resolved, and the relationship (who we meet, who we don't).
2. Write the value story: what the customer achieved, backed by numbers they will recognise.
3. List risks to the renewal and how to address each.
4. Create a PowerPoint deck of at most ten slides for the meeting in [template], and a one-page internal prep note with the commercial position and what I want to agree.

Mark every figure with its source. Don't contact the customer; I will review everything first.

Every Friday at 13:00, review my open opportunities closing this quarter [CRM view or Excel export].

For each one, check recent activity in email, Teams and meetings with the customer. Flag an opportunity as at risk when: there has been no customer contact for [14] days, the close date has moved, the decision maker hasn't been involved, or open questions are unanswered.

Create an Excel table of at-risk deals: customer, value, close date, reason for risk with evidence, recommended next step. Then draft a short check-in email for each of the three biggest at-risk deals and propose CRM updates (close date, stage, next step) for me to approve.

Don't change anything in the CRM and don't send anything without my approval.

We are launching [product or offer] on [date]. The brief is in [brief file]; approved messaging is in [messaging document]; brand guidelines are in [guidelines].

Create a launch kit organised by audience:
1. Customers: a blog post (600–800 words), web page copy, and three social posts.
2. Sales: a one-page value proposition, an FAQ with the ten most likely customer questions, and objection handling.
3. Internal: a short announcement email to employees.

Use only claims supported by the brief and messaging documents, and list any claim you would need to verify. Keep the terminology consistent across all pieces. Save everything to [folder], then propose a 30-minute review meeting with [names] and show me the invitation before sending it.

Review the performance of the [campaign] campaign using [analytics export or report] against the targets in [campaign plan].

1. Show results by channel, audience and creative against target, as a table with a chart.
2. Identify what is working, what is lagging, and the most likely reasons, with the data behind each.
3. Recommend the three changes with the biggest expected impact (budget, channel, message or content), each with an owner and a date.
4. Draft a short update for [stakeholders] with the findings and recommendations.

Separate what the data shows from what you infer. Show me the update before sending.

Run this every [Tuesday] at [9:00] until [end date].

[Competitor] has just [announced / launched / changed]: [link or description].

1. Research the announcement and reactions to it on the web, and find what we already have on this competitor in [competitive intelligence folder] and recent internal discussions.
2. Write a one-page assessment: what changed, who it affects among our customers, where we are stronger and where we are exposed. Back every claim with a source.
3. Recommend a position (respond, ignore or wait) and why.
4. Based on that position, draft: an internal note for sales with a short talk track and answers to likely objections, and three key messages for [communications / PR].

Be factual about the competitor; no disparaging language. Show me everything before sharing.

Analyse customer feedback from [period]: survey results in [file], support case themes in [export], meeting notes with customers in [folder] and relevant Teams discussions in [channel].

1. Identify the top five themes, with how often each appears, its trend and two or three representative quotes (anonymised).
2. Separate what customers praise from what frustrates them.
3. For each theme, recommend a concrete action and who in the organisation should own it.
4. Create a short PowerPoint deck (at most eight slides) and a one-page Word summary.

Don't include customer names or personal data. State how many responses or cases each theme is based on.

A new case has come in from [customer]: [case description or the email].

Pull together everything relevant: previous cases and how they were resolved, recent email and Teams conversations with the customer, the service agreement and SLA in [contract folder], and similar issues in our knowledge base [site or folder].

Write a one-page case brief:
1. Customer and contract: SLA, response times, entitlements.
2. History: related past cases and what fixed them.
3. The likely cause, with the evidence, and what still needs to be confirmed.
4. Immediate next steps and who should take them.
5. Anything sensitive to be careful about (an open escalation, a complaint, an upcoming renewal).

Cite each source. Don't contact the customer.

Here is a customer's question: [paste the email or case text].

1. Find the best-matching articles in our knowledge base [site or folder] and list them with a one-line reason for each.
2. Draft a reply in [language] that explains the solution in plain language, step by step, adapted to this customer's situation. Use only steps that appear in the approved articles.
3. If the articles don't fully answer the question, say what is missing and draft a short internal question for [team or expert].
4. Under the draft, list which article each step comes from.

Keep a friendly, professional tone, at most 200 words. Save the reply as a draft; don't send it.

Every working day at 8:00 and 13:00, take the open case export in [file or folder] and the SLA terms in [SLA document].

1. Calculate the time left to breach for each case and sort the queue by it.
2. For the cases that breach within [8] hours: the owner, what is blocking the case (based on the case notes and related email and Teams messages), and the recommended action.
3. For cases waiting on the customer, draft a short, polite reminder.
4. Show the result as an interactive table, and post a three-line summary to the Teams channel [channel] after I approve it.

Don't change any case or contact any customer without my approval.

I need to escalate case [case number] for [customer] to [team or person].

From the case notes, email and Teams history and any meeting transcripts about this case, create a Word handover document:
1. Summary in five sentences: the problem, its business impact on the customer, and the current state.
2. Timeline: what was tried, when, by whom, and the result.
3. What the customer was promised and by when.
4. Open hypotheses and what has already been ruled out.
5. The recommended next step for the new owner.

Then draft a handover message to [team or person] and a short update to the customer explaining who now handles the case and what happens next. Show me both before sending.

The [month] close figures are in [Excel file]; the budget and the previous forecast are in [file].

1. Find all variances against budget and against forecast above [threshold: amount or %], by cost centre and account.
2. For each, look for the explanation in email and Teams discussions with the budget owners and in the commentary files in [folder]. Quote the source.
3. Where no explanation exists, list the variance as open and draft a short question to the budget owner.
4. Write a variance commentary in Word (at most two pages) for [CFO / leadership], with a summary table at the top.

Don't change the figures. Mark clearly which explanations are confirmed by a source and which are your interpretation. Show me the questions before sending them.

Every [Monday] at [8:00], create the finance flash for [leadership team].

Use the latest figures in [Excel file or folder], the plan in [plan file] and finance discussions in [Teams channel] from the past week.

Format: one Word page plus one summary slide.
1. Headline KPIs against plan and the previous period: [list of KPIs].
2. The three biggest movements and their drivers.
3. Exceptions that need a decision or action, with an owner.
4. What to watch next week.

Keep the same structure every time so readers can compare. If the source file hasn't been updated since the last run, stop and tell me instead of reusing old figures. Show me the draft before it is sent to [distribution list].

The auditor's request list is in [file]. Our supporting documents are in [folders or SharePoint sites].

1. Create an Excel tracker: request ID, request, matching documents (with links), status (complete / partial / missing), owner, due date.
2. For each request, find the documents that best support it and summarise in one sentence what each one shows.
3. Where evidence is missing or incomplete, say exactly what is missing and draft a request to the likely owner.
4. Write a short status summary for [finance lead]: how many items are complete, the riskiest gaps, and what needs a decision.

Don't share any document with the auditor; I will review the package first.

[Regulation or law, for example a new reporting requirement] takes effect on [date].

1. Research the official text and reliable commentary on the web. Summarise the main obligations, deadlines and penalties in plain language, citing the exact articles.
2. Search our internal documents [policies, processes, contracts folder] for the areas it affects and list them.
3. Create an Excel action tracker: obligation, affected process or document, gap, proposed action, owner (department), deadline.
4. Write a two-page Word memo for [management / legal / compliance].

This is not legal advice: mark every point that needs review by a lawyer, and never present an interpretation as the text of the law.

[Name] joins as [role] in [team] on [start date]; their manager is [manager].

Using our onboarding materials in [HR site or folder], the team's documents and the manager's calendar:
1. Create a 30-60-90 day plan in Word: goals, key people to meet, training and the first deliverables.
2. Propose a first-week schedule: introduction meetings with [names], training sessions, and time for setup. Check the calendars for conflicts and show me the proposed invitations; don't send them yet.
3. Draft a welcome email from the manager and a short introduction message for the team channel [channel].
4. Make a checklist for the manager and IT (equipment, access, accounts), based on our onboarding checklist.

Use only information from our materials; mark anything that needs confirming with HR.

We are introducing a new [policy, for example hybrid working] effective [date]. The policy is in [document]; the previous version is in [document].

1. Summarise what changes for employees in five bullet points, comparing it with the previous version.
2. Write an FAQ with the 15 questions employees are most likely to ask, answered in plain language. Base every answer on a specific section of the policy and cite it.
3. Look through [HR mailbox or Teams channel] for questions people have already asked on this topic, and make sure the FAQ covers them.
4. Draft an announcement email for all employees and a shorter version for managers with tips for team discussions.

Where the policy doesn't answer a question, don't invent an answer; list it as "for HR to decide". Show me the drafts before sending.

Microsoft announced this change: [Message Center ID and text, or a link to it].

1. Explain in plain language what changes for our users, when, and whether anyone has to do anything. Separate what Microsoft states from what you infer.
2. Check our internal documentation and training materials in [IT site or folder] for anything this change makes outdated, and list it.
3. Draft: a short email or news post for users ([language]), a Teams message for [champions channel], and three to five FAQ entries for the help desk.
4. If admins have to act (a setting, a policy, a deadline), list the steps and the deadline separately for the IT team.

Keep the user text under 200 words and free of jargon. Show me everything before it is sent or published.

Whenever someone @mentions me in the Teams channel [incident channel], read the latest messages in that channel and prepare an update:

1. For leadership: three lines covering what is affected, the current status and the next expected update.
2. For users: a short plain-language notice about what doesn't work, a workaround if one has been mentioned, and when the next update will come.
3. A timeline of the incident so far, kept in one Word document in [folder] and appended with each update.

Use only facts stated in the channel; never estimate a fix time unless someone in the channel has given one. Prepare the messages for my approval; don't post or send anything yourself.