A small project does not need a large collection of apps. It needs an unchanged input, a working copy, a reviewable delivery and a way to recover the files. This walkthrough uses the site's downloadable practice resources so you can test the process with non-sensitive material.
Create four project folders
| Folder | Contents | Rule |
|---|---|---|
| 01-input | Original brief and supplied facts | Keep the original unchanged |
| 02-working | Drafts and decision notes | Use clear version names |
| 03-delivery | Only the agreed final files | Open each file before sending |
| 04-records | Scope, approvals and handoff note | Keep private and permitted records |
These names are an organisational example, not a software requirement. Avoid using a client's name in a public link when permission has not been given.
Run one complete text-file handoff
Download the tote portfolio brief. Save an unchanged copy in 01-input. Create tote-copy-v1.md in 02-working and rewrite the description from the supplied facts. Record what you removed and why in a separate note.
Save a second version after the factual review. Reopen it from the saved location and check the title, dimensions, closure and care instruction. Then copy only the agreed output into 03-delivery. The folder should not include unrelated drafts, private notes or a file called final-final-really-final.
Markdown files are ordinary text. You can open them in a text editor or paste their contents into a document editor. For the cleaning exercise, use a spreadsheet application capable of importing CSV. Use software you already have permission to use and check its current requirements before relying on a new installation.
Export is a separate quality check
If the recipient needs DOCX or PDF, export through the application rather than renaming the extension. Open the exported file independently and check that text, tables and page breaks remain readable. If the recipient needs CSV, confirm the separator, encoding, headers and text/date handling.
For a spreadsheet, a visually attractive export can still contain incorrect formulas. Compare key figures manually and preserve the original data. For a video, a saved project file is not the same as the requested playable export.
Test your backup by restoring one file
Use your normal approved backup location and copy a practice file there. Restore it into a separate test folder and open it. Check the content, not only the filename. A backup that has never been restored has not demonstrated that you can recover a usable version.
Keep confidential material only in locations permitted by the project agreement. A public share link may solve an access problem while creating a privacy problem. Test sharing with fictional data first and remove access when it is no longer needed.
Make the handoff self-explanatory
Include a short note naming the files, version, included deliverables and unresolved questions. The delivery checklist provides a reusable structure. Ask the recipient for a specific review, such as checking three SKU descriptions against the approved facts.
The finished practice pack demonstrates file formats and content, not a claim that every office suite or paid software plan was tested. When a real buyer uses a different application, confirm compatibility before promising that format.
Practice work and illustrative amounts are labelled in the article. See how we prepare and correct guides and how the resource checks work. Report a specific error or broken step.