Handling RFIs and Submittals with AI
Construction administration is the phase where a well-designed project can still go wrong. An unanswered RFI creates a change order. A missed submittal lets the wrong product get installed. Every day the CA team spends on administrative work is a day not spent in the field catching real issues. AI is well suited to both tasks — RFIs and submittals are structured, repetitive, and language-heavy, which is exactly what language models are good at.
What You'll Learn
- How to draft professional RFI responses that protect the design intent and avoid scope creep
- A workflow for reviewing shop drawings and product data submittals
- How to use AI to maintain the submittal log and track closure
- Common CA pitfalls where AI makes things worse
The RFI Response Prompt
A good RFI response does three things: answers the question, protects the contract, and keeps the project moving. AI is excellent at getting the tone right. Template:
Act as a senior architect in construction administration. Draft a professional response to this RFI. Keep the tone firm but collaborative. Reference the specific drawing sheet, detail, or spec section that answers the question. If the RFI asks for information not in the contract, offer two paths: (a) direct the contractor to existing information if it exists, (b) state that the request falls outside the current scope and requires a COR. Do not commit the owner to extra work.
RFI number: {RFI-0142} RFI subject: {Finished floor elevation at vestibule} RFI text: {paste the full RFI text} Relevant documents: {A-101 grids B-3/4, A-501 detail 5, spec 09 65 13, spec 03 30 00}
The output is a polished draft. You verify the cited sheet/detail/spec actually addresses the issue, adjust the tone for the specific contractor, and send.
RFI Patterns and When to Push Back
Typical RFI archetypes where AI helps most:
The "clarification" RFI: Usually answerable by pointing to an existing document.
Direct the contractor to {sheet/detail/spec} which shows {specific information}. No additional drawings or CORs required.
The "scope expansion" RFI: Asking for extra work disguised as a question.
The information requested is not in the contract because {reason}. If the owner elects to include this, it will require a Change Order Request. Please proceed with the base scope as drawn until directed otherwise.
The "error in the drawings" RFI: The contractor is right; the drawings are inconsistent.
Acknowledge the inconsistency. Issue Supplemental Instruction SI-{#} clarifying that {resolved direction}. This is a clarification to the contract, not a change in scope.
The "value engineering" RFI: Contractor proposing a substitution.
Evaluate the substitution against the specification's "or approved equal" language. If the substitution meets the performance criteria, accept with conditions; if not, reject with specific reason. Do not approve without technical review.
Having AI produce all four archetypes as templates saves enormous time across a construction project.
The RFI Log
AI can maintain the RFI log automatically if you feed it each RFI as it comes in.
Update the RFI log. Add a new entry: RFI-0143, Subject: {X}, Received: {date}, Discipline: {arch}, Status: Open, Sheet Reference: {A-301}, Response Due: {date + 10 business days}. Then scan all open RFIs and flag any that are overdue.
Paste the log each week and ask for overdue flags and pattern analysis.
Submittal Review Workflow
Submittals are where product installations get locked in. Three types need different AI approaches:
Product Data Submittals
Act as the submittal reviewer. Here is the product data submittal for {submittal number — Section 09 65 13 Resilient Base}. The spec requires: {paste relevant spec paragraphs}. Check: (1) manufacturer listed is an approved manufacturer, (2) product meets the performance criteria (thickness, material, wear layer, flame spread), (3) colors correspond to the finish schedule, (4) installation instructions align with the spec. Recommend: Approved, Approved as Noted, Revise and Resubmit, or Rejected. Provide specific mark-up notes.
Shop Drawings
This is a structural steel shop drawing for beam B-14. Cross-reference against the structural drawings S-201 sheet (attached). Check: (1) member size matches, (2) connection type matches detail 5/S-501, (3) bolt quantity and diameter match, (4) coping geometry matches, (5) elevations align. Note any discrepancies. Do not approve geometry I cannot verify from the documents.
Samples
Sample submittals are mostly visual and benefit less from AI. Use image comparison:
Compare the two photos: (1) the approved mock-up sample photographed last month, (2) the new sample submitted today. Note differences in color, texture, and pattern. Are they within approved tolerance?
This is a useful first pass; the decision still rests with the architect of record.
Submittal Log Maintenance
Like RFIs, submittals need a living log.
Update the submittal log with this new submission: Submittal 05400-001, Section 05 40 00 Cold-Formed Metal Framing, Received: {date}, Action: Under Review, Review Due: {date + 10 business days}. Then flag any submittal that is overdue and any submittal that has been resubmitted more than twice.
Also useful: "List all submittals for Section 09 Finishes that are still open. Highlight those on the critical path per our latest schedule."
Contract Document Coordination
When a submittal or RFI reveals a conflict between drawings and specs, AI is excellent at drafting a supplemental instruction (SI) or architect's supplemental instructions (ASI) in AIA Document G710 format.
Draft an ASI per AIA G710-2017 resolving the conflict between drawing A-301 (which shows 5/8" Type X gypsum board) and spec Section 09 29 00 (which calls for 5/8" Type C gypsum board). Clarify that the correct product is 5/8" Type X to match the fire-resistance rating required per the G-001 life safety plan. Professional tone, clear direction, no acknowledgment of fault.
Pitfalls Specific to CA
AI creates specific risks in CA:
- Tone drift. AI tends toward conciliatory language. In adversarial CA situations, override the default tone in your prompt.
- Scope creep commitment. AI will sometimes volunteer work the owner did not ask for. Be explicit: "Do not offer any additional scope."
- Inaccurate sheet references. AI will sometimes make up a sheet number. Always verify by opening the contract set.
- Confidence in ambiguous situations. AI doesn't always know when it should say "defer to the owner" or "involve legal." Build that instruction into the prompt.
An End-of-Week CA Routine
A weekly routine that uses AI to stay on top of CA:
- Monday morning: Run the RFI log overdue check.
- Monday afternoon: Run the submittal log overdue check.
- Tuesday: Draft responses to any RFI older than 5 business days using AI templates.
- Wednesday: Submittal batch review using AI, then senior CA architect signs.
- Thursday: Field report summary (from photos and notes) drafted with AI for owner distribution.
- Friday: CA log update email to the owner — drafted with AI.
Typical time savings: 6-10 hours per week on a mid-sized commercial project.
Key Takeaways
- AI drafts high-quality RFI responses in seconds — always verify cited references
- Four RFI archetypes cover most situations: clarification, scope expansion, error correction, VE substitution
- Submittal review by AI works for product data and shop drawings; samples need human eyes
- Keep RFI and submittal logs alive with weekly AI-assisted overdue checks
- Override AI's default tone when the CA situation is adversarial or contractual