— Field Notes
Construction
— AI for the build business

Claude for
Construction.

The trades are sharp. The drag is in the office.

The six prompts from the field note, in full. Copy one, paste it into Claude, drop in your own material where the brackets are, and run it. Built to go from the truck to the books.

— Replace [brackets] with your own inputs

01

Site-walk voice memodaily report

Turn a two-minute voice memo from the truck into a clean daily report plus a client update.

You are my construction site reporting assistant. I'm going to paste a rough transcript of a voice memo I recorded while walking the site. Turn it into two things:

1. A clean DAILY REPORT with: date, project name, weather, crew/trades on site, work completed today, work planned for tomorrow, delays or issues, materials/deliveries, and safety notes.
2. A short PLAIN-ENGLISH CLIENT UPDATE (3–4 sentences) I can send as-is.

Keep my voice — direct and practical. Flag anything that reads like a delay, a cost risk, or a scope change with a warning symbol so I can follow up. If something in the memo is unclear, list it under "Need to confirm" instead of guessing.

Memo: [PASTE TRANSCRIPT]
02

Email threadlogged change order

Paste a thread and get every scope change pulled into a clean, signed-off log.

You're my change-order analyst. I'll paste an email thread between me, the client, and/or trades. Pull out every scope change discussed and build a change order log as a table: Date | Change requested | Requested by | Approved by (+date) | Reason | Cost/schedule impact | Status (approved / pending / disputed).

Then flag: any change done without written approval, any approval that's ambiguous, and any item where cost impact was never confirmed. End with a one-line summary of total estimated cost impact and how many items still need sign-off.

Thread: [PASTE EMAIL THREAD]
03

Inbox of RFIsdrafted replies

Drafts the responses in your voice. You read, approve, and send.

You're helping me respond to RFIs in my own voice. I'll paste one or more RFIs. For each, draft a clear, professional reply that answers the question directly, references the relevant drawing/spec/detail where I've given it, and stays neutral on cost and schedule unless I've told you the answer.

Match my tone: straightforward, no fluff, respectful. Where there isn't enough info to answer, write the reply with a bracketed [I need to confirm X] so I can fill it in. Number each draft to match the RFI.

RFIs: [PASTE]
04

Pile of receiptscoded to the job

Sorted and matched to the right job and cost code, ready for the books.

You're my job-costing assistant. I'll paste or list receipts (vendor, date, amount, description). Sort each one to the right job and cost code, then return a table: Date | Vendor | Amount | Job | Cost code | Category (materials / labor / equipment / subs / other) | Notes.

Use this list of my jobs and cost codes: [PASTE YOUR JOBS + CODE LIST]. If a receipt doesn't clearly map to a job or code, put it under "Unassigned — needs review" instead of guessing. Total the spend per job at the bottom.

Receipts: [PASTE]
05

Messy site notesaction list

Turned into a clear list with a name next to every item.

Turn my messy site notes into a clean action list. I'll paste raw notes. Return a table: Item | Owner | Due (if mentioned) | Priority (high/med/low) | Notes.

Every action item must have a name next to it — if I didn't say who owns it, mark the owner as [UNASSIGNED] so it stands out. Group by trade or area if that's clearer. Move anything that isn't an action (observations, FYIs) into a short "For awareness" list at the bottom.

Notes: [PASTE]
06

Five winning bidsproposal template

Becomes a reusable template you can run on the next job.

I'm going to paste 3–5 of my past WINNING proposals/bids. Study what they have in common: structure, section order, how I describe scope, how I handle pricing, inclusions/exclusions, and my closing/terms language.

Then build me a REUSABLE PROPOSAL TEMPLATE I can run on the next job: section headings, the standard language I reuse word-for-word, and clearly marked [FILL IN] fields for anything job-specific (client, scope, price, timeline). Keep my voice and formatting. Finish with a 6–8 item checklist of what to customize each time before sending.

Winning bids: [PASTE]
— From the truck to the books

The prompts save the hour. Systems give back the week.

These six clear today's paperwork. The bigger win is wiring them into how the business actually runs — so the office stops being the drag. That's the Operating Snapshot: a free 30-minute look at where the time really goes.