How Freelancers Can Use Claude Cowork to Review a Deliverable Folder Against a Client Checklist

Warning: Cowork can inspect local folders quickly, but it can only judge against the files and instructions you give it. Put the actual brief and promised asset list in the same review workspace.

Cowork requirements at a glance: Claude Desktop, a paid Claude plan (Pro/Max/Team/Enterprise), and Cowork research preview access.

If Claude Cowork is new to you

Start with the Claude Cowork explainer page in the site's Tools menu before you run this workflow. Cowork runs in Claude Desktop and can work on the local files you choose to share. For related examples, see the Claude Cowork tool hub and the Anthropic Workflows series.

Problem and who this is for

Before delivery, you need a boring but important answer: is everything here, is it named correctly, and does it match what you promised. That is exactly the kind of work people rush when they are tired.

This workflow is for freelancers and consultants who deliver a folder of client files and want Cowork to compare it against the brief before the handoff.

Prerequisites

• Claude Desktop with Cowork.
• One local deliverable folder.
• The client brief, statement of work, or promised asset checklist in the same workspace.
• A clear rule about what counts as complete.

How to gather the source material

1. Put the current deliverable files in one local folder.
2. Add the client brief or SOW to the same workspace.
3. Add one plain-text file called delivery-checklist.txt that lists each promised asset and any naming or format requirement.
4. Remove drafts, exports you do not plan to send, and unrelated scratch files.
5. If the client requires a specific archive structure, spell that out in delivery-checklist.txt.

Numbered workflow steps

1) Ask Cowork for a comparison report first

{
  "task": "Compare a local deliverable folder against a client checklist and brief",
  "input": {
    "deliverable_folder": "LOCAL FOLDER PATH",
    "brief_file": "LOCAL PATH TO CLIENT BRIEF OR SOW",
    "delivery_checklist_file": "LOCAL PATH TO delivery-checklist.txt"
  },
  "rules": [
    "Inspect the folder and list what is present.",
    "Compare actual files to the promised assets in the brief and checklist.",
    "Flag missing items, naming mismatches, wrong formats, and likely duplicates.",
    "Do not rename or move files yet."
  ],
  "output": {
    "present_assets": "What exists now",
    "missing_assets": "Promised items not found",
    "format_or_naming_issues": "Anything that violates the checklist",
    "suggested_fixes": "Specific cleanup actions before delivery"
  }
}

2) Fix the flagged items

Do the cleanup yourself or ask Cowork to perform only the specific file operations you approve.

3) Run one last delivery-ready check

{
  "task": "Run a final delivery-ready check on the cleaned deliverable folder",
  "input": {
    "deliverable_folder": "LOCAL FOLDER PATH AFTER FIXES",
    "delivery_checklist_file": "delivery-checklist.txt"
  },
  "rules": [
    "Confirm whether all promised assets are present.",
    "Confirm whether file names and formats match the checklist.",
    "Return a one-screen final verdict only."
  ],
  "output_format": {
    "type": "delivery_verdict",
    "sections": [
      "Ready to send",
      "Any remaining blockers"
    ]
  }
}

Tool-specific instructions

Claude Cowork

• Read the Claude Cowork explainer page in the site's Tools menu if you want the overview first.
• Cowork works on local files directly, which makes it a better fit than a normal chat workflow for folder inspection and cleanup.
• For recurring clients, consider a Cowork project so the same instructions and folder expectations stay attached to the task.

Quality checks

1. Every promised asset is explicitly accounted for as present or missing.
2. Naming and format requirements are checked against the actual checklist, not guessed.
3. No source file is renamed or moved unless you approved that step.
4. The final verdict is short enough that you can trust it as a pre-send gate.

Common failure modes and fixes

Cowork flags too many false problems

Fix: make delivery-checklist.txt more explicit about which files are optional and which are final.

Important files are buried in subfolders

Fix: either flatten the delivery folder or state the intended subfolder structure in the checklist.

The brief and checklist disagree

Fix: resolve that conflict yourself before the final review pass. Cowork can flag the mismatch, but you still need the decision.

Sources Checked

• Anthropic Claude Help Center: Get started with Cowork (accessed 2026-03-23) https://support.claude.com/en/articles/13345190-get-started-with-cowork
• Anthropic Claude Help Center: Installing Claude Desktop (accessed 2026-03-23) https://support.claude.com/en/articles/10065433-installing-claude-desktop
• Anthropic Claude Help Center: Use Cowork safely (accessed 2026-03-23) https://support.claude.com/en/articles/13364135-use-cowork-safely
• Anthropic Claude Help Center: Organize your tasks with projects in Cowork (accessed 2026-03-23) https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-cowork

Quarterly Refresh Flag

Review on 2026-06-21 to confirm any updates to Claude Skills, Cowork availability, mobile dispatch requirements, project behavior, and supported setup paths.