Prompt
You are writing reusable message templates for {{company_name}}, a {{trade_focus}} general contractor. These load into project-management software with merge fields — use [SUB_NAME], [PROJECT_ADDRESS], [DATE], [SCOPE_ITEM], [CLIENT_NAME], and [PM_NAME] as placeholders. Do not invent any other merge fields or any facts about the company.

Write this set:
1. Subcontractor bid invitation — scope summary, insurance and license expectations, and bid-due date.
2. Certificate-of-insurance and license request — what to send and by when.
3. Day-before schedule confirmation (short text version) — arrival window and what to bring.
4. Weekly client progress update — what got done, what's next, any decisions needed from the client.
5. Post-job review request for {{review_platform}}.

Rules:
- Plain contractor voice, no marketing fluff. Each email under 120 words; texts under 40 words.
- Do not include any language that guarantees a completion date, waives a lien right, or states warranty terms — those are contract matters, not template copy.
- Leave a [PM NOTE] where I should add a project-specific detail rather than inventing one.

Fill in your details and the prompt updates live — then copy.

What you get back (excerpt)

SUBCONTRACTOR BID INVITATION Subject: Bid request — [SCOPE_ITEM] at [PROJECT_ADDRESS] Hi [SUB_NAME] — Ridgeline Builders is bidding [SCOPE_ITEM] at [PROJECT_ADDRESS] and would like a number from you. Scope summary and drawings attached [PM NOTE: attach scope]. To bid, we'll need current proof of insurance and your active license on file. Please send your bid by [DATE]. Questions, call me directly. — [PM_NAME] DAY-BEFORE CONFIRMATION (text) Hi [SUB_NAME], confirming [DATE] at [PROJECT_ADDRESS], arrival 7-8am. Bring [PM NOTE: materials/equipment]. Reply to confirm. — [PM_NAME]

The full workflow

  1. Run the prompt once and edit each template into your own voice.
  2. Load the templates into your PM or scheduling software's merge fields.
  3. Set triggers for schedule confirmations, progress updates, and review requests.
  4. Reread quarterly and update anything that has changed.

Watch out for

Build with merge fields — never paste real subcontractor or client names, addresses, insurance certificates, or financial details into consumer AI tools.

Don't let a template promise a firm completion date or state warranty or lien language the AI invented — those are contract terms; keep them consistent with your signed contract and have the wording reviewed.

A template that requests a COI or license does not verify one — confirm every sub actually carries current coverage and a valid license before they set foot on your site.

Where this comes from

Every use case on this site is grounded in real reports from working general contractors — not invented by us.

More AI use cases for general contractors

← All 6 use cases: How General Contractors Use AI