At Alloovium, when we build software, we go back to first principles. Along the way, we find out some cool shit. This is where we share what we learn as we rethink construction practices with surprisingly long histories.
If you’re reading this, chances are inspections are part of your day on site. You know why they matter, but what problems shaped the way we do them today?
Being the construction workflow and paperwork history buffs that we are, we found three moments that expose different problems the modern plan is meant to address.
Rome fell because they didn’t run ITPs
Kidding, but now that I have your attention…
The first story begins with Vitruvius, a Roman architect. While writing about building materials, he spent a chapter on bricks. Vitruvius was concerned that bricks made in the hottest part of summer could be deceptive: the outside might look dry while the inside still held moisture.
Build those bricks into a wall and they would shrink as they dried. The plaster would lose its support, cracks would form, and sometimes the wall itself would fail. Vitruvius used Utica to make his point: its inhabitants would not allow bricks to be used in buildings unless they were at least five years old and approved by a magistrate. Someone had to decide whether the material was fit for use before it became part of the building.
The next moment takes us to Long Beach, California. At 5:54 pm on 10 March 1933, an earthquake struck Southern California. In and around Long Beach, 120 schools were damaged, including 70 that were destroyed. Had the earthquake hit during school hours, the loss of life could have been much greater.
The damage forced a hard look at how the schools had been built. Poor workmanship, substandard materials and poor ground conditions had all contributed. Within a month, California passed the Field Act, bringing state review of public school designs and inspection during construction. The question was no longer just whether a finished building looked sound. Its design and the work as it was built needed independent scrutiny.
The third moment takes us to the Trans-Alaska Pipeline and its weld X-rays. The pipeline was being built through mountains, rivers and permafrost. Its mainline welds were subject to radiographic inspection. In 1975, concerns emerged about the welds and the X-rays meant to prove their quality. A former employee of the radiography contractor, Peter Kelley, alleged that images of good welds had been substituted for images showing bad ones. Alyeska’s quality team had also found welding and radiograph problems, and the company expanded its audit to the 30,805 radiographs made that year.
The audit reported 274 apparent duplicate radiographs, 605 apparently missing radiographs and 1,948 welds with flaws beyond the acceptance criteria. These were different kinds of problems. A missing or suspect image did not, by itself, prove that a weld was faulty. But if the X-ray in the file belonged to another weld, what could anyone say with confidence about the weld already buried in the ground? The audit later established that 307 of the entries counted as missing related to welds that had not yet been made.
We won’t pretend these events form a neat lineage from Utica to California to Alaska. They do pose three different questions. Is the material fit to use? Who checks the work as it is built? Can we trust the evidence before the work is covered?
The modern inspection and test plan brings those questions into a planned process.
Today, people rarely describe a problem on site as an “ITP issue”. They talk about a missed inspection, a crew waiting to move on, rework, or a test result nobody can confidently match to the work. A well-run ITP brings decisions forward. An over-engineered one can bury them under administration.
We think the opportunity is to bring the planned check into that live moment on site. A supervisor can call with an update, and Alloovium can ask for missing details and prepare the relevant record. A configured workflow can then check the update against project documents and show which inspections, evidence or approvals still need attention.
When lots are reportedly ready for close-out, the workflow can check whether the required inspection sign-off has been recorded. If it is missing, Alloovium can bring the ITP requirement into view and prepare a follow-up for the team to review. The inspector performs the inspection, and the authorised people make the decision to proceed or not.
An ITP earns its place on a job when it changes what happens while the work is still in front of the crew. A requirement discovered after close-out can only explain the rework. A useful check reaches the people responsible while they can still act on it.