Start with an output brief
A weekly report needs a time window, approved metrics, a template and a list of open questions. State which values must be calculated and which claims require evidence. This reduces clarification work and exposes whether the available data can answer the task at all.
Separate cloud execution from desktop access
Cowork now also runs in the cloud; the current help describes web and mobile as beta, subject to plan and organizational enablement. Local folders, local connectors and desktop tools still require the connected desktop app. Record which step can keep running with the laptop closed before starting the pilot.
Open the smallest useful data scope
A cleaned copy of the required spreadsheet is enough for the first report. A complete drive or mailbox increases the room for error without automatically improving results. Separate the output folder from source files. You can then inspect which files were created and whether the originals remained unchanged.
Deliberately approve external actions
Official help distinguishes approval modes. In a pilot, sending messages, publishing and changing business systems are separate approval steps. A report may be prepared automatically while sending it to clients stays with its owner. The process also needs a rule to show missing source data as a gap rather than inventing a value.
Review the file before recurring operation
Acceptance compares totals with the source, opens the actual file and checks layout and citations. Schedule repetition only after that review. A failed run should clearly notify its owner and must not present an old output as current. This allows a useful process to scale without simply producing errors more frequently.
Keep it verifiable
Primary sources
- Cowork on web, desktop and mobileSource checked:
- Get started with Claude CoworkSource checked:
