Construction RFI Process for Fiber Projects

The crew has a question about the route. The foreman calls the project manager, someone sends a marked-up photo, and an answer comes back later that afternoon. The next morning, a different crew starts from the original drawing because the answer never reached its work package.

That is the gap a construction RFI process needs to close. The question needs a clear record, an assigned person responsible for getting it answered, and a path back to everyone whose work depends on the response. For fiber contractors and ISPs, that includes the people building, documenting, inspecting, and ultimately accepting the affected work.

A useful process follows the question through implementation. It establishes what remains unresolved, who can decide, which work is affected, and how the field receives the resulting instruction. The contract and project requirements determine the formal submission, notice, change, and approval procedures.

What is an RFI in construction?

RFI means request for information. During construction, it is a documented request to clarify missing, conflicting, or unclear project information. It might ask which detail applies to a particular handhole, how a route conflict is to be resolved, or which drawing revision controls an affected section.

The request should identify the specific uncertainty and the decision needed. A note saying “please advise” beside a photograph leaves the recipient to determine both the problem and the question. A useful RFI connects the location, relevant documents, observed condition, and requested clarification.

Define the relationship between RFIs and the project’s other processes before work begins. A technical answer may require additional design, substitution, commercial, or work-release decisions. Check those requirements separately rather than treating every response as complete authorization for everything described in it.

Establish the submission route and decision authority

Assign who checks field questions internally, who submits formal RFIs, who receives responses, and who makes sure the answer reaches the work. Identify backups so a routine absence does not leave a question sitting in one person’s inbox.

Separate the authority to explain a technical detail from the authority to approve a change in scope, price, schedule, or design. The contract may place those decisions with different parties. Record the actual assignments at project setup, including the route for questions that affect more than one discipline.

For a narrow contract example, FAR 52.236-21(a), in its February 1997 clause text, directs specified discrepancies to the Contracting Officer for a written determination when that clause applies. This illustrates why the applicable contract matters. It does not establish a universal submission route or document-precedence rule for privately contracted fiber work.

An inspector may identify and document a question within the assigned inspection scope. That role does not automatically include design approval or authority to direct the contractor’s methods. Keep the contractor responsible for its means, methods, and corrections, and identify the owner’s acceptance role under the governing arrangements.

Check the current information before sending the question

Have the assigned reviewer compare the field concern with the current issued drawing, specification, relevant detail, and previous responses. An answer may already exist in a revision the crew has not received. If so, the immediate task is to correct the distribution problem and communicate the controlling information.

Record which references were checked. “Reviewed plans” is difficult to trace later. The sheet number, detail, revision, and relevant specification section allow the next person to understand the same information. Retain the original field observation even if the internal review resolves the question without a formal RFI.

Keep the review proportional to the issue. A foreman should have a practical way to flag uncertainty without first preparing an office-quality package. The designated coordinator can help complete the formal request while preserving what the crew observed and what it needs answered.

Write an RFI that can receive a specific answer

Use the project’s required form or system. Where the company is developing its own supporting process, the following information provides a useful starting point:

Project, work package, and unique RFI identifier.
Exact location, structure, route segment, or other affected asset.
Drawing and specification references with revisions.
Observed condition and the information that is missing or conflicting.
A specific question and any clearly labeled proposed option.
Affected activity, needed-by date with its basis, attachments, and current work status.

Keep observed facts separate from proposals. A photograph may show that the available surface space differs from the drawing. It does not establish the location of an underground utility, the suitability of a revised route, or the approvals required to make that change.

Explain timing in terms of the work. “Needed before the crew installs this structure” gives the recipient more useful context than an unexplained urgent label. State when the activity is planned, when the question was identified, and what decision is pending. Follow the contract’s actual response and notice requirements; a requested date does not create a new contractual deadline.

Illustrative fiber-construction RFI

Assume the current plan locates a handhole where the project team has identified a conflict with another planned facility. The field record identifies the structure and drawing revision, describes the observed or documented conflict, and attaches an annotated plan extract and relevant photographs.

The question asks the authorized project party to confirm the required disposition and identify any revised location, detail, or further investigation needed. A proposed alternate location, if included, is labeled for review. The crew records the affected activity as awaiting direction under the project’s process. The example supplies no clearance, depth, or permission to relocate the structure.

A separate review may be needed for the connected conduit route, access requirements, property or permit limits, material quantities, and subsequent cable work. Listing those affected items helps the reviewer coordinate a complete response without assuming every item can be approved by the same person.

Track work status while the RFI is open

Use an RFI log that shows the current assignee, submission date, required response date or target, affected work, and next action. Identify whether the item is being drafted, awaiting response, awaiting clarification, or waiting on a related approval. Choose status names people can understand consistently.

Review open items against the upcoming work sequence. A question that can wait during one stage may become the next constraint when the crew moves. The project lead should know which item needs attention before committing labor, equipment, or materials to that activity.

An unanswered request does not establish permission to proceed. Decisions about pausing affected work, resequencing, or performing other work belong with the assigned personnel under the contract and applicable safety procedures. Emergency response takes priority over routine RFI preparation.

Review the answer before releasing it to the field

Check that the response answers the actual question, identifies the affected location, and includes the required references or attachments. If it directs the team to a revised drawing that has not arrived, keep the missing document visible as an open item. Ask for clarification when the response leaves a necessary decision unresolved.

Then check the related approvals. A technically acceptable option may still need the required contract-change process, permit review, product approval, or other authorization before execution. Record the reference for each required decision and who confirms readiness. Do not describe an RFI response as a change order unless the governing process gives it that effect.

Keep the original question and response intact. If a later answer supersedes the first, show the relationship and tell affected recipients which instruction controls. The record should explain the sequence without requiring the reviewer to reconstruct it from private messages.

Put the answer into the crew’s work package

Assign one person to distribute the response to the affected foreman, subcontractor, inspector, document coordinator, and other relevant roles. The distribution should identify the RFI, response revision, location, changed instruction, and any remaining restrictions. Avoid sending a long email chain without identifying the current direction.

Have the receiving field lead explain the change using the current package. For the illustrative handhole question, that means identifying the authorized location or required next investigation, the revised document, and the connected work affected. This short check can expose a missing attachment or an assumption before it enters the installation.

Follow the project’s method for withdrawing superseded field information. Preserve historical versions for the record while making the current instruction easy to identify at the work location. Include the change in the handoff when personnel or subcontractors change.

Close the RFI with the resulting records connected

Distinguish “answer received” from “implemented and recorded” in the company’s tracking method. The contract or owner’s system may define formal closure differently. A linked internal action record can track implementation without misrepresenting the owner’s RFI status.

Before closing that internal action, confirm the response was distributed, required approvals are recorded, affected instructions are current, and the resulting field and closeout records are assigned or complete as appropriate. Identify the actual disposition if the issue was withdrawn, deferred, or resolved through another process.

Review patterns across completed RFIs. Repeated questions about the same detail may point to unclear project information, a distribution problem, or a training need. Track the reason and affected work before drawing conclusions. A low RFI count alone does not establish that crews had everything they needed.

Give the field a dependable route to an answer

Connect field questions to authorized decisions, current crew instructions, and the resulting construction records.

Valor helps fiber construction companies and ISPs build operational systems around responsibilities, workflows, decision criteria, training, and field tools. Organizing how project questions reach decision-makers and return to crews supports its mission: Making Good Fiber Construction Repeatable.

Talk with Valor about improving how field questions and decisions move through your operation.

Construction RFI Process for Fiber Projects: From Field Question to Crew Instruction