AI Prompts for Construction: Bid Estimates, Safety Plans, and Project Management
Construction runs on documents. Bids, RFIs, safety plans, daily reports, change orders, punch lists, submittals. Every project generates thousands of pages, and most of it follows a predictable structure.
That's exactly where AI helps. Not replacing the judgment calls — those still need 20 years of field experience and a gut feeling about soil conditions. But drafting the first version of a safety plan, structuring a bid narrative, or formatting a progress report? AI can do in 5 minutes what used to take an hour.
These prompts are built for construction professionals: general contractors, subcontractors, project managers, estimators, and safety officers. Each one is tested, structured, and ready to paste. Fill in the brackets with your project specifics.
Want a prompt tailored to your exact trade or project type? The AI prompt generator can build one from a plain English description.
Bid Writing Prompts
1. Bid Proposal Narrative
You are an experienced construction estimator who writes
winning bid proposals. Write in a professional, confident tone
— not salesy.
Draft a bid proposal narrative for the following project:
PROJECT: [PROJECT NAME AND TYPE — e.g., 3-story mixed-use
building, highway overpass rehabilitation]
OWNER: [CLIENT NAME]
LOCATION: [CITY, STATE]
ESTIMATED VALUE: [DOLLAR RANGE]
BID DUE DATE: [DATE]
OUR COMPANY: [COMPANY NAME]
YEARS IN BUSINESS: [NUMBER]
RELEVANT EXPERIENCE: [2-3 SIMILAR COMPLETED PROJECTS]
KEY PERSONNEL: [PM, SUPERINTENDENT, SAFETY OFFICER NAMES]
LICENSES: [RELEVANT LICENSES AND CERTIFICATIONS]
Include these sections:
- Executive summary (why we're the right contractor)
- Company qualifications and relevant experience
- Project approach and methodology
- Proposed schedule overview
- Safety record and approach
- Key personnel qualifications
- Value engineering suggestions (if applicable)
- References
Keep the total under 5 pages. Be specific about approach —
generic "we prioritize quality and safety" statements without
detail don't win bids.
2. Bid Clarification Response
Draft a response to this bid clarification request:
PROJECT: [PROJECT NAME]
QUESTION FROM OWNER/ARCHITECT: [THE RFI OR CLARIFICATION
QUESTION]
OUR UNDERSTANDING: [WHAT WE THINK THEY'RE ASKING]
OUR POSITION: [OUR ANSWER — INCLUDE COST/SCHEDULE IMPACT
IF ANY]
Response should be:
- Professional and concise
- Reference specific spec sections or drawing numbers if
applicable
- State any assumptions clearly
- Note cost or schedule implications if the clarification
changes scope
- Under 1 page
3. Cost Estimate Summary
Create a formatted cost estimate summary for presentation
to [OWNER / INTERNAL REVIEW].
PROJECT: [NAME]
SCOPE: [BRIEF DESCRIPTION]
Include these CSI divisions with line items:
[LIST THE RELEVANT DIVISIONS — e.g., Division 03 Concrete,
Division 05 Metals, Division 07 Thermal/Moisture Protection]
For each division, create a summary table with:
- Line item description
- Quantity and unit
- Material cost
- Labor cost
- Equipment cost
- Subtotal
At the bottom include:
- Direct cost subtotal
- General conditions ([PERCENTAGE]%)
- Overhead ([PERCENTAGE]%)
- Profit ([PERCENTAGE]%)
- Bond (if required)
- Contingency ([PERCENTAGE]%)
- Total bid amount
NOTE: I'll fill in the actual numbers. I need the formatted
structure with proper categories and industry-standard line
items for a [PROJECT TYPE] project.
Safety Plan Prompts
4. Site-Specific Safety Plan
You are a construction safety professional with CSP
certification. Draft a site-specific safety plan.
PROJECT: [NAME AND TYPE]
LOCATION: [ADDRESS]
DURATION: [ESTIMATED TIMELINE]
PEAK WORKFORCE: [NUMBER OF WORKERS]
MAJOR TRADES ON SITE: [LIST — e.g., concrete, steel erection,
electrical, plumbing, HVAC]
KNOWN HAZARDS: [LIST — e.g., adjacent traffic, overhead power
lines, contaminated soil, confined spaces]
OWNER REQUIREMENTS: [ANY SPECIFIC SAFETY REQUIREMENTS FROM
THE CONTRACT]
Include these sections:
1. Project overview and scope
2. Safety responsibilities (GC, subs, workers)
3. Site-specific hazard analysis
4. Personal protective equipment requirements
5. Fall protection plan (if working above 6 feet)
6. Electrical safety procedures
7. Excavation and trenching safety (if applicable)
8. Crane and rigging operations (if applicable)
9. Hot work procedures
10. Emergency action plan (medical, fire, weather)
11. Training requirements and documentation
12. Incident reporting procedures
13. Weekly safety meeting schedule and topics
14. Subcontractor safety requirements
15. Drug and alcohol policy
Reference OSHA standards (29 CFR 1926) where applicable.
This needs to pass a third-party safety audit.
5. Job Hazard Analysis (JHA)
Create a Job Hazard Analysis for [SPECIFIC TASK — e.g.,
installing roof trusses, excavating a foundation, pouring
elevated concrete deck].
LOCATION: [WHERE ON THE SITE]
TRADE: [WHICH TRADE IS DOING THE WORK]
EQUIPMENT INVOLVED: [LIST EQUIPMENT]
WORKERS INVOLVED: [NUMBER AND ROLES]
ENVIRONMENTAL CONDITIONS: [WEATHER, ADJACENT WORK, TRAFFIC]
Format as a table with these columns:
1. Job Step (sequential)
2. Potential Hazards (specific to this step)
3. Hazard Controls (elimination → substitution → engineering
→ administrative → PPE)
After the table, include:
- Required PPE for this task
- Emergency contacts
- Nearest first aid station and hospital
- Competent person on site
- Sign-off lines for supervisor and each worker
Be specific to the actual task. "Be careful" is not a hazard
control.
6. Toolbox Talk Script
Write a 10-minute toolbox talk on [TOPIC — e.g., fall
protection, heat illness prevention, trenching safety,
electrical lockout/tagout, silica dust exposure].
AUDIENCE: [TRADE WORKERS — e.g., ironworkers, laborers,
electricians]
READING LEVEL: Keep it conversational and clear — many workers
on site have English as a second language
SEASON: [CURRENT SEASON — relevant for weather-related topics]
RECENT INCIDENT: [OPTIONAL — any recent near-miss or incident
that prompted this talk]
Include:
1. Opening hook (real incident or scenario — not a lecture)
2. Three key safety points with specific examples
3. Correct procedure step-by-step
4. Common shortcuts people take and why they're dangerous
5. Two discussion questions for the crew
6. Sign-in sheet section
This needs to be something a superintendent can read aloud to
a crew in the field. No jargon that sounds like it came from
a safety manual. Make it real.
RFI and Submittal Prompts
7. Request for Information (RFI)
Draft an RFI for the following issue:
PROJECT: [NAME AND NUMBER]
RFI NUMBER: [YOUR RFI NUMBER]
TO: [ARCHITECT / ENGINEER NAME AND FIRM]
FROM: [YOUR COMPANY AND PM NAME]
SPEC SECTION: [REFERENCE]
DRAWING REFERENCE: [SHEET NUMBER AND DETAIL]
ISSUE: [DESCRIBE THE CONFLICT, AMBIGUITY, OR MISSING
INFORMATION]
OUR UNDERSTANDING: [WHAT WE THINK THE INTENT IS]
PROPOSED SOLUTION: [IF YOU HAVE ONE]
SCHEDULE IMPACT: [WILL THIS AFFECT THE SCHEDULE IF NOT
RESOLVED BY (DATE)?]
COST IMPACT: [POTENTIAL COST IMPACT — YES/NO/TBD]
Format as a standard RFI with:
- Clear, specific question
- Reference to relevant documents
- Proposed resolution if applicable
- Required response date
- Impact statement
Keep it factual and precise. RFIs that ramble get pushed to
the bottom of the pile.
8. Submittal Cover Letter
Write a submittal transmittal/cover letter for:
PROJECT: [NAME]
SUBMITTAL NUMBER: [NUMBER]
SPEC SECTION: [SECTION AND TITLE]
DESCRIPTION: [WHAT IS BEING SUBMITTED — e.g., concrete mix
design, structural steel shop drawings, HVAC equipment data]
SUBMITTED BY: [SUBCONTRACTOR AND CONTACT]
SUBMITTED TO: [GC / ARCHITECT / ENGINEER]
Include:
- Transmittal header with project info
- Description of materials/documents included
- Specification compliance statement
- Any deviations from spec (LIST THEM CLEARLY)
- Number of copies and format (digital/physical)
- Requested review timeline
- Distribution list
If there are deviations, explain each one with the rationale.
"Or equal" substitutions should include a comparison chart.
Project Management Prompts
9. Weekly Progress Report
Draft a weekly progress report for [STAKEHOLDER — owner,
lender, internal management].
PROJECT: [NAME]
REPORT PERIOD: [DATE RANGE]
OVERALL COMPLETION: [PERCENTAGE]
SCHEDULE STATUS: [ON TIME / X DAYS AHEAD / X DAYS BEHIND]
WORK COMPLETED THIS WEEK:
[LIST MAJOR ACTIVITIES AND QUANTITIES — e.g., "Poured
Building A 2nd floor slab — 12,000 SF," "Set steel for
stairwells 1 and 2"]
WORK PLANNED NEXT WEEK:
[LIST PLANNED ACTIVITIES]
ISSUES AND CONCERNS:
[LIST ANY PROBLEMS — weather delays, material shortages,
design conflicts, inspection issues]
CHANGE ORDERS:
[NEW OR PENDING CHANGE ORDERS — number, description, status]
SAFETY:
[INCIDENTS / NEAR-MISSES THIS WEEK, OR "NO INCIDENTS"]
[INSPECTIONS COMPLETED]
Format professionally with headers. Include a schedule
comparison showing planned vs. actual completion percentages
for major milestones. Keep it to 2 pages maximum.
10. Change Order Proposal
Draft a change order proposal.
PROJECT: [NAME]
CHANGE ORDER NUMBER: [NUMBER]
REQUESTED BY: [OWNER / ARCHITECT / FIELD CONDITION]
DATE: [DATE]
DESCRIPTION OF CHANGE:
[DETAILED DESCRIPTION OF WHAT CHANGED AND WHY]
CAUSE: [Owner-directed / Design error / Unforeseen condition /
Value engineering / Regulatory requirement]
IMPACT:
- Cost impact: $[AMOUNT] — [breakdown: labor, material,
equipment, overhead, profit, bond]
- Schedule impact: [DAYS ADDED / NO IMPACT]
- Affected spec sections: [LIST]
- Affected drawings: [LIST]
SUPPORTING DOCUMENTATION:
[LIST — e.g., revised drawings, site photos, subcontractor
quotes, material quotes]
Format as a formal change order with signature blocks for
contractor, architect, and owner. Include a clear statement
that work should not proceed on this item until the change
order is approved and signed.
11. Punch List Generator
I'm doing a [PHASE — pre-drywall / substantial completion /
final] walkthrough on [AREA OF PROJECT].
Generate a comprehensive punch list inspection checklist for
[TRADE / AREA — e.g., interior finishes, MEP rough-in,
exterior envelope, sitework].
Format as a numbered checklist with:
- Item description
- Location field (room/area)
- Responsible sub
- Priority (life safety / functional / cosmetic)
- Status (open / in progress / complete)
Organize by system/trade. Include commonly missed items for
this phase. I'll use this as a template and delete items
that don't apply to this project.
Scheduling Prompts
12. Look-Ahead Schedule Narrative
Write a 3-week look-ahead schedule narrative for the
project team meeting.
PROJECT: [NAME]
CURRENT PHASE: [PHASE — e.g., foundations, structural frame,
MEP rough-in, finishes]
WEEK 1 ACTIVITIES:
[LIST WITH RESPONSIBLE SUBS]
WEEK 2 ACTIVITIES:
[LIST WITH RESPONSIBLE SUBS]
WEEK 3 ACTIVITIES:
[LIST WITH RESPONSIBLE SUBS]
CRITICAL PATH ITEMS: [WHAT CAN'T SLIP]
LONG-LEAD ITEMS: [MATERIALS WITH DELIVERY CONCERNS]
REQUIRED INSPECTIONS: [LIST WITH DATES]
COORDINATION ISSUES: [TRADE CONFLICTS OR SEQUENCING CONCERNS]
Format for reading aloud in a 15-minute meeting. Start with
what matters most. Flag items that need decisions this week.
End with action items and responsible parties.
13. Delay Claim Documentation
Help me document a delay claim for [TYPE — weather, owner-
caused, design change, unforeseen condition].
PROJECT: [NAME]
CONTRACT COMPLETION DATE: [DATE]
CURRENT PROJECTED COMPLETION: [DATE]
DELAY PERIOD: [START DATE TO END DATE]
DAYS CLAIMED: [NUMBER]
CAUSE OF DELAY: [DETAILED DESCRIPTION]
NOTICE GIVEN: [DATE OF WRITTEN NOTICE TO OWNER]
CONTRACT CLAUSE: [REFERENCE THE DELAY CLAUSE IN YOUR CONTRACT]
IMPACT:
- Critical path activities affected: [LIST]
- Trades impacted: [LIST]
- Additional costs incurred: [DESCRIPTION]
- Mitigation efforts taken: [WHAT YOU DID TO MINIMIZE IMPACT]
SUPPORTING DOCUMENTATION:
- Daily reports from [DATE RANGE]
- Weather data (if weather claim)
- Correspondence showing [ISSUE]
- Photos dated [DATES]
- Schedule comparison (baseline vs. current)
Write this as a formal delay claim letter. It needs to be
factual, reference the contract provisions, and clearly
establish the causal link between the delay event and the
schedule impact. This may end up in front of a mediator,
so keep it professional and evidence-based.
Contract Review Prompts
14. Contract Clause Analysis
Review the following contract clause and explain it in plain
English. Then flag any risks for me as the [GENERAL CONTRACTOR
/ SUBCONTRACTOR].
CLAUSE:
[PASTE THE CONTRACT LANGUAGE]
CONTRACT TYPE: [AIA A101, ConsensusDocs, custom, etc.]
MY ROLE: [GC / SUB / OWNER'S REP]
Tell me:
1. What this clause means in plain language
2. What obligations it creates for me
3. What risks it exposes me to
4. Whether this is standard or unusual for this contract type
5. Suggested modifications to reduce my risk (with specific
language)
6. Red flags I should discuss with my attorney
NOTE: This is for initial review and education. I will have
my attorney review the actual contract before signing.
15. Subcontract Scope of Work
Draft a scope of work for a subcontract agreement.
PROJECT: [NAME]
TRADE: [TRADE — e.g., electrical, plumbing, HVAC, drywall,
painting, concrete]
SUBCONTRACTOR: [NAME]
CONTRACT VALUE: [AMOUNT]
INCLUDED IN SCOPE:
[LIST ALL WORK ITEMS THIS SUB IS RESPONSIBLE FOR]
EXCLUDED FROM SCOPE:
[LIST ITEMS EXPLICITLY NOT IN THIS SUB'S SCOPE]
FURNISHED BY OTHERS:
[MATERIALS OR SERVICES PROVIDED BY GC OR OTHER SUBS]
Include:
- Specific drawing and spec references
- Quality standards and testing requirements
- Cleanup and waste removal responsibilities
- Protection of installed work
- Coordination requirements with other trades
- Warranty obligations
- Insurance requirements
- Payment terms and retainage
- Change order procedure
- Schedule obligations and liquidated damages (if applicable)
Be precise about scope boundaries. The gaps between subs'
scopes are where the problems live.
Tips for Using AI in Construction
AI drafts — you verify. Every prompt output needs review by someone who knows the project. AI doesn't know your soil conditions, your local codes, or the subcontractor who always shows up late.
Always check code references. AI may cite OSHA standards or building codes that have been updated. Verify every regulation reference against current published standards.
Keep proprietary data general. Don't paste actual project costs, client financials, or confidential bid numbers into AI tools. Use ranges or dummy numbers, then fill in the real figures in your final document.
Build a library. Once you customize a prompt for your company's style and typical project types, save it. Build your own collection for your team. If you need help building customized versions, the prompt generator can adapt any of these to your specific trade and project type.
These are starting points, not final drafts. The output gets you 70-80% there. The last 20% — the part that reflects your company's experience, your project's specifics, and your professional judgment — is still yours.
For more AI prompts for business operations, see our guides on AI prompts for business and AI prompts for project managers.