Fiber Construction RFI Workflow: One Issue, Three Separate Decisions

A radio call from a hole is not a design decision. After crews mobilize, the usual failure is not a missing form. It is one conversation that quietly rewrites issued intent on a live workfront, then treats the rewrite as if the owner already paid for that change.

This article covers only the post-mobilization, one-issue RFI intake and disposition workflow. Preconstruction handoff stays on its own page. Package QA does too. Crew management lives elsewhere. Inspection and closeout have their own pages. Classification happens here. The commercial paper does not.

What a Fiber Construction RFI Workflow Controls

A fiber construction RFI workflow is the post-mobilization control that records one field issue and issues a written response after that issue is classified. Draftech's project guidance uses 5 classes. Technical disposition stays off the commercial track. The contract and the named authority govern the outcome.

The function sits after mobilization. Crews are already on a released workfront. Something in the ground or on the pole does not match the issued sheet from the released package, or the sheet can be read two ways at the same station. The record has to freeze that question before anyone answers it by radio.

What is OSP construction management already maps control lanes from design basis through closeout. This page is narrower. It is the intake and disposition of one field issue after those crews are working. We do not retell readiness here. Inspection hold points stay off this page. The closeout package does too.

Draftech's operating boundary stays the same on this record. Engineering is 100% in-house. Construction is full turnkey through Draftech-managed subcontract crews under our QA/QC and safety program. We do not claim a self-perform construction crew today. Crews report field conditions. They retain responsibility for accepted means and methods. Our engineers control responses that affect engineering intent.

Classify One Issue Before Anyone Answers It

How the Fiber Construction RFI Workflow Classifies One Issue

Classification is a routing decision, not a severity score. The question is who may answer, and which paper the answer is allowed to become. We do not rank RFIs as high or low as if that rank were a contract term.

The five rows below are Draftech project guidance. They are governed by the contract and the permits. Owner requirements govern too. So do the applicable authorities on that workfront. They are not a national code. Florida DOT work uses different submittal names than a RUS Form 515 job. California DOT work keeps change orders in a different manual chapter than RFIs.

The table is a preview map. The next sections expand how those rows are used at intake and at close. A class can move after new evidence arrives. The row identity does not. We do not let a clarification quietly become a pay instrument because the crew is already standing there.

We treat the row as a routing identity that survives a later evidence upload, even when the reviewer later asks for a second photo or a station offset the first sketch omitted, because the class is who may answer rather than how severe the conflict looked on the radio.

Commercial change sits on the matrix so it can be refused as an RFI close. If the answer would move price or time, the RFI does not authorize the work. It points at the contract's change process, or at 1753.11 on RUS work, and the workfront stays held until that paper exists. Treating the fifth row as an RFI class is how we stop the other four rows from inheriting a pay claim the owner never signed in that close.

Intake: One Issue, Named Evidence, Named Location

The first defect is a compound question. NYSDOT Contract Administration Manual Section 91, Request for Information, Field Revisions and As-Builts, March 2024, issued as Engineering Bulletin 24-016, states that only one issue should be included per RFI. Subcontractors submit through the Contractor. RFIs are numbered in sequential order. Later mentions of that manual use CAM 91.

We copy the one-issue rule onto Draftech intake unless the governing contract writes a different form. Two conflicts in one paragraph produce one muddy answer. The log looks short. The field still has two open questions.

Sequential numbering is the other half of that rule. CAM 91 records RFIs in the order received. We keep a stable RFI identity even when a reviewer asks for more evidence. Extra information can attach to the same number. A second issue cannot. If the crew later finds a different conflict at the same pole, that is a new RFI, not a revision of the first paragraph on that workfront.

The record names a stable location identity and the current issued drawing or spec. It states the observed condition in the units the sheet already uses. A photo or sketch attaches when it shows that condition. A preferred response date may be recorded when the approved schedule actually needs it. We do not invent a house clock and call it a code requirement. A photo that does not show the named location identity, or a sketch that does not use the sheet's stationing, is not evidence we can route. It is a conversation that will have to be re-asked when the engineer sits down with the current issue.

