Identify the project and original question
Use the project and RFI references to locate the original request. A reply subject can be edited or forwarded without its earlier context, so do not rely on the title alone. In a fictional project, an answer to RFI-42 arrives in a conversation also discussing RFI-43. Staff need to establish which question was answered before updating the register. If the match is uncertain, hold the response for administrative review with both possible references visible rather than choosing the newest item.
Preserve the complete response package
Keep the original message, attachments and any referenced document versions available to the reviewer through approved project access. A short extracted summary may help navigation but should not replace the source. Check whether an attachment is missing or cannot be opened, and record that gap. Avoid describing the response as complete simply because the email arrived. If an answer refers to material elsewhere, give the reviewer a way to locate it without silently substituting a similarly named file.
Assign the review by responsibility
Ask the project team to define which role reviews each category of response and who covers absence. Sending copies to several people does not establish ownership. The task should identify the question, response reference and review still required. For fictional RFI-42, the coordinator may route the material to the nominated reviewer without deciding whether its technical content resolves the issue. Keep those responsibilities distinct so an administrative classification does not become an approval beyond the coordinator’s authority.
Separate receipt from the project decision
Define register states such as response received and review pending using the project’s approved terminology. Do not automatically mark a question resolved, work approved or an instruction issued when a response is ingested. The authorised reviewer must decide the appropriate next step. If the response raises another issue, record that follow-up with its own owner. This guide does not determine contractual effects or technical requirements; it helps preserve the evidence and route the decision to the people responsible.
Handle revised responses without losing history
A later reply may clarify or replace earlier material. Keep the relationship between versions visible and ask the reviewer which response currently applies. Check pending tasks or notifications that still point to the older package. Avoid deleting the earlier response simply to make the register look tidy. Record when a revised package arrived and which review remains outstanding. If staff have already distributed information, assign the required communication review rather than assuming an updated file automatically changes what everyone knows.
Test ambiguous and incomplete handovers
Use fictional examples covering a clear response, multiple RFI references, missing attachments and a revised answer. Inspect the actual review task and linked source files. Confirm the nominated person can find the item and that receipt alone does not trigger an instruction or approval. Repeat an incoming response to check that duplicate review tasks are handled deliberately. The routing process should leave the team with one understandable current action and the evidence needed to make the project decision.