TL;DR Walk the site. Talk into your phone for 3 minutes. Paste the transcript into ChatGPT with one prompt. Get a structured Scope of Works back. The whole thing takes 8 minutes and replaces the 90 minutes you currently spend at your desk on Sunday night writing it up.

March 2026 · Reading time: 7 minutes · Written by Ryan Ramsay, founder of BuildBrief

The Sunday-night problem

Every builder I know has the same Sunday night. Site visits done. Quotes due Wednesday. You're sitting at the kitchen table trying to remember what you saw on Tuesday at the Hawthorn job.

You open your notes. Three lines: "existing slab uneven, plumbing rough-in needs reroute, council approval already done." That was meant to be a Scope of Works. It's a haiku.

You either spend 90 minutes writing it from memory and guessing the gaps, or you send a vague quote and absorb the variations later.

There's a third option. Talk into your phone for 3 minutes during the site visit, get the transcript on the way home, paste it into ChatGPT, get a structured scope back.

Builders running this workflow tell me it's saved them hundreds of hours over a year. Below is exactly how it works.

The 8-minute workflow

Step 1 — Walk the site, talk to your phone (3 minutes)

The fastest way is ChatGPT Voice Mode on the Plus plan ($30/month AUD). Open the app, tap the headphones icon, just talk. It transcribes as you go and you can ask it questions in real time.

If you're on the free plan, every modern phone does this for free:

Walk the site, talk like you'd talk to an apprentice you'd brought with you. Don't try to be neat. Don't try to use builder-speak. Just describe what you see:

"OK so we're at the front of the house. Single storey weatherboard, looks 1940s, original windows. Front fence is leaning, probably 60 years old, will need replacing if the client wants it tidied up. Walking down the side now. Side path is narrow, maybe 800mm, that's going to be tight for getting materials through. There's an old shed at the back, asbestos sheeting, will need professional removal. Existing slab in the laundry is uneven, probably 30mm fall over 2 metres. Plumbing rough-in for the new ensuite — current waste line runs along the south wall, we'll need to reroute around the new vanity location. Electrical board is original, 60 amp, will need an upgrade for the new kitchen appliances. Council approval is in place, drawings dated March, all good there. Heritage overlay confirmed lifted last year."

That's 60 seconds of talking. It captures more useful information than 30 minutes of trying to write notes on site.

Step 2 — Get the transcript (1 minute)

iPhone: Open Voice Memos, tap the recording, tap the transcript icon (next to the play button), select all and copy.

Android: Open Recorder, tap the recording, tap "Transcript," copy.

ChatGPT Voice Mode: Skip this step — it's already in your chat.

Step 3 — The prompt (30 seconds)

Open ChatGPT (chatgpt.com or the app). Paste this, then paste your transcript underneath:

I'm an Australian residential builder. Below are my voice-note observations from a site visit. Turn this into a structured Scope of Works covering: demolition, structural, services (electrical / plumbing / HVAC), finishes, and external works. Use Australian construction terminology. Flag anything I noted as TBC, "check," or that needs further investigation. Format as headed sections with bullet points. Don't invent anything I didn't mention.

Voice notes: [paste transcript]

Hit enter.

Step 4 — Review and clean (3 minutes)

The output will be a properly structured scope. Read it once. Three things to check:

1. Did it invent anything? Sometimes the AI will fill in a gap with a reasonable guess. For example, if you said "electrical upgrade" without specifying amperage, it might add "100 amp upgrade" as if you'd said that. Delete or correct.

2. Did it miss anything? Voice notes can be vague. If you said "the bathroom needs work" without specifying, the scope will reflect that vagueness. Add what's missing.

3. Does the terminology match your standard? Some builders write "demo," some write "demolition." Some say "rough-in," some say "service rough-in." It'll pick something consistent — change it to your house style if needed.

3 minutes. Done.

Step 5 — Drop into your quote (30 seconds)

Copy the cleaned scope. Paste it into your quote document, contract, or HIA template. The hard work — converting messy site observations into structured scope language — is done.

A real example

Here's roughly what 60 seconds of voice notes looks like as cleaned-up scope.

A real builder's voice notes (transcribed):

"Right, kitchen reno, Camp Hill, single storey post-war weatherboard. Existing kitchen is small, maybe 3 by 4 metres. Cabinetry is original, particleboard, swollen at the base, going. Benchtop is laminate, going. Splashback tiles will all need to come off, that's going to take a day, the lath behind looks rough. Floor is cork over original timber. Client wants polished concrete look so we're going to grind and seal the existing slab, but I noticed there's a weird step at the doorway, about 30mm, will need to investigate when we lift the floor. Electrical, the existing layout is fine but they want pendant lighting over the new island so we'll need to add a circuit and new switching. Plumbing, existing rough-in is on the north wall, new sink location is also on the north wall so that should be fine, just extending. Gas was capped off years ago, they're going induction. Council approval, this is a non-structural reno so we're under exempt development, all good. Asbestos check, the splashback tiles are 1960s vintage so we'll need to test those before demo."

