Write it down once.
If you have explained something twice, it belongs here. Docs is what a new person reads instead of asking the same four questions.
Collections, not a folder tree
Runbooks, onboarding, client notes and payment terms, grouped so the whole crew can find them without a tour.
New people start here
Hours and availability, how to log time, when invoices go out, who approves what. The first day stops being a series of interruptions.
Terms sit next to the work
A client’s payment terms live in the same workspace as their board and their invoices, so nobody bills against a document they have never seen.
Collections, not folders
Runbooks, onboarding, client notes and terms, grouped so they can be found. Hierarchy invites arguments about hierarchy; a flat set of collections invites someone to actually write the page.
What a new person reads
How hours are logged, when they are approved, when invoices go out and who approves what. If the first week can be completed without asking a process question, the doc is doing its job.
- One page per subject, not a wiki tree
- Client terms sit beside that client’s invoices
- Workspace-wide, with a filtered view per channel
- Exports as Markdown files in collection folders
Written once
The rule is simple enough to hold: if you have explained something twice, it belongs here. Docs is the difference between a team that scales by hiring and a team that scales by answering the same four questions forever.