CAM 91 tells the Engineer-in-Charge to process RFIs within the time specified on the form. If that date cannot be met, the EIC notifies the Contractor of additional time needed. That is a form-level rule on New York DOT work. It is not a Draftech universal threshold.

FDOT Construction Project Administration Manual Section 8.11, Contractor Initiated Submittals, Topic No. 700-000-000, revised September 27, 2021, remains the listed current section in the August 4, 2026 CPAM compilation. Section 8.11.8 publishes a priority matrix and expected working-day response times for Department work. We do not copy those working-day figures onto projects that are not FDOT contracts. Later mentions use CPAM 8.11.

Keep the Technical Track Off the Commercial Paper

Caltrans puts change orders in a different chapter from RFIs. Construction Manual Section 5-3, Change Orders, July 2025, is the current manual section for change-order policy and execution. Requests for information live in Construction Manual Section 3-5 (Control of Work) at 3-521. They also live in Standard Specifications Section 5-1.42 (Requests for Information). Mixing those chapters is how an interpretation becomes a payment instrument before anyone authorized the payment.

Section 5-3 is explicit that payment for change-order work waits for an approved change order. The project engineer who stamped the plans must concur with engineering changes. That concurrence is not an RFI checkbox. It is a change-order condition. The reason we keep Section 5-3 off the RFI log is that payment for changed work waits for an approved change order, and the project engineer who stamped the plans must still concur with an engineering change before that order is the working instruction.

CPAM 8.11 splits contractor-initiated submittals into 3 types. Request for Information is one. Request for Modification is another. Request for Correction is the third. An RFI covers interpretation and contractor-identified errors or omissions. Some pay-adjustment questions also travel as RFIs. An RFI is not a Notice of Claim; Specification 5-12.2 is the claim path. Some RFI resolutions require a Supplemental Agreement. An RFM is a contractor request to modify the documents. An RFC is a request to correct noncomplying work that is the contractor's fault. Those are different submittal types. We do not collapse them into one log color.

On USDA Rural Utilities Service ReConnect work, 7 CFR 1753.11, Contract amendments, current through the September 9, 2026 Title 7 amendment, requires prior RUS approval before executing an amendment that alters terms and conditions or changes scope, regardless of amount. The same section requires prior approval when the amendment increases the amount to be paid by 20 percent or more, or when it causes an unbonded contract to require a performance bond. RUS Form 526, Construction Contract Amendment, amends RUS Form 515, Telecommunications System Construction Contract. ReConnect Construction Procedures Version 2.0, included in award documents, repeats those amendment gates and notes that route, site, or method changes can require additional environmental review. An RFI response is not Form 526. That prior-approval gate is why we refuse to close a ReConnect RFI as if the response itself were Form 526: an RFI can describe the field condition, but it cannot execute a terms or scope change, a 20 percent price increase, or an unbonded contract that now requires a performance bond.

Technical disposition answers the engineering question. Permit and owner conditions stay with the named external authority. Price or time still waits on the contract's change process. We keep those tracks on separate paper even when one field event trips more than one of them.

Who Answers: Crews Report, Engineering Disposes Intent

A crew can see a conflict that the sheet never named. Seeing it does not authorize a new design. Draftech-managed subcontract crews report the observed condition with location and evidence. They retain responsibility for accepted means and methods, and for their employees, under the contract and applicable safety rules. We do not take that duty away in an RFI response.

A means-and-methods question is often a trench box choice or a pull method that the issued design never had to name. The subcontract employer still owns that choice inside the accepted envelope. If the proposed method would change a clearance the engineer stamped, it has left means and methods. It is now an intent question, and our in-house team answers it. The crew does not get a radio exception for the part that crossed that line.

Our in-house engineers answer questions that affect engineering intent. If the issued design is still correct, the response says so and the work continues against that issue. If the design has to change, the response is not finished until the field revision is authorized by the person the contract names. CAM 91 distinguishes major field revisions, which need the original designer or another licensed professional under New York State Education Law, from minor changes that construction licensed professionals may implement under the Regional Construction Engineer. Change Orders and Field Change Payments in that manual are administrative payment processes and need not be sealed. This is not legal advice. On New York DOT work, the EIC follows CAM 91.

