Design & Coordination

The first shift reality capture brings to design is psychological as much as technical: you stop drawing against an idealised, orthogonal fiction and start drawing against the building as it actually is. Bring the point cloud into your modelling environment and the real geometry is simply *there* -- the wall that leans 50 millimetres over its height, the floor that falls 30 millimetres across the room, the column that is not quite where the grid says, the soffit that steps where an old alteration left it. You set out new elements to that reality. Joinery is scribed to the wall it will actually meet; a new floor build-up is designed around the real levels; a partition lands where it will genuinely clear the existing beam.

This sounds obvious, yet its absence is the source of a huge share of site problems. When you design against a drawn rectangle and the building is a slightly skewed parallelogram, the gap between the two becomes the contractor's problem, discovered late and resolved expensively by cutting, packing, re-ordering or improvising. When you design against the captured reality, that gap is closed on screen, deliberately, by someone who can see the consequences. The cost of accommodating a lean is trivial at the model stage and punishing at the installation stage, and the only thing that moves it from late to early is having the real geometry in front of you while you design.

There is a discipline to doing this honestly. The captured geometry is a measurement with a stated accuracy and with gaps, so you design knowing roughly how much the cloud can be trusted and where occlusion has left voids you must verify by other means before committing. You also design against a moment in time -- the clutter, the furniture, the temporary works captured alongside the permanent fabric -- so part of the skill is reading which points represent the building you are keeping and which are noise. Used with that judgement, designing against captured reality is the single most effective way to kill the 'it did not fit on site' failure before it is born. Used naively -- treating the cloud as perfect and complete -- it simply moves the surprise to a different place. The cloud is ground truth only to the accuracy it was captured at, and never beyond its occlusion shadows.

Design on a real project is a team sport, and its hardest moments are the seams where disciplines meet: where the architect's form, the engineer's structure and the services engineer's ducts, pipes and trays all have to occupy the same real space inside a building that already exists. Reality capture transforms this coordination by giving every discipline the same accurate basis. The scan-to-BIM model, or the point cloud itself, becomes the shared representation of the existing building, and each discipline models its new work against it in a federated model -- the combined model in which everyone's contributions are brought together and checked for conflict.

The power here is a single source of truth. Without capture, each discipline works from its own interpretation of old drawings and site notes, and the discrepancies between those interpretations become clashes that only reveal themselves when the trades arrive. With a captured as-built as the common reference, the architect routes the design around the real structure, the structural engineer sizes new interventions against the frame as it genuinely is, and the MEP engineer threads services through the space that is actually available -- all coordinated against one measured reality rather than several guesses. The federated model becomes a faithful composite of real existing conditions plus proposed new work, which is exactly what good coordination needs.

This is why reality capture and BIM are such natural partners, and the pairing is especially potent in existing buildings, where the cost of getting coordination wrong is highest and the information is otherwise weakest. It is worth repeating the honest caveat from the scan-to-BIM modules: building the existing-conditions model is still largely skilled manual work, and it is modelled to a chosen level of accuracy and detail -- so the coordination is only as trustworthy as the model's fidelity and the cloud's accuracy behind it. A wall modelled as a clean plane when the real one bows will coordinate beautifully in the model and fight you on site. Good practice keeps the point cloud available alongside the model precisely so the team can check the model against the raw evidence where it matters, and records what accuracy and level of detail the existing model was built to, so nobody over-trusts it.

The sharpest coordination tool reality capture unlocks is clash detection against the as-built. In a federated model you can automatically, or by eye, find where new work conflicts with the existing building -- where a new duct runs into a down-stand beam, where a riser collides with a slab, where a new partition fouls an existing column. The decisive point is *what* the new work is being checked against: not an idealised or out-of-date model of the existing building, but a representation derived from the captured reality. You are testing the design against the building as it genuinely is.

The value is almost embarrassingly simple to state. A clash caught in the model costs a model edit -- move the duct, resize the opening, reroute the run -- and a little of a coordinator's time. The same clash discovered on site costs rework: demolition, re-fabrication, delay, disruption to other trades, and sometimes a compromise that damages the design. Clashes with *existing* structure and services are among the most common and most avoidable, because they arise precisely from not knowing what was there -- and capture is the cure for not knowing. Running the new design against a captured as-built systematically converts expensive site surprises into cheap screen decisions.

Two honest qualifications keep this from becoming over-claimed. First, clash detection is only as good as the as-built it checks against: if occlusion left a service unrecorded, or the model simplified a feature away, the clash will not be caught -- so the quality, accuracy and completeness of the capture directly bound the reliability of the clash check, and the team must know where the blind spots are. Second, a detected 'clash' is a prompt for judgement, not an automatic verdict; tolerances, what counts as a real conflict versus acceptable proximity, and how to resolve it are design decisions. Used well -- against a well-planned capture, with the point cloud on hand to verify, and with the limits understood -- clash detection against the as-built is one of the highest-return uses of reality capture in the whole design process. It is also the bridge to the next idea: if you trust the geometry enough to clash-check against it, you may trust it enough to manufacture against it.

Pull the threads together and the real prize of capture-driven design emerges: one trustworthy, measured basis shared by the whole team. The architect, the engineers, the contractor and the fabricators all work from the same accurate representation of the existing building, so decisions compound instead of conflicting, and the disputes that usually erupt from differing assumptions about 'what is there' simply do not arise, because there is a measured answer everyone can see. This single-source-of-truth quality is the quiet foundation under every other benefit in this lesson; coordination, clash detection and confident design all flow from the team no longer arguing about reality but reading it.

That trust is what makes the most demanding modern method possible in existing buildings: prefabrication and off-site construction. Manufacturing a component -- a facade unit, a bathroom pod, a riser module, a run of plant -- away from site and delivering it to slot precisely into place is transformative for speed, quality and waste. But it is also unforgiving: the factory cannot improvise, so the real dimensions it manufactures to must be known *in advance* and must be *right*. You cannot safely fabricate a module to fit an existing structure you have only estimated. Reality capture supplies exactly the ground truth prefab depends on -- the accurate as-built geometry that lets a part be made to fit the first time. Capture, BIM and prefabrication form a chain: capture the reality, coordinate the design against it, manufacture to the captured dimensions.

The discipline, as ever, is honesty about accuracy. Prefabrication against a captured building raises the stakes on the capture: the accuracy must genuinely be good enough for the tolerances the manufactured part demands, the critical interfaces may warrant targeted verification rather than trust in the general scan, and where the fit is critical and the cost of error high, the capture accuracy at those interfaces is a matter for verified methods and, if it must be binding, a qualified surveyor. But the principle is powerful and clear: the better and more trustworthy your knowledge of what exists, the more of modern, model-based, manufactured construction you can safely bring to bear on an existing building. Capture turns the existing building from the riskiest unknown in the project into the shared, measured foundation the whole team builds on.