Brief Cowork like a capable employee

Describe the finish line first

Begin with the deliverable. Name who will use it, why it matters, what form it should take, and where it belongs. This gives Cowork a stable target while it plans the steps in between.

Avoid asking it to ‘look at this’ or ‘help with marketing.’ Ask for a specific result such as a two-page campaign brief for the owner, a cleaned spreadsheet with a change log, or five support-reply drafts ready for review.

• Outcome: the exact result you want at the end.
• Audience and purpose: who uses it and what decision it supports.
• Sources: the files, folders, or connected tools that are authoritative.
• Format and location: file type, structure, length, and filename.

State the permission boundary

Cowork can read information and, when tools permit it, take actions. Those are different risk levels. Tell Claude whether the task is read-only, may create a draft, may edit a copy, or may change a live system.

For a new workflow, keep the boundary at ‘draft only.’ Explicitly prohibit sending messages, publishing content, changing source records, spending money, or deleting files. Use manual approval when the task touches a new connector, sensitive information, or an action that is difficult to reverse.

Define how the result will be checked

Acceptance checks make quality visible. Ask Cowork to cite the filename or connected source behind important claims, surface missing facts, and perform a second pass focused on errors rather than style.

Do not ask Claude to declare its own work accurate and stop there. A person who understands the business should spot-check the evidence—especially names, amounts, dates, customer promises, policy statements, and calculations.

• Every factual claim traces to an approved source.
• Missing or conflicting information is flagged, not invented.
• The output follows the requested structure and length.
• A named person checks consequential facts before use.

Turn corrections into better instructions

After each run, sort your corrections into three buckets: missing source material, an unclear rule, or a task that was too broad. Fix the cause in the brief instead of adding a vague warning to ‘be more accurate.’

Save two or three examples that represent easy, normal, and awkward cases. Re-run them whenever the instructions change. That small test set helps you see whether a new version improved the process or quietly broke something that used to work.