# One Set of Field Notes, Two Deliverables **By Dan Cumberland** · Published August 3, 2026 · Categories: AI Strategy ![Featured image for One Set of Field Notes, Two Deliverables](https://cms.dancumberlandlabs.com/uploads/featured_image_63d7d23d53.webp) Illustration: Dan Cumberland Labs with Gemini. > Most construction project teams write the same field observation twice: once in the morning daily log, and again as a formal RFI. The rfi process in... Most construction project teams write the same field observation twice: once in the morning daily log, and again as a formal RFI\. The rfi process in construction requires that written record— but the daily log requires one too\. It's the same moment in the field, written up twice\. A superintendent who writes up a morning field observation in the daily log and then drafts it again as an RFI is doing one job twice\. According to Layer[1](/blog/blog-rfi-process-in-construction#ref-1), "observations in a field report may lead to RFIs but do not replace them"— they're parallel documents, not interchangeable ones\. And that distinction is costing your team real hours before the morning meeting ends\. This article walks through the full rfi process in construction— the 8\-step lifecycle, the dual\-documentation problem that turns one field observation into two writing tasks, what that burden costs by project size and team, and how AI tools are already collapsing both documents into a single act of writing\. For [how design professionals respond to RFIs](/blog/what-are-rfi-in-construction/), there's a companion article covering the other side of the table\. ## What Is the RFI Process in Construction? A Request for Information \(RFI\) is a formal written request for clarification about construction documents, drawings, specifications, or site conditions\. The contractor or subcontractor who encounters an information gap submits the RFI; the architect, structural engineer, or design consultant responds\. That response creates a formal obligation— which is exactly what a daily log entry does not\. The difference matters when there's a dispute\. A construction RFI is not a change order and does not authorize any change in scope or cost\. It asks a question\. Only a change order can authorize the answer\. Per Procore[2](/blog/blog-rfi-process-in-construction#ref-2), the RFI lifecycle follows eight steps: 1. **Create** — The contractor or sub identifies an information gap and drafts the RFI 2. **Submit** — The RFI goes to the architect or engineer, typically routed through the GC 3. **Review** — The design team reviews the question and relevant contract documents 4. **Respond** — The architect or design consultant provides a formal written response 5. **Approve** — The GC approves the response for distribution 6. **Distribute** — The response reaches the relevant parties: subs, field team, owner 7. **Implement** — The field team applies the clarification to ongoing work 8. **Close** — The RFI is formally closed in the project log Response times are rarely fast\. According to a landmark Navigant Construction Forum study of 1\.1 million RFIs across 1,362 projects, the median response time is 9\.7 days[3](/blog/blog-rfi-process-in-construction#ref-3)\. Procore[2](/blog/blog-rfi-process-in-construction#ref-2) puts the current range at 6\.4 to 10 days depending on region and project type\. Nearly two work weeks for a single question\. And roughly 1 in 4 RFIs never gets answered at all[3](/blog/blog-rfi-process-in-construction#ref-3)\. When a response doesn't come, the contractor faces a choice: stop work and document the delay, or proceed and take the risk\. Either way, the unanswered RFI creates legal exposure that shows up later in the claims trail\. ## The Other Document Running in Parallel The daily field report \(also called the daily log, superintendent's log, or construction daily report\) records site conditions, work performed, crew count, weather, safety events, and any issues observed that day\. It's a narrative protective record, not a contract document\. It does not replace an RFI\. That distinction matters more than most guides acknowledge\. As Layer[1](/blog/blog-rfi-process-in-construction#ref-1) states directly: "Field reports are not legal directives; RFIs are part of the formal contract communication process\." The daily log protects the contractor's record of what happened\. The RFI creates a formal obligation for the design team to respond\. Here's where the double\-entry problem starts: **One field observation, two deliverables** A single field observation becomes field notes, which then split into two separate documents: a daily log entry, which is narrative and protective, and a formal RFI draft, which is contractual and question-asking. The same moment in the field— an exposed footing that doesn't match the drawings, a spec callout that conflicts with a manufacturer requirement— generates two separate documents for two different audiences\. The daily log captures what the superintendent saw\. The RFI formally asks what the design team wants done about it\. Both documents matter\. But if there's ever a dispute, these two documents will be examined together— so they need to tell a consistent story\. Inconsistency between the daily log and a formal RFI can undermine a legitimate claim, even when the contractor was clearly in the right\. The information re\-entry is manual\. ArchDaily and Newforma[4](/blog/blog-rfi-process-in-construction#ref-4) document this precisely: larger projects require "human intervention to upload, download, and re\-enter information" across multiple systems\. That's not a technology limitation\. That's the workflow as most firms have built it\. ## What the Dual\-Documentation Burden Costs Field foremen spend 30–60 minutes per day on daily field reports alone, according to Rhumbix[5](/blog/blog-rfi-process-in-construction#ref-5)\. Add formal RFI drafting— which the Navigant Construction Forum pegs at an average of $1,080 per RFI in direct review and response costs[3](/blog/blog-rfi-process-in-construction#ref-3)— and the documentation burden on a mid\-size project is significant before 9am\. Project managers spend 6\.2 hours per week on document management tasks, with RFI tracking consuming 4–6 hours of that total, per a 2026 construction\.live study[6](/blog/blog-rfi-process-in-construction#ref-6)\. For the field team, it's not a productivity tax\. It's the job\. The scale compounds fast\. The Navigant study[3](/blog/blog-rfi-process-in-construction#ref-3) found that the average construction project generates approximately 9\.9 RFIs per $1 million in construction cost\. Run the math: - $10M project: ~100 RFIs - $50M project: ~500 RFIs - Each one generating both a daily log entry AND a formal submission > For a mid\-size contractor with 10 field supervisors, Rhumbix[5](/blog/blog-rfi-process-in-construction#ref-5) estimates the annual direct cost of administrative time waste at $182,000 to $395,000\. And that's before rework enters the picture\. According to Autodesk and FMI Corporation research[7](/blog/blog-rfi-process-in-construction#ref-7), 52% of rework in construction stems from poor project data and miscommunication\. Sloppy documentation isn't just expensive in labor hours— it's expensive in poured concrete that has to come out\. The documentation burden is a technology problem, not a people problem\. And AI is purpose\-built for exactly this kind of structured repetition\. ## How AI Collapses One Field Note Into Two Documents The technology to collapse that double\-entry already exists\. AI field documentation tools \(including Procore's RFI Creation Agent and Daily Log Agent, both launched at Groundbreak 2025[8](/blog/blog-rfi-process-in-construction#ref-8)\) can take a single field observation and generate two structured outputs: a formatted daily log entry and a draft RFI, simultaneously\. The superintendent still reviews and approves both\. What changes is the writing\. Here's what that looks like in practice— and what changes is the writing, not the judgment: 1. **Write the field note once** — the superintendent records what they observed: location, condition, drawing discrepancy, and any relevant spec references 2. **AI generates both documents** — the RFI Creation Agent drafts a formal RFI and cross\-references project specs; the Daily Log Agent generates a structured site report entry from the same input 3. **Superintendent reviews, edits, and approves** — both documents before submission That last step isn't optional\. An RFI is a legal document\. The superintendent's expertise is what makes the output accurate and defensible\. Construction\.live[6](/blog/blog-rfi-process-in-construction#ref-6) describes this workflow as: "Issue identified > agent drafts RFI from field note, cross\-references drawings and specs > routes to correct party\." The field pro still owns the result\. AI just stops them from writing the same thing twice\. In practical terms: less time writing, same legal accountability\. Varseno[9](/blog/blog-rfi-process-in-construction#ref-9) found AI delivers 50–70% less time on manual drafting and formatting\. Construction\.live[6](/blog/blog-rfi-process-in-construction#ref-6) puts AI\-assisted RFI resolution at 1\.8 days \(in workflows where AI tools are used across both the origination and response sides\) versus a manual average of 8\.2 days\. Engineers Universe[10](/blog/blog-rfi-process-in-construction#ref-10) confirms the core capability: "Raw field observation notes can be summarized for weekly construction progress reports through AI prompts"— the same input feeding multiple structured outputs\. Procore is the most concrete published example of the dual\-output workflow, but the principle isn't platform\-dependent\. For firms not yet on Procore or Autodesk Construction Cloud, the same workflow can be approximated with structured prompting into any AI writing tool\. The field note is the input; the RFI template and daily log format are the outputs\. The question is whether your firm has the process in place to capture field notes consistently enough for AI to use them— and [building an AI\-ready workflow for your team](/blog/building-ai-culture/) is where that work starts\. For a broader view of how AI fits into project\-based firm operations, the [AI automation guide](/blog/ai-automation-guide/) covers implementation patterns across the field and office\. And if you're evaluating [AI implementation for construction and professional services firms](/services/ai-implementation/), that's the place to start before buying any tools\. ## FAQ ### What does RFI stand for in construction? Request for Information\. In construction, it's a formal written request for clarification about documents, drawings, specifications, or site conditions— submitted by contractors or subcontractors to the design team[2](/blog/blog-rfi-process-in-construction#ref-2)\. This is distinct from RFIs in procurement contexts, which serve a different purpose entirely\. ### Who responds to an RFI in construction? The architect, structural engineer, or relevant design consultant provides the formal response, typically routed back through the general contractor[2](/blog/blog-rfi-process-in-construction#ref-2)\. Design professionals estimate it takes roughly 8 hours to receive, log, review, and respond to a single RFI\. The GC distributes the approved response to the relevant field parties\. ### How long should an RFI response take? The industry median is 9\.7 days, per the Navigant Construction Forum's study of 1\.1 million RFIs[3](/blog/blog-rfi-process-in-construction#ref-3)\. Response times range from 6\.4 to 10 days depending on project type and region[2](/blog/blog-rfi-process-in-construction#ref-2)\. AI\-assisted review can reduce this to under 2 days— construction\.live[6](/blog/blog-rfi-process-in-construction#ref-6) reports a 1\.8\-day average for AI\-managed RFI workflows\. ### What happens if an RFI is not answered? Roughly 1 in 4 RFIs receives no formal response[3](/blog/blog-rfi-process-in-construction#ref-3)\. Unanswered RFIs can create grounds for schedule delay claims and cost impact claims, particularly when the contractor was forced to proceed without the requested clarification\. Document every non\-response in the daily log immediately and by date\. ### What's the difference between an RFI and a change order? An RFI asks for clarification about what is required\. A change order formally authorizes a change in scope, schedule, or cost[2](/blog/blog-rfi-process-in-construction#ref-2)\. Never proceed with additional work based solely on an RFI response— that requires a change order\. The RFI gets you the design team's answer; the change order gets you authorization to act on it\. ### How is an RFI different from a daily field report? A daily field report is a narrative protective record of site activities and conditions— it is not a contract document\. An RFI is a formal contract communication that requires a formal design response[1](/blog/blog-rfi-process-in-construction#ref-1)\. The same field observation can generate both documents, but they serve different legal purposes\. The daily report documents what happened\. The RFI asks what should happen next\. ## The Documentation Overhead Is the Problem, Not the People The rfi process in construction isn't the problem\. Writing the same field observation in two different formats, for two different audiences, before the morning meeting ends— that's the problem\. Most platforms already have AI capability to close that gap\. The question is whether your firm's workflow captures field notes in a format the AI can use\. That's less a technology question than a process question— and it's a question worth answering before buying any tools\. If you're working through that at your firm \(or evaluating how to reduce your RFI cycle time without adding headcount\), [our framework for evaluating AI implementation decisions](/blog/ai-decision-framework-founders/) is a useful starting point\. If you want to talk through what this looks like for a firm your size, that's the kind of problem Dan Cumberland Labs works on with AEC firms directly\. The superintendent's job is to know what's happening in the field\. The documentation is the overhead\. AI can take that overhead off the table— not by replacing professional judgment, but by handling the structured repetition so the field pro can focus on the work\. ## References 1. Layer, "What Is a Field Report? A Guide for Architects During Construction" \(2025\) — [https://layer\.team/blog/what\-is\-a\-field\-report](https://layer.team/blog/what-is-a-field-report) 2. Procore Technologies, "RFIs: A Contractor's Guide to Requests for Information" \(2025\) — [https://www\.procore\.com/library/rfi\-construction](https://www.procore.com/library/rfi-construction) 3. Construction Management Association of America \(CMAA\) / Navigant Construction Forum, "Impact & Control of RFIs on Construction Projects" \(2013\) — [https://www\.cmaanet\.org/sites/default/files/resource/Impact%20&%20Control%20of%20RFIs%20on%20Construction%20Projects\.pdf](https://www.cmaanet.org/sites/default/files/resource/Impact%20&%20Control%20of%20RFIs%20on%20Construction%20Projects.pdf) 4. ArchDaily / Newforma, "Automating Construction Administration: Streamlining Submittal and RFI Review Workflows" \(2024\) — [https://archdaily\.com/1007667/automating\-construction\-administration\-streamlining\-submittal\-and\-rfi\-review\-workflows](https://archdaily.com/1007667/automating-construction-administration-streamlining-submittal-and-rfi-review-workflows) 5. Rhumbix, "Why Your Best Field Foremen Are Spending 6 Hours a Week on Paperwork \(And What It's Costing You\)" \(2024\) — [https://www\.rhumbix\.com/blog/why\-your\-best\-field\-foremen\-are\-spending\-6\-hours\-a\-week\-on\-paperwork\-and\-what\-its\-costing\-you](https://www.rhumbix.com/blog/why-your-best-field-foremen-are-spending-6-hours-a-week-on-paperwork-and-what-its-costing-you) 6. Construction\.live, "The State of Construction Workflows 2026: AI Agents & Automation" \(2026\) — [https://www\.construction\.live/blog/construction\-workflows\-2026](https://www.construction.live/blog/construction-workflows-2026) 7. Autodesk / FMI Corporation, "Construction Disconnected Report" \(cited via Bedrock, 2024\) — [https://bedrock\.cv/blog/why\-52\-of\-rework\-is\-preventable](https://bedrock.cv/blog/why-52-of-rework-is-preventable) 8. Procore Technologies, "Procore Advances the Future of Construction with New AI Innovations at Groundbreak 2025" \(2025\) — [https://www\.procore\.com/press/procore\-advances\-the\-future\-of\-construction\-with\-new\-ai\-innovations](https://www.procore.com/press/procore-advances-the-future-of-construction-with-new-ai-innovations) 9. Varseno, "How AI Is Transforming Construction RFI & Submittals in 2026" \(2026\) — [https://www\.varseno\.com/ai\-transforming\-construction\-rfi\-and\-submittals/](https://www.varseno.com/ai-transforming-construction-rfi-and-submittals/) 10. Engineers Universe, "Using AI on Electrical Construction Projects: RFIs, Submittals, and Field Reports" \(2025\) — [https://engineersuniverse\.com/studios/ai/aie\-ai\-construction\-rfi\-submittals](https://engineersuniverse.com/studios/ai/aie-ai-construction-rfi-submittals) --- **How we made this article:** We use AI in our research and writing so our small team can share more of what we learn. We verify the sources and take responsibility for every article we publish. [Read how we use AI.](https://dancumberlandlabs.com/how-we-use-ai/) --- ## About the author **Dan Cumberland** — Founder, Dan Cumberland Labs Dan Cumberland helps engineering and construction firms see where they stand with AI and decide what to build first. He created Pacemark, the AI maturity model behind that work, from research on more than 300 companies. - Take the assessment: https://pacemark.ai/signal/assessment/?track=aec&utm_source=dcl-site&utm_medium=link&utm_campaign=pacemark-assessment - Book a call: https://book.dancumberland.com/ai-strategy --- Source: https://dancumberlandlabs.com/blog/rfi-process-in-construction/