For: Freelancers and agencies
The useful outcome: A repeatable delivery routine
Define the recipient’s first task
Start by asking what the client should open first and what they need to do next. Select final files around that answer, not around the project’s internal folder history.
- Name the recipient and their purpose
- List agreed final deliverables
- Separate client assets from internal work
Use a handover map
Create folder names that show purpose, then include an index and short README. A recipient should not need to guess which logo, document, or asset is current.
- Use folders that mirror the index
- Make file names understandable out of context
- Put the first action in the README
Do a clean-recipient check
Open the local ZIP outside the source folder and use only its contents. This quickly reveals missing files and instructions that rely on unwritten context.
- Open files without the original workspace
- Check the index against the ZIP
- Date the delivered package
Questions, answered.
How many files should be included?
Include the agreed deliverables and any reference material the recipient needs to use them. Keep working files separate unless they are explicitly requested.
Can this become a team standard?
A custom project can document team naming, folder patterns, index fields, and review steps.