Where the hours go in a trade office
Ask the owner of a small electrical firm where the week goes and the answer is rarely the tools. It is pricing jobs from a site visit and a few photos, chasing a client to confirm extra work, building the monthly claim, and keeping the safety file current for the main contractor's next audit. Most of this already lives in Microsoft 365: quotes in Word, costings in Excel, client threads in Outlook and the crew chat in Teams.
That is where Copilot fits. It does not price a job and it does not know the Building Code. What it does well is turn your own notes, emails and templates into clean drafts, and pull the facts out of a long thread so nobody has to scroll through it. The work below is ordered the way a job runs: quote, contract, variation, payment claim, then the health and safety records that sit alongside all of them.
Quotes: from site notes to a document the client can read
Start with what you capture on site. Microsoft has added the ability to take a photo on an Android or iOS phone and use it in a Copilot prompt while working in Word, Excel or PowerPoint for the web, which suits a photo of handwritten measurements or a whiteboard sketch10. Back at the office, or in the ute, open your quote template in Word and ask Copilot to build the scope from those notes.
Keep the price out of Copilot's hands. Your rates, margins and supplier pricing belong in your costing spreadsheet or job management system. Copilot in Excel can help you check that spreadsheet, for example by explaining a formula or summarising labour hours by job, and Microsoft advises reviewing anything it creates before you rely on it11. It needs the workbook in a modern format such as .xlsx11. Saving the file to OneDrive or SharePoint also means colleagues and Copilot are working on the same version.
A generic worked example: picture a Hamilton plumbing business visiting a 1970s house for a bathroom renovation. The plumber dictates notes into OneNote and takes three photos. The office manager then prompts Copilot in Word: 'Using /Bathroom site notes, draft the scope section of our standard quote. List inclusions and exclusions separately. Exclude anything behind existing linings unless the notes say it was inspected. Do not add any price. List every assumption you made at the end.' The assumptions list is the part a client most often disputes later, so it is worth having Copilot write it down.
- Write the scope in plain English the client will understand, then a technical schedule for your own crew.
- State exclusions as clearly as inclusions; most variation arguments start with an assumed inclusion.
- Ask Copilot to flag words such as 'allow', 'approximately' or 'as required' so you can decide if they are fair.
- Check every quantity against your own takeoff before the quote leaves the office.
Residential contracts and the disclosure checklist
For residential building work, the Building Act 2004 brings extra steps. Where the work is valued at or above the threshold in the Building Act 2004, or the client asks, the contractor must give the client a disclosure statement and the prescribed consumer protection checklist before the contract is signed5. A written contract is required above the same threshold, and it should cover a description of the work, start and finish dates, the payment process and how variations will be agreed6.
Copilot can help assemble the pack but should not draft the statutory parts. The checklist is a prescribed form, so use the official version from building.govt.nz rather than asking Copilot to recreate it. Where Copilot earns its keep is the cover email and the plain-English summary of your own terms. A prompt such as 'Explain our payment stages from /Residential contract template in five short bullet points for a homeowner, without changing any dates, percentages or amounts' produces something a client will actually read.
Then compare. Ask Copilot to list every clause in your template that deals with variations, and paste that list into the job file. When a variation comes up in month three, the office already knows what process the contract promised.
Variations: write them down on the day
Most variation disputes are not about the price of the extra work. They are about whether anyone agreed to it. The building.govt.nz guidance for contracts says the contract should set out how variations will be agreed before the work continues6. The practical rule for a small firm is that a variation is not real until the client has it in writing.
Copilot shortens the gap between the conversation and the paper. If the site lead posts a voice note or a few lines in the job's Teams channel, the office can prompt: 'From the last message by the site lead in this channel, draft a variation notice for /Smith Street job. Include what changed, why, the effect on the programme, and a line for the client to approve. Leave the price as a blank for me to fill in.' Copilot drafts. A person prices and sends.
If variations were discussed in a Teams meeting with the client or the architect, Copilot can list what was agreed. To ask Copilot about the meeting after it ends, someone needs to turn on transcription during the meeting9. Tell everyone at the start that you are transcribing, and send the summary to every party so they can correct it.
- Prompt: 'List every change to scope mentioned in /Site meeting with client, with who requested it and whether a price was discussed. Mark anything that was not clearly agreed.'
- Prompt in Outlook: 'Summarise this thread with the client about the deck extension. What did they approve, in their own words, and on what date?'
- Keep each variation in a running Excel register with a status column, and ask Copilot to list items that are priced but not yet approved.
Payment claims under the Construction Contracts Act
The Construction Contracts Act 2002 sets out what a payment claim must contain. It must be in writing, identify the contract, the work and the period it relates to, state the claimed amount and the due date, show how the amount was calculated, and state that it is made under the Act7. If the contract is silent on timing, a payer who disputes the claim has 20 working days after it is served to provide a payment schedule7. Every payment claim must also be accompanied by the prescribed information in Form 17,8.
This is a good job for Copilot because the inputs are already in your files. Point Copilot at your approved variations register and the progress figures in Excel, and ask it to draft the covering claim in your template. Then check the six required elements and that Form 1 is attached, every time. A missing statement that the claim is made under the Act is a small slip with large consequences.
When a client sends back a payment schedule, ask Copilot in Outlook to compare the scheduled amount with your claim line by line and list the reasons the client gave for each difference. The Act requires a payer who schedules less than the claimed amount to explain how they calculated it and why7, so a missing reason is itself worth noting.
Health and safety records that match the work on site
Under the Health and Safety at Work Act 2015, every PCBU on a shared site has its own duties, and where duties overlap, each must so far as is reasonably practicable consult, co-operate with and co-ordinate activities with the others2. A subcontractor cannot hand its duties to the main contractor by contract2. That is why the safety file matters: it is the evidence you did your part.
Copilot can help you keep that file current, but the hazard thinking has to come from people who know the job. The Act requires a PCBU to engage with workers who are directly affected by a health and safety matter, so far as is reasonably practicable3. A task analysis written alone in the office by Copilot, and signed by a crew who never read it, is the opposite of engagement.
A better pattern for a Whangārei roofing firm: the crew talk through the job at the toolbox meeting and the leading hand records the main risks in a Teams post or a voice note. The office prompts Copilot: 'Turn these notes into our task analysis template for re-roofing a two-storey house. Keep the crew's wording for each hazard. For each control, say who is responsible. Flag any hazard mentioned with no control.' The crew then reads it, corrects it and signs it.
- Toolbox notes: ask Copilot to summarise the week's Teams safety posts into a one-page record for the site file.
- Inductions: ask Copilot to draft induction questions from your site rules, then test them on a new starter.
- Incidents: use Copilot to tidy the written account, but never to fill in what someone did not see.
Notifiable events and records you must keep
If a notifiable event happens, the PCBU must make sure WorkSafe is notified as soon as possible after becoming aware of it1. A record of each notifiable event has to be kept for at least 5 years from the date notice was given1. Copilot has no role in deciding whether something is notifiable; that call belongs to the owner or the person with safety responsibility, using WorkSafe's guidance.
Copilot can help afterwards. Once the notification is made, it can draft the internal incident report from witness statements, list the corrective actions with owners, and produce a short summary for the crew. Store the record in a SharePoint library with restricted access and a retention label, so it is not deleted early and not visible to people who do not need it.
Guardrails for a trade business using Copilot
Copilot only shows people content they already have permission to see4. In a small firm that often means everything, because the shared drive was set up years ago with one login. Before licensing Copilot, move payroll, staff files and incident records into restricted libraries. Our guide to checking permissions before a Copilot rollout covers the steps.
The NCSC's advice to small businesses is to train staff on responsible AI use and define clearly which data must not go into AI tools12. For a trade business, that list usually includes client bank details, staff medical information and anything covered by a confidentiality clause in a main contract. Keep the list short enough that a site lead can recite it.
- Copilot drafts quotes, variations, claims and safety records; a person prices, approves and signs them.
- Use official forms and checklists as published; do not have Copilot rewrite statutory content.
- Tell people when a meeting is being transcribed, and share the summary with every party.
- Restrict access to staff, payroll and incident records before anyone gets a Copilot licence.