Reading a structural file the way an auditor will

I spent years on the client side of public works before I founded this practice, and the habit I carried into consulting is simple: I read every structural file as the person who will one day have to defend it. Not the person who produced it.

On a public building, the file outlives the project team. Development permission rests on architectural and structural drawings signed by a registered consultant (Physical and Land Use Planning Act, 2019; Engineers Act, 2011). The National Construction Authority checks those same signed drawings before the contractor breaks ground (NCA Act, 2011). Years later, an auditor or a court may open the same file and ask one question: does it hold together?

What a defensible file shows

A defensible structural file shows the design assumptions, the load cases, the checking, and the chain of instructions on site. It shows where a variation was issued and why. It shows the inspection that preceded each concrete pour. None of this is exotic; all of it is ordinary practice done in order and kept.

The weakness I see most often is not in the analysis. It is in the record. A correct design with a thin file is a building you cannot account for. An auditor does not re-run your frame analysis — they read whether the consultant of record behaved like one.

Why the Central Bank towers were a record exercise

On the Central Bank of Kenya Pension Towers (KSH 3.5 B), the structural design was demanding, but the discipline that mattered was the supervision record carried through to handover and to the building's opening in May 2022. A tall reinforced-concrete building for an institutional client is, in the end, a documentation exercise as much as an engineering one.

My advice to any procurement officer evaluating a structural consultant is to ask not what they have designed, but what their file would look like if you opened it in five years. The answer tells you who you are hiring.