Good design deserves to be understood.
Landscape architects spend enormous effort developing thoughtful work. Then we communicate it through drawing sets, email attachments, meeting minutes and PDFs assembled for one moment in time.
Folii creates a clearer project experience for the people shaping the work — without asking your team to maintain a separate client portal.
In development · with the founding practicesOne project. Different views.
Not four copies of the project kept in step by somebody's diligence. One project, and four honest answers to the question of what each person needs to see.
Same project. Right information. Right people.
Your team
The complete working environment — the library, the current design, every version, every response and the decisions they produced.
Your client
The design, the reviews waiting on them, the items needing a response, the decisions already made and the documents you've published.
Your architect
The coordination information relevant to them, against the elements it concerns.
Your contractor
Approved selections, substitutions raised against the specification that governs them, field observations and reports.
The living record of the project.
Organise the project around the design itself — courtyard, entry, playground, planting, site furnishings, materials. Each area drawing directly from the practice library.
A version is a deliberate snapshot, not every keystroke. What you get afterwards is a history short enough to read and specific enough to explain itself.
In developmentNot Concept_Final_FINAL_v7.pdf
- Concept 01
- Client review4 decisions
- Concept 02
- Internal review3 changes
- Current design
And the history explains why it changed.
Present the work where the decisions live.
Build a review from the design information already in Folii. Present it, share it, collect the responses, approve, decide.
An internal planting review and a client design presentation use the same underlying structure without becoming the same experience — the audience changes what is asked for and what comes back.
The record is created by the review you needed to have anyway.
No one has to write the documentation afterward.
In developmentRemember why the design changed.
Every project carries a handful of changes that everybody argued about and nobody wrote down. Six months later you are reading meeting minutes. Six years later the practice is guessing.
In developmentDecision
Path shifted 6′ east.
- Why
- Arborist identified potential impacts to the existing root zone.
- Raised by
- Coordination review at 50% DD
- When
- 14 March
- Against
- Entry court — planting plan
Folii keeps the answer attached to the project — so the question is asked once.
Sharing shouldn't create another place to maintain.
Your team shouldn't update Folii and then update the client portal. A designer shares the courtyard review; the client responds; the response stays in the review; the team records the decision; the design moves on; the history stays connected.
The external experience is generated from the work itself.
How the library holds it →Ten practices are shaping what this becomes.
Free for the first year. Half an hour a week. One real project.