Our latest thoughts on AI and the industry that builds the world.
Trafikverket graded Hässleholm–Lund robustly unprofitable; eleven months later it was in the national plan, with more money than the agency asked for. On the anatomy of the state's most audited number, and why it is not read before the decision.
A deliverable is a dozen parts that must agree and end in one signed document. A chatbot answers one question at a time; Yesper does the work, like a colleague.
Trafikverket calculates the societal value of both the projects that make the plan and those that don't. Both groups land at the same score. The analysis exists; the system ignores it.
A metre of Stockholm metro costs 7.3 times more than in the 1970s, in real terms. The construction tempo is unchanged in fifty years: nine years then, nine years now. What grew is the years before ground is broken.
Hundreds of firms, temporary coalitions, a name on every deliverable: the industry's fragmentation is a negotiated liability architecture, and the tools that survive are the ones that respect it.
Software just ran a five-year public experiment on AI and skilled work. Read for the built world: help with steps plateaued, handing over whole tasks worked, and the signature never moved.
The scale that sorts AI maturity today was written down in 1978, for robots on the ocean floor, and it measured how much the human dares hand over. For an engineering firm, five steps are enough, from locked down to AI-integrated. The hard part is the climbs, and every climb has a concrete precondition.
A tender worth tens of millions can rest on a hundred files, while the decision is taken in forty-five minutes. Yesper reads the whole package and gives you every requirement on its own row: answer, status and source.
The term is about to be on every vendor slide in construction. The definition that makes it testable: judge what comes back after the handover. Plus the hours it frees, and the precedent from software.
Nine of ten transport megaprojects exceed their budgets, and almost all of the growth happens before construction starts. The key statistics on overruns, error costs, RFIs and productivity in European infrastructure, each with a primary source and a confirmed-or-contested label.
Of 26 new objects in the national plan, one gets a construction start before 2037. Five mechanisms explain why the planning chain eats the decade, each with its source.
Everyone in Visby agreed: the will and the money exist, execution capacity doesn't. But consensus is not capacity. Capacity is engineering hours.
Three countries, three eras, three methods, one finding: most cost growth happens before construction starts. The mechanism is lock-in, and it lives in the planning years.
Two months after the plan was fixed, Trafikverket said it out loud in Almedalen: delivery capability must be strengthened. The missing variable in every capacity debate is throughput per engineer.
Iron rules in 1919, concrete in 1924, AMA in 1950, the Eurocodes since 1975: a century of writing methods down so any desk gives the same result. That consistency turns out to be the preparation for handing work over whole.
Insufficient rail capacity puts 130–340 billion kronor of Swedish export value at risk every year, according to the rail industry's own report. Cost overruns get audited down to the krona; the cost of inaction is counted by no one.
A stormwater study is skilled engineering from end to end. So why does the week run long? Most of it goes to the disciplined execution of standard methods, and to running them again each time the plan moves.
Sweden is counting its physical readiness assets again: road bases, quarries, rail ferries. The capacity one step earlier, to investigate, design and review inside the classification boundary, is not on any list yet. It sets the pace of all the others.
Two Oslo construction-AI companies sold for a combined $630 million, and a Stockholm company raised a Series A led by Andreessen Horowitz. What the Nordic exits prove, and which seat in the vertical is still open.
Who is liable when AI does engineering work? Exactly who was liable yesterday. What changes is what the signature means.
Sweden writes its building rules once, nationally, then applies them through 290 municipal building committees, each with its own practice. Why the variance survived a legal ban, and why the new national building regulations widen it.
The association of Sweden's construction clients chose a seminar title most industries would never print about themselves. The state's cost follow-up, one shared Excel file per finished project, suggests they chose it accurately.
Planning, concept, preliminary, detailed, construction, as-built: the six stages nobody outside the industry knows, and the handoff where the overrun is born.
The fear assumes engineering is a fixed pile of work. It is a backlog instead: cheaper engineering means more gets built, not fewer engineers, and the judgment left to the engineer becomes worth more. Why replacement was never the real question.
A €75,000 environmental impact assessment isn't a document but an assembly of a dozen specialist studies at the front of a multi-year permit process. The anatomy behind the figure, and why the report is the cheap part.
Convert British benefit-cost ratios to Swedish NNK and one ruler holds four countries: Norway at −0.7, Sweden's plan at −0.3, Crossrail at +1.0. The difference is not how anyone counts, it is who lets the count decide.
A Swedish rail project cut roughly two billion kronor by re-evaluating a design alternative late in planning, a comparison that is normally too expensive to make. What freed engineering hours actually buy, and what Europe gets if such comparisons become routine.
Thirteen disciplines, two years, one 30-kilometre stretch of railway. Most of it is real engineering that deserves respect. That is exactly why the churn around it is a tragedy.
The national transport plan for 2026–2037 lowers funding for research and innovation from 7.4 to 4 billion kronor, while its own delivery depends on new working methods. Where the innovation comes from instead.
Sweco's Urban Insight analysis puts numbers on Europe's quiet water risk: water stress for 30 percent of the population, €18 billion in flood damage in one year, a fifth of treated water leaking away. The repair is thousands of small municipal projects, and each one carries its own paperwork.
Thousands of documents per project, but only 60–80 standardized types. Finite and standardized is exactly what an AI civil engineer can work through, type by type.
Two randomized trials, two opposite results: 55.8 percent faster on a bounded task, 19 percent slower on open-ended work. The shape of the task decides, and it also decides what is worth buying.
A quantity error follows straight into the bid price and then into the settlement. Yesper reads the model and takes off the quantities, every figure linked to its object.
Norconsult, Sweco and AFRY described AI to investors in the same year, in three different registers. Read together, the investor materials agree on one point: the leverage sits in design and engineering, before construction starts.
National annexes that silently override Eurocodes, codes that change meaning between editions, requirements split across languages. Why generic AI fails on European regulatory documents.
SwecoGPT, Sven AI, AFRY's AI hub, Ramboll Tech: the region's largest consultancies all run internal AI assistants, and adoption is real. A survey of what the tools solve, and of the layer still missing.
The most defensible productivity claim in engineering AI is not speed. It is one more design iteration per project at constant fee. Toyota proved why that wins.
In 2011, Sweden replaced its Planning and Building Act to speed planning up. The average local development plan in Stockholm County went from 35 to 62 months instead. How the paperwork took over, with sources.
Half the time, half the cost is the Swedish rail sector's own vision, not a government target. Audit data shows where the years go today, and which halves are addressable with existing technology.
A consulting hour sells two things: the doing and the knowing. When AI does the doing in minutes, the hour stops measuring what a client should pay for, and the next step is to price the deliverable instead.
The real shift of 2026 is not faster help; it is AI that takes whole deliverables end to end. An honest survey by job of what works now, what stays human, and what is still marketing.
Skanska booked a billion dollars of data-center orders in one quarter. AI is ordering buildings faster than the industry can grow the capacity to design them.
It starts with a button, not a prompt. What an AI civil engineer actually does between that press and a signed 40-page water and sewer study: the intake, the work, the check, and the engineer who signs.
An average construction project generates 796 formal requests for information, each a question the contract documents were supposed to answer. Processing them costs $1,080 apiece, the median answer takes 9.7 days, and one in five never comes.
An AI civil engineer produces the whole noise assessment draft end to end: it reads the material, runs the standard methods, and checks its own numbers, then an engineer reviews and signs. What it does, what it does not, and what stays human.
Five replicas of the same agent, each with a different reading directive, merged as a union. They catch the requirements a single pass misses every time, because one reader tires of insurance clauses and skims the ending.
One engineer calculated, two colleagues reviewed, and a small error still reached a delivered multi-million project. Why careful people miss things, and what happened when a machine re-derived the calculation on its own.
Swedish rules set no slope angle to copy; they ask for a judgment about this site. Yesper assembles the preparation from the activity's documents and the week's actual conditions, so site management judges instead of compiles.
The Get It Right Initiative puts the direct cost of construction error at £5 billion a year in the UK alone, and 10–25 percent of project cost once latent and indirect costs are counted. The numbers, the dispute data, and why a new rework study does not overturn them.
Software moves fastest where the work is enumerable, and infrastructure's written deliverables are a finite, enumerated list whose entries compose into entire statutory packages. A strategy essay on why the endgame is visible from here.
What happens to a design deliverable on a Trafikverket project between delivered and approved: the self-checks before delivery, the comment rounds, the requirement documents behind every remark, and who signs off at the end.
Eurocodes went from 58 parts to 74. AMA Anläggning grew a quarter. UK infrastructure consent takes 62 percent longer. The engineers stayed the same; the corpus of rules did not.
Same models underneath. Copilot works on the task; Yesper works on the whole deliverable and holds it together. The narrative, and the feature table where the two overlap.
SGU and Naturvårdsverket publish open geodata with no AI affordances, so we built the affordances: MCP servers and specialist agents that turn railway kilometre notation into answers about bedrock and protected areas.
Nearly everyone uses AI; few can point to the value. Four levels, ordered by how much of the organization the AI carries, and where the market stands in 2026.
The rulebook outgrew the humans who apply it. When the machine holds the rulebook, the engineer gets the judgment back: juniors learn on real problems, seniors design again.
What machine review of a tender package actually does: reads every file instead of sampling, extracts each requirement with a citation, checks the documents against each other, and flags deviations. The estimator keeps the decisions.
Selection on uncertain cost estimates systematically picks the underestimated projects, even when every estimate is honest. Why overruns need no villain, and what counters them, with sources.
Norway's external quality gates deliver an average 5 percent underrun across 111 large state projects. The cost growth that remains happens before the gate, in the front-end document phase that governance cannot reach.
No field has more theoretical AI upside and lower actual use than architecture and engineering. The explanation is not a conservative industry: for forty years, software could move the documents but never read them. That is what just changed.
A bid worth tens of millions rests on about a hundred files, and the meeting that approves it takes 45 minutes. Reading everything would take four people a week: the gap is covered by trust, and that is time arithmetic, not negligence.
The model proposes; the registry disposes. Standard codes, file IDs and citations all go through deterministic code, never the model, because traceability is an architecture, not a tone.
MIT: 95 percent of AI pilots deliver no measurable return. Why rollouts get stuck in cautious testing, and what sets apart the firms that lean in and start producing whole deliverables a new way.
In a design calculation nothing stands alone: change one input and the whole chain re-runs by hand. Why one small change costs a week, and what happens when re-running it takes minutes instead.
A procurement was cancelled after every single bidder missed the same line item, worth about 40,000 kronor. Tender documents concentrate large financial consequences into single words and page breaks, and the industry's catch mechanism is still keyword searches in PDFs.
AI now does the document work in law, clinical medicine and software, while the professional keeps the judgment and the signature. Construction is the largest industry in the world still without its version.
AI Act risk classes, NIS2 duties that travel through supplier chains, data residency and the security review IT will run: the questions an engineering firm should ask before signing with an AI vendor, in one checklist.
Replacing a single lamp along a rail line takes minutes. The documents before and after take longer than the job. On compliance built for megaproject risk, applied to the smallest tasks in maintenance.
A framework for costing engineering AI on your own numbers: the hours in a deliverable, the price of the revision loop, and the two terms most business cases leave out.
Wide-format railway drawings crash standard PDF rendering at exactly 32,767 pixels; invisible Unicode characters quietly corrupt Swedish numbers. The file that breaks the pipeline is always the one the reviewer needs, so the engineering under the demo is what decides whether document AI works at all.
How engineers come to trust an AI colleague: first-run moments from live infrastructure projects, including the runs that needed correcting and what those corrections taught the system.
Autodesk and FMI priced construction's bad data at $1.85 trillion for a single year. Followed upstream, the figure leads to ambiguous plans and specifications, multiplied through every handoff in the supply chain.
The standards that govern infrastructure are civilization's memory: humanity already agreed on how to build a retaining wall and a stormwater system. The engineering that remains is fitting the settled solution to one specific place.
Every model call we removed is one fewer place a number can silently change on its way to an engineer. Four deletions, one rule: LLMs for judgment, code for transformation.
One ambiguous clause in a specification is reinterpreted at every handoff between designer, contractor and subcontractor, and the cost grows at each step. On the mechanism that turns small design defects into large bills on site.
Germany's biggest rail project has no opening date, HS2's cost estimate has grown by half, and Ostlänken went from 13 to 111 billion kronor. What Europe's slowest projects share is not geology: it is immature designs procured, reviewed, disputed and redone.
What engineers and IT departments actually ask before deploying AI in construction: who is liable, whether it trains on your data, whether you can trust its citations, and what it costs. Straight answers, each linked to the full explanation.
Riksrevisionen has twice audited where Swedish infrastructure costs grow, and twice placed the increases in the planning phase, before construction begins. A guided read of the two reports, with the exact figures and how to cite them.
The rules of infrastructure engineering are public down to the last national annex. The judgment that gets them right was never archived: it lives in senior engineers, and it has always retired with them. That is starting to change.
The whole map, openly published: what is worth buying today, what to expect from it, what the industry's own AI builds have actually become, and the corner that still stands empty.
Labour productivity in construction has fallen while every other major sector advanced. The Swedish figures, the global pattern, and why the bottleneck sits in documents rather than on site.