The method
Give every file a clear place in its lifecycle.
River Folder uses four stages and five durable rules. The goal is not a perfect folder tree. It is a workspace that another person can understand without asking its creator to translate it.
Four stages
One lifecycle from arrival to archive.
- 01
Intake
Capture incoming files, notes, links, exports, and requests before sorting them. The intake folder is temporary by design and should be reviewed on a regular cadence.
Set up an intake review →Exit conditionEvery item is deleted, referenced, or moved into active work. - 02
Active
Keep the current working set small. Names should sort predictably, ownership should be visible, and superseded drafts should leave the active folder.
Apply the naming pattern →Exit conditionThe work is approved, cancelled, or ready to package. - 03
Deliver
Collect final outputs, supporting context, and a handoff index. A recipient should know what is final, what each file is for, and what remains open.
Build a handoff package →Exit conditionThe recipient can use the package without the working folder. - 04
Archive
Retain the smallest useful record: approved outputs, source material with lasting value, decisions, and an inventory. Remove caches, duplicates, and obsolete exports.
Create a durable archive →Exit conditionThe archive explains what was kept, why, and for how long.
Five rules
Structure should answer questions, not create them.
These rules stay useful across shared drives, local folders, cloud storage, and version-control repositories.
- 01
Name for retrieval
Include only details that help someone identify, sort, or act on the file.
- 02
Separate current from historical
Do not make people inspect five drafts to discover which one matters.
- 03
Keep context beside the work
Use a README or handoff index instead of relying on chat history.
- 04
Use a small status vocabulary
Draft, reviewed, approved, final, and archived are usually enough.
- 05
Archive intentionally
Retention should be a decision, not the result of never deleting anything.
Shared vocabulary
Use status words consistently.
Choose one status per file and define what it means for your project.
Apply the method to a real folder.
Start with the cleanup guide, then compare your result with the worked workspace.
