Module · Vault
Promote proven project material, ratify lessons with their source, and carry trusted construction knowledge into the next job.
The problem
The detail that prevented a leak, or the sequence that avoided a delay, usually stays with one person, or one project.
What it costs today
Construction knowledge lives in one inbox, one closeout binder, or one person's memory - and it leaves when the project or the person does.
The waterproofing detail that prevented a failure, or the clause that avoided a dispute, stays with the person who learned it and rarely reaches the next project.
Even when a lesson does get repeated, the original document, event, or decision behind it is usually gone, so no one can check whether it still applies.
What changes with Vault
Vault turns selected project material into governed organizational knowledge, with its source attached and a person accountable for every lesson it grounds.
Promoted documents keep their original project and source, so anyone reviewing a lesson can trace it back to where it came from.
A lesson becomes available to guide future work only after a responsible person reviews its evidence and approves it.
Which one
Library holds external published authorities. Vault holds your organization's own promoted material and ratified lessons. Documents holds the files of a single project.
Vault is a governed archive of promoted documents and human-ratified lessons that guide future projects.
Library holds external published authorities - specifications, standards, regulations, and licensed reference corpora - with edition and license kept visible.
What it holds
Promoted material and ratified lessons each carry their source and approval state.
Specifications, standards, regulations, and licensed reference corpora stay external to any one project.
Who approves it
A responsible person ratifies each lesson before it can ground future work.
Nothing to ratify - content stays governed externally by its publisher, region, and edition.
How you use it
You consult approved, in-scope lessons when planning or reviewing a new project.
You browse governed corpora and cite the exact clause and edition you relied on.
How it works
Vault keeps every lesson tied to the material that supports it and the person who approved it.
Selected project material moves into Vault while it keeps its original project and source.
Write a lesson by hand, or start from a supported lesson proposal.
Confirm the event, document, or project material that supports the lesson before it goes further.
A responsible person reviews and approves the lesson - nothing grounds future work before this step.
Keep the lesson available only where its approved scope applies, and revisit that scope over time.
Mark a lesson stale, expired, replaced, or withdrawn honestly as conditions change.
In practice
A sample of the material Vault holds, each with its source and review state.
Documents
A finished project's closeout report is promoted into Vault with its original project and source attached, ready to reference on the next job.
Waterproofing
A site team proposes a lesson about the waterproofing detail that fixed a repeat leak; a supervisor reviews the evidence and ratifies it.
Procurement
A lesson about ordering a specific equipment category early is scoped to that category, so it only applies where that scope is set.
Subcontractor
After a costly delay, a team writes a lesson requiring a specific subcontractor qualification check before award, with the delay record attached as evidence.
Product in action
Promote a document, ratify one lesson from its evidence, and make approved, in-scope lessons available to the next project.
Vault walkthrough
Promote a document with its source project attached, ratify one lesson from its evidence, and make approved, in-scope lessons available to the next project. Proposed lessons change nothing until a person ratifies them. Vault does not pick lessons by question relevance.
Capabilities
FIG. 01
Document promotion
A promoted document keeps its original project and source visible on the record before and after the move.
A document moves into Vault while its original project and source stay visible on the record.
FIG. 02
Lesson ratification
The evidence behind a proposed lesson, and its current state, stay visible before you approve it.
See the evidence behind a proposed lesson and its current state before you approve it.
Capabilities
Every lesson in Vault keeps a record of where it came from and who approved it.
Selected project documents move into Vault with their original project and source kept on the record.
Write a lesson directly, or start from a supported proposal drawn from project material.
A lesson becomes available to guide future work only after a responsible person approves it.
Every lesson carries an honest lifecycle state, so no one mistakes an unreviewed proposal for ratified guidance.
Set the narrowest valid scope for a lesson, and mark it stale, expired, or replaced as conditions change.
Using it well
A few habits keep Vault trustworthy as it grows.
Works well when
Reach for something else when
FAQ
Common questions about Vault with Brickato.
We load your own package on the call and you interrogate it yourself. If the findings do not hold up, you will know inside twenty minutes.
