For: Creators and project leads
The useful outcome: A file-organization routine
1. Make a staging folder
Create a temporary local folder containing only what is intended for delivery. This protects the package from accidental working files and makes the inventory easier.
- Create the staging folder deliberately
- Select approved files only
- Check for accidental drafts
2. Name for an unfamiliar reader
Prefer names such as Brand-Primary-Logo.svg or Proposal-Final.pdf over internal shorthand. Put different asset types in predictable folders.
- Use purpose before internal project codes
- Keep related assets together
- Avoid competing final labels
3. Write the recipient notes
Add a README with the package purpose, starting point, and any agreed next action. Then build and inspect the local ZIP using only the staging folder.
- State the recipient’s next step
- Build the ZIP from staging
- Check it independently
Questions, answered.
Should version numbers be used?
Use them when they help distinguish approved iterations, but avoid several competing “final” labels.
Are source files always included?
Only when they are part of the agreed delivery; the package should reflect what the recipient needs, not every file produced.