Practical Task
Build a contractor status checkpoint or closeout punch list
Work hasn't started or the status is unclear? Build a factual status packet and next request. Near signoff, use the same records for a neutral punch list.
What this helps you do
Homeowners who have paid a deposit but still need clarity on the start, permits, or schedule, or who are ready to check open items before closeout.
What you need
- The accepted estimate, contract, or written scope
- Any approved changes, invoices, and payment confirmations you have
- Available permit records, applications, and schedule messages
- Dated photos or observations and relevant messages, with the sender and date
- A note of missing records or conflicting accounts; you can start with incomplete records
Do it step by step
- 1
Choose the job: a status packet if work has not started or the status is unclear; a punch list if you are approaching signoff. You can use the checkpoint Task without comparing estimates first.
- 2
Label the supplied records and build a short timeline. For each important entry, cite the document, clause, message sender, or photo and its date; mark absent dates and records as unknown. Record payments as shown, without guessing what they funded.
- 3
Separate agreement terms and written changes, dated promises or explanations, and observable site conditions. Keep unanswered questions and contradictory or disputed accounts visible, with each account attributed. A missing permit copy does not prove there is no permit; a promise does not prove work happened.
- 4
For a pre-start or unclear-status packet, list the questions the records leave open: deposit accounting, permit/application status, start conditions, the next confirmed work date, and who owns each unresolved site or design question. Ask for documentation or confirmation; do not invent an owner, date, delay cause, or missing work.
- 5
For closeout, create a neutral punch list with the promised scope, observed condition, supporting source/date, question or requested follow-up, and evidence that would close each item. Mark items needing qualified inspection or expert judgment instead of diagnosing from photos.
- 6
Check the packet against the originals. Keep payment, warranty, legal, code, and safety judgments with qualified professionals; AI should not decide breach, payment entitlement, or whether to pay or withhold funds.
- 7
Draft one concise status request or closeout message using the checked packet. Ask for specific missing records or answers, and use a response date you choose. Review before sending; keep unknowns and disputed points explicit.
Use this in your AI assistant
Starter instructions
Copy the starter below, then paste it into ChatGPT, Copilot, Gemini, Claude, or whichever capable AI assistant you use. If this Task calls for photos or files, attach them in that AI assistant too — not on this page.
Help me create a neutral contractor project checkpoint. If I have not said whether work has yet to start, the status is unclear, or I am approaching signoff, ask which output I need: a status packet or closeout punch list. Use only the agreement, written changes, invoices/payment records, messages, permit records, and dated photos/observations I supply. For important claims and timeline entries, identify the supporting source, date (or unknown), and who said or observed it. Separate agreement terms, recorded payments, attributed promises/explanations, observable conditions, missing records/unknown status, and contradictory or disputed accounts. Preserve both accounts with sources; do not resolve conflicts by guessing. Do not infer that work or a permit does not exist merely because its record is missing, or that a promised date means work occurred. For pre-start/unclear status, make a one-page packet and focused questions about deposit accounting, permit status, start conditions, schedule, and unresolved responsibilities, only where the records leave questions open. For closeout, make punch-list rows with scope source, observation, question/request, closure evidence, and any qualified inspection needed. Do not diagnose construction defects, code violations, warranty coverage, legal breach, or payment rights from photos or incomplete documents. Do not recommend paying, withholding, or recovering funds, invent delay causes, or assign unsupplied dates or owners. Flag legal, permit, technical, and safety questions for the appropriate qualified person or authority. End with one calm factual request I can check against the originals and edit; ask me for a response date rather than inventing one. Materials and project stage: [PASTE/ATTACH].
Helpful checkWhat a good result looks like
A short, source-backed status packet and next request, or a closeout punch list, with dates, attribution, unknowns, and conflicting accounts visible and consequential judgments handed to qualified people.
Tips and watch-outs
- Keep 'not mentioned,' 'not completed,' and 'completed incorrectly' separate; they require different evidence.
- Keep a contractor's statement about permits, spending, or a future date attributed until the relevant record or authority confirms it. Missing paperwork is an open question, not proof of breach.
- For structural, electrical, roofing, plumbing, code, safety, or other technical judgments, use a qualified professional rather than asking AI to decide from photos.
- Preserve original photos, documents, and messages outside the AI conversation if they may matter later.
OptionalGo deeper when you want to
When work has not started, use a status packet before a punch list
A deposit, moving start date, or unclear permit status is enough to make the records worth organizing. It does not establish why the project is delayed, whether an agreement was breached, or who is entitled to a payment. You do not need completed work to use this checkpoint.
Make a short packet from the supplied agreement, payment records, permit documents, messages, and dated observations. Give each timeline entry a source, date, and speaker or observer. Keep agreement terms, recorded payments, promises, observations, unknowns, and conflicting accounts separate; preserve both sides of a disputed point without choosing a winner.
- Missing record: a permit copy has not been supplied. Current permit status: unknown until the relevant record or authority confirms it.
- Attributed promise: a message gives a future start date. Actual start: only report what dated records or observations establish.
- Recorded payment: the confirmation shows an amount and date. What it funded: unknown unless the supplied accounting documents it.
- Contradictory accounts: keep each source and date, then ask for the record or clarification that could resolve the difference.
Pre-start request pattern, not a claim about your project
Based on the attached status packet, please clarify the items still marked unknown: the deposit accounting, current permit/application status, remaining start conditions, next work date, and the person responsible for each unresolved site question. Please provide the supporting records and correct any disputed entries. Add only the questions your records leave open, and choose the response date yourself.
Keep four evidence states separate all the way through closeout
A useful project checkpoint should never collapse the signed scope, a homeowner observation, a contractor explanation, and a technical conclusion into one sentence. Those are different kinds of evidence with different authority.
For every open item, identify which state you actually have before drafting the punch list.
- Promised scope: supported by the accepted agreement or written change.
- Observable condition: what can be described without diagnosing the cause.
- Attributed explanation: what the contractor or another party said.
- Qualified judgment needed: code, defect, structural, safety, warranty, or other technical conclusion the packet cannot establish.
Evidence-safe punch-list row
Scope source: roof replacement. Observation: several shingles appear visibly marked/dented in the attached photos. Contractor statement: the marks should blend in. Request: please confirm how this item will be evaluated or corrected before closeout. Qualified inspection: needed if the question is whether the condition is defective or technically acceptable.
Do not let AI invent leverage because the project feels high-stakes
Payment rights, warranty coverage, code compliance, breach, and the right to reject work can depend on the contract, local law, licensing rules, and qualified technical findings. A photo plus a worried homeowner is not enough for the assistant to decide those issues.
Use AI to organize the evidence and questions. Preserve the original documents and photos. Confirm permit status with the local authority, and leave legal rights, payment decisions, and technical or safety judgments to the appropriate qualified professional. The assistant should not tell you to pay or withhold funds, infer how a deposit was spent, or decide fault from an incomplete packet.
Close each punch-list item with evidence, not vibes
A punch list becomes easier to manage when every item has a clear closure condition: corrected work, a written explanation accepted by the homeowner, a missing document supplied, or a qualified inspection resolving the technical question.
That structure can later become a lightweight project-control record instead of a long text-message thread nobody can reliably reconstruct.
Part of a larger Workflow
See where this Task fits
Use this Task on its own, or return to the full Workflow for the other pieces and their order.