Keep drawings and RFIs connected

Identify the document before the question

A sheet number alone may point to several versions. Record the project, drawing title, sheet or detail number, revision identifier, and issue date shown on the document. Include the source location or document register entry. If the revision is unclear, make that uncertainty visible and ask the assigned document controller to confirm it.

A filename such as 'latest-plan-final' or a download's modified date may describe file handling rather than the drawing's issue. Build the reference from the document and register; use the link to retrieve it.

Make one question easy to answer

Describe the location and the specific ambiguity. Point to the relevant references and attach the evidence needed to understand that question. Distinguish a requested clarification from a suggested interpretation. Record the RFI identifier, sender, date, assigned recipient, and requested response date using the project's established fields.

NYSDOT's guidance illustrates focused questions and supporting attachments. Follow your project's communication process. Mixing an inlet label, a missing material record, and tomorrow's crew allocation makes it harder to identify which question a response answers.

Separate the events in your log

A response received, an issued revision, and a completed field handoff are useful separate tracking events. Record dates and source references for each event that applies. Some responses clarify existing information without a new drawing; others leave documentation tasks outstanding. The log should show the actual outcome, not force every request into an identical sequence.

The log does not create authority to change work. Preserve the response and supporting documents, including the responder's stated qualifications. A status label cannot replace the source communication.

Connect revisions without erasing the trail

If an updated sheet is issued, link its identifier to the RFI and to the relevant transmittal or register entry. Record whether it replaces or supplements an earlier reference as stated by the issuing documents. Do not infer that every sheet in a package has changed because one sheet carries a new revision.

Follow the project's rules for superseded copies. Distinguish the reference intended for current use from the historical copy supporting an earlier record. Retaining history and controlling the working set are related but distinct tasks.

Close the documentation loop

When a response arrives, record which references it addresses and whether additional documentation remains pending. Identify who needs the resulting information and record the distribution actually completed. A message drafted, a file sent, and a receipt acknowledged are different observations; use the one your evidence supports.

Before handoff, ask another reader to find the question, response, and referenced documents. Identify outstanding owners or deadlines. A 'closed' label should not conceal unfinished distribution, coordination, or separate change-review tasks.

Fictional training example

Worked example: Cedar Lane drainage sheets

Fictional training scenario. Project CL-12 has inlet labels on drainage sheet C-204, revision 2, that differ from the schedule on C-205, revision 1. The coordinator logs RFI-018: 'Please clarify the intended inlet identifier at station 12+40.' Marked excerpts and their revision details accompany the question.

A response is filed on 20 October. A later transmittal issues C-205 revision 2 and identifies the prior sheet it replaces. The log links both records and records the field team's receipt. The response date, issue date, and handoff date remain separate. No design solution is invented in the log.

C-204 remains revision 2. The coordinator does not renumber it merely to match C-205. The earlier C-205 copy remains traceable to the original question, while the working register identifies the newly issued reference.

Try it yourself · Fictional scenario

Practice: turn a reply into a complete handoff

Fictional exercise. RFI-026 asks about conflicting drainage-structure labels on project HB-08. On 22 October, the assigned reviewer replies: 'Use the identifiers in attached schedule DS-03 revision 3; revised drawing C-310 to follow.' The coordinator files the reply and marks the RFI closed. No revised C-310 has arrived, and distribution to the field team is not recorded.

Your task

List the event that is complete and two documentation tasks still open.
Write a log update that preserves the reviewer's qualification.
Draft a handoff identifying an owner and evidence needed for the remaining tasks.

Use your own notes or a sheet of paper. Compare your response with the example below when you are ready.

Reveal a sample response

'Response received 22 October; attached DS-03 revision 3 filed with RFI-026. Reviewer states revised C-310 will follow. Revised drawing receipt and field distribution remain unrecorded.' This preserves the distinction between the response and the outstanding document work.

'Document coordinator to track the promised C-310 revision and link its issue record when received. Coordination lead to distribute the response and schedule through the project process, then record recipients and the available delivery evidence.' The exercise does not establish permission to proceed with any particular activity.

Keep in mind: A useful RFI status tells the next person what happened and what is still needed.

Your practical checklist

Project, sheet, detail, revision, and issue information are recorded.
The question isolates a specific ambiguity and location.
Original requests, attachments, and responses remain accessible.
Response qualifications and unresolved items are visible.
Related revisions link to their actual issue records.
Distribution evidence and remaining handoff owners are identified.