AI helps most with three pre-start jobs: turning drawings, specification and quote into a scope checklist, turning that scope into a long-lead list with order-by dates, and turning both into a risk register. ChatGPT or Claude can draft each in an afternoon, but you supply the real lead times and decide which risks matter.
The trap is the assistant's confidence. It will happily state a lead time for fire doors, or leave out an item that is not named in the documents you gave it. So every list below follows one source rule: nothing goes on it unless it comes from a document, a supplier's written quote or your own record of a past job. Where the source is missing, the item goes on the list as a question.
The examples use a ten-week office fit-out of 140 square metres for an IT support firm that needs a small server room. It has the mix that causes pre-start trouble: long-lead items, client-supplied equipment and a landlord's access rules.
The pre-start checklist: 42 items in seven groups
Each row says what to have and what proves you have it. If you cannot point to the proof, the item is not done. Print it, or paste it into your assistant's project as the master list.
Scope and paperwork
| Item | Proof it is done |
|---|---|
| Scope written down: inclusions, exclusions, assumptions and allowances | One page the client has initialled or replied "agreed" to |
| Drawings and specification carry the same revision as the quote | Revision letters match in a short note on file |
| Client-supplied items listed, each with an owner, a delivery date and a storage place | A list the client has confirmed in writing |
| Contract or order signed, with change procedure and payment milestones | Signed copy in the job folder |
| Insurance and licences confirmed for you and every sub | Certificates filed, expiry dates in the diary |
| Permits, approvals and inspection hold-points listed with who requests each and the notice needed | A table with a date or "not required" against every line |
Site and access
| Item | Proof it is done |
|---|---|
| Existing conditions recorded | Dated photo set plus a note of anything already damaged |
| Utilities located and any isolations or shutdown windows booked | Written confirmation from the client, landlord or provider |
| Access, parking, delivery and lift or loading limits understood | Rules sent in writing by the landlord or building manager |
| Working hours, noise and dust rules and key holder known | Named person and phone number on the site sheet |
| Welfare, storage, waste route and a delivery spot that blocks nobody | Marked on a simple site plan |
| Hazardous materials such as asbestos checked for in an older building | A survey report on file, or a written "none known" and advice taken before anything is disturbed |
Safety and compliance
| Item | Proof it is done |
|---|---|
| Risk assessments and method statements for the high-risk tasks | Signed by the person doing the work |
| Induction and emergency plan: assembly point, first aid, emergency contacts | Sign-in sheet on day one |
| Subcontractor competence and paperwork collected before they arrive | Checklist ticked per sub |
| Fire safety for the work period: extinguishers, hot-work rules, protection of existing alarms | Rules on the site sheet; alarm isolation agreed in writing |
| Notifications and signage the job needs | List with who sent what and when |
| Incident and near-miss route known to everyone | One phone number and one form |
Procurement and long-lead items
| Item | Proof it is done |
|---|---|
| Every item with a lead time of three weeks or more identified | A list traced line by line to the quote and drawings |
| Lead times given by the supplier, with the date they said it | Email or quote filed with the list |
| Approvals listed: samples, shop drawings, finish choices, who approves and how long it takes | A column of turnaround days with named approvers |
| Order-by dates worked back from need-on-site dates, with a buffer | The sum shown on the sheet, not just the answer |
| Orders placed, deposits paid, delivery windows booked and storage arranged | Order numbers and confirmation emails |
| A fallback for the two riskiest items | An alternative product or supplier priced and noted |
| One tracking sheet showing ordered, confirmed, dispatched, delivered | Updated weekly, owner named |
Programme and people
| Item | Proof it is done |
|---|---|
| Baseline programme with dependencies, inspection hold-points and the critical path marked | A dated copy kept unchanged for later comparison |
| Subcontractors booked for dates, not "week 6 or so" | Confirmation messages saved |
| Weather- and season-sensitive work checked against the calendar | Notes on the programme where exposure matters |
| Float identified: where you have slack and where you have none | A column showing days of float per task |
| Labour plan by week, with cover if someone is off | A named person per task per week |
| Handover requirements known at the start: certificates, manuals, test records | A handover list agreed with the client |
Money
| Item | Proof it is done |
|---|---|
| Budget set against the quote, contingency shown separately | A sheet where contingency is its own line |
| Cash-flow forecast for deposits, stage payments and sub payments | Week-by-week in and out, reviewed monthly |
| Supplier credit terms and deposit requirements recorded | Terms in the procurement list |
| Variation procedure: who can instruct, how priced, how approved | Written into the contract or a signed note |
| Allowances and provisional sums tracked against selection dates | Each allowance has a "decide by" date |
| Retention or holdback terms understood | One line in the contract summary |
Communication
| Item | Proof it is done |
|---|---|
| Kick-off meeting held with the client, key subs and the landlord's contact | Minutes or an action list sent the same day |
| One named decision-maker on the client side with authority to approve | Name in the contract or kick-off notes |
| Decision log with the date each client choice is needed | A table the client has seen |
| Weekly update day and format agreed | First update sent on schedule |
| Photo and daily-log routine set up | One folder structure for the job |
Five of these items are the easiest to leave vague on a small job: the written scope, client-supplied items, approvals, lead times and the decision log. The sections below put the assistant to work on exactly those.
Draft the scope checklist from the documents you already hold
Start by pasting or uploading the quote, the drawings' text and any specification. Ask the assistant to separate what the documents say from what they leave open. A scope that says "electrical works as required" is a trap: it is cheap to write and expensive to discover.
I run a small building firm. Below are the quote and notes for an office fit-out. Build a scope checklist with these columns: scope item; where it appears in the documents (quote line or drawing); what information is missing; the question to ask the client or supplier; whether it is likely to have a long supplier lead time (yes, no or unknown).
Rules: use only what is in the documents. Never state a lead time. If a scope item is vague, say so and write the question. Then, separately, list items that jobs like this often need but that are NOT mentioned in the documents, as questions only. Do not add them to the scope.
DOCUMENTS:
Fit-out of first-floor office, 140 square metres: strip out existing partitions; new stud partitions and glazed screens to drawing A-02; suspended ceiling with LED panels; electrical works as required; data containment (cabling by client); split air conditioning to comms room; floor finishes; decoration; reception counter (joinery); fire doors to comms room.A typical reply comes back as a table, and the useful rows look like this:
| Scope item | Missing information | Question | Long lead? |
|---|---|---|---|
| Electrical works as required | No circuit schedule, no distribution board specification | Is a board upgrade included? What is the load of the server equipment? | Yes |
| Glazed screens to A-02 | Glass type, door types, acoustic requirement | Is there a performance specification? | Yes |
| Fire doors to comms room | Rating, hardware, certification route | Who provides the certificate at handover? | Yes |
| Split air conditioning | Cooling capacity, condensate route, supplier | What is the heat output of the IT equipment? | Unknown |
| Reception counter (joinery) | No drawing reference | When will the design be frozen? | Yes |
| Floor finishes | Product, areas, subfloor condition | Is a sample approved? | Unknown |
Below that sits a second list of things the documents do not mention: temporary power, protection of existing finishes, waste removal, making good, testing and certificates, and out-of-hours working. These are questions for the client, not additions to your price. If the assistant slides them into the scope as if agreed, push back and ask for the reply again.
Here is what the fix looks like on one line. Before: "Electrical works as required." After: "Supply and install a new 12-way distribution board in the comms room; 14 twin sockets to drawing E-01; LED panel lighting to the ceiling plan; emergency lighting to the comms room; test and certify. Excludes: power to the server rack (client's electrician) and data cabling (client's IT provider)." The second version has quantities, a drawing reference, exclusions and named owners. Your quote may already have all that; if it does not, the checklist found it before the client did. For a room-by-room version of the same idea, see the bathroom scope-of-work tutorial.
Finally, ask the question that catches what the documents cannot:
List everything in this job that depends on a party outside our contract (client, landlord, utility, internet carrier, authority, another contractor) and what each needs by when for us to keep the programme. Mark anything not mentioned in the documents as "assumed".In the fit-out example this surfaces the internet line. It is not in the quote because the client orders it from a carrier, yet the IT firm cannot commission the server room without it. The carrier quoted six weeks.
Long-lead list: working back from the day each item is needed
A long-lead item is anything whose delivery time could hold up work if you order it when the work starts. The sum is the same for each item:
Order-by day = need-on-site day − buffer − supplier lead time. Subtract the approval time again to find the day you must start the approval. Count in working days.
Here it is for ten items on the fit-out. Day 1 is the Monday you open the site, "Wk 0" means the week before, and "Wk −6" is six weeks earlier still. Lead times stand in for supplier quotes (the figures you would ask for in writing), approvals are working days for samples or drawings to be signed off, and each buffer is five days unless noted.
| Item | Lead time | Approval | Needed on site | Start approval by | Order by |
|---|---|---|---|---|---|
| Distribution board and sub-mains upgrade | 6 weeks | 3 days | Wk 2 Wed | Wk −6 Fri | Wk −5 Wed |
| Glazed office partitions | 8 weeks | 5 days | Wk 3 Fri | Wk −7 Fri | Wk −6 Fri |
| Fire-rated door sets | 5 weeks | 5 days | Wk 5 Mon | Wk −2 Mon | Wk −1 Mon |
| Reception joinery | 7 weeks | 5 days | Wk 8 Wed | Wk −1 Wed | Wk 0 Wed |
| LED panel lighting package | 3 weeks | 3 days | Wk 5 Tue | Wk 0 Thu | Wk 1 Tue |
| Split air-conditioning unit | 3 weeks | 3 days | Wk 5 Fri | Wk 1 Tue | Wk 1 Fri |
| Access control controller and readers | 4 weeks | 2 days | Wk 6 Fri | Wk 1 Wed | Wk 1 Fri |
| Carpet tiles (buffer 3 days) | 2 weeks | 3 days | Wk 8 Mon | Wk 4 Fri | Wk 5 Wed |
| Network rack and switches (client's supplier) | 4 weeks | none | Wk 8 Fri | Wk 3 Fri | Wk 3 Fri |
| Broadband line (client's carrier) | 6 weeks | none | Wk 9 Fri | Wk 2 Fri | Wk 2 Fri |
Read it from the top. Five of the ten need their approval started before the site opens, four of those need the order itself placed before then, and the glazed partitions need their approval seven weeks ahead. That is a finding for the kick-off meeting, because those orders only happen if the client approves samples and drawings before the site opens. The two client items are on your list, but not on your order sheet: you cannot order them, so you must chase them.
A quick sum shows the cost of waiting. Suppose approval for the partitions starts on day 1, when you open the site. Approval takes 5 days and the lead time is 40, so they arrive around day 46. They are needed on day 15, so you are 31 working days, more than six weeks, late on every task that depends on them. The distribution board, started on day 1, arrives around day 34 against a need on day 8: 26 days late. The assistant can produce this list quickly, but it can only fill the lead-time column from your documents.
From the scope checklist below, list every item that needs ordering from a supplier. For each, give: the quote line, the day it is needed on site (from the programme CSV), and whether the supplier's lead time is: GIVEN IN WRITING (quote it and the date), NOT GIVEN, or ESTIMATED. Never fill NOT GIVEN with a typical figure. Then calculate order-by day = need day - 5 - lead time (in working days), and show the sum for each line.The realistic mistake here is the assistant "helpfully" writing "fire doors: typical lead time 2 weeks" when the supplier said five. If you let that figure through, the order-by date moves by fifteen working days and the error shows up when the doors do not. The source rule exists for exactly this. Anything the assistant labels ESTIMATED goes on a "chase the supplier" list, and the order-by sum waits for the supplier's answer.
When a promised delivery slips after you have ordered, the programme needs a fast rewrite; the tutorial on updating a programme after delays works through exactly that. To keep supplier terms and lead times together in one place, the supplier management tutorial covers tracking.
A risk register that gets read: scoring and early-warning signs
A register nobody reads is paperwork. Keep it to eight to ten risks, each with a likelihood and an impact from 1 to 5, a score (likelihood times impact), an owner, an early-warning sign and a response. Treat anything scoring 12 or more as red. Ask the assistant to brainstorm, then you score.
Using the scope checklist and the long-lead table below, draft a risk register for this job. Give 10 risks. For each: the risk in one sentence, the cause, an early-warning sign I can check weekly, and a practical response. Do NOT score them; I will do that. Base the risks on the documents, and mark any that come from general experience as "general".After you score them, the top of the register for the fit-out might look like this:
| Risk | L | I | Score | Early warning | Response |
|---|---|---|---|---|---|
| Glazed partitions arrive after the week 3 need date | 3 | 4 | 12 | No dispatch confirmation by the end of week −1 | Chase weekly; price a stock alternative |
| Client changes the comms room layout after first fix | 4 | 3 | 12 | Decision log item still open at week 2 | Freeze date in writing; price changes at once |
| Electrical isolation window refused or moved | 3 | 4 | 12 | No written confirmation by week 0 | Ask the landlord for two alternative windows |
| Broadband line not live for commissioning | 3 | 3 | 9 | No carrier installation date by week 3 | Escalate to the client; agree a temporary line |
| Fire door certificates missing at handover | 3 | 3 | 9 | No certificate in the supplier's dispatch pack | Request with the order; check on delivery |
| Client pays a stage payment late | 2 | 4 | 8 | Invoice unpaid after the agreed days | Stage payment terms in writing; stop-work wording |
| Joiner not available when the counter arrives | 2 | 3 | 6 | No confirmed date by week 5 | Book the fitting day with the order |
Review it for ten minutes at the weekly update, looking only at the early-warning column. When one fires, the response starts that day. If you want the generic version of a risk register that is not construction-specific, a simple AI risk register for small businesses has a template. For the safety side of pre-start paperwork, see writing a method statement for a small build with AI.
Keep the job in one ChatGPT or Claude project
Create one project per job so the assistant keeps the scope, programme CSV, long-lead table and quotes in view without you pasting them again. Claude's help centre says projects are available to all users, including free accounts, which can create up to five. It adds that enhanced project knowledge, which lets a project hold far more material, is limited to paid plans, and that sharing a project is for Team and Enterprise plans only. For ChatGPT, OpenAI's help pages have listed project file limits of 5 files on Free, 25 on Go and Plus, and 40 on Pro, Business and Enterprise, so check the current numbers before you plan around them.
List prices as of October 2026: ChatGPT Plus is $20 a month; Claude Pro is $20 a month or $17 a month billed annually ($200 up front); Claude Team Standard seats are $25 monthly or $20 billed annually, for 2 to 150 seats. ChatGPT Business Standard seats are $25 monthly or $20 annually with a two-seat minimum. For a firm that keeps client documents in the project, a business plan is the safer choice because business plans do not train on your content by default, whereas consumer plans have a privacy switch you must set yourself.
Paste this into the project's instructions so every answer follows the source rule:
You are the pre-start planner for [job code], a small construction project. Use only the documents in this project. Never state a lead time, price or regulation unless it is quoted in a project document, and cite the document and line. If information is missing, write a question instead. Show every date calculation as a sum in working days. Keep client names and personal data out of your replies; use the job code.Test it on your last job before trusting it on the next
The cheapest way to find the assistant's blind spots is a look-back test. Take the documents from a finished job, run the three prompts above, and compare the output with what actually went wrong. Which surprise would the scope checklist have flagged? Which late delivery would the long-lead table have caught? Which risk was missing? Score it simply: surprises caught, surprises missed and false alarms.
Then apply three-source reconciliation to the live job. Every item on the long-lead list must trace to a line in the quote or drawings. Every line in the quote must appear in the scope checklist. Every risk with a score of 12 or more must have an owner and a weekly early-warning check. Anything that fails the trace is either an invention or a gap, and either one is worth finding before day 1. If the same errors recur, tighten the project instructions rather than abandoning the tool; if the assistant keeps ignoring a rule, put that rule first.
Kick-off day: the one-page pack
Use the assistant to compress everything into one page for the kick-off meeting, and bring it to the client:
- The agreed scope in ten lines, with the open questions underneath.
- The order-by table, with the client's own actions highlighted.
- Decisions needed from the client, each with the date after which it costs time.
- The top five risks and what you will do if each fires.
- Access rules, working hours and key contacts.
- Handover requirements, so nobody is surprised by the certificate list at the end.
Ask the assistant to check the page against your checklist, one group at a time, and list anything without proof. Then read the handover list against the handover pack checklist so the paperwork you will need at the end is already on the programme. A good kick-off turns your list of questions into the client's list of deadlines, and that conversion is the point of the whole exercise.
Questions about AI and pre-start planning
Can ChatGPT tell me how long fire doors or windows take to arrive?
It can give a typical figure, but lead times vary by supplier, product, finish and season, so a typical figure is a guess. Ask the supplier for the lead time in writing, with the date they gave it, and put that on your list. If the supplier will not commit, record that as a risk and add a larger buffer.
How early should I order long-lead items?
Work back from the day the item is needed on site: subtract a buffer, the supplier's lead time and the time approvals take. Anything whose result falls before your start date needs ordering, or at least approval, before you open the site. Re-run the sum whenever the programme moves.
Does a small job need a risk register?
A light one does. Eight to ten risks, each with a score, an owner, an early-warning sign and a response, reviewed for ten minutes a week, is enough. The value is in naming the awkward items before they bite, such as client decisions, landlord access rules and deliveries from outside your contract.
Is it safe to put client drawings into ChatGPT or Claude?
Check your contract for confidentiality terms first. Business plans from OpenAI and Anthropic do not train on your content by default, while consumer plans have a privacy setting you must review. Replace client names and addresses with a job code, and keep personal data out of the prompt.
What if the assistant misses an item?
It only reads what you give it, so anything not named in the documents is invisible to it. Ask it directly what depends on parties outside the contract, then run the look-back test: feed it the documents from your last job and see whether it would have flagged what actually went wrong.
Further reads
- How Small Builders Use AI to Price Variations and Change Orders — Pricing the changes that follow a missed scope item
- AI Tools for Home Builders: Build Schedules, Delays and Sub Chasing — A weekly routine for small home builders: sub-chasing messages, a delay log with float, selections worked back from lead times, plus the tools and prices.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Claude help centre (what are projects) and Claude pricing page; OpenAI help pages for ChatGPT Projects as checked in October 2026. Lead times, prices and risk scores in the worked example are illustrative.