Showcase · How we tell a programme’s story
Problem, what the model showed, the decision it changed.
When a programme is hard to explain, we build a scroll-driven visual story of it. Not a fly-through, not a slide deck: each engineering problem in turn, what the data and the 3D model revealed, and the decision that followed — so a board can follow it in ten minutes and a site team can recognise their own work in it.
Boards decide in ten minutes. Reports take ten hours.
The model, the survey and the programme already hold the argument. What is usually missing is a way to walk a non-specialist through it in the order it was discovered — problem first, evidence second, decision last — without asking them to open a viewer or read a method statement.
Six parts, always in this order.
The programme in numbers
Four or five figures that set the scale and the constraints — assets, live services, interfaces, margin for error.
The constraints
What shapes every decision: what must stay live, what cannot be lifted, how long each window is.
One chapter per problem
Three beats each: the problem, what the model showed, the decision. A sticky visual on the left changes as the reader scrolls the beats on the right.
Before / after you can drag
Record drawing against survey model, option A against option B, as-planned against as-built. The reader finds the difference themselves.
How the capability works
Where the model lives between chapters: the design meeting, the temporary-works review, the planning session, the site briefing.
Access and leave-behinds
Password-protected link for the client, an offline copy for the room, one-page case studies per chapter, and nothing claimed that has not been measured.
One chapter, as a reader would see it Invented example
The duct that wasn’t where the drawing said.
A made-up highway overbridge deck replacement, chosen because the shape of the problem is common to almost every programme: the record drawings say one thing, the ground says another, and the difference is only cheap to fix if it is found early. Scroll the three beats; the drawing follows.
01 · The problem
Two words on a drawing: “approx. position”
The new abutment piles for a deck replacement sit close to a services duct that the record drawings place only approximately, with no depth. The design works on paper. Nobody can say whether it works in the ground, and a diversion would add months.
02 · What the model showed
Closer and shallower than anyone had recorded
A survey-based model put the duct 300 mm from the pile line and 1.4 m shallower than the record. Overlaid on the design it was a plain clash — visible to the whole team, months before site, without a trial hole.
03 · The decision it changed
Move the piles, not the duct
The pile line moved 600 mm, the diversion came out of the programme, and the road-closure plan was rewritten around the new sequence — before anything was ordered. That one line is what the chapter exists to deliver.
Honest enough to show the client’s own engineers.
A story page is only useful if the people who did the work recognise it. These rules keep it that way.
Have a programme that is hard to explain?
We can build the story of it in weeks, from the survey, models and programme you already have. Ask for a private preview and we will walk you through a real one, with its owner’s permission.