Freelancers & Consultants17 min readUpdated Nov 1, 2026

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

Use Claude Cowork to compare a deliverable folder against the client brief and catch missing files before delivery.

claude coworkdeliverable reviewchecklist reviewfolder reviewclient delivery

Workflow summary

Quote this workflow accurately

Markdown version
Best for
Before a handoff, you need answers to three unglamorous questions: Is everything here? Is it named correctly? Does it match what was promised? A missed export, incorrect format, duplicate, or version mismatch can unde...
Input
Claude Cowork on Pro, Max, Ultra, Team, or Enterprise ; confirm administrator settings where applicable. A scoped deliverable workspace containing only this client's current delivery set and associated requirements. T...
Primary tool
Claude Cowork
Output
Use Claude Cowork to compare a deliverable folder against the client brief and catch missing files before delivery.
Main risk
False missing file flags. Check case differences, subfolders, aliases, alternative accepted formats, and checklist versions. Update delivery checklist.txt rather than letting Claude guess.
Verification step
Every asset promised in the signed brief or approved change order has a separate row and explicit status. Expected names, formats, and subfolders come from the actual checklist, not Claude's preferences. The report di...

Continue from this article

Warning: This is a pre-delivery inspection, not permission to edit client assets. Cowork must compare actual files against the agreed brief and checklist before any cleanup. Do not rename, move, delete, modify, convert, or send any file unless you approve that specific operation. A final verdict is not approval to send on your behalf.

Cowork requirements at a glance: Claude Cowork is available on Pro, Max, Ultra, Team, and Enterprise plans, not Free. For inspecting a real folder on your computer, use Claude Desktop with the scoped folder connected and start the task there. Web/mobile cloud sessions can use files supplied to them, but a mobile-started session cannot automatically inspect a desktop-connected directory.

If Claude Cowork is new to you

Cowork is now available through Claude on desktop, web, and mobile. If your account has the unified Claude experience, describe the task in a conversation; if you still see separate Chat and Cowork choices, choose Cowork. New tasks on Pro, Max, and Ultra run in the cloud by default, even when started on Desktop; the old Only on your computer control is gone. Team availability is in beta and Enterprise depends on administrator enablement.

For a local delivery folder, the important distinction is where you start: Anthropic says a cloud Cowork task can reach an approved desktop-connected folder only while Desktop is open and only if the session started on Desktop or is a scheduled task. It fetches a copy of the individual files it needs; it does not automatically upload the whole folder. Start on Desktop if the review requires local filenames, paths, subfolders, or write access. Later you can monitor the cloud session from your phone. A task started directly on mobile does not gain the local-folder bridge.

Related examples are in the Claude Cowork tool hub and the Anthropic Workflows series.

Problem and who this is for

Before a handoff, you need answers to three unglamorous questions: Is everything here? Is it named correctly? Does it match what was promised? A missed export, incorrect format, duplicate, or version mismatch can undermine a good project.

This workflow is for freelancers and consultants delivering a folder of client assets, including design exports, documents, reports, or other agreed files. It creates an auditable comparison report, supports limited approved cleanup, and ends with a concise ready-or-blocked verdict. It does not decide contractual conflicts or send the files.

Why Cowork fits this workflow

The work depends on inspecting the delivered set: folder paths, filenames, file extensions, subfolders, likely duplicate versions, and document content where applicable. Cowork can compare that set against a specific written delivery standard and prepare a discrepancy report before any changes are made.

This is not an automatic quality guarantee. File extensions can be misleading, and some creative or technical formats need specialist applications to validate. Claude's report should distinguish a verified observation (such as “file X is missing”) from an inference (such as “these two images may be duplicates”). The final acceptance standard remains the contract, client instructions, and your own functional checks.

Why not normal Claude chat or just a Skill?

A brief upload and checklist can be compared in an ordinary Claude conversation. Cowork becomes more useful when the task requires workspace inspection across many files, a repeatable issue classification, explicit confirmation before file changes, and a final read-back of the actual delivery set. The difference is the inspection and gatekeeping process, not a claim that chat can never work with files.

