A structural engineer's fee proposal should state the stages of work and what each delivers, the information it assumes the client or architect will provide, what is excluded, and how changes are priced. AI can draft each section from your enquiry notes and standard clauses, but you decide the scope, the assumptions and the liability wording.
Many fee disputes start in the assumptions, not the price. The proposal assumed a measured survey, and the client assumed the engineer would arrange one. A proposal that lists each assumption, with what happens if it proves wrong, is the document AI drafts best, because the structure repeats from job to job and your judgement supplies the content.
Stage-based scope: what each stage delivers
Break the work into stages the client can understand and stop after. For a small domestic job, four stages cover most work. Each stage needs a deliverable the client can recognise, the inputs you need, and a fee basis, because a stage without a deliverable is a stage nobody can dispute and nobody can price.
| Stage | What the client receives | Fee basis | Inputs assumed from others |
|---|---|---|---|
| 1. Site visit and appraisal | A short note on what was seen, the structural approach proposed and open questions | Lump sum | Access to the property; the architect's current drawings |
| 2. Design, calculations and drawings for the approval submission | Calculations, structural drawings and a specification note, issued once for submission | Lump sum | Final architectural layout; confirmed finishes; any survey or ground information |
| 3. Queries and revisions | Written replies to the builder's and approving authority's structural queries; up to two rounds of drawing revisions | Hours-based, capped | Queries sent in writing through one contact |
| 4. Site visits | Visits at agreed points, each followed by a short written note | Lump sum for a stated number of visits | Reasonable notice; the work open and accessible when we arrive |
The point of the last column is that every stage depends on someone else. Stage 2 cannot start without a stable architectural layout, and Stage 4 cannot happen if the steel is already boxed in. Writing those dependencies down is what separates a proposal from a price list.
The worked proposal: a rear extension and a new steel beam
The job is a detached two-storey house. The client wants a single-storey rear extension about 4.2 m wide and a new opening of about 3.6 m in the ground-floor wall into it, which needs a steel beam. The architect has issued plans at revision B. No survey exists beyond the architect's measurements, there is no ground investigation, and the builder has not been chosen. The figures below are illustrative. Use your own rates and hours.
| Stage | Hours by grade | Calculation | Fee |
|---|---|---|---|
| 1. Site visit and appraisal | Principal 1.5, engineer 4.5 | 1.5 x $150 + 4.5 x $110 = $225 + $495 | $720 |
| 2. Design, calculations and drawings | Principal 3, engineer 12, technician 8 | $450 + $1,320 + $680 | $2,450 |
| 3. Queries and revisions (capped) | Principal 1, engineer 4 | $150 + $440 | $590 |
| 4. Two site visits with notes | Engineer 6, principal 0.5 | $660 + $75 | $735 |
| Total | 40.5 hours | $720 + $2,450 + $590 + $735 | $4,495 |
The rate card behind those sums is $150 an hour for a principal, $110 for an engineer and $85 for a technician. The same card prices variations later, which is what makes the proposal self-consistent: any change in scope has a route to a price that the client has already seen. Stage 3 is capped, not fixed, because it depends on how many questions the builder asks.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowAssumptions about information provided: where disputes begin
The assumptions section is the longest part of a good proposal and the part most often cut. Write each assumption as one sentence, and give the consequence beside it. A consequence turns a vague hedge into a priced term.
| Assumption | Why it matters | If it proves wrong |
|---|---|---|
| The architect provides current plans, sections and elevations in digital form before Stage 2 starts | Design cannot start on a layout that is still moving | Work waits; Stage 2 time runs from the date complete information arrives |
| No more than two revisions to the architectural layout after design starts | Each layout change can reopen the calculations | Further revisions are charged at the variation rates |
| The existing structure is as shown on the drawings or as seen at the visit | We cannot see inside floors, walls or foundations | The builder opens up to confirm before work starts; different conditions mean design changes priced as a variation |
| No ground investigation is provided; foundations are designed on an assumed bearing pressure stated in the calculations | Ground conditions drive foundation size | If the contractor finds poorer ground, we advise on revised foundations as a variation |
| Finishes and loads, such as roof covering and floor build-up, are confirmed before Stage 2 | Heavier finishes change beam and foundation sizes | Changes after issue are a variation |
| Instructions come in writing from one named contact | Conflicting verbal instructions are the root of many scope arguments | We act only on written instructions from that contact |
| One submission to the approving authority is made from our Stage 2 issue | Resubmissions generate more queries | Further submissions are additional work |
The ground assumption deserves a comment. It is the sort of statement the engineer must write, not the AI, because the bearing pressure is a professional judgement. The AI's job is to make sure the statement exists, is phrased consistently with the calculations, and has a stated consequence. Decide the number yourself.
Exclusions, written as the client's own questions
Clients rarely read exclusions as law. They read them as answers to "does that mean you'll do X?" Write each exclusion so that it answers the question in ordinary words, and say who normally does the work, because "excluded" with no owner reads as a gap rather than a boundary.
| Exclusion | How to word it for the client | Who usually does it |
|---|---|---|
| Temporary works | "We do not design the temporary supports used while the wall is opened. Your builder designs them and is responsible for them." | Contractor |
| Neighbour matters | "We do not prepare notices or agreements with neighbours." | Client or their adviser |
| Ground investigation | "We do not carry out or commission ground investigation. If the ground differs from our assumption, we will advise on changes as a variation." | Specialist contractor |
| Non-structural design | "Drainage, heating, electrics and thermal performance are not included." | Other consultants or the builder |
| Opening up the existing building | "We inspect what is visible. Opening up is by the builder, and we need to see what is found." | Contractor |
| Construction supervision | "Our site visits are checks at agreed points. They do not replace the builder's responsibility for workmanship." | Contractor and the approving authority's inspections |
| Items designed by suppliers | "Where we specify a performance requirement, for example for roof trusses, the supplier designs the item and we review the submission." | Supplier |
| Defect or damp diagnosis | "Not included. A condition report can be quoted separately." | Surveyor or specialist |
Variation terms: a rate card and a notice rule
Variations are where the earlier sections earn their keep. They need three things: a trigger, a price route and a notice step. Triggers come straight from the assumptions table: a late layout change, a different ground condition, extra revisions, extra visits or extra scope. The price route is the rate card. The notice step is a promise to tell the client the estimated cost in writing before starting work that exceeds a set amount, in this illustration $300.
Three worked variations show how it behaves with the proposal above.
- A loft conversion added after Stage 2. Principal 3 hours ($450), engineer 12 hours ($1,320) and technician 6 hours ($510) give an estimate of $2,280, sent for written approval before any work starts.
- A third round of architectural revisions. Engineer 3 hours ($330) plus technician 2 hours ($170) gives $500, because it exceeds the two included in the assumptions.
- An extra site visit. Engineer 3 hours at $110 is $330, the same as the rate card's standard visit.
Payment terms, validity and start-date assumptions belong here too. Keep the validity period and the start window in the same paragraph, because a fee that is valid for 30 days but assumes a start within 60 should say so.
Prompt one: draft the stage scope from your enquiry notes
Strip the client's name and site address from the enquiry first, and use placeholders. A shared Project in ChatGPT or Claude can hold your stage definitions and clause library so you do not paste them each time; check your plan's limits and data settings before you store anything client-related. Then give the AI the notes and the rules.
You are helping a structural engineering practice draft the scope
section of a fee proposal for a small domestic project.
Use ONLY the enquiry notes and the stage definitions below.
Output a table with these stages: 1 Site visit and appraisal; 2 Design,
calculations and drawings for an approval submission; 3 Queries and
revisions; 4 Site visits. For each stage give: what the client
receives; what we need from the client or architect; what is NOT
included; fee basis (leave the fee as [FEE]).
Rules: do not add services that are not in the notes. Do not use the
words ensure, guarantee, full, complete, all, any, or "including but
not limited to". Do not promise approval or programme dates. If
something is missing, write [CONFIRM: what is needed].
ENQUIRY NOTES (client and address removed):
Detached two-storey house. Single-storey rear extension about 4.2 m
wide. New opening about 3.6 m in the ground-floor wall into it.
Architect plans at revision B. No survey beyond the architect's
measurements. No ground investigation. Builder not chosen. Client
wants to submit for building approval within 8 weeks.Even with the word list, a first draft usually over-promises. These are typical slips, illustrative, with the fixes.
| AI wording | Problem | Fix |
|---|---|---|
| "Structural design of the property" | Widens scope to the whole house when only the extension and opening were discussed | "Structural design of the new rear extension and the new opening shown on architect's drawings revision B" |
| "Supervise construction to completion" | Turns spot-check visits into supervision, shifting responsibility to you | "Two site visits at agreed points, each with a short written note" |
| "Secure building approval within 8 weeks" | A promise about someone else's timetable | "Issue the Stage 2 package for submission within [X] weeks of receiving complete information" |
| "Unlimited revisions" | Invented generosity that undermines Stage 3's cap | "Up to two rounds of revisions; further rounds at the variation rates" |
| "Foundations to suit the ground" | Hides the ground assumption | "Foundations designed on an assumed bearing pressure stated in the calculations" |
The third row is the one to watch. AI models write reassuring verbs, and reassurance in a fee proposal is a commitment. The tutorial on ChatGPT for structural engineers, and what is safe and what never is covers why calculations stay outside the AI conversation, and the same boundary applies to any number in a proposal that comes from your judgement.
Prompt two: extract every assumption, then hunt for contradictions
The second prompt reads the scope as a sceptical colleague would. It asks what the scope quietly relies on, what it forgot to exclude, and where scope and exclusions disagree. Run it in a fresh chat.
Read the draft proposal below. 1) List every statement that depends
on something the client, architect or contractor must provide or do
(information, access, decisions, timing). For each, give the
assumption in one sentence and what happens to the fee or programme if
it proves wrong. 2) List any exclusion I would normally expect on a
domestic extension that the draft does not mention. My standard
exclusions: temporary works, neighbour matters, ground investigation,
non-structural design, opening up, supervision, supplier design,
defect diagnosis. 3) List contradictions between scope and exclusions.
Do not rewrite anything.
DRAFT:
[paste]The third list is the one that earns its keep. A typical contradiction, illustrative: Stage 3 says "review contractor's proposals for temporary works", while the exclusions say temporary works are the contractor's design and responsibility. Both sentences read fine alone. Together they invite a builder to say that you reviewed the temporary works and so share responsibility for them. Decide which you intend, and word the other to match: either remove the review, or offer it as a separately priced variation with a statement that review does not transfer the contractor's responsibility.
Prompt three: read it as the client, the builder and your insurer
A proposal is read by people with different interests. Ask the AI to take each in turn and list questions, not rewrites. The questions are for you to answer, and the answers become assumptions or exclusions.
Read the proposal below three times. First as the client, a first-time
homeowner: list what I might believe I am getting that is not clearly
stated. Second as the builder: list what site responsibilities the
wording could imply I share with the engineer. Third as the engineer's
professional indemnity insurer: list statements that read as promises,
warranties or duties beyond a normal duty of care. List questions
only. Do not rewrite.
PROPOSAL:
[paste]On the worked proposal, a typical output asks the client's questions first: "Does the fee include the beam being installed correctly?", "Who checks the foundations before the concrete is poured?" Both lead to better wording. The first is answered by the supervision exclusion. The second is answered by Stage 4's timing, if the visit is scheduled before the pour, and the proposal should say that the visit is at the stage the engineer chooses and with notice from the builder. Without that line, the client believes you will check every pour.
What AI should not draft unattended
Some clauses carry legal weight and sit outside what any language model should decide for you. They are limits of liability, reliance by third parties, indemnities, termination, copyright and payment remedies. Use AI to explain a clause in plain language, to compare your wording with the scope for clashes, and to produce a list of questions for your solicitor. Do not use it to produce the final text. Some professional indemnity policies carry conditions about the contract terms you accept, so ask your broker what yours requires before the clause library is finalised.
The same caution applies to anything that states a credential or a fact. Your name, your professional status, your insurance details and the standards you design to are yours to write. The tutorial on preparing the professional indemnity renewal proposal form with AI shows how to separate a fact you can evidence from a sentence a tool produced.
A four-page layout that clients actually read
Length matters less than order. Put what the client most wants first and what protects you where it cannot be missed.
| Page | Contents | Why it sits there |
|---|---|---|
| 1 | Project summary, total fee, validity and start assumptions | The client sees the price and what it covers within seconds |
| 2 | The four-stage table: deliverables, fee basis, inputs assumed | Defines the work before any hedging begins |
| 3 | Assumptions with consequences, then exclusions in plain wording | Reads as a list of dependencies, not a wall of terms |
| 4 | Variation rates and notice rule, payment terms, reliance and liability wording (reviewed), signature block | Everything contractual in one place, referring back to pages 2 and 3 |
For how other firms handle the staged-fee idea, the tutorials on a two-stage design-build fee letter and on how architects use AI for fee proposals are useful comparisons. If you also write reports for these jobs, the structural report template with a plain summary you can check keeps the same plain-English habit. For the wider picture across consulting work, see AI for consulting engineers: fee proposals and reports, not calculations.
Silent assumptions, clashing clauses and reassuring verbs
- The silent assumption. The proposal relied on a measured survey and never said so. At Stage 2 the client has none and expects you to supply one within the fee. The symptom is a dispute over a task that no document mentions. The assumption extractor catches this before issue.
- The contradictory clause. The scope reviews something the exclusions disclaim. A builder then quotes the scope back at you after a problem on site. The contradiction search in prompt two catches it, and so does reading the scope and the exclusions side by side.
- The reassuring verb. "Ensure", "secure", "guarantee" and "full" slip in through an AI draft or a copied template. They surface after something goes wrong, when the word is quoted. Search the final text for them and every "all", "any" and "including but not limited to". Each hit needs a defined meaning or a replacement.
Seven checks before the proposal goes out
- Compare every fee in the text with the table, and the table with your hours sheet.
- Check that each assumption has a consequence, and each consequence maps to the variation rates.
- Search for the banned words and reassuring verbs listed above.
- Read the scope and the exclusions side by side for contradictions.
- Confirm the drawing revision, dates and project description match the architect's latest issue.
- Have your solicitor or broker review any liability, reliance or indemnity wording that has changed since the last approved version.
- Save the approved version with its date, and note which clauses came from the library and which are new.
To judge whether the process works, count variation requests and disputes per project over a few months and note which assumption triggered each one. If the same assumption keeps failing, rewrite it in the library, add a question to your enquiry call, or price the item up front. Treat a time saving as a bonus. As an illustration, a proposal that took two hours from enquiry to issue might take about 50 minutes with a library, the prompts and the checks, but only if the time saved is not taken from the review.
Keep a clause library and review it after each job
After three or four proposals, a pattern emerges, and the library is where it lives. Keep standard assumptions and exclusions grouped by project type: domestic extension, loft conversion, commercial fit-out, report-only. Put a review date and a version note beside each clause, and let the AI do the part it is good at: choosing the clauses that fit the enquiry notes, filling the brackets, and flagging gaps against the library. When a job produces a dispute, fix the clause once, in the library, and every later proposal inherits the correction.
Questions about AI and engineering fee proposals
Should AI write the liability and reliance clauses?
Not unattended. Limits of liability, reliance by third parties and indemnity wording carry legal weight, and some professional indemnity policies set conditions on the contract terms you accept. Use AI to explain the clauses in plain language and to spot clashes with the scope, but have your solicitor and broker approve the text.
How many stages should a small domestic proposal have?
Four is common: site visit and appraisal, design and calculations for the approval submission, queries and revisions, and site visits. Fewer stages hide work inside lump sums, and more can read as padding. Split a stage only when the client may stop after it, or when its fee basis differs.
Is it wise to quote a lump sum for the whole job?
Lump sums suit stages where the scope is stable. Use hours-based or capped pricing for stages driven by other people, such as builder queries and revisions. Whatever the basis, state it per stage, so a change in scope has a visible pricing route through your variation rates.
Can I paste the client's enquiry email into an AI tool?
Remove the client's name, address and contact details first, and use placeholders. Enquiries often include personal information and site details. Check your plan's data settings and your client terms, and ask an adviser about the rules in your market before putting identifiable material into a general AI tool.
What if the client pushes back on the exclusions?
Offer to price the item as an optional extra instead of deleting the exclusion. A client who wants temporary works review or a ground report can buy it as a stated variation. Removing an exclusion without adding a fee and an assumption quietly moves risk onto you.
Further reads
- Structural Engineer Inspection Report: Photos and Notes to a Draft With AI — The next document in the job: an inspection report from photos and notes.
- Engineering Proposal Software With AI: What Small Firms Pay — What proposal software costs small engineering firms.
- Best AI for Engineering Firms: Proposals, Specifications, Minutes — Proposals, specifications and minutes across an engineering practice.
- Accounting Fee Proposal Template: Draft and Price It With AI — Another professional fee proposal with scope and exclusions.
- How to Mention AI Use in Client Contracts and Proposals — How to mention AI use in contracts and proposals.
- Custom Home Builder Proposal: Draft Allowances and Exclusions With AI — The builder's side of exclusions and allowances.
- HR Consultant Proposal Template: Scope, Fees and Exclusions With AI — A scope, fees and exclusions pattern from another profession.
- AI in Land Surveying: Proposals, Field Notes and Client Updates — A land surveying firm's admin workflow: AI drafts the proposal, the field log and the client update, while the surveyor owns every figure and the sign-off.
- Engineering RFP Responses With AI: Win Themes and Compliance Matrix — A practical engineering bid workflow: extract requirements, choose provable win themes, draft from approved evidence and check every answer.
- How Engineering Firms Are Using AI: Six Jobs and Their Limits — Six jobs engineering firms give AI, rated for effort and risk, with the evidence behind each and the uses to leave alone.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: general professional practice for staged scope, assumptions, exclusions and variations. Every fee and hour in the worked proposal is illustrative and should be replaced with your own.