A builder removes a wall on a Tuesday, props it, and rings an engineer on Wednesday because building control has asked for calculations.
Everybody now has a problem. The work is done, the options are limited, the solution will be more expensive than it needed to be, and somebody is standing in a house that cannot be used.
Why this keeps happening
Because structure is invisible until it is a problem. Clients think of an engineer as somebody who produces a document for building control rather than somebody whose input shapes what is possible.
The right sequence for most projects
Concept, early structural input, developed design, calculations and details, then construction. The early input costs little and changes the rest.
When early involvement genuinely pays
Removing structure, opening up a space, adding storeys, basements, unusual spans, anything on a difficult site and any existing building with unknowns.
When it can reasonably wait
Simple, well understood work where the structural solution is obvious and standard. Saying so honestly builds the credibility for the projects where it matters.
Explain what early input actually does
Tells the designer what is achievable, what a span would cost, whether a column is unavoidable and where the structure wants to be. It shapes a better scheme.
Explain the cost difference
Early input is hours. A solution designed around completed work is a different and larger exercise, and occasionally something has to be undone.
Explain the building control point
That structural information is usually required and that discovering this late is what causes the emergency, which connects to feasibility study questions before any drawings.
Explain what happens when work has already started
That it is not a catastrophe, that there is a process, and what the engineer needs immediately. Frightened builders need a route rather than a lecture.
Explain the temporary works point
That propping and support during the work is a real consideration and whose responsibility it is. It is frequently nobody's until something moves.
Explain the coordination with other consultants
Who does what, what an engineer needs from an architect and what the contractor needs from the engineer, which is the ground in project enquiries for engineering consultancies.
Explain what a builder can and cannot decide
Contractors make structural judgements on site every week, most of them sound and some of them not, and homeowners have no way of telling which is which. Saying plainly which decisions need an engineer, and why, gives a client the confidence to ask a question rather than trusting whoever is holding the hammer.
Explain who is responsible for what
When something goes wrong, clients discover that responsibility was distributed between people who each assumed somebody else held it. Setting out what the engineer is responsible for, what the contractor is and what remains with the client is the clarity that makes a project defensible afterwards.
Publish an early advice service
A short, fixed fee conversation at concept stage. It is a small product that prevents large problems and it wins the full appointment later.
Publish what you need to start
Drawings, dimensions, photographs, what is being removed and what is above, which is the checklist in site visit and survey questions before a proposal.
Be reachable when the wall is already down
These enquiries arrive urgently, mid morning, from a site, and the firm that answers is the one appointed, which is the case for proactive support answering questions before customers ask.
Getting started
Publish the right sequence, an early advice service and what you need to start, then capture urgent site enquiries at any hour. SpideyChat for professional services firms answers from your published pages, plans are on the pricing page, and the chatbot ROI calculator works through the numbers.