A Skill can standardize issue categories or verdict wording; it does not by itself inspect the folder, reconcile inconsistent source documents, or prove the client files are complete.

Prerequisites

  • Claude Cowork on Pro, Max, Ultra, Team, or Enterprise; confirm administrator settings where applicable.
  • A scoped deliverable workspace containing only this client's current delivery set and associated requirements.
  • The signed-off client brief, statement of work (SOW), or other authoritative scope document, plus the current delivery checklist.
  • A plain-text delivery-checklist.txt describing every promised asset, file format, naming convention, folder structure, optional item, and exclusion.
  • Permission under the client agreement to process these files with the selected cloud AI service. Redact credentials, customer data, and secrets before sharing material.
  • Time to approve each proposed cleanup operation individually, review the final report, and send the files yourself.

Set up this workflow as a Cowork project

Use the same narrow layout each time, whether on disk or represented by a deliberately prepared set of cloud attachments:

client-delivery-review/
  deliverables/
  client-brief/
  checklist/
  final-verdicts/
  archive/
  delivery-checklist.txt

Place only files you intend to deliver in deliverables/. Put the signed scope and other controlling requirements in client-brief/, and the client's QA list and relevant acceptance criteria in checklist/. The root delivery-checklist.txt is your explicit asset-by-asset delivery standard. Keep older exports, unapproved drafts, and unrelated client material in archive/ outside the connected input scope, or preferably outside this workspace entirely. If you must connect the parent directory, move archive/ outside it beforehand; a text instruction alone does not revoke the access you grant to a folder.

For recurring clients, you may keep reusable instructions in a Claude Project, but do not assume a Project automatically mirrors your local filesystem or retains an up-to-date folder snapshot. Anthropic says Projects are accessible across devices, while Projects linked to local folders support Cowork sessions on Desktop only. Paste the following JSON as human-readable task or project guidance, not as a software command:

{
  "project_name": "Client Delivery Review",
  "project_purpose": "Inspect a delivery workspace against the controlling client brief and checklist; report discrepancies, obtain approval for each file operation, and return a final delivery-readiness verdict.",
  "project_instructions": [
    "Inspect only deliverables, client-brief, checklist, and delivery-checklist.txt unless I authorize a named additional source.",
    "Use delivery-checklist.txt as the asset-by-asset delivery standard and compare it to the client brief/SOW.",
    "Account for every promised asset: present, missing, wrong format, naming mismatch, duplicate, optional, or needs review.",
    "Record observed file paths, expected filenames, format requirements and evidence for discrepancies.",
    "Flag conflicts between the brief/SOW and checklist; do not decide which requirement wins.",
    "Produce a comparison report FIRST, with no file changes.",
    "Do not rename, move, delete, modify, overwrite, export, or convert any file without approval for that exact operation.",
    "Never interpret a general fix-all statement or choosing Automatically approve as approval for broad cleanup.",
    "After the user confirms cleanup is complete, re-inspect the actual current set and prepare a short Ready to send / Any remaining blockers verdict.",
    "Save review reports in final-verdicts only when the specific write path is available and approved; otherwise return a report for manual saving.",
    "Do not send files, emails, links, or client messages."
  ],
  "file_naming": "client-delivery-review-client-name-yyyy-mm-dd"
}

How to gather the source material

  1. Prepare the actual final files in deliverables/; avoid including in-progress versions as if they were shippable.
  2. Put the agreed brief or SOW into client-brief/, plus any subsequent approved change orders.
  3. Put client-provided QA requirements into checklist/.
  4. Fill in delivery-checklist.txt with one entry per promised asset: expected file or filename pattern, required format, subfolder, whether optional, and any exclusion. State if there are multiple valid formats.
  5. Remove older exports, scratch files, credentials, and other clients' data from Claude's access scope. Do not rely on a prompt alone to protect files that were unnecessarily connected.
  6. Decide which input route applies. The report is only as complete as the actual files and paths Claude can inspect.

Choose the file-access route

