River Folder
Use the templates

Worked example

One project, organized from first input to final archive.

This fictional community handbook refresh shows the River Folder method in practice. The content is illustrative, but every filename, folder role, status, and handoff step is usable.

Community_Handbook_Refresh/
|-- 00_about_this_workspace.md
|-- 01_intake/
|   |-- inbox/
|   |   |-- stakeholder-notes-2026-06-02.md
|   |   `-- handbook-source-2024.pdf
|   `-- source-links.md
|-- 02_active/
|   |-- planning/
|   |   `-- content-plan-v02-reviewed.md
|   |-- research/
|   `-- work/
|       `-- handbook-draft-v04-reviewed.docx
|-- 03_deliver/
|   |-- outputs/
|   |   `-- community-handbook-v05-approved.pdf
|   `-- handoff/
|       `-- handoff-package-index.md
`-- 04_archive/
    |-- final/
    |-- reference/
    `-- archive-inventory-2026.csv
00

Explain the workspace first.

00_about_this_workspace.md sits at the root so a new contributor can understand the project before opening files at random. It records the project purpose, accountable owner, folder roles, active status, and next review date.

Current stateContent approved. Final PDF packaged. Source files retained for the next annual review.
01

Capture inputs without pretending they are organized.

The intake area holds raw notes, the prior handbook, and source links. Items remain here only until the weekly review decides whether to delete, reference, or move them into active work.

  • Preserve the original filename when provenance matters.
  • Add a date when several similar inputs may arrive.
  • Do not edit source material in place.
02

Keep one obvious current working set.

The active folder separates planning, research, and working documents. Version numbers are zero-padded, and a status word appears only when it changes how someone should use the file.

handbook-draft-v04-reviewed.docxReviewed working copy. Comments are resolved before the approved export is created.
03

Deliver outputs with a package index.

The recipient receives the approved PDF, editable source files when needed, and handoff-package-index.md. The index identifies each file, its purpose, its status, and any open decisions.

community-handbook-v05-approved.pdfApproved publication copy. This is the document readers should use.
04

Archive decisions, not clutter.

The archive retains the approved PDF, the editable source, the final content plan, and an inventory. Duplicate exports, temporary review copies, and downloaded caches are removed.

Retention noteKeep until superseded by the next approved handbook, then retain the final PDF as the historical record.

Final manifest

What leaves the project.

The handoff and archive contain a small, deliberate set of files.

FilePurposeStatusDestination
community-handbook-v05-approved.pdfReader-facing handbookApprovedDeliver + archive
handbook-source-v05.docxEditable sourceFinalHandoff + archive
handoff-package-index.mdPackage map and open itemsFinalHandoff
archive-inventory-2026.csvRetention registerCurrentArchive

Build this structure with plain files.

Download the README, handoff index, and archive inventory used by the example.

Open the templates