BAU LÜTZ
The mobile version of the website is currently being developed.
For now, please open this website on a computer.
THE BAU LÜTZ APPROACH
OUTPUTS AND TRACEABILITY
A project is easier to govern when data, sources, revisions, and decisions remain legible. Bau Lütz defines the necessary deliverables according to the mandate and the decision to be made.
|
01 INITIAL FRAMEWORKObjective, scope, stakeholders, assets, available documents, known constraints, and open questions. The initial framework prevents later phases from starting from different assumptions. READ THE METHOD → |
02 REGISTERS AND MAPSA register of available and missing data, a constraints map, sources, revisions, and responsibilities. Depending on the complexity of the engagement, it may take a tabular, graphic, or narrative form. START A PRELIMINARY STUDY → |
|
03 SCENARIOS AND DECISIONSAlternative comparisons, decision criteria, minutes and a decision log show what was chosen, by whom, when and with which consequences. PROCESS FOR PUBLIC AUTHORITIES → |
04 FINAL DOSSIERTechnical records, responsibility matrices, reservations and proposed next phases may form an updateable dossier. Not every output is included in every mandate. REQUEST AN INITIAL DISCUSSION → |
TRACEABILITY
A DOCUMENT IS USEFUL WHEN IT CAN STAY CURRENT
Simple rules that prevent competing versions
|
01 SOURCEOrigin and reliability of information. |
02 VERSIONDate, author and document status. |
|
03 DECISIONOwner, criterion and consequence. |
04 UPDATEResponsible party, deadline and planned check. |
WHAT THE CLIENT ACTUALLY RECEIVES
A project record that remains useful
Depending on the mandate, outputs may include an initial framework, a constraints map, scenario comparisons, decision records, and an updatable dossier. Every document states its source, version, owner, and status.
Question: retain or replace a building envelope? Sources: survey, technical data sheets, specialist checks. Decision: owner, criterion, date. Next step: authorized further assessment.
It prevents competing versions, makes choices understandable to new stakeholders, and allows work to resume without losing context.
INITIAL FRAMEWORK
Objective, scope, stakeholders, assets, available documents, known constraints, and open questions. The initial framework prevents later phases from starting from different assumptions.
REGISTERS AND MAPS
A register of available and missing data, a constraints map, sources, revisions, and responsibilities. Depending on the complexity of the engagement, it may take a tabular, graphic, or narrative form.
SCENARIOS AND DECISIONS
Alternative comparisons, decision criteria, minutes and a decision log show what was chosen, by whom, when and with which consequences.
FINAL DOSSIER
Technical records, responsibility matrices, reservations and proposed next phases may form an updateable dossier. Not every output is included in every mandate.
TRACEABILITY
A DOCUMENT IS USEFUL WHEN IT CAN STAY CURRENT
Simple rules that prevent competing versions
SOURCE
Origin and reliability of information.
VERSION
Date, author and document status.
DECISION
Owner, criterion and consequence.
UPDATE
Responsible party, deadline and planned check.