The AI AdoptionFree AI pre-audit

21 AI use cases for construction.

Every use case on this page, grouped by where it happens in the business. Each one links to its entry below.

Every place in a building business where AI can take over the chasing, the retyping or the checking, from the first enquiry to the last defect after handover. Each use case names the apps it connects, gives a prompt to try in Claude, and says what stays with you.

By The AI Adoption · Published on

  1. Winning workAmong the ten best

    How to automate your quotes?

    A late quote often loses the job. With this, the draft is ready the same day. You just check the price and send.

    • Gmail
    • Outlook
    • Claude
    • HubSpot
    • Pipedrive
    • Slack
    • Google Sheets
    • Excel

    You keep

    Every quote while auto-send is off. With it on, only a quote with a special detail waits for you to check and send; the others go out and the person in charge is told.

    Its full workflow, step by step, and its first test

    Try this prompt in Claude

    Read this enquiry against my rate card. List the scope and quantities, and flag any special detail. If a detail or a rate is missing, write the question for the customer and stop. Otherwise, draft the quote in my template, priced only from my rates, with the special details noted at the top.

  2. Winning workAmong the ten best

    Bid on more jobs, without the paperwork

    One missed requirement buried in a tender pack can cost you the job. Now every pack becomes a checklist with pages and dates. You only decide whether to bid, then submit.

    • Gmail
    • Outlook
    • Google Drive
    • SharePoint
    • Claude
    • Google Sheets
    • Excel
    • Slack

    You keep

    The decision to bid, once you have read the flagged clauses, and the final check of the pack before you send it. A decline is drafted for you.

    Its full workflow, step by step, and its first test

    Try this prompt in Claude

    Read this tender pack. Check that every file on the attachment list is present and readable, and list any that are not. Build a checklist with one line per requirement: what is asked, the document, its page and the deadline. Flag clauses on payment, insurance and damages. Do not infer requirements the pack does not state.

  3. Winning work

    How to keep your quotes in line with supplier prices?

    When a supplier raises a price, your next quotes still use the old rate. Here, every new price list is matched to your rate card, the changes are flagged, and your rates move only once you approve them.

    • Gmail
    • Outlook
    • Claude
    • Google Sheets
    • Excel

    You keep

    Every change to your rate card, approved by you or your estimator before the next quote uses it.

    Try this prompt in Claude

    Here is the new price list from [supplier] and our rate card. Match each item on the list to the rate card lines it feeds. List every price that changed, with the old and the new price and the lines affected, then the items you could not match. Change nothing in the rate card.

    Fill in the words in blue first.
  4. ApprovalsAmong the ten best

    Stop chasing approvals by hand

    Your jobs wait on the council, the surveyor or the client to sign off. With this, every request is followed until the yes is in. You just check the reminders and send.

    • Gmail
    • Outlook
    • Claude
    • Google Forms
    • Google Sheets
    • Excel
    • Slack
    • Teams

    You keep

    Each chase, checked and sent from your inbox. Past your limit, the emails stop and the person who asked picks up the phone.

    Its full workflow, step by step, and its first test

    Try this prompt in Claude

    Today is [date]. For each row of this approvals tracker, read the replies. Mark Approved only on a clear yes in writing. Flag a question, a change or a no for the person who asked. If nothing came back, the due date has passed and the row has fewer than [limit] chases, draft a short, polite chase: job, item, date asked.

    Fill in the words in blue first.
  5. Approvals

    How to answer every council request before its deadline?

    A council request for more information stalls the approval while you chase each consultant by hand. Here, every item goes to the right person, is chased, and comes back as one reply.

    • Gmail
    • Outlook
    • Claude
    • Google Sheets
    • Excel
    • WhatsApp
    • Google Docs
    • n8n

    You keep

    Every technical answer, with your team and consultants. Your project lead checks and signs the response before it is lodged, and decides what to do when a reply is late.

    Try this prompt in Claude

    Here is the council’s request for information on [application], with our team and consultant list. Split it into items. For each one, give the item in the council’s words, who should answer it and the drawings it touches, due [number] days before the council’s date. Do not answer any technical item yourself.

    Fill in the words in blue first.
  6. On siteAmong the ten best

    Track your extras on site instantly, without friction

    Extras agreed on site get lost on the way to the office. Now each day’s notes become the site report, and every extra becomes a variation to sign. You only set the price.

    • WhatsApp
    • Claude
    • Google Drive
    • Procore
    • Slack
    • DocuSign
    • PandaDoc
    • Xero

    You keep

    The price and time on each variation, set by you or your project manager. Nothing goes out for signature until they are set.

    Its full workflow, step by step, and its first test

    Try this prompt in Claude

    Write today’s site report for [job] from these notes and photos, in my template: work done, issues and photos. Check each request made on site against the attached scope. For any work the contract does not cover, draft a variation: what was asked, by whom, citing the notes and photos. Leave price and time blank.

    Fill in the words in blue first.
  7. On siteAmong the ten best

    How to automate project delay tracking?

    A schedule fed by hopeful updates rarely shows where a job is running late. Here, only site updates that prove a milestone move the schedule. Your project manager confirms the rest.

    • WhatsApp
    • Gmail
    • Claude
    • Google Sheets
    • Smartsheet
    • Slack
    • Looker Studio
    • Power BI

    You keep

    Every new date and its reason, set by the project manager. When a key date moves, you decide what the client hears.

    Its full workflow, step by step, and its first test

    Try this prompt in Claude

    Here are yesterday’s updates from site and our programme, with the proof each milestone needs. For each update, say which task it belongs to and whether it proves the milestone. List the tasks past their planned date without proof, and those with no update for [days]. Do not mark anything done on a hopeful sentence.

    Fill in the words in blue first.
  8. On site

    How to get every install’s parts ready the day before?

    A missing part means a wasted trip or a second visit. Here, tomorrow’s jobs are checked each afternoon, parts are ordered and confirmed, and each tech knows where to collect them.

    • ServiceM8
    • simPRO
    • Claude
    • Gmail
    • WhatsApp
    • Slack

    You keep

    Every order, checked against the quote and sent by the office. When a reply is late or a part is short, the office calls the branch or sorts it out with the crew.

    Try this prompt in Claude

    Here are tomorrow’s booked jobs with the parts on each accepted quote, our van stock sheet and the parts already on order. List the parts each job still needs. Group them into one order per wholesaler, with the job number as the order reference. Count a part as in the van only if the stock sheet shows it.

  9. On site

    How to automate your meeting minutes?

    Minutes go out late, actions slip, and extra work agreed in the room often goes unbilled. Here, minutes are ready the same day, actions are followed to done, and extras reach the director.

    • Google Meet
    • Teams
    • Claude
    • Google Docs
    • Gmail
    • Slack
    • Outlook
    • Google Sheets

    You keep

    The minutes, read by the project manager against what was said before they go. Any extra work goes to the director, who prices it and agrees it in writing with the client.

    Try this prompt in Claude

    Here is today’s site meeting transcript, our minutes template, last meeting’s open items and the agreed scope. Write the minutes: decisions, actions, owners and dates, open items carried over. Then list each decision outside the scope, with the line of the scope it goes beyond. Add nothing the transcript does not say.

  10. On site

    How to find any answer in your plans and specs?

    The answer is usually in the specification or the contract, on a page nobody has time to find. Here, each job’s documents sit in one Claude project, and every answer comes with the page it was taken from.

    • Claude
    • Google Drive
    • SharePoint
    • Procore

    You keep

    The decision, made once you have opened the cited page. A question the documents do not answer goes to the architect or the engineer.

    Try this prompt in Claude

    Answer only from the documents in this project: the drawings, specification and contract for [job]. For each answer, give the document and the page. If the documents do not answer the question, or two of them disagree, say so and stop.

    Fill in the words in blue first.
  11. On site

    How to keep every subcontractor’s insurance and licences current?

    A subcontractor working on an expired insurance certificate leaves the risk with you. Here, every certificate and licence is read for its expiry date, renewals are chased before they lapse, and no new work order goes out without them.

    • Gmail
    • Outlook
    • Claude
    • Google Sheets
    • Excel
    • Procore

    You keep

    The decision to let a subcontractor start without a current document. The AI never waives one.

    Try this prompt in Claude

    Here are the insurance certificates and licences our subcontractors sent us. For each document, give the subcontractor, the type, the policy or licence number and the expiry date, exactly as written. List anything expiring within [days], anything unreadable, and any subcontractor missing a document from our required list.

    Fill in the words in blue first.
  12. ClientsAmong the ten best

    Update every client weekly, without writing a word

    The Friday update gets written from memory, late, one job at a time. Now it comes from the week’s site reports and photos. You only check the ones that mention a delay or money.

    • Google Drive
    • Procore
    • Claude
    • Slack
    • WhatsApp
    • Gmail
    • Outlook
    • n8n

    You keep

    Any update with a new date or an unexpected cost. It waits in drafts until you read what it promises and send it.

    Its full workflow, step by step, and its first test

    Try this prompt in Claude

    Write this week’s client update for [job] from these site reports, programme and photos, in the tone of my past update. Cover progress, next steps and decisions needed. First list any missing day, or report that disagrees with the programme. Flag every new date or cost the client did not expect.

    Fill in the words in blue first.
  13. Clients

    How to close every defect after handover?

    Defects reported after handover come in by text, email and photo, and some are never closed. Here, each one is logged with its photos, sent to the trade responsible and chased, and closed only once the client confirms.

    • Gmail
    • WhatsApp
    • Claude
    • Google Sheets
    • Procore
    • Slack

    You keep

    Whether an item is a defect under the contract, decided by your site manager, and the client’s confirmation before it is closed.

    Try this prompt in Claude

    Here are the messages and photos the client has sent since handover, and our list of trades on the job. List each defect once: what it is, where, the photo it comes from and the trade responsible. Mark anything that looks like wear or a new request, rather than a defect, for my site manager to decide.

  14. MoneyAmong the ten best

    Never handle an invoice. Ever. With complete peace of mind.

    Every supplier invoice is read, checked against its order and docket, and lined up for payment. Anything wrong is caught and queried before it reaches you. You only approve the payment run.

    • Gmail
    • Outlook
    • Claude
    • Slack
    • Google Drive
    • Teams
    • SharePoint
    • Xero

    You keep

    The payment run. Checked invoices wait in Xero or QuickBooks for your approval; refuse one and your reason goes to the supplier or to the team.

    Its full workflow, step by step, and its first test

    Try this prompt in Claude

    Compare this invoice with its purchase order and signed docket, line by line, showing quantity and unit price from each. Mark each line matching, in our favour, or against us beyond [tolerance]. Check supplier, number and amount against this list of paid invoices. If a document is missing, say which and stop. Draft a supplier query for any line against us.

    Fill in the words in blue first.
  15. MoneyAmong the ten best

    How to automate your accounting checks?

    Accounting errors often surface at month-end, when there is least time to fix them. With this, possible issues are caught through the month, each with a suggested fix. Your finance manager decides every change.

    • NetSuite
    • Xero
    • Claude
    • Google Sheets
    • Excel
    • Slack
    • WhatsApp

    You keep

    Every change in the books, decided by your finance manager. Anything still open as month-end nears reaches you before the books close.

    Its full workflow, step by step, and its first test

    Try this prompt in Claude

    Here are this month’s bills, sales invoices and bank lines for [business]. Match each line by invoice number, supplier or customer, amount, currency and business. List any possible duplicate, missing document, unmatched bank line or line from another business, with its source and a suggested fix. Change nothing.

    Fill in the words in blue first.
  16. Running the businessAmong the ten best

    How to bring information scattered across different software into one place

    Automatically pull information from the tools your businesses use into one clear view. Spend less time switching between systems and piecing together what’s happening.

    • NetSuite
    • Procore
    • n8n
    • Make
    • Google Sheets
    • SharePoint
    • Looker Studio
    • Power BI

    You keep

    The decisions you take from the view. A connection that stays broken comes to you or your AI specialist, and its figures are never shown as current.

    Its full workflow, step by step, and its first test

    Try this prompt in Claude

    Here are this month’s figures exported from [software] for each of our businesses, with our list of business and project names. Put every line in one table: business, project, amount and source date, each line counted once. List any line you cannot place, and any business whose figures are missing or older than the others.

    Fill in the words in blue first.
  17. Running the businessAmong the ten best

    How to spot broken automations before they hold up your business

    Automatically check that each automation delivers its expected result. The person responsible is alerted when something is missing, and you’re notified if it stays unresolved. Alerts close once it’s working again.

    • Google Sheets
    • Excel
    • n8n
    • Make
    • Slack
    • WhatsApp

    You keep

    The fix itself, by the person responsible. If an automation is still broken after the alert, you or your AI specialist take it over.

    Its full workflow, step by step, and its first test

    Try this prompt in Claude

    Here is our list of automations, with when each should run, what it should leave and who owns it, and this week’s run history. For each one, say whether it ran on time and left its output. A run with nothing to process counts as done. For each failure, write a short alert for its owner: which automation, its last success and what to check.

  18. Running the business

    How to automate your recurring prompts?

    A prompt you retype every week only runs when someone remembers it. Here, it runs on a schedule under a business account, after the data is verified. A person checks the result before anything is sent.

    • Claude
    • Procore
    • Google Sheets
    • Slack
    • Teams

    You keep

    The approval of each result before anything is sent, and the choice of what the job may read.

    Try this prompt in Claude

    Here is a prompt I run by hand every week and an example of the result I want. Rewrite it as instructions for a scheduled job: the data it needs and where it comes from, the checks before it starts, the exact result, and what should stop it. Point out anything in my prompt that only works because I am there.

  19. Running the business

    How to automate AI answers for each business?

    When you run several businesses, an AI assistant can mix up their details. Now each business has its own folder, and every answer lists the files it used. You check the sources before relying on the answer.

    • Claude
    • Google Drive
    • SharePoint

    You keep

    The check of the sources before you rely on an answer. Who can see each business’s folder is set business by business.

    Try this prompt in Claude

    You work for [business] only. Use only the files in this project. Before answering, check the question is about [business]; if it could be about another of our businesses, ask which one. At the end of every answer, list the files you used.

    Fill in the words in blue first.
  20. Running the business

    How to automate your team’s AI access?

    When staff use personal AI accounts, your documents can leave with them. Here, every account belongs to the business, set up by role and removed when someone leaves. The owner tests each new access before any sensitive data goes in.

    • Google Sheets
    • Excel
    • Claude
    • Google Drive
    • SharePoint

    You keep

    Who gets access to what, decided by you, and the test of each new access before any sensitive data goes in.

    Try this prompt in Claude

    Here is our list of roles and the folders, tools and data each one needs. Draft an access matrix: one line per role, what it may read, what it may change, and what stays with the directors. Flag any role that would see financial or client information it does not need.

  21. Running the business

    How to automate turning know-how into procedures?

    What your managers know often lives only in conversations. With this, a recorded walkthrough becomes a draft procedure, and questions are answered from the approved version. Each procedure’s owner approves and dates it first.

    • Google Meet
    • Zoom
    • Claude
    • Copilot
    • Google Docs
    • Word
    • Google Drive
    • SharePoint

    You keep

    Every procedure, approved and dated by its owner before anyone relies on it, and every question it does not cover.

    Try this prompt in Claude

    Here is the transcript of [manager] explaining how we [process]. Write it as a procedure: the steps in order, the exceptions, and who signs off what. Use only what the transcript says, and list every point that is unclear or missing as a question for [manager].

    Fill in the words in blue first.

Where to start.

Start with one, on a past job, with files you are allowed to use. The ten marked as the best have their full workflow, a first test and the detail of each step in the ten best AI use cases for construction.

To find which of these fits your business first, book a free AI pre-audit: forty-five minutes on your own work, with a clear next step, with or without us.

Bring your questions.

Free AI pre-audit