How can an engineering consultancy use AI without risking its technical judgement?

Where do an engineering consultancy's unbillable hours actually go?

Ask a structural or civil engineering practice where the week goes and the answer is rarely the analysis. It is everything wrapped around it. A commission starts with a fee proposal: scope, exclusions, deliverables, a resourcing assumption and a fee build-up, usually adapted from whichever similar proposal someone can find. It continues with calculation packages that need a cover sheet, a design basis, a list of assumptions, loadings and references to the relevant standards before an independent checker will look at them. It ends with a technical report or design note that turns the engineer's working into something a client, an approving body or another consultant can read.

Around all of that sits the practice's quality system. Document registers, check and approval records, revision histories, and the CPD logs that professional bodies such as the ICE and IStructE expect chartered members to keep. None of it is optional and none of it is billable in the way the engineering is.

These jobs land on the engineers who know the work best: associates and directors who sign off design, and who are also the people the practice most needs on fee-earning tasks.

Why does the same engineering information get written up twice?

An engineer's working already contains most of what the write-up needs. The design software holds the model and the results. The spreadsheet holds the load take-down. The email thread holds the client's brief and the agreed changes. Yet the calculation narrative is typed fresh, the assumptions are copied from the last job and corrected by hand, and the report restates what the calculations already say in longer sentences.

The duplication is worst at revision. A change to the brief ripples through the calculations, then has to be chased manually through the cover sheet, the assumptions register, the report and the transmittal. Every manual step is a place where a superseded figure can survive into an issued document, which is exactly the kind of error a checker is there to catch and exactly the kind that wastes the checker's time.

Which engineering processes are the strongest candidates to rebuild?

The best first rebuild is the document your practice produces most often with the most senior input. In most engineering consultancies that is one of four.

• Fee proposals. The scope library, exclusions and fee build-up already exist across past proposals. A rebuilt proposal process assembles a first draft from the brief and the practice's own precedents, and fee estimating can draw on how long similar commissions actually took.
• Calculation write-ups and technical notes. The cover sheet, design basis and narrative are drafted from the engineer's working and the practice's templates, with each figure traced to its source. The technical reports page covers this in detail.
• Quality records. Check and approval records, document registers and revision logs are produced as the work moves, rather than reconstituted before an audit. See quality records.
• CPD records. Engineers attend talks, read guidance and learn on the job, then struggle to log it. A simple rebuilt process captures the activity and the reflection when it happens, in the format their institution asks for.

If you are unsure which of these costs your practice most, the audit estimates it from your own answers.

Where must engineers stay in control?

Engineering judgement is never delegated. The rebuilt process does not choose a design approach, pick a partial factor, interpret a standard or decide that a check has passed. It drafts the words and assembles the document; the engineer supplies the reasoning and owns the result.

Three controls are built in from the start. First, every drafted figure carries a link back to the calculation or model it came from, so the checker can verify rather than re-derive. Second, the practice's existing prepare, check and approve sequence is kept, with a named engineer at each step, and nothing is issued until the approver has signed. Third, anything the process could not source is flagged as missing rather than filled in. A blank that asks a question is safer than a plausible sentence nobody wrote.

What would a rebuilt process mean for your engineers' week?

The associate who used to spend an evening turning a set of hand calculations into a presentable package now spends that time checking a complete draft. The director reviewing a fee proposal reads a document that already follows house style, instead of rewriting the scope from memory. Graduates learn the practice's standards from well-formed drafts rather than from last year's file.

To estimate what that is worth, take the hours each engineer spends on write-ups and proposals in a normal week, multiply by the number of engineers, by your charge-out rate and by 46 working weeks. The unbillable hours calculator runs the sum.

How is one engineering process rebuilt in 30 days?

We sit with the engineers who produce the document and map where each part of it comes from. The process is then built on the practice's own templates, precedents and quality procedures, and tested on live commissions, not samples. In the fourth week the team is trained and it becomes the way that document is produced, with 30 days of support afterwards. The team behind it has more than 35 years in industry, combined, and includes a civil engineer who worked as a Works Manager on TfL LoHAC and at Interserve, Jackson Civil, Barratt and Ringway Jacobs, so engineering documentation is familiar ground.