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

Warning: Client folders often include credentials, invoices, or unrelated files. Strip the folder down before upload and never upload raw password files.

Problem and who this is for

A project can look ready on paper and still be blocked on day one because something basic is missing, such as logins, brand files, approved copy, or the right contact. A missing-assets checklist catches those gaps before production starts.

This workflow is for freelancers, consultants, and small teams who start from a messy client folder and need to know what is still missing before work begins.

Prerequisites

• Claude access.
• The client brief, proposal, or kickoff summary.
• The current working folder or a trimmed upload set with the project materials you already have.
• A place to store the final checklist.

How to capture or gather the source material

1. Create a clean working folder with only the files that matter for project start.
2. Include the brief, signed scope summary, brand assets list if one exists, current copy or references, and any onboarding email notes.
3. Do not upload password vault exports. Instead, create a plain text note that says which accounts you already have access to and which ones are still pending.
4. If the folder has duplicates, delete them before upload. Claude works better when the folder is small and intentional.
5. If you have screenshots of missing permissions or broken links, turn those into one plain text note rather than uploading clutter.

Numbered workflow steps

1) Upload a trimmed source pack to Claude

You can upload the files directly in a chat or add them to a Claude project if the work will continue over several days. The key is to upload the files that define what should exist at project start, not your entire archive.

2) Ask Claude to map what the project appears to require

Before you ask for a final checklist, ask Claude to infer the required assets, approvals, and access from the uploaded material. Tell it to mark what is present, what is implied, and what is missing.

3) Review the inferred requirements

This step matters because some projects assume things that were never formally promised. If a deliverable truly needs a missing asset or login, keep it on the checklist. If it is just a nice-to-have, remove it now.

4) Generate the missing-assets and access checklist

Ask Claude for a checklist grouped by assets, approvals, access, and reference materials. Ask for the checklist in a format you can paste into your task manager.

5) Send the smallest possible follow-up request

Use the output to send one concise follow-up to the client. A focused request for eight concrete missing items is much better than a vague 'we still need some things from you' email.

Tool-specific instructions

Claude is the best primary tool here because it handles uploaded documents well and works cleanly with project-style context when a folder has several related files. It is especially useful when the job is structured review, not brainstorming.

NotebookLM is a good alternative when you want more source-grounded question answering across the same document pack. ChatGPT is a workable fallback for a smaller set of files when you want a fast first pass.

Copy and paste prompt blocks

Requirement extraction prompt

{
  "task": "Extract the required start-of-project assets, approvals, and access from the uploaded client materials",
  "goal": "Find what is missing before production starts",
  "instructions": [
    "Use only the uploaded brief, notes, and folder contents.",
    "Infer what the project requires to start safely.",
    "Separate present items from missing items.",
    "Do not assume credentials exist unless the source says they exist."
  ],
  "output_format": {
    "present_assets": [],
    "missing_assets": [],
    "present_access": [],
    "missing_access": [],
    "approvals_needed": [],
    "references_or_inputs_still_needed": []
  }
}

Final checklist prompt

{
  "task": "Turn the reviewed extraction into a missing-assets and access checklist",
  "input": {
    "reviewed_extraction": "PASTE THE REVIEWED OUTPUT"
  },
  "instructions": [
    "Group the checklist by assets, access, approvals, and references.",
    "Keep each item concrete and client-readable.",
    "End with a short summary of what blocks production right now."
  ],
  "output_format": {
    "assets": [],
    "access": [],
    "approvals": [],
    "references": [],
    "current_blockers": []
  }
}

Quality checks

1. The checklist distinguishes between assets, permissions, and approvals.
2. Nothing on the list assumes logins or files that were never actually provided.
3. True blockers are obvious at a glance.
4. The final list is short enough to send as one clean client follow-up.

Common failure modes and fixes

Claude marks too many things as missing

Fix: remind it to separate true blockers from helpful extras. Some nice-to-have references are not actual setup blockers.

The client folder is too messy

Fix: trim the source pack harder. The more irrelevant files you upload, the weaker the checklist gets.

The checklist is too internal to send

Fix: keep one internal version and ask for a second client-facing version that uses plain language.

Sources Checked

• Anthropic Claude Help Center: Uploading files to Claude (accessed 2026-03-24) https://support.claude.com/en/articles/8241126-uploading-files-to-claude
• Anthropic Claude Help Center: What are projects? (accessed 2026-03-24) https://support.anthropic.com/en/articles/9517075-what-are-projects
• Anthropic Claude Help Center: How can I create and manage projects? (accessed 2026-03-24) https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects
• Google Workspace: NotebookLM product page (accessed 2026-03-24) https://workspace.google.com/products/notebooklm/
• OpenAI Help Center: Data analysis with ChatGPT (accessed 2026-03-24) https://help.openai.com/en/articles/8437071-data-analysis-with-chatgpt

Quarterly Refresh Flag

Review on 2026-06-22 to confirm any changes to tool availability, file handling, supported source types, limits, plan requirements, and mobile workflow steps.