Create a copy-paste prompt pack for a [CONSTRUCTION ROLE] working on [PROJECT TYPE]. Project delivery and contract context: [DELIVERY AND CONTRACT CONTEXT] Common documents or tasks: [COMMON TASKS] Project controls and safety requirements: [PROJECT REQUIREMENTS] Audience and communication style: [AUDIENCE AND STYLE]
Known current project issues: [CURRENT ISSUES]
Produce 8 distinct prompts, each 110 to 170 words, for the most common work in this setting. Include prompts for a daily field report, an RFI draft, a two-week lookahead, a subcontractor coordination message, and a task-specific pre-task planning or toolbox-talk draft. Choose the other three based on my common tasks; useful options include meeting minutes, submittal review questions, change-event fact summary, punch-list grouping, or schedule-risk review.
Every prompt must use its own bracketed inputs, specify a precise output format, and tell the AI to ask up to 3 clarifying questions only if a required fact is absent. Require the model to preserve source facts, identify assumptions, and separate observations from contract interpretations. It must never approve work, certify payment, issue a directive, interpret legal entitlement, replace a competent person’s safety judgment, or invent dimensions, dates, drawings, specifications, costs, inspection results, or commitments.
Add a one-line "Use for" label above each prompt and a short "Verify before sending" line below it. The verification checks must cover drawing/specification references, trade responsibility, dates, location, safety hazards, schedule impacts, document-control rules, and required approval routing. Before answering, confirm that every prompt keeps formal notices, changes, and safety decisions with the authorized project personnel.Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [CONSTRUCTION ROLE] | State your role, such as superintendent, project engineer, project manager, or estimator. | General contractor project engineer |
| [PROJECT TYPE] | Describe the type of project and its main trades or systems. | Four-story outpatient clinic renovation with occupied spaces below and mechanical, electrical, drywall, and flooring trades. |
| [DELIVERY AND CONTRACT CONTEXT] | State delivery method, parties, contract document hierarchy, and notice or RFI process. | CM-at-risk; owner, architect, and GC use Procore; RFIs require drawing reference, proposed resolution, and architect response; contract notices are handled by the project manager. |
| [COMMON TASKS] | List the recurring field and project-management documents you need to prepare. | Daily reports, RFIs, two-week lookaheads, subcontractor emails, OAC minutes, submittal logs, and punch-list tracking. |
| [PROJECT REQUIREMENTS] | List safety program, schedule, quality, reporting, and document-control requirements. | Daily safety huddle, OSHA-compliant site rules, Primavera schedule updates weekly, photo documentation, and Procore document control. |
| [AUDIENCE AND STYLE] | Describe recipients and the required communication style or template conventions. | Direct, factual writing for foremen, design team, owner representatives, and internal PMs; use numbered action items. |
| [CURRENT ISSUES] | List active coordination, access, material, design, or schedule issues relevant to the project. | Duct route conflicts with a beam at Grid C-4; flooring delivery may miss the October 18 install window; nighttime access needs hospital approval. |
How to use
- Fill the project context with actual contract procedures and document-control rules before generating the pack.
- Use each generated prompt with current drawings, specifications, logs, and field observations attached or pasted as facts.
- Verify the document references, trade ownership, dates, and routing before putting a draft into the project system.
- Follow up with: "Adapt the RFI prompt to our company template and require a proposed resolution only when field conditions support one."
Variations
RFI draft
Use this to turn a documented design conflict into an RFI draft for authorized review.
Draft an RFI for [ISSUE] at [LOCATION]. Relevant drawing and specification references: [REFERENCES] Field condition and evidence: [FIELD FACTS] Potential impact: [IMPACT] Required RFI template fields: [TEMPLATE] Return a factual subject line, question, existing document requirements, observed condition, attached-evidence list, requested response date if supplied, and neutral potential impact. Separate facts from any proposed resolution. Do not invent dimensions, conflicts, costs, schedule days, or contract entitlement. Do not direct work to proceed. Before answering, check that every reference is supplied and that the question is answerable by the design team. Ask up to 3 clarifying questions only if a required field is missing.
Daily field report
Use this at the end of a shift to organize field facts into a consistent report.
Create a daily construction field report from these notes: [FIELD NOTES]. Project and date: [PROJECT AND DATE] Required report fields: [REQUIRED FIELDS] Weather and workforce information: [SITE DATA] Return labeled sections for work performed by trade and location, manpower, deliveries, equipment, inspections, visitors, safety observations, delays or disruptions, photos to attach, and next-day planned work. Preserve exact facts and mark missing fields as "not reported." Separate observed delays from causation or responsibility. Do not invent weather, headcount, inspection results, incidents, or progress percentages. Ask up to 3 questions only if a required report field cannot be inferred from the notes.
Two-week lookahead
Use this for coordination planning before the weekly subcontractor meeting.
Build a two-week construction lookahead for [WORK WINDOW]. Current schedule activities: [SCHEDULE DATA] Trade commitments and constraints: [TRADE INPUTS] Access, inspections, and material status: [CONSTRAINTS] Return a table by date or workday with activity, location, responsible trade, predecessor, required material or approval, access/safety constraint, and decision needed. Then list the five highest schedule risks with owner and due date. Do not convert this into a contractual schedule update or invent durations, crew sizes, approvals, or commitments. Flag conflicts that require superintendent, PM, owner, or design-team confirmation. Ask up to 3 clarifying questions only if dates, activities, or trade inputs are missing.
Tips
- An RFI should ask one answerable design question and cite the controlling documents; an open-ended complaint creates delay without a usable response.
- Keep daily reports factual and contemporaneous, separating what was observed from why it happened or who may be responsible.
- A lookahead is a coordination tool, not a replacement for the contractual schedule; show prerequisites, access, inspections, and materials explicitly.
- Never let a draft message become a field directive unless it has gone through your project’s authorized approval and document-control path.
FAQ
Can AI prepare an RFI or change-event notice?
It can prepare a factual draft from your records. The authorized project personnel must verify contract requirements, entitlement, routing, and deadlines.
Can AI write a toolbox talk?
It can draft a topic-specific discussion aid, but the competent person and field leadership must assess the actual site hazards and controls.
What should I avoid putting in a construction prompt?
Avoid confidential bids, personal information, unapproved claims, and facts you cannot verify. Use the current controlled drawings and specifications, not remembered details.