AI for builders.Payment claims answeredbefore the deadline.

A builder running a handful of jobs has a lot of moving paperwork. Every subcontractor needs current insurance, licences and safety documents before they start. Every week brings payment claims to assess, variations to price and RFIs to chase with the architect or engineer. The site diary needs writing up whether or not anyone had time.

Most of it arrives by email and lives in inboxes, spreadsheets and phone photos. Nothing is hard on its own, the trouble is the volume, and some of it runs on legal deadlines.

That makes construction a good fit for automation: lots of documents, clear rules about what should be there, and real costs when something slips. It is a poor fit for letting software make the decisions, so we do not.

Payment claims come first because the clock is strict. Under Queensland's Building Industry Fairness (Security of Payment) Act 2017, Holding Redlich's practical guide explains that a respondent must give a payment schedule within the earlier of the period in the contract or 15 business days after receiving a payment claim. If a valid claim gets no schedule in time, the recipient becomes liable to pay the full amount claimed. The QBCC's industry guide to security of payment laws covers the process in more detail. A missed email can turn into a bill, so this is often the first thing we automate. If you build outside Queensland, we check your state's rules during The Delete List call.

Safety documents come next. Safe Work Australia sets out duties to prepare, keep, comply with and review a safe work method statement (SWMS) for high risk construction work, and says the PCBU must provide a copy of the SWMS to the principal contractor. WorkSafe Queensland says a PCBU must prepare a SWMS before starting any high risk construction work. Automation can make sure a SWMS has arrived and been filed. Whether it is adequate for the task is still a safety call for a competent person.

Personal information turns up too, in licence copies, induction records and payroll details. The OAIC's guidance on commercially available AI products says privacy obligations apply to personal information put into an AI system, and recommends as best practice not entering personal information into publicly available AI chatbots. Our builds use business accounts with documented data terms.

The Delete List turns a 45-minute call into a written report. With the director and whoever handles contracts admin, we trace one live job from subcontractor onboarding through to a progress claim.

We look for deadlines tracked in someone's head, documents checked by opening every attachment, and reports rebuilt from scratch each week. Payment claim handling and subcontractor compliance are worth checking first because the cost of a miss is so high.

You get a written report naming 3–7 tools, each with its setup time and hours a week returned, plus a fixed price if you want us to set them up. If The Delete List doesn't find you 20 hrs per month, we refund the $999. Anything we build for you is live within 14 days, or we refund you.

• Talk us through putting a progress claim together. How many hours does one take?
• A variation gets agreed on site. How does it end up on an invoice?
• A quote request lands while you're on site. When does the customer get a price?
• If you won two more jobs this month, where would it jam first?
• A new subbie starts Monday. How does their induction happen?
• Which features in your job software do you pay for and never use?