Use Claude Cowork to Review a Project Handover Pack Before Sharing

A handover pack can look finished while still hiding a missing owner, a stale date, or a claim that never appeared in the source notes. This Claude Cowork workflow produces a review report before anyone shares the pack.

Evidence label: Documentation-based guide. The files and findings below are fictional and illustrative. No Claude Cowork run is claimed.

What you need

Use Claude Cowork on a paid plan and a surface where it is available. Anthropic’s current help page says Cowork is available on paid plans, with access varying by desktop, web, mobile, and workspace settings. Claude is also rolling out a unified Chat and Cowork experience, so your message box may not show a separate Cowork selector.

Use two fictional files: a source note and a draft handover. Keep them in a folder that contains no real client or employee data. This review asks for a report only. It should not move, rename, edit, or share files.

Fictional input

Create handover-source.txt:

Project Atlas handover notes, 2026-10-20

Current status: pilot is open to the internal support team.
Next review: 2026-10-27.
Owner for the pilot: Maya Chen.
Open item: confirm whether the support rota covers weekends.
Access note: the dashboard is available to the support team, but the notes do not name the access group.

Create handover-draft.txt:

Project Atlas handover

Status: pilot is live for all customers.
Next review: 2026-10-27.
Owner: Maya Chen.
Support: the team covers all weekend requests.
Dashboard access: Support-All.

The draft changes the audience, turns an open question into a result, and adds a group name that is absent from the source. Those are the findings the review should surface.

Review brief

Open Claude and start a Cowork task if your account shows that option. If your account has the unified experience, describe the same bounded task in the message box and follow the current controls. Add both files to the approved task context, then paste this brief:

Review handover-draft.txt against handover-source.txt.

Write a file named handover-review.txt with these sections:
1. Supported details, each with a short source quote.
2. Conflicts, each showing the draft wording and the source wording.
3. Missing or unsupported details.
4. Approval questions for the project owner.
5. A release decision containing only: HOLD FOR REVIEW or READY FOR HUMAN CHECK.

Rules:
- Read both files. Treat handover-source.txt as the reference for this review.
- Do not edit, rename, move, upload, email, or share either source file.
- Do not decide whether the project is ready for customers.
- Do not invent an owner, date, access group, coverage schedule, or status.
- If the source does not state something, write NOT STATED.
- Keep source quotes short and exact.
- Stop after creating handover-review.txt and show me its contents for review.

Before starting, confirm that the task scope is read-only. Do not grant a write or sharing permission just to make the review convenient.

Illustrative output

This is an editor-written target, not a captured Cowork result:

Supported details
- Next review: "Next review: 2026-10-27."
- Pilot owner: "Owner for the pilot: Maya Chen."

Conflicts
- Draft says "pilot is live for all customers." Source says "pilot is open to the internal support team."
- Draft says "the team covers all weekend requests." Source lists weekend coverage as an open item.

Missing or unsupported details
- Dashboard group "Support-All": NOT STATED in the source.
- Customer-wide availability: NOT STATED in the source.

Approval questions
- Is the pilot still limited to internal support?
- Does the support rota cover weekends?
- Which group has dashboard access?

Release decision
HOLD FOR REVIEW

Acceptance checks

The review is usable when:

It catches the customer-wide status conflict.
It keeps weekend coverage as an open question.
It flags Support-All as unsupported.
It quotes the source for supported dates and ownership.
It creates a report without changing the two input files.
A named human owner can answer the approval questions.

Troubleshooting

Claude cannot see a file: check the task’s approved file context and confirm the file finished uploading before restarting the bounded review.
It edits the source: stop the task, restore the original from a known copy, and rerun with an explicit read-only boundary. Do not treat the edited file as the source of truth.
It merges source and draft claims: require a source quote beside every supported detail and label absent evidence NOT STATED.

Limits and next step

Cowork can handle multi-step knowledge work, but its output still needs review. Anthropic documents unique risks for Cowork because it can work with files and carry out tasks. Use the smallest folder and permission scope that can answer the review question.

TRY: a fictional or approved low-risk handover pack with a clear owner.

SKIP: production folders, personal data, or any task that would need automatic sharing or deletion.

USE: the review file as a release gate for a human owner, not as proof that the handover is correct.

For a source-linked Claude Project workflow, see separate launch facts from assumptions. For one practical AI-for-work lesson each week, get The Weekly Verdict.