Claude for trades: quotes, variations and health and safety paperwork

What Claude is good for on a trade business

Claude reads and writes. Give it a plan PDF, a photo of a whiteboard, a voice note turned into text, or a supplier's price list, and it will turn them into a tidy document. It handles PDFs, Word files, spreadsheets and photos, and you can attach up to 20 files to one chat¹. That suits the way a job file actually looks: a consent drawing, an email chain from the client and a few phone photos.

It also makes mistakes and sounds sure while making them. Anthropic says plainly that Claude can produce things that look correct and are badly wrong². On a quote, a wrong quantity costs margin. On a safety document, a wrong control can hurt someone. So the rule on site applies here too: Claude drafts, a competent person checks and signs.

• Quotes and scopes of work from your notes and the plans.
• Variation records written up the same day, with photos attached.
• Task analyses and site-specific safety plans drafted from your own templates.
• Toolbox talk notes, induction sheets and incident write-ups.
• Client emails that explain a delay or a cost change without starting an argument.

Set it up once: a Project for the business

A Project is the place to keep the material Claude should reuse on every job. From the Projects page, choose New Project, add files with the plus button, and use Set project instructions for the standing rules³. On a Team plan, you can share the Project with your estimator and site leads, with view or edit permission³.

Load it with what makes your business yours: your standard terms of trade, your last six good quotes with prices removed or kept as you choose, your scope templates, your exclusions list, your safety plan template, and your hazard register. Then write instructions in plain words, for example: write in New Zealand English; use metric units; list exclusions and assumptions under their own headings; never invent a price, a quantity or a product code; mark anything you are unsure about with a question for the estimator.

Pick the plan with care. Consumer plans ask each person whether their chats can be used for model training, and keep data for different periods depending on that choice⁴. Team and Enterprise run under Anthropic's commercial terms, which say Anthropic may not train models on customer content⁵. If the business holds client addresses, staff details and pricing in Claude, use a business plan in the company's name.

Quotes and scopes: a step-by-step method

Start from the job, not from a blank prompt. Upload the plans or the client's brief, your site notes and any photos. Then ask Claude to do the reading before the writing: list every item of work the documents show, the items it thinks are missing, and the questions you need answered before you can price.

Next, ask for a scope of work in your template. You supply the prices, either typed into the chat or as a spreadsheet you upload. Claude can return the quote as a Word document or an Excel workbook once Code execution and file creation is switched on under Settings, then Capabilities⁶. Ask for the inclusions, exclusions, assumptions and the period the quote is valid for, all as separate sections.

A hypothetical example. A six-person electrical firm in Palmerston North is asked to quote a kitchen and laundry rewire in an older house. The owner uploads the client's email, eight photos of the switchboard and the rooms, and a list of rates. Claude lists the work it can see, and asks whether the switchboard will need replacing, whether the client wants extra outlets in the laundry and who is patching the plaster. The owner answers those three questions, Claude drafts the quote, and the owner checks every quantity against the photos before sending it.

Be explicit about whether the document is a quote or an estimate, and say so in your template. Your terms of trade, and your own advice, decide how you handle that distinction. Claude should simply use the word your template uses, every time.

• Upload the plans, photos and client brief together.
• Ask for missing items and open questions first.
• Supply your own rates; never let Claude estimate prices from the internet.
• Ask for exclusions and assumptions in their own section.
• Check quantities against the drawings yourself before sending.

Residential contracts and variations

For residential building work, the Building Act 2004 and its regulations require a written contract when the work is worth thirty thousand dollars or more including GST, and require the builder to give the client a prescribed checklist and disclosure information before the contract is signed^7,16. The Building Act 2004 also sets out implied warranties and a defect repair period of 12 months after completion⁷. Claude can help you assemble the paperwork, but use the official checklist and the prescribed wording, not a version Claude writes from memory.

Variations are where disputes start. The fix is boring: write every variation down on the day, describe the change, the reason, the cost and the time effect, and get the client's written agreement before the work is done. Claude makes this fast enough that it actually happens. At the end of the day, a site lead types or dictates a few lines into the chat on their phone, attaches two photos, and asks for a variation notice in the company's format. The office checks it and sends it to the client for approval that evening.

