Structural Engineer Brief Preparation Checklist

Write the thing you want answered as a single sentence a stranger could follow, then read it back and check it does not already contain your own answer.

A question that carries its answer inside it invites agreement rather than assessment, and that is the most common way an owner steers a conversation without meaning to.

Write down separately what prompted you to make contact and what you actually want to know, because the trigger and the question are often not the same thing.

People arrive because a door started sticking and then ask about an extension, and the engineer needs to know both things are on the table.

Say plainly whether you are asking about something you have noticed at the property or something you want to do to it, since those lead to different conversations.

The two kinds of enquiry need different information and often different visits, and mixing them delays both.

Write down what you would do differently depending on the answer, so the point of asking is visible to both sides from the outset.

An engineer who knows what hangs on the answer can say which parts of the question matter and which are not worth the effort.

Avoid naming the solution you have in mind inside the question itself, and keep it as a clearly separate note if you want to mention it at all.

A solution put forward by the owner narrows what gets considered; offer it to a qualified structural engineer as an idea to react to, never as the starting point.

Note anything you have already been told about the subject and by whom, marking clearly which of it came from somebody qualified who actually attended the property.

Opinions from people who have not seen the building should be passed on as hearsay; ask the qualified structural engineer to form their own view regardless.

Describe the property plainly, including how many storeys it has, what the external walls appear to be made of and what the roof looks like from outside.

A short plain description lets an engineer judge what kind of visit and what information is likely to be needed before anything is arranged.

Say what you understand about when the property was built and where that understanding came from, marking it as uncertain if you are not genuinely sure.

Owners repeat a date from a listing or an estate agent as though it were established, and an engineer treats a sourced date very differently from a repeated one.

Describe the floor construction as far as you can tell from what is visible or audible underfoot, and say plainly where you are guessing rather than observing.

What a floor is made of and what it is doing are questions for a qualified structural engineer; describe what you notice and stop short of concluding.

List the parts of the property you have never been able to see into, such as a sealed void, a boarded floor, a closed-off cellar or an unreachable roof space.

Knowing in advance what cannot be seen shapes what an engineer proposes, and it is information only somebody who lives there can supply.

Say whether the property is attached to another and describe what appears to be shared at each level, including walls, a roof, a chimney or a boundary structure.

Shared structure carries obligations towards other owners that vary locally; those must be settled with appropriately qualified advisers and the relevant authority.

Avoid labelling anything in the property as structural or as carrying something, and describe instead where it is, what it looks like and what sits above it.

Whether an element plays a structural role can only be established by a qualified structural engineer, and an owner label in a brief is easily read as fact.

List the drawings, reports and paperwork you already hold, including anything prepared for work that was considered and then never carried out.

A scheme that was dropped still leaves behind whatever was understood about the building at the time, and that is worth handing over even though the scheme itself went nowhere.

Say clearly which of the usual documents do not exist for this property, rather than leaving the engineer to ask for them one at a time.

A brief that names the gaps is answered faster than one that quietly omits them, and it sets realistic expectations on both sides.

Note what you could obtain if asked to, such as records held by a previous owner, a managing agent, a former neighbour or the local authority.

An engineer can only ask you to chase something they know might exist, so listing possible sources is genuinely useful.

Describe what parts of the property can be accessed and what cannot, including any locked area, tenanted part, shared space or room you cannot empty.

Where access depends on somebody else agreeing, raise it before a visit is arranged and ask the professional what they need to be able to see.

Note whether anything at the property can be opened up and who would need to agree to it, particularly where a lease, a joint owner or a neighbour is involved.

Do not open up any part of the property in advance to be helpful; ask the qualified structural engineer what they want exposed and who should do it.

Offer your own photographs and sketches as observations rather than as survey information, and label them that way so nobody works from them by mistake.

Owner sketches get scanned into files and treated as measured information, which is a hard mistake to undo once it has happened.

Write down what you understand the engineer is being asked to look at, and say what you are deliberately not asking about at this stage.

Putting the boundary in your own words gives the professional something concrete to correct, which is far more useful than a general enquiry.

Ask whether the appointment includes attending the property, how many visits are anticipated and what each visit would be expected to cover.

Some questions can be addressed from information supplied and others cannot, and knowing which this is changes everything that follows.

Ask what happens if something is found that sits outside what was agreed, and how that would be raised with you before anything further is done.

Do not assume additional findings are automatically covered; agree with the professional how anything unexpected will be handled and by whom.

Note which parts of the project other appointed professionals are dealing with, so the same ground is not covered twice or left out by both of them.

Gaps between consultants are more common than overlaps, and the owner is usually the only person with sight of every appointment.

Ask whether liaising with a local authority, a neighbour, a lender or an insurer forms part of the appointment or is expected to sit with you.

