Keep RFIs, handover and asset information connected to the work that created them

Project information becomes expensive when it is separated from its source. An RFI answer can change installation. A submittal can establish the product actually used. A test record can be the only evidence an operator has at handover. Keep those records with the affected drawing, requirement and decision while the job is still moving.

Use one register for open work

Workshop’s work register holds RFIs, submittals and other findings with a status, ball in court and due date. Create an item when there is a question, an information need, a discrepancy or a required review. Link the item to the source document and drawing region where possible, then state the decision needed and the effect of waiting.

An RFI should ask one answerable question and cite its evidence. A submittal should identify what is proposed, what requirement it is being checked against and what approval or response is needed. Do not use either record as an inbox label; the value is in the link between evidence, responsibility and disposition.

Worked example: replace an air-handling unit and leave an operable record

An existing unit is removed, a replacement is installed, and the controls sequence changes. The project creates an RFI about a duct transition, a submittal for the selected unit, a finding about access clearance, and closeout material that includes the approved submittal, startup record, controls sequence, test result, warranty and maintenance information.

Use this Workshop brief while the work is live:

For the air-handling-unit replacement, create an evidence-linked register for RFIs, submittals, deficiencies and closeout information. Link each item to the affected drawing, requirement or photo. Show its status, responsible party, due date, decision needed and downstream effect on installation, controls, test records or handover. Produce a handover index that identifies the current record, its source and any open condition.

Review the register with the people who own the decisions. The handover output is an index, not a promise that every document is complete: asset or system; required record; current document and revision; source; accountable party; acceptance or outstanding condition. Use the work register to pursue the gaps before handover rather than discover them after the team has left site.

Close the loop on the drawing and the requirement

When a response arrives, add it to the project record and update the work item. Check whether it changes a requirement, drawing, quantity, programme or quote. If it does, make the dependent work visible and give it an owner. A closed RFI that never changed the installation record is a future site question waiting to happen.

Workshop can frame an item’s evidence on the relevant sheet and keeps a Requirements view beside the work register. Use both when reviewing an answer: see the exact location, then confirm whether the stated requirement is met, changed or still unresolved.

Assemble handover from the delivery record

Handover is a usable record for the next responsible person: current drawings, approved product information, testing and commissioning records, warranties, operations and maintenance material, and the decisions that explain any departure from the original design. The exact information requirement belongs to the contract, owner and asset, so build the index from those governing sources rather than a generic folder template.

Before transfer, check each item for its current edition, asset or system it relates to, responsible source and open condition. Keep unresolved deficiencies visible with their owner and next action. A PDF dump is storage; an indexed evidence set can support operation, maintenance and later change.

Open Workshop to keep project documents, registered questions and their evidence together from the first clarification through handover.