ChatGPT output (after the prompt above):

Scope of Works — Kitchen Renovation, Camp Hill

DEMOLITION

  • Strip-out of existing cabinetry (original particleboard, water-damaged at base)
  • Remove existing laminate benchtop
  • Remove existing splashback tiles (test for asbestos prior — 1960s vintage)
  • Remove existing cork flooring and underlying treatment

STRUCTURAL

  • Investigate 30mm step at doorway transition (TBC — once flooring is lifted)
  • Existing slab to be ground and sealed for polished concrete finish

SERVICES — ELECTRICAL

  • Existing electrical layout to remain
  • Install new circuit and switching for pendant lighting over kitchen island

SERVICES — PLUMBING

  • Existing plumbing rough-in retained on north wall
  • Extend rough-in to new sink location on north wall
  • Note: gas line previously capped — induction cooking, no gas reinstatement required

FINISHES

  • Wall preparation (lath behind splashback noted as rough — assess after tile removal)
  • New cabinetry, benchtop, splashback (specifications TBC)
  • Polished concrete floor finish (existing slab)

EXTERNAL WORKS

  • Not applicable to this scope

APPROVALS / COMPLIANCE

  • Confirmed exempt development under non-structural renovation
  • Asbestos test required prior to splashback demolition
  • All works to comply with NCC and AS/NZS standards

Total time from finishing the site walk to having that scope: about 7 minutes.

What you don't need

You don't need to buy:

Where it falls down

A few things worth knowing.

Background noise kills transcription. If you're recording on a windy site or near a saw, the transcript will have gaps. Walk to a quieter spot for the structured bits.

Don't rely on it for measurements. If you say "approximately 2.4 metres," it'll record that. If you say a specific dimension that you'll quote against, write that one down on paper. AI gets numbers wrong about 5% of the time.

It can't see. Voice notes describe what you see — the AI doesn't. Photos are still your friend. Take photos as you go and reference them in your voice notes ("there's a photo of the splashback I'm describing now").

Verify the regulatory references. If the AI adds "compliant with AS 3500" or similar, double-check. It's usually right but it can confidently cite a 2008 standard that's been superseded.

What this connects to

This workflow is downstream of one bigger problem: how vague the brief is when you arrive on site.

If you're walking into a site visit with no idea of the homeowner's budget, timeline, scope or constraints, the voice notes capture more of what you observe — but you're still piecing together what the project is. That part needs to happen before you ever drive out.

That's why we built BuildBrief. Homeowners fill out a structured brief on your website before the site visit — scope, budget bracket, timeline, constraints, any council issues. By the time you're standing on site recording voice notes, you already know what the project is. Join the waitlist →

FAQ

Do I need ChatGPT Plus? No. The free plan handles this perfectly. Plus is only worth it if you want Advanced Voice Mode for hands-free use during the actual site walk.

Can I do this with Claude or Gemini instead? Yes. Claude is excellent at long, structured documents. Gemini is good if you're already on Google Workspace. The prompt above works in any of them — just paste and go.

What about privacy with voice notes? Don't say client full names or addresses out loud during the recording. Use first names or "the client." Same redaction principles as text — see the AI privacy guide.

How long should the voice note be? 60 seconds to 3 minutes is the sweet spot. Under 60 seconds, you'll miss things. Over 3 minutes, the transcription gets unwieldy and the AI may miss details mid-way.

Can the AI generate a quote price from the voice notes? No. And don't ask it to. Use it for the scope description, never for the pricing. Your rates and takeoff stay with you.

What if the homeowner wants to walk the site with me — should I still record? Tell them you record voice notes for accuracy. Most are happy with it. Some won't be — read the room. If recording isn't appropriate, do a 60-second walk-through alone after they leave to capture observations.

Where to go from here

Pick the next site visit you've got. Try the workflow once. 3 minutes of voice notes, the prompt above, see what you get back.

Most builders find their Sunday night gets shorter by 60–90 minutes immediately. That's the whole pitch.

Once the scope is structured, the next step is the 12-minute quote workflow — same prompt structure, same 80% efficiency gain. And if you're new to ChatGPT generally, start with the 9 uses guide.

If you want the brief to arrive structured before the site visit happens — so you're not piecing scope together on site at all — that's BuildBrief.

About the author

I'm Ryan Ramsay, founder of BuildBrief. I write about how Australian residential builders can use AI to win back the hours admin and quoting steal from them. The BuildBrief AI Tips and Tricks blog publishes a new piece every fortnight.

Question or want to share a workflow that works for you? Email hello@wolfari.com.au.