Route A: inspect the connected local directory (recommended). Start the task in Claude Desktop, connecting only the approved delivery workspace. Keep Claude Desktop open while the task inspects, re-inspects, or performs individually approved local file operations. A new Pro/Max/Ultra Cowork task still runs in the cloud; it can fetch copies of selected local files for processing. A separate mobile-started cloud task is not an equivalent way to inspect the local directory.

Route B: upload an approved delivery set to a cloud session. Provide the brief, checklist, and selected deliverable files explicitly. If folder hierarchy matters, supply a file manifest with relative paths and compare it against the actual package yourself. A flat set of uploads cannot establish that the real, untouched local delivery folder has the required directory structure or that no additional files exist. This route is suitable for a preliminary document review, not an independently verified local-folder verdict. Download any generated report manually.

Confirm on the specific account how cloud Cowork represents uploaded files, names and subfolders, whether it can inspect every relevant format, and whether reports can be written back to the intended local final-verdicts/ folder. If full folder enumeration is unavailable, label the review partial and run the final check against the actual local folder.

Before making confidential client deliverables available to a cloud Cowork session or through the desktop file bridge, confirm the applicable Anthropic data-processing and retention terms, the client's confidentiality requirements, and any organizational approval. A connected folder is not proof of local-only processing.

Numbered workflow steps

1) Configure read-only inspection and request a comparison report

Use Manually approve for this task. Anthropic's current choices are Manually approve, Automatically approve (safety-checked, then may ask), and Skip all approvals (no automatic action check). The second option is not equivalent to the third, but neither automatically enforces your client-specific one-operation-at-a-time rule. Keep the requested inspection explicitly read-only and approve no changes at this stage.

Paste the prompt below. Adapt its input field to the folder you actually connected, or list the files and paths you explicitly provided to a cloud session.

{
  "task": "Perform a read-only pre-delivery inventory and comparison against the client brief and delivery checklist.",
  "input": {
    "source_mode": "DESKTOP CONNECTED FOLDER OR EXPLICIT CLOUD UPLOADS",
    "deliverable_folder": "deliverables",
    "brief_folder": "client-brief",
    "checklist_folder": "checklist",
    "delivery_checklist_file": "delivery-checklist.txt",
    "cloud_manifest": "IF UPLOADED, LIST EACH SOURCE FILE AND RELATIVE PATH; FLAG STRUCTURE UNVERIFIED"
  },
  "rules": [
    "Inspect only the approved scope. Make no file changes or external transmissions.",
    "List every expected deliverable in the checklist, including optional items and exclusions.",
    "Compare each expected asset with a specific observed path, format, and naming convention.",
    "Classify as present, missing, wrong format, naming mismatch, duplicate, optional, or needs review. Multiple flags may apply.",
    "Label suspected duplicates as suspected until content or version is checked.",
    "Report any contradiction between the SOW/brief and the checklist without choosing a winner.",
    "For each discrepancy, suggest a single concrete possible correction; do not execute it.",
    "Distinguish inspected data from inferred or unverified format/content checks.",
    "If the input was only uploaded files, do not claim to have enumerated the actual local delivery folder.",
    "Stop and ask for human review before cleanup or final verdict."
  ],
  "output": {
    "asset_matrix": "Each promised asset, expected path/format, observed file, status and supporting evidence",
    "present_assets": "Items meeting the checklist",
    "missing_assets": "Items not found in the examined set",
    "format_or_naming_issues": "Observed mismatches by file",
    "duplicates_or_optional_items": "Suspected duplicate versions and optional items",
    "brief_checklist_conflicts": "Human decisions required to reconcile requirements",
    "suggested_fixes": "One specific operation or manual action per issue",
    "unverified_checks": "Formats, content quality or directory paths not independently verified"
  }
}

Review the comparison report against the contract. A “present” status only confirms the claimed criterion Claude examined; it does not necessarily mean the exported file opens correctly or meets every technical specification. Check suspicious duplicates and extension-based format claims with the appropriate application. Resolve any checklist-versus-brief conflict yourself before moving to cleanup.

2) Fix issues individually, with explicit permission