For commercial work, the Construction Contracts Act 2002 sets rules for payment claims, including that a claim is in writing and states that it is made under that Act⁸. A payer who disputes the claim responds with a payment schedule, and under the Construction Contracts Act 2002 the default time to do that is 20 working days if the contract does not set one⁸. Ask Claude to check your draft payment claim against a checklist you have taken from the Act or from your lawyer. Do not ask it to tell you what the Act says and rely on the answer.

• One variation, one notice: change, reason, cost, time effect and approval.
• Attach the photos to the notice, not just to the chat.
• Keep a running variation register as a spreadsheet Claude updates from each notice.
• Send the notice before the extra work starts.

Safety paperwork that matches the actual site

Under the Health and Safety at Work Act 2015, a business has a primary duty of care to ensure, so far as is reasonably practicable, the health and safety of workers and others affected by the work⁹. The Health and Safety at Work Act 2015 also expects risks to be eliminated where reasonably practicable, and minimised where they cannot be⁹. Paperwork does not discharge that duty. It records how you meet it.

This is where AI help can go wrong. A generic safety plan that reads well and matches nothing on site is worse than a short honest one. WorkSafe's guidance asks businesses to identify the risks of the actual work, assess them, and choose controls, involving the workers who do the job¹⁰. So use Claude for the writing, after the thinking has happened on site.

A practical routine for a site-specific safety plan: walk the site with the lead hand and take photos. Back in the ute, dictate the hazards you saw and the controls you agreed. Upload the photos and the notes into the safety Project, and ask Claude to fill your template, keeping your words for the controls. Then ask it a second question: which hazards in the photos are not covered in the notes? Treat its answer as a prompt for a second look, not as a finding.

Toolbox talks work the same way. Give Claude the topic, the job and the crew, and ask for a five-minute talk with three questions to ask the team. The value is in the questions, because they get the crew talking about this site.

• Walk the site first; write the document second.
• Keep your own words for controls; let Claude tidy the layout.
• Ask Claude what the photos show that the notes miss.
• Have the person responsible sign the plan, not just the person who typed it.

Shared sites, incidents and records

On a shared site, several businesses often owe the same duty at once. The Health and Safety at Work Act 2015 requires them to consult, cooperate and coordinate with each other so far as is reasonably practicable⁹. Claude is useful for the coordination emails: a short note to the main contractor listing your hazards, your controls and what you need from them, drafted from the safety plan you already wrote.

If a notifiable event happens, such as a serious injury, the Health and Safety at Work Act 2015 requires WorkSafe to be told, and a record of the event to be kept for at least five years⁹. WorkSafe's own pages explain how to notify¹¹. Claude can help you write a clear, factual timeline afterwards from witness notes. Judging whether an event is notifiable is not a job for Claude. That decision, and the call to WorkSafe, belong to a person.

For restricted building work, the Building Act 2004 requires the licensed building practitioner to provide a record of work on completion⁷. Claude can draft it from your job notes into the required form, and the practitioner checks and signs it.

Data, privacy and the fake invoice problem

Client names, addresses, staff phone numbers and injury details are personal information under the Privacy Act 2020, and the business is responsible for keeping them secure and for what it discloses to services overseas¹². The Office of the Privacy Commissioner expects a person to review AI output before acting on it, and expects the business to assess privacy risk before it starts¹³. Keep injury and medical details out of general chats. Put them in the incident system you already use.

Trades are a common target for invoice fraud: an email that looks like it is from a supplier, asking you to pay to a new account. Own Your Online, run by the NCSC, advises checking any change of payment details through a separate, known channel¹⁴. Claude can help an office manager spot odd wording, but a phone call to the supplier's known number is the actual control.

• Use a business plan for anything with client or staff details⁵.
• Keep medical details in your incident system, not in Claude chats.
• Ring the supplier on a known number before you change payee bank details¹⁴.

A two-week start for a trade business

Allow two hours in week one to build the business Project and load your templates. Then use Claude on the next three quotes, writing each one twice, once the old way and once with Claude, and compare the scope and the questions. In week two, move variations onto the same-day notice routine and draft one site-specific safety plan from a real site walk. At the end of the fortnight, keep what saved the office time and drop what added checking work.

• Business plan bought in the company's name.
• Project built with terms, templates and the hazard register.
• Three quotes drafted with Claude and checked against drawings.
• Same-day variation notices running on one job.
• One safety plan written after a real site walk and signed by the responsible person.