The construction manager routes the record. Routing is not answering. A manager who answers engineering intent on a whiteboard has just created a second design authority.

OSP documentation for construction handoff already owns the release of issued records into the field. This page does not retell that handoff. It assumes the current issue is already the working file, and the RFI cites that file.

One thing I still reject in our own log is a single RFI that asks for a clearance interpretation and a quantity adjustment in the same paragraph. We used to let that through because the crew was already standing there. It made the log look efficient. It also mixed a technical answer with commercial paper the owner had not authorized. The limitation of our preferred one-issue workflow is that the log looks slower than a radio call. We accept that trade-off because a compound paragraph is how a technical confirmation inherits a quantity claim the owner never authorized on that same closed record.

Close the Record Without Turning It Into a Change Order

Closing the RFI is a records test. The accepted answer has to appear in every active instruction it affects. If the answer confirmed the issued design, the RFI closes against that confirmation. If the answer changed engineering intent, the controlled revision has to exist before the crew continues past the affected condition.

Confirmation close is the common case and the one teams skip. The response should cite the issued sheet and the observed condition, then state that the issued design still governs. The crew returns to that issue. No redline is opened. No quantity is rewritten. The log shows a closed question, not a silent redesign. A confirmation close still has to name the issued sheet and the observed condition in the same units, then state that the issued design governs, so a later as-built clerk cannot treat the closed RFI as if it had already rewritten the plant.

Revision close is slower on purpose. The RFI stays open until the person named by the contract authorizes the field revision, and until that revision is the working instruction. CAM 91's as-built rule is the reason: recording the change later is not what authorized it. On Caltrans work, Section 5-3 still has to produce an approved change order under that manual chapter before anyone pays for the changed work. On ReConnect work, Form 526 still has to exist before a scope or terms change is executed. We keep the RFI open through that authorization because CAM 91 treats as-builts as a record of field revisions that have already occurred, not as the paper that made the revision legal, and Caltrans Section 5-3 still requires the approved change order before anyone pays for the changed work.

CAM 91 is blunt about as-builts: they document field revisions that have already occurred. They are not the mechanism to authorize the revision. How to update as-built drawings after construction owns that later record problem. We do not rebuild as-built practice here. We refuse to treat a redline that has not been authorized as if it were already accepted plant.

Fiber construction management is the service that keeps this intake on one clock with in-house engineering and managed crews. The manager does not become the designer. The designer does not become the employer of the crew.

Recommended Next Step by Operator Type

Rural cooperative or single-state ISP with one workfront: run one-issue intake and close clarifications against the issued design. Do not open commercial paper because a sheet needed a sentence of interpretation. If the operator has no named engineering responder yet, name one before the next hole is opened.

ReConnect or other RUS-funded OSP under Form 515: treat a scope or terms change as a Form 526 question, not as an RFI closeout. A 20 percent price increase is a prior-approval gate under 1753.11 even when the field condition looks small. Route and method changes can reopen environmental review. Hold the workfront until that gate is named.

Multi-state build touching DOT right-of-way: use the named manual for that state. CAM 91 on New York DOT work. CPAM 8.11 on Florida DOT work. Section 5-3 for Caltrans change orders, with RFIs under 3-521 and Standard Specifications 5-1.42. Do not import FDOT working-day figures onto a California job, and do not treat a Caltrans change order as if it were an RFI.

If the current log already closed a clarification as a quantity change, reopen that number against the issued sheet before anyone writes a pay instrument. Fiber construction management holds one-issue intake on the same clock as those sheets. A skipped confirmation is not a redesign.

Active in 24 states. Available across all 50 U.S. states. If a live workfront is already mixing a field question with a price discussion, reach out at info@draftech.com.

For qualifying routes, Draftech engineers the first 20,000 linear feet at no cost, from feasibility and field survey through permit approval. Request the free design package; owner review is required.