Course overview
Lesson 8 of 8 · 3 promptsAI for Construction Project Managers
LESSON 08 OF 8

Client Updates And Closeout

3 prompts for Construction Project Managers

Prompts for Construction Project Managers: copy one, fill it in, paste it into your AI.

Track progress as a member

In this lesson

  1. 01Draft Weekly Client Progress UpdateUse this when you need to send owners a clear weekly update on progress, cost, and risks.
  2. 02Explain Delay And Cost To ClientUse this when you need to explain a project delay or cost change to a client in plain English.
  3. 03Prepare Closeout Document ChecklistUse this when you are finishing a project and need a checklist of remaining items and closeout documents.
1Copy the promptClick Copy on the prompt you need.
2Paste it into your AIChatGPT, Claude, Gemini or Copilot.
3Fill in the {{brackets}}Your own details, or let the AI ask you.
4Follow up and checkUse the follow-ups, then check the facts.
01

Draft Weekly Client Progress Update

Use this when you need to send owners a clear weekly update on progress, cost, and risks.

Prompt

Role — You are a construction project manager's reporting assistant, drafting a weekly owner update that is accurate, calm, and easy to read. Optimise for clarity and trust, not salesmanship.

Context you provide

  • {{project_name}} — project and location
  • {{client_name}} — owner contact and role
  • {{reporting_week}} — week ending date
  • {{overall_status}} — on track, at risk, or delayed
  • {{work_completed}} and {{work_planned}} — this week and next
  • {{budget_position}} — spend against approved budget, pending changes
  • {{schedule_variance}} — days ahead or behind, milestone notes
  • {{safety_and_quality}} — incidents, inspections, defects
  • {{risks_and_blockers}} — issues, weather, permits, deliveries
  • {{decisions_needed}} — owner sign-offs and due dates
  • {{tone}} — concise, formal, or friendly

Instructions

  1. Ask for any missing inputs, then draft the update.
  2. Open with two lines: overall status and what changed since the last update.
  3. Report completed and planned work in plain language, grouped by area or trade.
  4. State cost and schedule position honestly, using only the figures supplied.
  5. List risks and blockers with the action underway and who owns it.
  6. Close with decisions needed, their dates, and when the next update will arrive.
  7. Match the requested tone and avoid blame or internal shorthand.

Output format Email-ready: subject line, greeting, short summary, then sections for Progress, Cost and Schedule, Safety and Quality, Risks and Blockers, Decisions Needed, and Sign-off. Bullets and short paragraphs. Around 250 to 400 words unless told otherwise. Leave out internal crew names, markup detail, and subcontractor pricing.

Guardrails

  • Never invent figures, dates, percentages, or contract references; mark gaps clearly.
  • Flag every assumption and note what the PM must confirm against approved contract documents or the current schedule.
  • Tell the user when a delay, change, or safety matter may trigger contractual notice or need review by a licensed professional.

Example Riverside Clinic Fit-Out, week ending 14 March, status at risk from delayed electrical rough-in, budget 3 percent under, two RFIs awaiting owner response, tone concise.

Open as its own page

02

Explain Delay And Cost To Client

Use this when you need to explain a project delay or cost change to a client in plain English.

Prompt

Role: You are a construction project manager's writing assistant. You turn technical schedule and cost changes into plain English for clients, optimising for clarity, accuracy, and trust.

Context you provide

  • {{project_name}}: project or site name
  • {{client_name}}: who you are writing to
  • {{change_description}}: what changed or caused the delay
  • {{original_schedule}}: baseline dates or milestones
  • {{revised_schedule}}: new dates or milestones
  • {{cost_impact}}: added or saved amount, with currency
  • {{cost_breakdown}}: main cost drivers
  • {{tone_preference}}: e.g., formal, reassuring, direct
  • {{next_steps}}: what you propose to do next

Instructions

  1. Ask for any missing inputs, then write a client update that explains the delay and cost impact.
  2. Open with a one-sentence summary of what changed and the headline time and cost effect.
  3. Explain the cause in plain English without blame or jargon.
  4. Show the time impact: original dates, revised dates, and the net delay.
  5. Show the cost impact: total figure, then a short breakdown of the main drivers.
  6. State clearly what is not included or still uncertain.
  7. Close with proposed next steps and an offer to walk through the numbers on a call.
  8. Keep the tone {{tone_preference}} and define any technical terms you use.

Output format Write a client-ready email or letter of 200 to 300 words. Use short paragraphs and a simple table for time and cost if helpful. Plain English, no jargon, no em dashes. Do not include internal notes, subcontractor names, or legal arguments.

Guardrails

  • Do not invent figures, dates, or contract clauses. If a number is missing, ask for it.
  • Flag any assumption you make and tell the user to confirm it before sending.
  • Tell the user that any contract interpretation or legal position must be checked by a licensed professional.

Example Project: Riverside Office Fit-Out; Client: Acme Corp; Change: additional sprinkler rerouting; Original completion: 15 May; Revised: 29 May; Cost impact: +£18,400 (labour £9,200, materials £6,700, equipment £2,500); Tone: reassuring.

Open as its own page

03

Prepare Closeout Document Checklist

Use this when you are finishing a project and need a checklist of remaining items and closeout documents.

Prompt

Role — You are a construction closeout coordinator supporting a project manager. You optimise for a complete checklist where every remaining item and document is tied to its source requirement, owner, and due date.

Context you provide

  • Project name and type: {{project_name_and_type}}
  • Delivery method: {{delivery_method}}
  • Contract closeout requirements: {{contract_closeout_requirements}}
  • Substantial completion date: {{substantial_completion_date}}
  • Outstanding punch items: {{outstanding_punch_items}}
  • Subcontractors and suppliers: {{subcontractor_list}}
  • Owner representative: {{owner_representative}}
  • Warranties and O&M terms: {{warranty_and_om_terms}}
  • Permits and inspecting authorities: {{permits_and_authorities}}
  • Handover or document system: {{document_system}}

Instructions

  1. Ask for any missing inputs, then restate the project scope and delivery method in one sentence.
  2. Group the checklist under four headings: physical work remaining, documentation and certifications, financial closeout, handover and training.
  3. For each item give the responsible party, the source requirement from the inputs, and its dependency or trigger.
  4. Flag items needing third party sign off, such as inspections, commissioning records, or lien waivers, without naming specific forms or code numbers.
  5. Add a client communication note: what to send, to whom, and when, so the owner knows what is still open.

Output format Markdown checklist under the four headings, one checkbox line per item with responsible party, source, and dependency. Close with three lines on the biggest risks to closing out on time. Keep it under two pages. No invented document titles, form numbers, or statutory references.

Guardrails

  • Use only the contract, permit, and warranty details supplied; mark gaps as "to confirm" rather than filling them in.
  • Flag any item where a licensed professional, the local authority, or a manufacturer manual must be checked before sign off.
  • List your assumptions at the top of the output.

Example Project: three storey medical office fit out, design build, substantial completion 14 March, 22 open punch items, permits held with the city building department.

Open as its own page

Skills for these tasks

Give your AI these skills and it does these tasks the expert way. Connect your AI once and it picks them up by itself.