△
RFI Cue
Task-specific guidance for ordinary RFI drafting, routing, and tracking issues.
Project 10
Manage Requests for Information and Field Clarifications
Create, route, track, incorporate, and close one formal RFI or approved field clarification without making an unauthorized design or scope decision, using the approved drawings, specifications, schedule, and contractual RFI channel as the controlling project information.
Field Cue System
These cues appear at the point of work. They identify genuine ambiguity, unauthorized field improvisation, routing errors, and document-control failures before they become disputes, rework, or unpriced changes.
✋
Critical RFI Cue
Unauthorized field improvisation, a bypassed channel, or an unincorporated response is possible.
⛑
Field Coordination Cue
Practical coordination with trades, inspectors, and field supervision while an RFI is pending.
▤
Authority Alert
Permit, code, or authority-having-jurisdiction conditions may control the response. Verify before assuming.
▧
Contract Instruction Cue
Follow the executed agreement's specific RFI channel, numbering, and response-time terms.
▱
Documentation Cue
Recordkeeping, version-control, and traceability guidance for RFIs and field documents.
Job Overview
This project qualifies you to identify, write, route, track, and close a formal request for information or approved field clarification on a residential project without making an unauthorized design or scope decision in the field. The finished work product is one closed and auditable RFI record: a numbered question with document references, a tracked routing and response history, a distributed and incorporated response, and an evaluated cost and schedule impact.
You will confirm that a genuine ambiguity, conflict, or omission exists rather than an already-defined coordination task, inspect and document the affected field condition, write a factual question tied to specific document references, route it through the contractually required channel, track it to a timely response, verify the response actually answers the question, distribute it to every affected party, update the active field documents, and close the record only after field implementation is verified.
This project builds directly on the document-control discipline established in Project 02 and the sequencing logic from Project 04, and it feeds directly into the change-control system in Project 11: an RFI response that affects cost or time becomes a potential-change record the moment that effect is identified.
Skills You Will Demonstrate
- PM-055 — Identify unclear information.
- PM-056 — Write an RFI.
- PM-057 — Track submitted questions.
- PM-058 — Record responses.
- PM-059 — Distribute clarifications.
- PM-060 — Update field documents.
Where This Skill Fits
The RFI process protects the scope baseline approved in Project 01 from unauthorized field improvisation. Every RFI in this project must be checked against the current documents organized in the Project 02 job file and the sequencing logic built in Project 04 before it is written, so that a question already answered by an existing document is never submitted as new. When a response changes cost, time, or scope, it becomes the first entry in the Project 11 change-control system rather than a silent field adjustment.
The distribution and document-update discipline taught here — closing an RFI only after the response is incorporated into the active drawing set, schedule, and affected logs — is the same discipline used later for change orders, inspection corrections, and every other controlled field document in this book.
Scope and Intended Use
This project covers:
- confirming that a document conflict, omission, dimension issue, coordination issue, or required design clarification is genuine before submitting an RFI
- inspecting the field condition and collecting supporting photographs, measurements, and sketches
- writing a factual RFI with exact document references, affected-work description, and a required response date
- routing the RFI through the contractually required channel and tracking it by age and schedule impact
- receiving, verifying, and recording the response, and identifying any new effects it creates
- distributing the response to every affected party and obtaining acknowledgment for critical changes
- updating active field documents, logs, and schedules to reflect the incorporated response
- verifying field implementation and closing the RFI record
This project does not authorize the learner to:
- make a design, engineering, or code-compliance decision in place of the architect, engineer, or authority having jurisdiction
- answer a design question through unauthorized field improvisation while a response is pending
- bypass the architect, engineer, owner representative, contractor, or permit authority when their role controls the response
- use an RFI to transfer ordinary contractor means, methods, coordination, or already-defined scope to the designer
- treat a response as authority to proceed beyond its stated scope, or treat an unauthorized proposal embedded in a question as an approved solution
Any conflict between the current drawings, specifications, schedules, addenda, and prior RFI responses must be identified and referenced specifically in the RFI rather than resolved by field assumption.
Reference Conventions
Establish these references before drafting begins, and do not change them mid-record without a documented revision.
| Term | Definition |
|---|---|
| RFI | A numbered, written request for clarification of a genuine document ambiguity, conflict, omission, or required design decision |
| Field clarification | An approved written answer to a field question that does not require a formal RFI but is still recorded and incorporated under document-control rules |
| Controlling response | The most recent written answer that governs the affected work, superseding prior assumptions or verbal discussion |
| Work hold | A defined stop on affected work, or a defined limit on which unaffected work may continue, pending an RFI response |
| Potential change | A record created when an RFI response is identified as affecting cost, time, or scope |
| Incorporation | The act of marking, replacing, or updating an active field document so the RFI response becomes the controlling instruction |
| Closure | The state of an RFI record after distribution, incorporation, impact evaluation, and verified field resolution are all complete |
RFI Record Header
Before routing an RFI, record the following identification directly on the RFI form:
Project name: ______ RFI number: ______ Date submitted: ______ Originator: ______
Document reference(s): ____________ Required response date: ____________ Responsible responder: ____________
Prerequisites
- Access to the current approved drawings, specifications, addenda, schedules, submittals, and prior RFI log for the project
- Identification of the contractually required RFI channel, responsible responder, and response-time requirement
- An RFI form or platform, field photograph and sketch record, and RFI log ready for use
- A defined confidentiality and distribution rule for RFI records
- Confirmation of who is authorized to identify a work hold for the affected area pending response
Common Field Fundamentals
Every RFI in this book, from a single dimension conflict on a residential remodel to a multi-trade coordination question on the Chapter 20 capstone, follows the same sequence: confirm, inspect, reference, write, route, track, verify, distribute, incorporate, close. Learning that sequence here means every later RFI, and every response that becomes a potential change, starts from a method you already trust.
Confirm ambiguityChecked against current documents before drafting; not a means-and-methods question
Field inspectionPhotographs, measurements, sketches tied to the exact affected location
Document referenceExact drawing, detail, note, specification, and schedule citation
RoutingContractually required channel; correct responsible responder
TrackingAge, required response date, schedule impact, escalation
Response verificationConfirmed complete, authorized, and within its stated scope
DistributionEvery affected party notified; acknowledgment for critical items
Incorporation and closureField documents updated; field work verified; record closed
Genuine Ambiguity Versus Means-and-Methods
An RFI exists to resolve document ambiguity, conflict, omission, or a required design clarification — not to transfer ordinary contractor means, methods, sequencing, or already-defined scope to the designer. Before drafting, confirm the question cannot be answered from current drawings, specifications, schedules, details, addenda, submittals, or a prior RFI, and confirm it is not a coordination decision the contractor is responsible to make.
PM-055 – PM-060
Information Control / Field Clarification Management
Residential RFI and Field Clarification Record
A. Finished-Project Specification
Deliverable: one closed RFI record containing the confirmed ambiguity, exact document references, field-condition evidence, the routed question, tracked submission and response dates, the verified response, distribution and acknowledgment records, any resulting potential-change record, updated field documents, and verified field implementation.
B. RFI Record Document Schedule
| Section | Content | Source | Purpose |
|---|---|---|---|
| Identification | RFI number, date, originator, project reference | RFI log | Establishes the tracked record |
| Document references | Exact drawing, detail, note, specification, schedule, and prior-communication citations | Current drawing set, specifications, addenda | Ties the question to controlling documents |
| Field condition | Factual description of the observed conflict or missing information; photographs, measurements, sketches | Field inspection | Supports the question with verifiable evidence |
| Affected work | Trade, area, milestone, material, inspection, cost, and schedule condition affected | WBS, schedule, lookahead | Defines what depends on the response |
| Work-hold status | Whether unaffected work may continue; temporary protection or hold requirements | Field supervision | Prevents unauthorized improvisation while pending |
| Routing | Channel, responsible responder, contractual response time, required response date | Executed agreement | Ensures the RFI reaches the party with authority to answer |
| Response | Full recorded answer; verification it answers the complete question | Responder | Establishes the controlling instruction |
| Impact evaluation | New cost, time, scope, safety, permit, or coordination effects created by the response | Field review, estimator | Feeds the Project 11 change-control system when applicable |
| Distribution | Every affected party notified; acknowledgment obtained for critical changes | Communication log | Ensures the response reaches everyone who needs it |
| Incorporation and closure | Updated field documents; verified field implementation; closure evidence | Document register, field verification | Confirms the response actually governs the completed work |
C. Information and Document Takeoff
- Source records: current approved drawings, specifications, addenda, schedules, submittals, and prior RFI log, sufficient to confirm genuine ambiguity and cite exact references without inventing missing information.
- Field evidence: photographs, measurements, and sketches of the affected condition, dated and tied to the exact location.
- Routing record: written confirmation of the contractually required channel, responsible responder, and response-time requirement, obtained before submission.
- Revision control: a document register and marking convention sufficient to distinguish the current controlling document from every version superseded by the RFI response.
D. Acceptance Standards
| Check | Standard |
|---|---|
| Genuine ambiguity | Confirmed not already answered by current documents and not a means-and-methods question before submission |
| Document references | Exact drawing, detail, note, specification, and schedule citations included; no reference left general |
| Question content | States the observed conflict factually; does not conceal a preferred solution inside the question |
| Routing | Submitted through the contractually required channel to the correct responsible responder |
| Tracking | Age and required response date tracked; overdue items escalated through the approved notice process |
| Response verification | Confirmed to answer the complete question and not exceeded beyond its stated scope |
| Distribution | Every affected party notified; acknowledgment obtained for critical changes |
| Incorporation | Affected field documents marked or replaced; verified against the response before closure |
| Closure | Closed only after distribution, incorporation, impact evaluation, and field resolution are all complete |
E. Preparation — Confirm the Ambiguity and Inspect the Field Condition
- Identify a genuine ambiguity, conflict, omission, dimension issue, coordination issue, or required design clarification. Confirm the issue affects actual field work rather than a hypothetical condition.
- Confirm the answer is not already available in current drawings, specifications, schedules, details, addenda, submittals, or prior RFIs. Search the current document register and RFI log before proceeding.
- Confirm the issue is not solely contractor means, methods, sequencing, or an already-defined responsibility. Do not submit an RFI for a decision the contractor is responsible to make.
- Inspect the field condition and collect photographs, measurements, sketches, and affected-area information. Date and locate every piece of evidence collected.
- Identify the exact drawing, detail, note, specification, schedule, and prior communication references. Record each reference by sheet number, detail number, and revision.
F. Draft and Route the RFI
- Describe the observed conflict or missing information factually. State exactly what the documents show or fail to show, without characterizing intent.
- Describe the affected work, trade, area, milestone, material, inspection, cost, and schedule condition. Identify everything that depends on the response.
- Do not conceal a preferred solution inside a misleading question. If a solution is suggested, label it separately as a proposal.
- Present a proposed solution only when authorized and label it clearly as a proposal. Confirm authorization before including a proposed solution.
- Identify the date by which a response is needed to avoid impact. Calculate this date from the current schedule or lookahead.
- Identify whether work can continue safely in unaffected areas. State this explicitly in the RFI record.
- Identify temporary protection or hold requirements pending response. Record what must be protected or held and by whom.
- Assign the RFI number and enter it in the log. Use the project's controlling numbering convention.
- Route the RFI through the contractually required channel. Confirm the channel matches the executed agreement.
- Do not bypass the architect, engineer, owner representative, contractor, or permit authority when their role controls the response. Confirm the addressee holds the required authority before submitting.
G. Track, Receive, and Verify the Response
- Record submission date, responsible responder, contractual response time, and required response date. Enter each field in the RFI log.
- Notify affected trades that the item is pending and identify the work hold. Confirm every affected trade has received this notice.
- Track the RFI by age and schedule impact. Update the log at each schedule update and coordination meeting.
- Escalate overdue RFIs through the approved notice process. Do not allow an overdue RFI to remain unescalated past the required response date.
- Receive the response and verify it answers the complete question. Compare the response against every part of the original question.
- Identify new ambiguity, cost, time, scope, safety, permit, or coordination effects created by the response. Record any new effect as a separate finding.
- Request clarification when the response is incomplete or unauthorized. Do not treat an incomplete or unauthorized response as final.
- Confirm whether revised drawings, sketches, calculations, permit revisions, or product approvals are required. Identify each required follow-up document.
- Do not treat a response as authority to proceed beyond its stated scope. Confirm the response's scope before authorizing any field action based on it.
H. Distribute, Incorporate, and Close the RFI
- Distribute the response to every affected party. Use the distribution list identified in Step 7.
- Obtain acknowledgment from field supervision and responsible trades for critical changes. Confirm acknowledgment is recorded, not assumed.
- Mark or replace affected field documents according to document-control rules. Follow the Project 02 document-control system exactly.
- Update the drawing register, revision log, submittals, procurement, WBS, schedule, lookahead, quality plan, inspection plan, and safety plan as affected. Update every log the response actually affects.
- Create a potential-change record when cost or time may change. Route this record into the Project 11 change-control system.
- Photograph or document field implementation where appropriate. Record evidence that the response was actually built as answered.
- Verify the work conforms to the response and approved documents. Inspect the completed or in-progress work against the incorporated response.
- Close the RFI only after distribution, incorporation, impact evaluation, and field resolution are complete. Do not close a record with any of these four conditions outstanding.
- Preserve the question, attachments, response, distribution, changes, and closure evidence in the job file. File the complete record in the Project 02 job file under the controlling RFI section.
Common RFI Record Inspection
Inspect every RFI record using the same checks regardless of project size or complexity.
- Ambiguity check: confirm the question was genuinely unanswered by current documents and was not a means-and-methods question before it was submitted.
- Reference check: confirm every document reference cited is exact — sheet, detail, note, specification section, and revision.
- Routing check: confirm the RFI was submitted through the contractually required channel to the responsible responder.
- Tracking check: confirm age and required response date were tracked and overdue items were escalated.
- Response check: confirm the response was verified as complete and authorized before being treated as controlling.
- Distribution and incorporation check: confirm every affected party received the response and every affected field document was updated before closure.
Complete the RFI Record Inspection Checklist in the Inspection Checklist section below before beginning Project 11.
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Failure Points and Troubleshooting
Cleanup
This project ends with the RFI record closed and filed, not left as an open question with an unverified answer.
- Confirm the RFI log shows the item as closed with all four closure conditions satisfied
- Confirm every affected field document has been marked or replaced and matches the RFI response
- Confirm distribution and, where required, acknowledgment records are complete
- Confirm any identified cost or time effect has a corresponding potential-change record in the Project 11 log
- Provide the closed RFI record, updated documents, and any potential-change record to Project 11 for change-control processing
Field Terms
- RFI
- A numbered, written request for clarification of a genuine document ambiguity, conflict, omission, or required design decision.
- Field Clarification
- An approved written answer to a field question that does not require a formal RFI but is still recorded and incorporated.
- Controlling Response
- The most recent written answer that governs the affected work, superseding prior assumptions or verbal discussion.
- Work Hold
- A defined stop on affected work, or a defined limit on which unaffected work may continue, pending an RFI response.
- Potential Change
- A record created when an RFI response is identified as affecting cost, time, or scope.
- Incorporation
- The act of marking, replacing, or updating an active field document so the RFI response becomes the controlling instruction.
- Closure
- The state of an RFI record after distribution, incorporation, impact evaluation, and verified field resolution are all complete.
- Means and Methods
- Contractor-responsibility decisions about how work is performed, not a proper subject for an RFI to the designer.
- Escalation
- The approved notice process used to raise an overdue RFI to the level required to obtain a timely response.
- RFI Log
- The controlled record tracking every RFI by number, date, reference, response date, and status.
Skill Check
- What must be confirmed before drafting an RFI, and where should the learner check first to confirm the answer is not already available?
- Why is a means-and-methods question not a proper subject for an RFI to the designer?
- What is the difference between describing an observed conflict factually and concealing a preferred solution inside the question?
- Why must an RFI be routed through the contractually required channel rather than the fastest available informal contact?
- What must the learner do if work in the affected area cannot safely continue while an RFI is pending?
- What four conditions must be satisfied before an RFI record may be closed?
- Why does a response that answers one condition not automatically authorize a broader field change?
- What happens to a cost or time effect identified in an RFI response if it is not captured as a potential-change record?
- What are three possible causes of a trade working from an unincorporated document, and how does the learner confirm which one occurred?
- Why must the question, attachments, response, distribution, and closure evidence be preserved together in the job file?
Competency Rubric
| Competency | Independent Pass Standard | Not Demonstrated | With Assistance | Independently |
|---|---|---|---|---|
| PM-055 | Confirms a genuine document ambiguity, conflict, omission, or required design clarification exists before drafting an RFI, and rules out means-and-methods questions | |||
| PM-056 | Writes an RFI with exact document references, factual field-condition description, affected-work identification, and a required response date | |||
| PM-057 | Routes the RFI through the contractually required channel and tracks it by age, required response date, and schedule impact through escalation if needed | |||
| PM-058 | Verifies and records the response as complete and authorized, and identifies any new cost, time, scope, safety, or coordination effect it creates | |||
| PM-059 | Distributes the response to every affected party and obtains acknowledgment for critical changes | |||
| PM-060 | Updates every affected active field document, log, and schedule, and closes the RFI only after distribution, incorporation, impact evaluation, and verified field resolution are complete |
Mark one column per competency. Only Demonstrated Independently awards the competency; Demonstrated with Assistance authorizes additional supervised practice but does not complete the requirement.
Inspection Checklist — RFI Record Inspection Checklist
| Item | Standard | Meets Standard (Y/N) | Correction (if any) |
|---|---|---|---|
| Ambiguity confirmed | Not already answered by current documents; not a means-and-methods question | ||
| Document references | Exact sheet, detail, note, specification, and schedule citations included | ||
| Question content | States the conflict factually; any proposal clearly labeled and authorized | ||
| Routing | Submitted through the contractually required channel to the correct responder | ||
| Work hold | Affected and unaffected work status defined; affected trades notified | ||
| Tracking | Age and required response date tracked; overdue items escalated | ||
| Response verification | Confirmed complete, authorized, and within stated scope | ||
| Distribution | Every affected party notified; acknowledgment obtained for critical changes | ||
| Incorporation | Every affected field document marked or replaced and matched to the response | ||
| Closure | Closed only after distribution, incorporation, impact evaluation, and verified field resolution |
RFI log status: ____________ Open items carried forward: ____________
RFI record declared closed: ______ (Pass/Fail) Date: ____________ Project manager name: ____________
Performance Check
With the RFI response received and reviewed, confirm the ambiguity was genuine and not already resolved by current documents, every document reference cited is exact, the question was factual and any proposal was clearly labeled and authorized, the RFI was routed through the contractually required channel to the responsible responder, work-hold status was defined and affected trades were notified, age and required response date were tracked with escalation used if needed, the response was verified as complete and within its stated scope, distribution and required acknowledgment are recorded, every affected field document has been updated to match the response, and the record was closed only after distribution, incorporation, impact evaluation, and verified field resolution were all complete. Complete the RFI Record Inspection Checklist and correct any failed item before beginning Project 11. If an item fails, identify whether the error occurred in ambiguity confirmation, document referencing, drafting, routing, tracking, response verification, distribution, or incorporation before revising.
Project Closeout
You have completed the tenth project in the construction project management sequence: managing a request for information and field clarification without making an unauthorized design or scope decision. This project required you to identify unclear information (PM-055), write an RFI (PM-056), track submitted questions (PM-057), record responses (PM-058), distribute clarifications (PM-059), and update field documents (PM-060).
You now have a closed and auditable RFI record with verified response, complete distribution, updated field documents, and any resulting potential-change record identified. That record carries directly into the next project: operating the integrated change-control system that prices, authorizes, and implements the cost and schedule effects an RFI response can create.
File your closed RFI record, updated field documents, and any potential-change record where Project 11 can incorporate them into the change and allowance log. Every later cost, schedule, and document-control decision affected by this clarification depends on this exact record.