Prefer to perform fixes yourself, using the report as a punch list. If you delegate a change to Cowork, approve one specific operation at a time, naming the exact source and destination, such as “rename deliverables/report-FINAL2.pdf to deliverables/report.pdf and do nothing else.” Check the result, then separately approve another operation if needed.

Do not instruct Claude to “fix everything,” “clean the folder,” or “delete duplicates.” Even if it suggests a plausible cleanup, do not let it touch files until you've chosen the operation. Keep originals or backup copies where appropriate. Any deletion still requires approval under Anthropic's policy, but the article's rule is stricter: no file modification, move, rename, conversion, or deletion without per-operation approval.

If Claude lacks writeback access because the session started in the cloud or the folder is disconnected, make the changes yourself and proceed. A generated checklist or suggestion is not evidence that a local file changed.

3) Re-inspect and request the final delivery verdict

After you confirm cleanup is complete, instruct Cowork to inspect the current actual files again. It must not rely solely on the first report or its own prior assumptions.

{
  "task": "Re-inspect the current approved delivery set and return the final delivery-readiness verdict.",
  "input": {
    "deliverable_folder": "deliverables",
    "delivery_checklist_file": "delivery-checklist.txt",
    "human_cleanup_confirmation": "YES, THE USER HAS CONFIRMED CLEANUP IS COMPLETE",
    "review_boundary": "LOCAL FOLDER VERIFICATION OR UPLOAD-ONLY PARTIAL CHECK"
  },
  "rules": [
    "Use the current state of the actual accessible files, not the earlier draft report alone.",
    "Account for every promised asset and re-check names, paths, formats and required subfolders.",
    "Show blockers, unresolved contract/checklist conflicts, and checks that cannot be verified.",
    "Return Ready to send only if required items are present, inspectable and matched to the approved checklist, with no unresolved blockers.",
    "If folder structure or file content could not be inspected, state NOT VERIFIED instead of issuing an unconditional Ready verdict.",
    "Do not rename, move, delete, modify, export or send any client file.",
    "Prepare the report for the user to save in final-verdicts if local writeback is unavailable."
  ],
  "output_format": {
    "type": "delivery_verdict",
    "sections": [
      "Ready to send: YES / NO / NOT VERIFIED",
      "Any remaining blockers",
      "Unverified checks",
      "Files and criteria reviewed"
    ]
  }
}

4) Save the reports and deliver personally

Save the inspection report and final verdict under final-verdicts/, using client-delivery-review-client-name-yyyy-mm-dd as the naming pattern. If the task cannot write there, download and save them yourself. Verify the final packaged folder, including actual file-open and export checks in the relevant software. Send the approved files and any client communication yourself, outside Cowork.

Expected output

The first artifact is an asset-by-asset discrepancy matrix, not just a yes/no statement. It identifies which promised files exist, which are missing, whether paths and formats appear correct, which items are duplicates or optional, what conflicts require a human decision, and exactly what was and was not inspected.

The second artifact is a concise Ready to send / Any remaining blockers verdict. An unconditional “Ready” is appropriate only after a fresh inspection of the actual delivery set and resolution of all material blockers. For a cloud-upload review with incomplete folder visibility, the verdict must say NOT VERIFIED or otherwise describe the incomplete checks. You, not Claude, make the final handoff decision.

Future delivery checks

For the same client, keep the instructions but update delivery-checklist.txt for the next scope or approved change order. Remove previous exports from the working input set before review. Do not assume the Claude Project tracks local folder changes or automatically discovers new deliverables.

Reusable prompt:

{
  "task": "Begin a new read-only delivery review using the current approved brief and checklist.",
  "rules": [
    "Enumerate the actual accessible deliverables and record the inspection boundary.",
    "Create the asset comparison matrix before suggesting edits.",
    "Flag missing items, wrong formats, naming mismatches, likely duplicates and requirement conflicts.",
    "Do not change files or send anything.",
    "Wait for approval for each specific cleanup operation and obtain confirmation before the final verdict."
  ]
}

