top of page

HVAC RFIs: Work Back from Procurement to Set a Response-Needed Date

Oct 14
5 min read
Original navy and copper Nexora cover showing a backward procurement timeline from AHU installation to the RFI response-needed date.

An HVAC RFI marked “due in fourteen days” can appear under control while the equipment release date quietly slips. The missing information may be needed before a supplier can finish a selection, prepare a submittal or reserve a manufacturing slot. A response-needed date should therefore come from the affected work sequence. The administrative response period remains useful, but it answers a different question.


1. Identify the activity the answer actually unlocks


Name the equipment tag, the unresolved decision and the first blocked activity. For example, a conflicting AHU coil-connection orientation might prevent the supplier from finalizing its general arrangement. The RFI response is then a predecessor to drawing preparation, followed by review and release. It is not merely an item due before installation.


Distinguish three dates: the contractual or configured response due date; the planned date the project needs a usable answer; and the actual date that usable answer arrives. Retain all three when they differ. Changing a due date in a register does not change a contractual obligation, establish delay responsibility or recover lost programme time.


Procore’s RFI documentation treats the response due date and schedule impact as distinct fields. Its configured due date also respects project working days. This is a reminder to check the software’s date logic; another register may count calendar days instead.


2. Trace the procurement chain backward


Begin with the equipment’s required installation date, then identify when it must be available on site. Work backward through receiving or staging, manufacture and transport, order release, external review, and preparation of the submission that depends on the clarification. Include only activities that genuinely follow this answer. If some work can proceed in parallel, model that overlap explicitly rather than subtracting every duration in one long chain.


Procore’s submittal planning guidance uses required-on-site dates, lead time and review periods to back-calculate submission milestones. The same dependency reasoning can be extended upstream to an RFI, but the RFI date must be calculated from the project’s actual remaining activities, not copied from an unrelated submittal default.


Obtain the supplier’s current lead-time statement and identify its starting event. “Six weeks” may start at approved drawings, a technically complete order, or a confirmed release; those are different dates. Confirm whether the duration includes shipping, factory shutdowns and other stated constraints. Record the evidence date and avoid counting transport twice when it is already included.


3. Calculate an original calendar-day example


Assume one simplified AHU procurement chain with sequential activities and an installation target of 15 January 2027. All durations below are hypothetical calendar days, measured by ordinary date subtraction. They are not industry-standard response times or supplier commitments. Assume the answer fully resolves the technical issue and no resubmittal is needed.


  1. Receiving and staging: 2 days. Equipment must be available on site by 13 January 2027.

  2. Manufacture and transport after release: 42 days. Release must occur by 2 December 2026.

  3. Order finalization and release after review: 2 days. Reviewed information is needed by 30 November.

  4. External technical review: 10 days. The complete submission must enter review by 20 November.

  5. Supplier drawing preparation after clarification: 4 days. Clarification must be available by 16 November.

  6. Explicit planning buffer before preparation: 3 days. Set the project response-needed date to 13 November 2026.


The total look-back is 2 + 42 + 2 + 10 + 4 + 3 = 63 calendar days. Therefore, 15 January 2027 minus 63 days gives 13 November 2026. If the agreed planning allowance for answering this RFI is fourteen calendar days, the planned issue date is 30 October 2026. That allowance is an example input, not a statement about the project contract.


Original calendar-day procurement sequence: response needed 13 November 2026, preparation starts 16 November, submit 20 November, review complete 30 November, release 2 December, on site 13 January 2027, install 15 January.

Original sequential planning example. All durations are hypothetical calendar days; supplier calendars, parallel activities, review cycles and project float require separate verification.


This creates a testable question: was a complete RFI issued early enough for the planned response period? A short deadline caused by late issue should be visible. Labelling it urgent cannot manufacture the review time that was omitted from the original plan.


4. Write the date’s consequence into the question


A concise hypothetical RFI could state: “AHU-04 coil connections are shown on opposite sides in drawing M-402 Rev C and schedule M-601 Rev B. Please confirm the required side when viewed in the direction of airflow and identify the controlling revision. The supplier cannot complete the general arrangement until this is resolved. A usable response is needed by 13 November 2026 to support the attached procurement sequence and 2 December release.”


Attach the conflicting marked-up references and the short date calculation. Ask for the decision needed to proceed; do not bury several unrelated equipment issues in one RFI. Identify who will update the supplier package after the response. An answer such as “coordinate with approved information” may require further clarification if the approved documents still conflict.


5. Test lateness against the remaining sequence


Suppose the usable answer arrives on 19 November, six calendar days after the response-needed date. Three days consume the explicit buffer. With every other duration unchanged, the remaining three days move the planned installation from 15 January to 18 January 2027. This is the result for the isolated example chain, not a finding of overall project delay.


The GAO Schedule Assessment Guide emphasizes integrated schedules that connect activities and milestones. Apply that principle before treating one late RFI as a critical-path delay: check dependencies, available float, parallel work, other constraints and the current schedule update. Distinguish the deliberately inserted three-day buffer from total float calculated by the project scheduling model.


If a new supplier forecast adds seven calendar days to manufacture and transport, recalculate the response-needed date and identify the changed evidence. Do not preserve an obsolete green status merely because the original due date has not passed. Potential recovery actions, such as phased submissions or a different release sequence, need technical and commercial approval; an RFI tracker cannot authorize them.


6. Keep the register useful after a response


  • Record the programme revision, required-on-site milestone, lead-time source and day-count convention.

  • Track the date of a usable answer separately from an acknowledgement or incomplete response.

  • Confirm that the answer reached the supplier and the dependent submission was updated.

  • Close the RFI according to the project workflow, while continuing to track the downstream release and delivery milestones.


Nexora’s paid HVAC RFI Pack provides a register, form, tracker, dashboard and HVAC question library to organize that record. Its priority-based required-by calculations use calendar days. Compare those calculated dates with the project response-needed dates and the applicable project calendar; the workbook is not a working-day scheduler or critical-path model. The benefit is a clearer question and follow-up record anchored to the work it must unlock.



Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page