Correspondence with authorities and other interested parties has consequences; agree in writing who is speaking to whom before anybody makes contact.

Record what you understand to be excluded, and ask for that understanding to be confirmed back to you rather than left as your own assumption.

An exclusion you inferred is not an exclusion anybody agreed; ask the professional to state the boundary of the appointment in writing.

Say who will need to read whatever the engineer produces, including a builder, a designer, a lender, an insurer, a neighbour or a future buyer.

Output written for one reader often cannot be used by another, and saying who the readers are before it is written is far easier than asking afterwards.

Ask what form the output will take, whether that is a letter, a written report, drawings, calculations or some combination of those.

Owners frequently expect drawings and receive a letter, or expect a report and receive sheets they cannot read on their own.

Ask whether anybody other than you may rely on what is produced, and what would be needed if somebody else has to be able to.

Reliance is a formal matter that varies between appointments; settle it with the professional concerned rather than assuming a document can be passed on freely.

Say if you need something written in terms a non-technical reader can follow, and ask whether that is possible alongside whatever the technical output has to be.

Asking for a plain covering explanation is reasonable and much easier to arrange at the outset than requested afterwards.

Ask what will still be unresolved once the output is delivered, and what would be needed to close each of those remaining points.

Almost every piece of work leaves something conditional, and knowing what before you receive it prevents an unwelcome surprise at the end.

Agree how you will receive the output and where the definitive copy will be kept, so that later versions can be told apart from earlier ones.

Reports circulate as attachments and quickly multiply, and nobody can then say which version anyone is actually holding.

List everyone already appointed on the project and write down what each of them believes the engineer is going to be doing.

The gap between what a designer expects and what an owner expects is usually invisible until an engineer asks a question that exposes it.

Ask whether your designer expects to instruct the engineer or whether you will hold the appointment directly, and record the answer.

Who instructs whom affects responsibilities and correspondence; settle it with the professionals involved before any work begins on the question.

Note anything a builder or trade has already said about the structure, and pass it on as a report of what was said rather than as established fact.

Remarks made on site are not assessments; ask the qualified structural engineer to reach their own view and say where they disagree.

Say whether work has already started at the property and describe exactly what has been done so far, without softening or summarising any of it.

Work already carried out changes what an engineer can advise on; describe it fully and ask whether anything should stop while the question is open.

Note whether anybody else has a say in decisions about the property, including a joint owner, a leaseholder, a family member or a managing agent.

Decisions that have to go through somebody else take longer, and an engineer planning their work benefits from knowing that early.

Ask how information should travel between the engineer, your designer and anybody on site, and who is copied into what.

Where messages route through the owner by default, technical questions arrive garbled and answers come back the same way.

Note anything you are aware of that limits what can be done to the property, including a shared wall, a right of way, a covenant or an obligation to a neighbour.

Obligations of this kind vary and carry legal weight; confirm what applies with appropriately qualified advisers rather than working from recollection.

Say whether the property carries any designation you are aware of, and treat that as something to confirm locally rather than as something you already know.

Designations and the constraints attached to them vary by location and must be confirmed with the relevant local authority before anything is planned.

Describe how people and materials would reach the property and the working area, including how narrow the route to the rear is and any step, gate or shared passage.

Access constrains what is practical long before it constrains anything else, and it is routinely left out of an owner description.

Note whether the property will remain occupied and whether anybody living there would be affected by parts of it being opened up or disturbed.

Living arrangements affect what investigation is realistic, and an engineer would rather know before proposing something unworkable.

Say what you would find unacceptable to lose, such as a chimney breast, a particular window position, a mature tree or a run of original joinery.

Stating this early lets those constraints be worked with, whereas raising them later means going back over ground already covered.

Note anything already ordered, agreed or committed to for this project, because those commitments narrow what an engineer has left to work with.

Where something has already been committed to, ask the qualified structural engineer whether it should be paused before the question is answered.

Mark every statement in the brief as something you have seen, something you were told or something you assume, and keep the three plainly apart.

A brief read without those markers becomes a description of the building, and assumptions inside it get relied on as though they were observations.

Resist writing your own conclusions into the brief, even where you feel confident, and put the observation that led to the conclusion instead.

Conclusions in an owner brief anchor the thinking of everybody who reads it; leave every structural judgement to the qualified structural engineer.

Date the brief and reissue it when it changes rather than editing it quietly, so anyone can tell which version a response was answering.

Quiet edits make it impossible to work out later why a professional answered the question they did.

Record anything you notice after the brief has gone out as a dated addition rather than folding it into the original text.

The order in which things were noticed is often relevant, and rewriting the brief destroys that sequence.

Ask the engineer to tell you where the brief is asking the wrong question, and treat being told so as a useful answer rather than a setback.

Owners frequently ask about a symptom when the useful question lies elsewhere, and a professional will usually say so if invited to.