Trace a drawing conflict through the RFI and revision history

Learning draft. No credit or certificate is issued. Read the course status.

What you will learn

Assemble a focused drawing question using exact project references.
Distinguish a response from an issued revision and its distribution.
Keep historical references understandable as the working document set changes.

03.01

Describe the conflict before proposing its resolution

Drawing conflicts should be recorded at the level of the actual discrepancy. Identify the project, location, sheet, detail or schedule entry, revision, and issue date on each side. Explain what differs and why the reader needs clarification. Do not solve the conflict by selecting the newer-looking file, a familiar label, or a customary detail from another project.

NR-26 provides a focused question: D-201 revision B labels the structure at station 18+20 as I-07, while D-202 revision A identifies the schedule entry as I-17. The packet does not establish which identifier governs. A marked excerpt can help locate the conflict, but the full source reference must remain available. A cropped image without revision context can leave a reviewer answering a different question.

03.02

Build a request that supports a specific answer

For this exercise, request RFI-028 identifies the discrepancy, cites both documents, attaches the relevant excerpts, and asks for the intended structure identifier and the associated written reference. It identifies the requesting role and the party designated by the project to respond. Record a requested response date as a coordination need, not a fabricated contractual deadline.

Separate suggested interpretations from the question. Label 'I believe I-17 is a typo' as a proposal, not fact. NYSDOT's guidance illustrates focused requests and supporting attachments, but its agency procedures do not automatically govern this fictional project.

Keep unrelated issues separate. The conflicting lot on MD-031 belongs in the material evidence process unless the project's coordination procedure explicitly connects it to this request. Mixing label clarification, material review, and delivery scheduling under one RFI can obscure which part a response resolved.

03.03

Read the response for scope and unfinished work

The fictional response to RFI-028 arrives on 20 October at 15:00: 'Use identifier I-07 for the structure at station 18+20; revised drainage schedule to follow.' This answers the identifier question and identifies a further document action. Preserve the full response, responder, receipt time, and attachment references. Do not reduce it to 'all drainage approved.'

A coordination record can show 'response received; schedule revision pending.' That wording does not decide whether particular work may proceed, whether a contract change exists, or whether another authorization is necessary. Those questions belong to the assigned project process. If the response's authority or intended use is unclear, record a clarification action rather than expand its meaning.

03.04

Connect the issued revision to the original question

On 21 October, transmittal TR-009 issues D-202 revision B and identifies revision A as replaced. The new schedule uses I-07 at station 18+20. Log the transmittal, issue date, new revision, replaced reference, and relationship to RFI-028. D-201 remains revision B; it should not acquire another revision simply because a related schedule changed.

Distinguish historical evidence from the working set. An earlier report may correctly cite D-202 A. Keep that reference understandable while controlling current copies under project rules. Do not change the earlier report to imply that the later schedule was available from the beginning. Preserve the sequence.

03.05

Verify the handoff at the right level

Distribution is a separate event. Record TR-009 received at 13:20 and sent to the field team at 13:30. If receipt is unacknowledged, say so. Drafting, sending, acknowledging receipt, and updating a field copy are different events; record the one your evidence supports.

A complete handoff tells the next reader where to find the original conflict, the response, the issued schedule, and any remaining distribution task. Use project-defined status labels consistently. A single 'closed' value may be insufficient when the technical question is answered but a document-handling action remains open. Keep the distinction explicit without inventing additional approval gates.

Worked example · Fictional project

Worked example: RFI-028 event history

19 October, 11:00: RFI-028 sent with D-201 B and D-202 A excerpts. 20 October, 15:00: response identifies I-07; revised schedule pending. 21 October, 13:20: TR-009 and D-202 B received. 21 October, 13:30: coordinator sends the issued reference to the field distribution list; acknowledgement not yet recorded.

The status at the 14:00 handoff is: 'Identifier response and revised schedule received; distribution sent, acknowledgement pending.' Original D-202 A remains linked as the source of the question. Nothing in this sequence resolves the separate lot mismatch or establishes a general authorization to change other drainage work.

Try it yourself · Fictional scenario

Put the module into practice

The draft RFI log says only: 'RFI-028 closed 20 October; drawings updated.' At that date, the response had arrived but TR-009 had not. You now have the event history in the worked example and must correct the log for a 21 October, 14:00 handoff.

Your task

Identify the timing problem and the missing document references.
Prepare a replacement status note that keeps the correction traceable.
Identify one remaining action and the evidence that would resolve it.

Write your response in your own notes before opening the sample. This exercise is for practice and does not record a score or course completion.

Reveal a sample response

The old entry incorrectly places the drawing update on the response date and omits D-202 B and TR-009. A dated correction should identify that earlier wording, then record the 20 October response and 21 October revision receipt as separate events. Preserve the original request and response links.

At 14:00, distribution has been sent but receipt is unrecorded. The coordinator can follow the project's distribution process and record the resulting acknowledgement or other required evidence. The correction does not reopen the answered identifier question merely to track a separate handoff task.

Keep in mind

An RFI history should preserve the chain from exact source conflict to response, issued documents, and the actual handoff completed.