How to track RFIs in construction: from spreadsheet to GPS map.

What you get

• Log the RFI at the GPS location where the conflict arose

  Drop a pin at the station or structure where the field question came up. Every person on the project sees the RFI at the correct location — not in a row of a spreadsheet they have to search to find.

• Track status from submitted through response through closed

  Open, response received, response incorporated, closed. Each RFI moves through its status lifecycle on the map. The PM sees which RFIs are still waiting on a response — and how long they have been waiting.

• Attach photos and plan sections to the RFI pin

  The photo of the field condition and the relevant plan section live at the GPS pin — not in a folder structure someone has to hunt through. The response from the engineer can be attached when it arrives.

• See overdue RFIs before they become schedule problems

  Filter the map by status to see which RFIs are past due. The map shows where the overdue items are concentrated — which segments have the most unresolved questions — before the issue affects the pour schedule.

• Connect the RFI to the directive or change order that follows

  When the engineer's RFI response triggers a directive or change order, link it at the same GPS location. The paper trail from the original question to the cost-bearing record is connected at the location where it all happened.

Why not spreadsheets, sticky notes, or memory?

• RFI-014 at Sta. 38+50 looks identical to RFI-015 at Sta. 12+00 in a numbered row — the location is gone.
• When the superintendant asks 'which RFIs are open in Segment C?' the spreadsheet cannot answer that question without filtering and cross-referencing a drawing.
• Overdue RFIs hiding in the middle of a 60-row log do not announce themselves — the PM has to audit the entire spreadsheet to find them.
• Multiple parties editing different copies of the RFI log creates version conflicts that no one discovers until a status meeting.
• A verbal response to an RFI that never gets logged is as good as no response — and provides no protection when the work is disputed.

How to track RFIs step by step

1. 1

   Log the RFI at the moment the field question arises

   The field foreman discovers that the conduit shown on the plan conflicts with an existing gas main at Station 38+50. That is when the RFI is created — not at the end of the day, not in tomorrow's daily report. Open HeavyCivilHelper on the phone, drop a pin at the GPS coordinate, and log the RFI with a photo of the condition. The work at that station stops. The RFI is open.

2. 2

   Describe the conflict with enough detail to get a useful response

   Include: the station or location, what the plan shows, what exists in the field, what work is blocked, and any relevant spec reference. Attach photos. A vague RFI gets a vague response — and a vague response does not support a change order when you need one.

3. 3

   Submit the RFI to the right party and note the deadline

   Most contracts specify a response time — 10 business days is common. Note the submission date and the response deadline. If the contract has a critical path clause, note whether this RFI affects a critical path item. The PM can see the overdue deadline on the map without reviewing the full log.

4. 4

   Track the RFI until a written response is received

   A verbal 'go ahead and do it' from the inspector is not a response. An RFI stays open until a written response from the authorized party is received and attached to the record. Mark the response date and update status to 'Response Received.'

5. 5

   Incorporate the response and close — or escalate to a directive or CCO

   If the response is a straightforward clarification, close the RFI when the work is complete. If the response authorizes additional scope or a design change, open a directive or change order request at the same GPS location. The RFI is the source document for the cost-bearing record.

How HeavyCivilHelper tracks RFIs

RFI is a native record type in HeavyCivilHelper — not a workaround or a text note on a custom pin. Here is exactly what the workflow looks like from the moment a field conflict arises to the moment the RFI is closed.

• Field crew opens the app at the conflict location

  The foreman is at Station 38+50 when the conduit conflict is discovered. They open HeavyCivilHelper on their phone. Their GPS position is already on the map. They tap to drop a pin at that exact coordinate and select RFI as the record type.

• Description, photos, and spec reference logged on the spot

  The RFI form prompts for: what does the plan show, what exists in the field, what work is blocked, and any spec section reference. The foreman attaches photos of the condition. The submission timestamp and GPS coordinate are captured automatically — no one has to remember to log them later.

• PM and inspector see it on the map immediately

  The RFI pin appears on the project map as soon as it is submitted — yellow for open. The PM in the office sees it without a phone call. The agency inspector on their tablet sees it at the same time. The number on the pin matches the RFI number in the log.

