Use AI for the words around a survey, never the numbers in it. Give it your scope, assumptions and fee basis to draft the proposal, dictated field notes to tidy into a consistent job log, and a one-line job status to write each client update. The surveyor supplies every measurement, checks every figure and signs.
Keep client plans, title documents and deeds out of free tiers. These three jobs only need text, so strip names and addresses before pasting, or use a business plan whose content is not used for training by default. Free consumer plans can use chats to improve their models depending on a privacy setting in your account, and some keep chats for human review.
A four-person firm might send a dozen proposals a month and spend most of every Friday writing status emails nobody enjoys. Neither job needs a surveyor's judgement, which makes them the safest place to start. The field log sits closer to the work, so it gets stricter rules.
Set aside an hour first to write down three things: your standard proposal headings, your field log layout and the milestones at which clients hear from you. The assistant works from those, which keeps the firm's wording the firm's own, and each of the three jobs below reuses them.
Where the line sits: text for AI, numbers for the surveyor
Everything below depends on one boundary. Words go to the assistant. Measurements, calculations and conclusions stay with the surveyor. The table shows how that plays out in the three documents this workflow touches.
| Document | AI drafts | The surveyor supplies and checks | Stays out of the AI |
|---|---|---|---|
| Proposal | Wording of scope, assumptions, exclusions and timing; the cover email | The scope decisions, the fee and its basis, anything promised about what will be located or set | Title documents, deeds, client plans |
| Field log | A tidy narrative from dictated or typed notes, in your log layout | Every measurement, point identifier, unit and description of evidence found; the sign-off | Raw data files, coordinate lists, control sheets, instrument exports |
| Client update | A short message for the milestone reached | The date, what is and is not yet known, and the next step | Any boundary position, dimension, area or conflict finding before the plan is signed |
The signed plan, the report and every legal opinion sit outside this workflow completely. For what AI can and cannot help with in the field itself, what helps and what never replaces field checks draws the same line from the other direction.
Which plan a client's information can go into
Where a document is pasted matters as much as what the assistant writes. The vendors' own pages show why a free tier is the wrong place for client detail.
- Claude consumer plans (Free, Pro, Max): training on your chats depends on a model-improvement setting, and a thumbs-up or thumbs-down keeps the whole conversation for up to five years, according to Anthropic's privacy article.
- Gemini app, personal accounts: with Keep Activity on, chats are used to provide and improve Google's services, including training its models, and a subset are reviewed by humans; reviewed chats are kept for up to three years, even if you delete your activity. Switched off, chats are still saved for 72 hours, as Google's Gemini Apps help page explains.
- ChatGPT consumer plans: there is a data-controls setting for using chats to improve the model, and Temporary Chat is kept for up to 30 days.
- Business plans: ChatGPT Business and Claude Team both list at $25 a user a month billed monthly, or $20 billed annually, with a two-seat minimum, and neither trains on business content by default. Gemini in Google Workspace and Microsoft 365 Copilot are the other route if your firm already uses those suites.
Settings and labels change often, so check the current setting in your own account before relying on this list. A simple three-tier rule keeps the decision automatic.
| What you are pasting | Where it can go |
|---|---|
| Generic text: your own template headings, tone guide, exclusion checklist | Any tier |
| Client-identifiable text: names, addresses, parcel references, fees, enquiry emails | A business plan, or any tier once anonymised |
| Plans, deeds, title documents, instrument or data files | Not in these workflows; if ever needed, only on a plan your contract and professional rules allow |
Anonymising takes thirty seconds. Replace names and addresses with placeholders before pasting, then put them back in the draft. Before: "Mrs [surname] at 14 [street name] wants her fence line checked before building a garage." After: "[CLIENT] at [SITE ADDRESS] wants the fence line checked before building a garage." The assistant writes just as well from the second version, and nothing identifiable leaves the building. For more on where free tools stop, see free AI tools for land surveyors and their limits.
Proposals: from enquiry to fee letter in about twenty minutes
A land survey proposal is a promise about work that has not happened yet, so what it leaves out matters as much as what it says. A good one has these parts: the type of survey and its purpose, the deliverables, the assumptions (access, records provided, vegetation, visibility of markers), the exclusions, the fee and what it is based on, the timing, and how changes are handled. The assistant drafts the prose; you decide each of those parts first.
You are drafting a survey proposal for a small land surveying firm. Use plain, professional English. Use ONLY the facts I give you. Do not add promises, timelines, accuracy claims or legal conclusions.
Use these headings: Scope of work, What we assume, What is not included, Timing, Fee, How to accept.
Do not write or alter our standard terms; I will attach them separately.
ENQUIRY (anonymised): [CLIENT] at [SITE ADDRESS] wants a boundary survey before building a garage; unsure whether the fence marks the line.
SURVEY TYPE: boundary survey with signed plan.
DELIVERABLES: signed survey plan (PDF); corner markers set only if the client chooses that option.
ASSUMPTIONS: access to the whole boundary in normal hours; client supplies deed and any earlier survey; existing markers recorded, not assumed correct.
EXCLUSIONS: buried services; resolving a dispute with a neighbour; any work on adjoining land.
FEE: [fee] fixed; markers [fee] extra. TIMING: field date confirmed within [number] working days of acceptance.A typical first draft is shown below as an illustration, cut to its first four sections.
Scope of work. We will carry out a boundary survey of [SITE ADDRESS] for [CLIENT]. The work comprises research of the deed and records provided, a field survey to locate evidence of the boundaries, calculation of the boundary positions from that evidence, and a signed survey plan.
What we assume. Access to the whole boundary during normal hours; copies of your deed and any earlier survey; existing markers will be recorded but are not assumed to be correct.
What is not included. Locating buried services; resolving any dispute with a neighbour; work on adjoining land. Setting new corner markers is available as an option.
Timing. We will confirm a field date within [number] working days of acceptance. Weather and access can move that date.
That draft is acceptable. Weaker ones, and the same assistant on a bad day, add lines like these, each of which a surveyor should strike or rewrite:
- "We will locate all easements and encumbrances." You can only show what the documents provided disclose, so say that instead.
- "All corners will be marked." Marking is an option the client buys, not a default.
- "The survey will establish the legal boundary." That is a professional conclusion and belongs in the signed plan, not a sales line.
- "Field work will be complete within 10 working days." Dates come from your calendar, never from the assistant.
- "Accurate to within [any figure]." Accuracy claims are the surveyor's, tied to the method and instrument. Never let the assistant volunteer one.
The fee line is the one most worth thinking through before you prompt, because the fee basis decides what the proposal has to say about changes. Three bases cover most land survey work.
| Fee basis | Suits | What the proposal must spell out |
|---|---|---|
| Fixed fee | A defined job with known access and records, such as a straightforward boundary or topographic survey | What triggers extra fees: a second field visit, missing markers, extra records research, a revised plan after the client changes the brief |
| Phased fee | Jobs where the records are uncertain: research first, a call to decide, field work second | What phase one delivers, which decision it feeds, and that phase two is quoted after it |
| Time with a cap | Complex or open-ended jobs | Your hourly rates from your rate card, the cap, and the point at which you will warn the client before reaching it |
Give the assistant the basis in a sentence and ask for a short "Changes and extras" paragraph to match. Keep amounts and rates as placeholders in the prompt and fill them in from your own fee sheet; an assistant has no business inventing a rate.
Before the proposal goes out, a person ticks a short list: the fee matches the fee sheet; every deliverable is named; access and records assumptions are stated; the exclusions are all present; a validity period is shown; the standard terms are attached unaltered; the client's name and site are spelt correctly.
A second pass worth adding comes from catching made-up figures in AI-drafted proposals, which suits any draft that carries amounts.
The time sum is easy to check against your own diary. A firm that writes twelve proposals a month at 45 minutes each spends nine hours on them. If a saved prompt and a surveyor's review bring each one to 20 minutes, the saving is 12 x 25 minutes, or five hours a month, and those hours go on the part a person has to do anyway: deciding the scope.
Both timings are assumptions for the example; time your own next three proposals before relying on them.
Field notes: dictate on site, tidy at the desk
Surveyors already take notes that only the author can read. The aim is not to replace them but to turn them into a consistent log that the office, and the surveyor six months later, can follow.
A good log entry holds the date, crew, weather, instrument identifiers, control points or marks used, evidence found and not found at each corner, access problems, anything the client said or did on site, and follow-ups. The assistant's job is layout and wording only.
Rewrite the field notes below into our field log layout: Date and crew; Weather; Equipment; Control used; Evidence found; Evidence not found; Access and site conditions; Client contact; Follow-ups.
Hard rules: copy every number, unit, point identifier and description of evidence exactly as written. Do not round, convert, reorder or correct any number. Do not add anything that is not in the notes. If something is unclear, write [CHECK] followed by the unclear words.
After the log, add a list headed NUMBER AUDIT showing every number in my notes next to the same number in your log.
NOTES: [paste dictated or typed notes]Take notes dictated into a phone at the end of a morning, ums included: "found old iron pipe at the north east corner about point three five below ground bent over, no sign of the south east, fence along the east side looks about half a metre inside to me, rear access blocked by a shed, owner Thursday". A reliable assistant returns something like this, with the doubtful parts flagged rather than smoothed over (illustrative):
| Log heading | What the assistant wrote | What you check |
|---|---|---|
| Evidence found | Old iron pipe at the north-east corner, approximately 0.35 [CHECK: metres or feet?] below ground, bent | Unit and depth against your field book |
| Evidence not found | No marker found at the south-east corner | That "no sign of" really means "not found" after a proper search |
| Site conditions | East fence appears to sit about 0.5 m inside the line [CHECK: this is an opinion, not a measurement] | Whether an opinion belongs in the log at all |
| Access | Rear access blocked by a shed | Nothing; this is a plain fact |
| Follow-ups | Owner to be contacted Thursday [CHECK: which Thursday] | Date against your calendar |
Dictation gives the assistant cleaner material when the crew follows a few spoken habits:
- Say the heading first ("evidence, north-east corner"), because the assistant files each fact under the heading it last heard.
- Say numbers with their units ("zero point three five metres") and spell identifiers a character at a time.
- Say "not found" only after you have described the search you made.
- Say "my opinion" before any opinion, so it can be separated from observation and kept out of the log.
Three habits on the desk side keep the result safe. First, the original dictation or the scan of the handwritten page stays attached to the job; the tidy log is a convenience copy. Second, run the number audit every time. You can also paste both versions into a compare tool, such as the compare feature in a word processor, and look at what changed. Third, read the log with the field book open at the page. Describing evidence is where a helpful assistant does the most damage: "found" becoming "set", or "iron pipe" becoming "iron pin", changes the meaning of a note. A realistic miss would be a tidy log that turns "old iron pipe, bent, 0.2 m below ground" into "iron pipe found", dropping the depth and the condition. It would only surface months later, when someone asks why the plan shows a disturbed marker. That is why the prompt says to preserve every descriptive word.
If your notes are already typed in an app, the same prompt works on an export. For the next step, turning cleaned-up notes into a report, see how surveyors turn site notes into reports.
Client updates: the seven messages a survey job needs
Clients ask the same question at every stage: what is happening, and when do I hear next? Seven milestones answer it. The assistant drafts each from a template you approve once; you fill in the dates.
| Milestone | What the message contains | What it never contains |
|---|---|---|
| 1. Enquiry received | Acknowledgement, what you need from them, when you will reply | A price, unless it comes from your fee sheet |
| 2. Proposal sent | What is attached, how to accept, how long it is valid | Pressure or promised start dates |
| 3. Accepted, research started | What you are doing first, what they must provide, a timing range | Predictions about what the records will show |
| 4. Records gap or delay | The cause in plain words, what you are doing, when you will update again | Blame, or a firm new date you do not control |
| 5. Field work scheduled | Date and time window, access needs, weather caveat | Promises about completing in one visit |
| 6. Field work done | That the crew has finished, what happens next, expected review time | Any finding, measurement or opinion |
| 7. Plan delivered | What is attached, how to read it, who to call with questions | New advice that is not on the signed plan |
Here is milestone 4 filled in, written the way an assistant should write it:
Hello [first name],
A quick update on [SITE ADDRESS]. We are still waiting on a copy of an earlier record from the records office, which we need before the field visit. We asked for it on [date] and have chased it today.
Nothing is needed from you at the moment. We will update you again on [date], or sooner if the record arrives. Once it does, we will offer you a field date.
Regards, [your name]Two details make the draft work. It names the actual wait rather than saying "we are working on it", and it gives a date for the next update instead of a date for the finished survey. The first reduces phone calls and the second keeps you from promising what you do not control. Milestone 6 deserves a note: the temptation is to share early news ("the fence looks to be inside the line"). Until the plan is signed, a client should not be told that, and the draft must not suggest it.
To produce any of the seven, feed the assistant a one-line status and the milestone number:
Write milestone 5 (field work scheduled) for [CLIENT] at [SITE ADDRESS]. Facts: crew arrives Tuesday [date] between 8 and 10 am; they need access to the rear boundary and the gate left open; weather may move the date, and we will text by 6 pm the day before if it does. Use our friendly, plain tone. Add no other facts, dates or promises.The Friday status sweep
Updates slip because nobody owns them. A weekly sweep fixes that. Every Friday, export the job list with each job's status and the days since the last client contact, anonymise it, and ask the assistant which message each job is due. A surveyor then reviews the drafts and sends them. For five jobs, the answer might look like this:
| Job | Status | Days since contact | Message due |
|---|---|---|---|
| A: boundary survey | Waiting on records office | 9 | Milestone 4, records delay |
| B: topographic survey | Crew booked next Tuesday | 2 | Milestone 5, field work scheduled |
| C: setting out | Field work done, drafting | 4 | Milestone 6, field work done |
| D: boundary survey | Proposal sent, no reply | 7 | Gentle proposal follow-up |
| E: topographic survey | Plan with surveyor for review | 3 | None; contact is recent |
A service standard helps here: pick a maximum silence, say seven days, and write it at the top of the sheet. The assistant flags anything older than the limit, and the surveyor decides what to say. Job D shows a common trap. The assistant may suggest "just checking in" for a proposal that has gone quiet, which is weak. Ask it instead for a message that offers one concrete next step, such as a ten-minute call or an answer to one question the proposal may have raised.
A prompt library the whole firm can use
The prompts above are worth little if they live in one person's chat history. Store them where the office can reach them: a shared document, or a project in ChatGPT or Claude, both of which offer shareable projects on business plans, with the instructions saved once. Keep one project per document type rather than per client: a proposals project, a field log project and a client updates project. Standard text goes in; client files never do. OpenAI is retiring custom GPTs (the announced date for existing ones to stop running is 11 December 2026), so build on projects instead of a custom GPT.
Give each prompt a version number, a date and a named owner. When a surveyor improves the number-audit line, everyone gets the better version, and when something goes wrong you can see which version produced it.
Five ways it goes wrong, and the check that stops each
- Wrong client in the draft. A long chat can carry one client's address into another's proposal. Start a new chat for every job.
- A promised date. An update can say "survey complete by Friday" because the assistant wanted to sound helpful. Dates come from your calendar and are pasted into the prompt, with an instruction never to calculate one.
- An early finding. A status email can repeat a surveyor's passing remark that a wall "seems to be over the line". The rule is that no update contains a position, dimension or opinion until the plan is signed.
- A softened note. A friendly rewrite can lose detail from a field note. The prompt says to keep every descriptive word, and the number audit catches the rest.
- Terms rewritten. An assistant asked to "tidy" a proposal can reword a limitation clause in the standard terms. Attach the terms as a fixed file and never paste them into a prompt.
If the firm already has an AI policy, add these five rules to it. If it does not, the same five lines are a workable policy for a small practice, and clients who ask will appreciate a straight answer. For wording to adapt, how to mention AI use in client contracts and proposals is a good place to start.
Questions surveying firms ask before using AI for admin
Do I need to tell clients I use AI for drafting?
Check your own terms of engagement and your professional body's guidance, because expectations differ and are changing. Many firms add a short line to their standard terms saying AI may help draft correspondence while the surveyor remains responsible for all measurements and conclusions. The tutorial on mentioning AI in client contracts has wording to adapt.
Can I keep one long chat open for all my jobs?
It is better not to. A long chat carries earlier clients' names and details into later drafts, which is how a proposal ends up quoting the wrong address. Start a fresh chat for each job, paste only that job's anonymised text, and close it when the job moves on.
Is a free AI tier ever fine for survey work?
Yes, for generic text that contains no client information: a template layout, a tone-of-voice guide, a checklist of exclusions. Anything with a name, address, parcel reference, fee or plan belongs on a business plan or must be anonymised first. Deeds, title documents and plans stay out of these workflows altogether.
Should my insurer know about this?
It is worth a short conversation. Check your professional indemnity policy conditions and ask your insurer or broker whether they have guidance on AI use in client documents. Take the same approach with any data-protection adviser you use, particularly if clients' personal details appear in the text you draft.
Further reads
- AI for Building Surveying: A Worked Fee Quote and Enquiry Reply — A worked fee quote and enquiry reply.
- Responsible Use of AI in Surveying Practice: A Small Firm's RICS Checklist — A responsible-use checklist for a small surveying practice.
- How to Write Business Proposals Faster With AI — General proposal drafting steps to borrow.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Anthropic's privacy centre article on model training for consumer plans; Google's Gemini Apps privacy help page on Keep Activity; ChatGPT Business and Claude Team plan pricing and data terms (October 2026). Check your own professional body's rules on AI use and client confidentiality.