RECAP FOLDER STRUCTURE ====================== Copy this tree when you start any new project or campaign. Create it on day one, not at the end. The whole point is that capture happens while the work is happening, so the folder has to exist before there's anything to put in it. Recommended location: a cloud drive (Google Drive, Dropbox, OneDrive) that syncs locally, NOT a desktop folder and NOT a downloads folder. Cloud-first means it survives a dead laptop, a lost SD card, and a "control-Z that didn't work." /[CLIENT or BRAND] - [PROJECT NAME] │ ├── recap-file.md <- the living record. Update as you go. │ ├── 00-to-be-sorted/ <- inbox. Anything you download or screenshot │ lands here first, then gets filed. Never │ let this be the desktop. │ ├── 01-brief-and-goals/ <- the original ask, scope, contracts, SOW, │ kickoff notes. │ ├── 02-strategy-and-plan/ <- the game plan, media plans, timelines, │ decision docs. │ ├── 03-working-files/ <- drafts, source files, anything in progress. │ ├── 04-assets/ │ ├── images/ │ ├── video/ │ ├── schematics/ <- diagrams, layouts, floor plans, wireframes. │ └── screenshots/ <- rename them. "Screen Shot 2026..." is useless │ in six months. │ ├── 05-budgets-and-invoices/ <- what it cost, who got paid, barter records. │ ├── 06-final-deliverables/ <- the polished output the client actually got. │ ├── 07-results-and-reporting/<- dashboards, exports, screenshots of numbers, │ the project-management board export. │ └── 08-handoff/ <- transition doc, access list, account quirks, anything the next person needs. THREE WIRING RULES THAT MAKE THIS STICK ======================================= 1. POINT DOWNLOADS AT THE INBOX. Change your browser's download location (or set up an automation) so anything you save drops into a "to-be-sorted" folder inside your synced cloud drive, not a local downloads folder you'll never look in again. 2. ONE .md HISTORY PER PROJECT. If you use AI tools on the work, make a standing rule: every project keeps a chronological .md log of what happened and what was decided. That way a new chat, a new tool, or a new teammate can read it and pick up without you re-explaining everything from scratch. 3. SYNC THE DRIVE LOCALLY, CONNECT IT TO YOUR AI. Keep the cloud folder synced to your machine and connected to the AI platforms you work in, so the files are reachable instead of trapped. Template by David Estrada · Axer Strategies · axerstrategies.com