The contracts manager wants a progress update. The office has site notes, an email about a delayed delivery and a spreadsheet whose job references need checking. Someone has to turn that lot into something the customer can actually use.
That is where I would start a conversation about AI for contractors. Pick the piece of work you want to improve, then decide whether an assistant belongs in it. Buying a collection of tools before agreeing that job leaves you with more places to check.
My shortlist would start with document drafting, searching project information and help understanding spreadsheets. Each deserves a different test. Any claim about faster work should survive the time spent preparing the inputs, checking the answer and putting the result where it belongs.
AI for contractors: shortlist the task first
Picture an illustrative building contractor whose office manager prepares customer updates from notes supplied by the contracts manager. The draft needs completed work, outstanding decisions and the next planned visit. Some notes describe work that has been requested but remains unapproved.
I would write the intended handover on a sheet of paper: the contracts manager confirms the facts, the office prepares the update, someone checks it and the approved version goes into the job record. Then I would look for the slow part.
If the facts are available and writing takes the time, a drafting assistant deserves a trial. If everyone is searching for the latest information, start with document organisation. If nobody can say whether the additional work was approved, ask the person responsible before generating any prose.
My comparison would be:
- Document drafting: trial when you have usable notes and a clear reviewer.
- Project search: trial when the relevant records live in a system you already use.
- Spreadsheet assistance: trial when someone understands what the columns mean and can check the result.
- Automatic sending or record changes: leave these outside the initial trial.
This is why I put the workflow into Design. Agree the handover, the owner and the acceptance test before choosing the technology.
Document drafting: a sensible starting point for Copilot
Microsoft's guide to Copilot in Word describes creating drafts from prompts, notes or referenced files, refining existing writing and summarising documents. It also says availability depends on your subscription or licence and organisational settings. Check what your business can actually use before planning around a demonstration.
For the illustrative contractor, I would test a customer update using fictional site notes. Ask for separate headings for completed work, outstanding questions and planned activity. Tell the assistant to preserve uncertainty and flag missing information. Then see whether the output follows those instructions.
Include an awkward note: the replacement item has been discussed, but the customer has yet to confirm it. The reviewer should check whether the draft preserves that distinction. A polished sentence that implies agreement would fail my test.
The contracts manager should compare the draft with the notes before anything goes to the customer. Check names, job references, commitments and wording around unfinished work. Keep the approved update in the agreed job record.
I would trial this before buying a separate writing product. If Word already sits in your workflow and the required capability is available, you have a clear place to test it. Measure the whole task, including correction and filing. Attractive prose alone would leave me unconvinced.
Project search: make the source part of the answer
If your business already uses Procore, project search is another candidate. Procore describes its Deep Search Agent as searching project information including specifications, drawings, requests for information and submittals, with links back to the source documents. A request for information is a recorded project question; a submittal is information or material submitted for review.
That is a supplier description, rather than an independent performance test. I would ask for a demonstration using a fictional equivalent of a difficult question your team actually handles. Have the person who knows the answer check the result and open the linked source.
For example, ask which recorded response addresses a particular installation query. Check whether the answer leads to the relevant record and whether the person reviewing it can establish which revision applies. Include an unresolved query and see how the product presents the gap.
Check the proposed package too. Procore's product guidance says Procore AI is generally available with a Digital Coworker package and tells users to validate AI work against their records. It also distinguishes the supported classic Documents tool from Document Management, which it says the AI cannot yet learn from. Confirm the UK package, supported project tools and setup with the supplier.
I would consider this route for a contractor already committed to Procore. I would need a broader operational case before recommending a new project platform primarily to get an AI search feature. Start with the handovers covered in our field service software buying guide.
Spreadsheet help: keep the checking visible
Microsoft's Copilot in Excel guidance describes summarising data, finding trends, generating formulas and explaining existing formulas. It explicitly asks users to review, edit and verify the output.
I would use a copy of a fictional job-cost workbook for the trial. Give the columns clear names and ask the assistant to explain an existing formula or suggest a way to group costs by job reference. Have the bookkeeper or quantity surveyor check its work. A quantity surveyor, often shortened to QS, handles commercial and cost-related work.
Before asking for analysis, agree what the workbook represents. Are the costs ordered, delivered or invoiced? Does the total include work awaiting approval? Decide how missing job references should be treated. Write those definitions beside the test.
Then check the suggested formula against examples whose expected answer you have established independently. Include an empty field, a duplicate reference and a cancelled item. Ask the reviewer to explain why each result is correct.
My preference would be to keep repeatable calculations in an understood spreadsheet formula with a named owner. An assistant can help prepare or explain that formula; the business still needs someone who can maintain it. If the checking takes longer than the original task, put the trial aside and improve the workbook itself.
Which tools would I leave off the initial list?
I would postpone anything whose value depends on letting it make commitments on your behalf. Automatically sending customer updates, accepting changes to scope or turning an uncertain site note into a final record would all sit outside my first trial.
I would also park products that duplicate a handover you could simplify directly. If the office retypes a job reference because the site form has no agreed field for it, fix the form and test the revised process. Make the case for another product after that.
For specialist estimating tools, I would ask the estimator to define a separate trial around the work they understand. Keep quantities, exclusions, assumptions and checks visible. Avoid bundling that decision into a general office-assistant purchase simply because both products carry an AI label.
Ask every shortlisted supplier to demonstrate:
- Where the input comes from and how the user selects it.
- What the reviewer can inspect before accepting the result.
- Where the accepted output is saved.
- What happens when information is missing or contradictory.
- Who supports the workflow after setup.
A product that leaves those questions unanswered stays off my buying list.
Run a trial your office can judge
This week, choose a recurring task and write down what a satisfactory result looks like. Use fictional records or material already approved for the chosen tool. Name the person preparing the input and the person checking the output.
Record the current route through the task, including chasing, checking and filing. Repeat the exercise with the proposed assistant. Keep notes on preparation effort, corrections, unanswered questions and whether the final record reaches its proper home.
Include an awkward example as well as an easy one. Ask the people doing the work whether they could repeat the process without someone standing beside them. Finish with a decision: continue, adjust the workflow or stop.
My buying rule is simple: the tool earns its place when the complete job becomes easier to run and someone can still explain the result. Keep the shortlist small enough to prove that.
If you want help deciding where to start, we can talk through the job that is taking up your office's time.