Tool-specific instructions, tips, and caveats

  • Local folders: For real filesystem inspection, start in Claude Desktop with the intended folder connected. The desktop bridge must be available for local reads or authorized writes. Cloud execution does not automatically expose local drives.
  • Cloud uploads: Uploading selected files can help check their content, but it does not prove the complete local folder is ready, especially when names, subfolders, hidden files, or duplicate exports matter.
  • Approval modes: Use Manually approve for consequential file actions. Never treat Automatically approve as agreement to a broad cleanup, and never enable Skip all approvals for a client-delivery audit.
  • File format checks: Check whether a file opens, its embedded content and layout, and any specialist technical requirements in the native application. A .pdf, .pptx, or .zip extension alone is not conclusive.
  • Scope: Connect only the client's approved workspace; omit secrets, unrelated clients' data, and material outside the delivery agreement.
  • Keep a review trail: Retain the specific checklist version, inventory, approved changes, and final verdict. A one-screen summary alone is insufficient for later reconstruction.

Quality checks

  1. Every asset promised in the signed brief or approved change order has a separate row and explicit status.
  2. Expected names, formats, and subfolders come from the actual checklist, not Claude's preferences.
  3. The report distinguishes verified facts, suspected duplicates, and unverified technical checks.
  4. Drafts and unrelated client files were outside the inspected scope.
  5. No file was renamed, moved, deleted, converted, or otherwise modified without approval for the exact operation.
  6. Contradictions between the brief and checklist were resolved by the freelancer or client, not silently by Cowork.
  7. The final re-check inspected the current deliverables and did not reuse stale results.
  8. The final verdict is blocked or marked NOT VERIFIED if material checks could not be completed.
  9. No files, emails, or links were sent automatically. The freelancer made the final delivery decision.

Common failure modes and fixes

False missing-file flags. Check case differences, subfolders, aliases, alternative accepted formats, and checklist versions. Update delivery-checklist.txt rather than letting Claude guess.

False confidence about file formats. Verify with the native program, especially for exported graphics, slide decks, archives, or editable source files.

A checklist conflicts with a contract or change order. Keep the conflict in the report and obtain a human decision before marking the asset complete.

Claude starts changing files while reviewing. Stop the task and return to a read-only inventory. Restore from a known-good backup if a modification occurred. Switch to Manually approve and require explicit approval for one operation at a time.

A cloud-upload review reports the entire local folder ready. Reject that conclusion. Request a real local-folder re-inspection from Desktop, or manually check the actual package and label the cloud review partial.

The final verdict never appears in final-verdicts/. Save the report manually if direct local writeback was not available; confirm the path exists before relying on it.

Safety and confidentiality

Client deliverables can contain trade secrets, personal data, credentials, unpublished campaign assets, or contract-protected information. Only allow Claude access to material you have permission to process with the chosen cloud service. Anthropic says new Cowork tasks run on its servers and can fetch copies of connected local files; a local folder does not mean the processing remains local. Apply the data-handling verification above for confidential files. Do not allow automatic file sending, uploading to external client locations, deletion, or unapproved access broadening. This workflow is a quality gate, not a replacement for contractual acceptance or human review.

Sources Checked

Official Anthropic documentation accessed November 1, 2026:

Quarterly Refresh Flag

Review on February 1, 2027, or sooner if Anthropic changes account eligibility, connected-folder access, permission labels, file outputs, or cloud data handling. Recheck the actual workflow on the intended account before relying on it for consequential work.

Something off in this workflow?

Related Workflows

How Freelancers Can Use Claude Cowork to Turn a Sales Call Into a Personalized Proposal While Traveling

Capture a sales call recap while traveling, then use Claude Cowork with approved proposal templates and scope rules to draft a personalized proposal for review.

Read Workflow

How to Turn a New Client Folder Into a Missing Assets and Access Checklist With Claude

Turn a new client folder, brief, and current project materials into a missing assets and access checklist with Claude.

Read Workflow

How Freelancers Can Use Claude Skills to Turn a Client Intake Form Into a Project Kickoff Brief

Turn a client intake form and scattered onboarding notes into a project kickoff brief with Claude Skills.

Read Workflow
Reader Feedback

Help keep PromptedWork sharp

Share a broken step, outdated prompt, or general feedback. This is only for improving this specific workflow.