Where it came fromnot recorded
Why it matterednot recorded
What it was attached tonot recorded
What it still reachesnot recorded
“Use the 40mm cavity detail here, not the standard one.”
The practice has this. Nobody can act on it.
Stored is not the same as remembered
Mudo does not fetch the note. It returns what was around it.
Where it came from
Raised in a consultant coordination meeting, and recorded there.
Why it mattered
It resolved a clash between two consultants' assumptions.
What it was attached to
The decision that closed the issue, and the drawing revision that followed it.
What it still reaches
The specification clause reused on every project since.
None of that was written down as knowledge. It is the project record the clause was attached to, which is why the clause is still worth something two years later.
Found where it is needed, not in a library nobody opens.
Knowledge & memory
Stored is not the same as remembered
The junction detail was changed.
Technically present. Useless.
- Where it came fromA decision recorded in the registers, on an earlier job
- WhyThe original detail failed review on a similar substrate
- Attached toThe drawing set it was issued against
- Still reachesThe specification clause that came out of it
Knowledge is attached to the projects and records it came from, so it is found at the moment it is needed. The statement above is a decision type and the fragments are kinds of context — no project, drawing, date or person is real.
In short
AvailableAvailable now to practices on a qualifying plan.- What it is
- The practice's accumulated knowledge: a clause library, a product library, templates, and a memory of how things were decided, all held inside the working system.
- Who it is for
- Practices where the answer to "have we done this before?" is a person rather than a search.
- What is different
- Knowledge is attached to the projects and records it came from rather than kept in a parallel library, so it is found at the moment it is needed instead of being maintained as a separate exercise.
- Availability
- Available on every plan, including the free Starter tier.
- How it connects
- Clauses inform specifications and proposals, products attach to projects, and decisions recorded in the registers become the practice's memory of why.
Part of Know.
Verified against the Mudo application on .
The knowledge a practice cannot find
Ask any director what their practice knows that it cannot retrieve, and the list is immediate: the detail that worked, the specification clause that avoided a dispute, the product that failed on site, the reason a decision was made four years ago.
None of it is written down anywhere findable. It is in a folder structure organised by project, which is the wrong axis for every one of those questions.
Attached to the work
Knowledge is only ever retrieved at the moment it is needed, which is while doing something else. That is why a library maintained as a separate exercise is not used.
Keeping clauses, products and decisions inside the system where the projects are means they are reachable at the moment of the question rather than requiring a detour.
Decisions are knowledge too
The decisions register is the most underrated part of this. Two years later, when somebody asks why a wall moved, the answer being a record rather than a recollection is the difference between a conversation and a dispute.
Common questions
What is practice knowledge management for architects?
It is the problem of not losing what the practice has learned: the clause that settled an argument, the product that failed, the reason a decision was made. In most practices this knowledge exists only in the memory of whoever was there, which makes staff turnover expensive in a way that is hard to see.
How is this different from a shared drive?
A shared drive stores documents that do not know what they relate to. Here the clause library, product library and decision records live in the same system as the projects, so a clause is reachable while you are writing the thing that needs it.
What this page is based on
Every capability described here was checked against the running application before publication. These are the parts of it you can open for yourself.
- /practice/knowledge-memoryKnowledge and memory, as a practice-wide screen in the application.
- /practice/clause-library, /practice/product-libraryThe clause and product libraries are separate implemented, routed surfaces.
Stop solving the same detail for the third time.
Free for solo practices: one user, two projects, no card.