Your report gets relied on by people who never hired you.
A geotechnical report or a structural review is written for one client and one purpose. Then it is passed to the owner, the contractor, the lender and the next consultant. Reliance is what turns one fee into a claim from four directions.
Build the practice file Read the short answer firstOften more people than signed your agreement.
Ground and structure claims surface late.
Shared across every claim in the year.
Who can bring a claim against my engineering report?
Potentially anyone who relied on it and lost money, not only the client who paid for it. Reports move through a project. An owner uses it to decide, a contractor prices from it, a lender funds against it, and a later consultant builds on it. Each of those is a person who may say they relied on your work, and professional liability responds to the claim rather than to the invoice.
This is why the two most useful pieces of paperwork in this discipline are not technical. They are the limitation and reliance wording in your report, and the retroactive date on your policy. One controls who is entitled to rely on you. The other controls which years of your work are insured at all.
Most professional claims arrive years after the work. In this discipline that gap is longer still, because the thing that reveals the problem is time itself: settlement, movement, a wet winter, a load that was never applied until the building was occupied and fitted out. A report written early in a project can be the subject of a claim long after the building is finished and the firm has moved on to other work. That is not a reason to worry. It is the reason claims made cover, run-off and the retroactive date matter more here than in almost any other profession.
Three are paperwork and one is the policy.
Reliance and limitation wording
State in the report who it was prepared for, what it may be used for, and that others rely on it at their own risk. It does not make a claim impossible and it is not meant to. It sets the boundary you can point to, and its absence is noticed immediately when something goes wrong.
Scope, and what you did not do
What you were asked to assess, what you assumed, what you were not able to inspect, and what was outside the engagement. The claims that are hardest to defend are the ones where the report is silent about its own limits, because silence gets read as coverage of everything.
The retroactive date
Professional liability is written on a claims made basis, so the policy that answers is the one in force when the claim arrives, and it only reaches back as far as the retroactive date. Changing insurer or letting cover lapse can quietly reset that date and strand years of past reports.
The limit is annual and shared
One limit usually answers every claim made in the policy year, and on many wordings defence costs come out of it. Two claims in one year on a long project history is not unusual, which is the argument for looking at the limit against your report volume rather than against a single job.
Three that had nothing to do with the engineering being wrong.
The report that travelled
A geotechnical report prepared for a feasibility study was handed to the eventual purchaser and used to price the foundation. Conditions on part of the site differed from the boreholes taken for a different question. The engineering was sound for the scope it was written for, and the argument was entirely about who was entitled to rely on it.
The date nobody checked
A firm moved insurers to save premium. The new policy carried a retroactive date matching the new inception rather than the original one. Every report written before that date was uninsured, and nobody noticed until a claim arrived on a six year old project.
The design-build handshake
An engineer took on a delegated design element under a contractor’s design-build agreement. The contract asked for a fitness for purpose outcome rather than reasonable skill and care. That is a promise rather than a standard, and professional liability answers negligence, not promises.
The ones that come up on a project with a long tail.
Does a limitation clause actually stop a claim?
It does not prevent someone starting one. What it does is define the scope and the intended audience of your work in your own words, written before anything went wrong, which is a materially better position than explaining it afterwards. Treat it as scope control rather than as a shield.
A client wants to name us on their policy. Is that the same protection?
No. Being added to somebody else’s liability policy does not answer a claim about your professional judgement, and most wordings would not respond. Professional liability follows the professional. Being named on a project policy and holding your own cover are separate things and you generally need both.
We are a two person firm. Are we treated differently?
The exposure per report is not smaller, and what changes is the market rather than the risk. Smaller firms are placed outside the programme, with markets that suit their size. Same team, same speed.
What happens to old reports if we close the practice?
They stay live as an exposure and the policy that would answer them ends with the practice. That is what run-off cover is for, and the option to buy it usually expires shortly after the policy ends rather than remaining open indefinitely.
Does the policy cover us for work in another province?
Ask, do not assume. Territorial and jurisdiction wording varies, and licensing to practise is a separate question from whether the policy responds. Both need answering before you accept work outside British Columbia.
Two that decide the same claim: the retroactive date and run-off cover when a practice closes.
Not the question you had? Send the question through the practice file and a licensed broker will answer in writing.
Check the date before you check the limit.
The limit decides how much is available. The retroactive date decides whether anything is. Both are on one page of your policy.