The slowest part of many projects is not the work. It is waiting for the right files: the logo in a usable format, the final version of the copy, the original photos rather than the ones from the website. Every missing asset is a follow-up email and a day lost.
You can prevent most of it by asking precisely at the start. Below is a checklist you can copy into your kickoff message, adapt per project, and reuse.
How to use this checklist
Pick the sections that apply to the project, delete the rest, and send it with a single place to upload everything. Tell the client which items are essential and which are nice to have, so a missing optional item does not block the start.
Brand assets
- Logo as a vector file (SVG, EPS, AI or PDF), all versions.
- Logo as a PNG with transparent background, at least 2000 px wide.
- Light or reversed logo for dark backgrounds, if one exists.
- Brand colours as HEX, plus CMYK or Pantone for print.
- Fonts or font names, with licence details.
- Brand guidelines document, even if out of date.
If clients struggle with the logo, our guide to collecting logo files from clients explains vectors in plain language you can borrow.
Documents and copy
- Final copy in an editable format (DOCX, Google Doc export or plain text), not a PDF.
- Who signs off copy, by name.
- Legal text that must appear: disclaimers, registration numbers, terms.
- Existing material to reuse: brochures, old website text, reports.
Photos
- Original photos at full resolution, not screenshots or images saved from a website.
- Photographer credits and usage rights for each set.
- People in photos: confirmation that consent for use exists, where it matters.
- Preferred shots marked or listed, if there are many.
Video and audio
- Original video files, not compressed versions from a messaging app or social platform.
- Music with licences, or a note that we should source it.
- Subtitles or transcripts if they exist.
- Previous edits for reference, if this is a recut.
Access and context
- Accounts we need, shared through a password manager or invitation, never pasted into an email.
- Examples the client likes and dislikes, with a sentence on why.
- Deadlines and key dates.
- One point of contact for questions.
Naming and formats
A short instruction here saves sorting later:
- Keep original filenames where they come from a camera or designer.
- For documents, use
Client - Topic - YYYY-MM-DD. - Do not rename files to “final”; a date is more honest.
- Whole folders are welcome if the structure means something.
The request message
Copy and adapt:
Hi Jordan, thanks for kicking off the winter menu project. To get started, could you upload the files below using this link? You do not need an account, and you can drop whole folders.
Essential: logo as SVG, AI, EPS or PDF; brand colours; the final menu text as a Word document. Nice to have: food photos from the last shoot (originals, please, not from the website); your brand guidelines.
The link stays open until Friday 20 November. If you are not sure where something is, tell us and we will help track it down.
Set up the upload link
The checklist works best with one place to send everything. An upload link, also called a file request, gives the client a page in their browser where they drop files, and the files land in your project folder.
Settings worth using:
- Destination: the project’s intake folder, such as
Clients/Northwind/2026-11 Winter menu/01-incoming. - Message: paste the essential items into the request so they are on screen during upload.
- Deadline: match it to your kickoff date.
- Separate folders per uploader: useful when several people at the client send files.
- File types or size limits: only if you need them. Restricting too tightly blocks the odd useful file.
On dosya.dev, file requests support all of these, and uploaders only see their own files. You get a notification when files arrive, and if your team lives in Slack or a project tool, the Zapier integration can post a message there whenever something new lands in the intake folder, or create the whole request automatically when a new project starts. The broader workflow is in our guide to receiving files from clients.
Review the intake the same day
When files arrive, run through the checklist again:
- Tick off what arrived and what is missing.
- Open each key file: vectors are really vectors, photos are full size, documents are editable.
- Send one follow-up message listing everything still needed.
Then move approved files from intake into the working folder. Our post on organising cloud storage for client projects shows a folder structure that keeps intake, work and delivery apart.
A clear request, one place to upload, and a same-day review. That is usually the difference between starting on Monday and starting next month.
Frequently asked questions
What files should I ask a client for at the start of a project?
It depends on the work, but most projects need brand assets such as logos, colours and fonts, any copy or documents, original photos or video, access details for existing accounts, and examples of what the client likes. Ask for originals rather than exports wherever possible.
How do I make sure clients send the right file formats?
Name the formats explicitly in your request, explain in one sentence why they matter, and give an example of what not to send, such as a screenshot of a logo. Review files the day they arrive so you can ask again while the project is fresh.
What is the easiest way for clients to send many files?
An upload link pointed at the project folder. The client opens it in a browser, drops files or whole folders, and leaves. No account is needed, and everything arrives at full size in one place.