A simple, bookmarkable web page your superintendents can use to produce polished, complete RFIs — every time.
The problem
Incomplete or poorly written RFIs create delays, back-and-forth with architects and engineers, and cost real time on the job. The standards exist — they just aren't being followed consistently in the field.
How it works
1
Super fills out a simple form
Project name, spec section, drawing reference, description of the issue, and what response is needed. Takes 2–3 minutes.
2
AI drafts the RFI to your standard
The tool is trained on your examples of what a good RFI looks like. It fills in language, structures the request properly, and flags anything missing.
3
Super gets a polished draft + coaching notes
They receive the ready-to-send RFI alongside a brief explanation of what was improved — so they learn, not just copy-paste.
4
Review, copy, and send
No login, no account, no software to install. Open the page, fill out the form, get the output. Bookmark it and done.
What the output looks like
Sample output
Project:Maple Creek Phase 2
RFI No.:RFI-047
Spec Section:03 30 00 — Cast-in-Place Concrete
Drawing Ref.:S-201, Detail 4
Date Required:November 14, 2025
Issue: Drawing S-201, Detail 4 indicates a 6" slab at the garage-to-living transition, however the foundation plan on S-101 dimensions this transition at 4". Confirm the correct slab thickness and provide a revised detail if required to avoid a pour discrepancy at this location.
Added
Spec section reference (03 30 00)
Original had no spec section. Architects need this to route the RFI to the right party.
Improved
Issue description rewritten for clarity
"The slab thickness doesn't match" → specific drawing callouts, dimension conflict, and location identified.
Added
Response required date
No deadline was provided. Added 5 business days from submission — adjust before sending if the pour is sooner.
Watch
Verify RFI number with your log
RFI-047 is a placeholder. Confirm the next sequential number in your project RFI log before submitting.
What I need from you to build this
2–3 examples of RFIs you consider well-written (real or anonymized)
2–3 examples of bad ones, with notes on what's wrong if possible
The standard sections you expect every RFI to include
Any formatting or referencing conventions your PMs expect
Cost to you
$0to build. Free to use.
I'm building this as a learning project. Hosting is free on Cloudflare. The only ongoing cost is a small AI API fee — fractions of a cent per RFI — which I'll absorb. No strings attached. If it works well and you want to expand it, we can talk about that later.