Documentation
Recommended workflow · Use case
Document a project or works
A recommended path for turning decisions, photographs, files, and deliverables from a project into useful Place memory.
Scenario: roof refurbishment
A building community hires a technical team and contractor to refurbish its roof. Visits, photographs, quotes, certificates, and decisions accumulate over several months.
The goal is not merely to store files, but to reconstruct what happened, who decided it, and which document supports it.
1. Establish context before volume grows
Confirm the destination Place and work through the correct Account. Use a project grouping when it becomes available; until then, keep titles and relationships consistent.
Define who needs access and what should remain internal to each team.
2. Capture progress as it happens
Record visits, issues, decisions, and photographs when they occur. Distinguish the date of the event from the date it was entered.
Start with essential content and add people, status, and relationships later; do not lose an important observation for lack of metadata.
3. Group files deliberately
Use one Dossier for files sharing context, visibility, and discussion, such as a drawing issue or monthly certificate.
If a file needs a different audience, separate it into another Card instead of building hard-to-maintain exceptions.
5. Close with understandable memory
Identify final deliverables, connect corrections to what they replace, and accept into durable memory what the Place must retain.
Exports and formal handover packages are not available yet; this model already avoids making closure depend on someone's private folder.