Approach
Approach defines how decisions are made. Applied shows where that method enters real project domains. This page focuses on the method itself: constraints, interfaces, tolerances, responsibility boundaries, and documented decisions that remain stable through execution.
What this page does
This page does not describe a product and does not present a project portfolio. It defines a decision method: how a system is read, where risk enters, and how ambiguity is reduced before decisions become physical and difficult to reverse.
In this author hub, Position defines the role, System Laws define the stable boundaries, Approach defines the decision method, and Applied shows how that method is translated into real project domains.
Operating principles
Limits are not problems discovered at the end. They are design input from the beginning.
Wall, frame, leaf, glass, floor, supporting structure, and adjacent finishes must relate clearly or the system begins to drift.
The system lives in millimetres: gaps, offsets, clearances, alignment, and repeatability.
Who measures, who confirms, who supplies, who executes, and what remains outside the agreed scope must be clear.
If a decision is not recorded, it remains open to interpretation. Open interpretation returns later as delay, correction, or conflict.
A quiet visual result comes from coherent geometry and honest structure, not from decoration used to conceal unresolved conditions.
One system category: windows and doors
In building envelopes, windows and entrance doors are often treated as different products. From a system perspective, they belong to the same category: controlled openings inside a structural and climatic boundary.
Both interact with wall construction, installation position, supporting conditions, tolerances, thermal transitions, access, and interface detailing. Their functions differ, but their systemic dependencies remain closely related.
This is why project coordination follows interfaces and constraints rather than product labels. The building defines the boundary conditions; the selected element must respond to them.
Method: how decisions are made
- Define the boundary. Establish what belongs to the system and what remains outside it: wall quality, floor level, supporting conditions, adjacent finishes, access, transport, and installation conditions.
- List the constraints. Geometry, collisions, clearances, weight, handling, sequencing, and actual site conditions are design input, not late-stage surprises.
- Choose reference planes. Finished wall or raw wall? Finished floor or subfloor? Clear opening or installation opening? The chosen reference determines every measurable result that follows.
- Define tolerances. Gaps, offsets, allowances, movement, and installation clearances become part of the system decision. They are not aesthetic leftovers.
- Assign responsibility boundaries. Who measures, who verifies, who supplies, who transports, who installs, and which assumptions remain excluded must be explicit.
- Document the outcome. Drawings, dimensions, notes, exclusions, and a written decision trail turn the method into something stable, transferable, and repeatable.
- Verify the transition into execution. Before production, delivery, or installation begins, confirm that the agreed geometry, interfaces, access conditions, and responsibilities still correspond to the actual project situation.
In steel, glass, window, and door systems, errors are expensive, visible, and often difficult to reverse. A method prevents improvisation on site from becoming the default project logic.
Reference planes and the point of no return
Many systems fail not because the initial idea was wrong, but because a reference was fixed too early, incompletely, or against the wrong physical condition.
Finished floor versus subfloor. Finished wall versus raw wall. Clear opening versus installation opening. Structural support versus visible finish. These are not drafting details. They determine dimensions, gaps, alignment, fabrication, and installation logic.
Once the wrong reference is transferred into fabrication or installation, the rest of the system begins compensating for it. That is where calm geometry is lost and hidden conflict becomes physical.
Execution and responsibility boundaries
A coherent method does not erase specialised responsibility. It makes responsibility visible before work begins.
Production, transport, unloading, installation, supporting structures, substrate quality, site preparation, electrical interfaces, and specialist verification may belong to different parties. Their boundaries must follow the actual project and the agreed scope.
The purpose of documentation is not to move responsibility away. It is to prevent responsibility from remaining undefined.