The site doesn’t read the model

Field Notes: The site doesn’t read the model

PRACTICE – OCTOBER 2026

Between 2009 and 2014 I supervised building construction in Brazil, running teams of twenty to thirty people. Almost everything we built from was 2D. Whether two things would clash underground or inside a wall had been worked out, if it had been worked out at all, across hundreds of separate drawings that nobody could see together.

I went back to modelling after that, and I have since worked inside federated models on some of the largest infrastructure projects in Australia. I have watched clash detection resolve problems months before anyone poured concrete. I have also watched those same projects send A1 sheets to site as if the model had never existed.

On most projects the model is built by the design team, coordinated by the design team and reviewed by the design team. By the time the information reaches site it has been flattened into sheets. Sections are cut where someone in the office decided a section was needed. When the question on site falls between two of those cuts, the answer is a phone call, an RFI or a guess.

I spent a lot of those years guessing. On one job I had to work out where the underground services actually ran, because the drawings didn’t agree with each other or with what was in the ground. Several stormwater pipes were crushed once the slab was poured over them. The specification was right, but the wrong pipes had been installed, at the end of a chain of errors I won’t go back through here. The concrete pathway had to be broken out in several places where other services ran along or close to it, and some of the toilets had to be demolished because the plumbing didn’t match the drawings either. It cost weeks of work and a great deal of money.

Nobody involved was careless. The information existed. It was spread across so many sheets that no one could hold it all in their head, and the people building it had no other way to see it.

The industry usually explains this as a skills problem, as if site teams don’t use BIM. I think that has it backwards. Site teams use whatever they can open quickly, on whatever computer is in the site office, without asking IT for a licence or a login. For most of the last twenty years that has meant paper and PDF. The model was never offered to them in a form they could use, so they never used it, and we concluded they didn’t want it.

When I started sending models out as a file that opens in a browser, they travelled further than my models ever had. On a recent bridge job, the lead engineer on the client’s side sent the file to the whole project team, for the people who don’t use the modelling software but want to see what the bridge looks like. One of the other consultants replied the next morning to say they had passed it on to their own team, and that “the HTML version is very useful.” The client has since asked whether they can have it on future projects. They will, because it now goes out with every job I do for them.

That is why Udraft 3D exists. I built it because the model I was delivering stopped at a door the people who needed it most could not open. It now goes out with my documentation as a single file that opens in a browser, so anyone on the project can look at the structure without installing anything.

The drawings still matter. They are the contract, they carry the signatures, and they will be on site long after everyone has forgotten the model. But a drawing set is a series of decisions about what to show, and the people building the structure deserve to see the rest of it.

A model that only lives in the design office can only prevent problems in the design office.

Edla Ucker · Founder, Udraft · udraft.com.au

Scroll to Top