Write effective Cowork requests
Cowork can handle complex, multi-step work, but the quality of its results depends heavily on how clearly you describe what you need. This unit covers practical techniques for writing requests that help Cowork plan effectively and produce results you can actually use.
Lead with the outcome and the deliverables
Cowork works best when you describe the result you need rather than listing individual steps. Instead of telling Cowork how to do the work, tell it what you need at the end—and what you want delivered.
Compare these approaches:
- Step-by-step: "First pull the email threads with Contoso from last week. Then summarize what we discussed. Then find the latest deck in SharePoint. Then draft a one-page briefing and save it as a Word doc."
- Vague outcome: "Help me get ready for Thursday's meeting with Contoso."
- Outcome with deliverables: "Get me ready for Thursday's meeting with Contoso. Pull recent email threads, summarize what we discussed last time, and draft a one-page briefing I can review before the call."
The third version gives Cowork the freedom to plan—but it also tells it what to produce. That combination is the core of an effective Cowork request: describe the result you want, and name the deliverables that will get you there. If you find yourself writing a long list of steps, that's often a signal to reframe as an outcome.
Include context that matters
Because Cowork is grounded in Work IQ, it can already access signals from your email, meetings, files, and chats. Adding specific context to your request (names, timeframes, attached files) helps Cowork narrow in on the most relevant information:
- Name the people involved. "Pull the latest emails between me and the account manager about the Contoso renewal."
- Specify timeframes. "Summarize my inbox from the past week" is more useful than "Catch me up."
- Attach files when helpful. Drag and drop files onto the chat input, or select Add attachments to reference files from OneDrive, SharePoint, or Teams.
- Mention the audience. "Write this for the leadership team" produces different results than "Write this for the engineering team."
Tip
You can enter detailed instructions in your request. If you have a lot of context to share, include it. Cowork can handle long inputs.
Set the right scope
A request that's too broad can lead to unfocused results. A request that's too narrow limits what Cowork can do for you. Aim for a clear goal with defined boundaries:
- Too broad: "Organize everything."
- Too narrow: "Move my 2 PM meeting to 3 PM." (A single action doesn't need multi-step coordination.)
- Right scope: "Look at my calendar for the next two weeks. Identify meetings I could decline or shorten, and propose a plan to free up at least three hours of focus time."
Steer as you go
You don't have to get the request perfect on the first try. Cowork's interactive model lets you adjust as work progresses:
- Answer clarifying questions. When Cowork needs more information, it presents options for you to choose from, or you can type your own answer.
- Send follow-up messages. If you think of something while Cowork is still working, send another message. Cowork adjusts its approach.
Schedule recurring work
Some tasks are worth delegating once and running on a schedule. You can describe both the task and the timing in natural language, and Cowork sets it up for you. For example:
- "Send me a daily briefing every morning at 9 AM."
- "Every Friday at 3 PM, summarize my unread emails from this week."
Cowork confirms the schedule and asks for your approval before activating it. You can manage scheduled prompts from the Scheduled tab in the Tasks view or from the Schedule section in the side panel.
Try it
Pick a real task from this week that involves more than one app or deliverable. Write a request for Cowork that describes the outcome, names the people or files involved, and specifies what you want delivered. You don't have to send it yet—just notice how the request takes shape when you lead with the outcome.