Start with the condition
Capture what is physically present, where it occurs and why it conflicts with the planned work. Photos and field notes belong with this original observation.
Use an issue while the path is still being determined
An issue is useful when the team first needs to investigate responsibility or decide whether formal clarification is required. It keeps the unresolved field condition visible before an RFI exists.
Create the RFI when a formal answer is needed
When the question requires design clarification or an authoritative project response, create the RFI from the issue rather than retyping the field condition. The original evidence should remain linked.
Shift responsibility clearly
Once the RFI is sent, the project may now be waiting on the design team rather than the superintendent. That handoff should be visible so the team knows who has the next move.
Bring the answer back to the field
When the response arrives, connect the direction to the original condition and the affected work. If the answer changes cost or scope, the next path may be a change order rather than immediate correction.
Keep the original condition or communication, the current responsibility and the next action connected instead of recreating the same item in multiple places.
Why this is useful in Timbrana
Timbrana lets the field condition begin as an issue and move into an RFI without losing the photos, location, discussion or reason the question was raised.
What this means for the company
The company spends less time rebuilding field context when a condition moves from the superintendent to the PM and then to the design team. Photos, location, the original issue and the formal question stay connected as responsibility changes.