• Status moves through the lifecycle on the map

  When the engineer's response arrives, the PM updates status to Response Received and attaches the written response. When the response is incorporated into the work and the RFI is closed, the pin turns green. Everyone on the project sees the current state without asking anyone to pull up a report.

• Overdue RFIs surface before they become problems

  The RFI log view shows which records have been open longest and which are past the contract response deadline. The PM sees which stations have the most concentrated open RFIs before the next day's work plan is set — without auditing a 60-row spreadsheet.

• Directives and change orders linked at the same location

  When the RFI response triggers a scope change, the PM opens a Directive record at the same GPS pin. The paper trail from the original field question to the cost-bearing record is connected at the location where it all happened — ready when the change order negotiation starts.

Common RFI types on civil and public works projects

The following RFI types came up on a real 5-mile public works roadway project tracked in HeavyCivilHelper. Each one was logged as a GPS pin at the station where the conflict arose.

• Utility conflicts

  Existing utility not shown on the plan — or shown incorrectly. The crew cannot proceed at that station until the engineer responds with a resolution.

• Conduit discrepancies

  Plan shows conduit in a location that conflicts with an existing structure, grade, or right-of-way limit. A common RFI on urban roadway projects.

• ADA compliance questions

  Curb ramp geometry, detectable warning surface dimensions, or accessible route alignment that does not match the plan or the inspector's interpretation of the standard.

• Pavement section changes

  Subgrade condition differs from the geotech report. The contractor asks for direction on the modified section and documents the changed condition.

• ESHA and environmental compliance

  Biological survey findings, sensitive habitat boundaries, or agency-imposed buffer requirements that affect the work at a specific location.

• Signal and electrical conflicts

  Signal pole conflicts, conductor schedule discrepancies, pull box sizing issues — each one is a specific station on the corridor.

Common questions about tracking RFIs in construction

How do most contractors track RFIs?

Most small and mid-size contractors track RFIs in a numbered spreadsheet — a column for the RFI number, a column for the description, a column for who it was sent to, and a column for the response date. The problem is that a numbered list has no spatial context. RFI-014 at Station 38+50 looks the same in the spreadsheet as RFI-015 at Station 12+00. The location — which determines which crew is affected and what work is blocked — is invisible in the list.

What should an RFI log include?

A complete RFI log should include: RFI number, date submitted, submitted by, submitted to (designer, owner, or engineer), description of the question or conflict, location (station, room, floor, or zone), specification reference, current status (open, responded, closed), date of response, and any cost or schedule impact. If you are tracking on a map, the GPS coordinate replaces the text-based location and connects the record directly to where it applies.

What is the best way to track RFIs on a large project?

On a large project with dozens of concurrent RFIs, the most effective approach is location-first tracking: each RFI is pinned to the GPS coordinate where it arose. The superintendent can see which sections of the project have open RFIs before the crew arrives. The PM can filter by status to see which RFIs are overdue. No one has to cross-reference a numbered list with a drawing to figure out which zone has the most open questions.

How long should an RFI stay open?

Contracts often specify response times — 10 business days is common on public works projects, though some contracts specify tighter windows for critical path items. An RFI should stay open in your tracking system until you receive a formal written response and the response is incorporated into the work. Closing an RFI prematurely because you received a verbal answer is one of the most common documentation mistakes — the verbal answer does not protect you if the work is disputed later.

What happens when an RFI results in a change order?

When an RFI reveals a plan conflict, changed condition, or scope addition that has cost or schedule impact, the response to the RFI often triggers a change order request. The RFI becomes the foundation of the change order: it documents the question, the existing condition, and the engineer's response that authorized the additional work. Tracking the RFI and the resulting directive or change order together — at the same location — makes the paper trail easier to reconstruct.

Can HeavyCivilHelper track RFIs on a mobile device in the field?

Yes. HeavyCivilHelper has iOS and Android apps where field crews can log an RFI directly from the location where the issue arose. Drop a pin at the GPS coordinate, describe the field condition, attach photos, and submit — all from the phone. The RFI appears on the project map immediately, visible to the PM in the office and the inspector on their device. No need to call the office and describe where the issue is.