Architectural Rfi Decision Tracking Examples: Three Workflow Scenarios

Examples make architectural RFI decision tracking easier to design because they reveal where a neat diagram meets messy work. The scenarios below are not claims about a particular company; they are test cases small architecture firms and design-project administrators can run against a template or software trial.

Scenario 1: A ceiling conflict needs a sketch before framing continues

Create the record before the first follow-up. Capture Project and RFI number, Question and location, Referenced drawing or specification, then move it through register the question and governing references and assign the decision owner and needed-by date. If an rfi approaches its needed-by date without a decision, do not improvise in a private message; assign the exception, set a review date, and preserve the evidence needed for the next decision. Close with an explicit outcome and reason. ### Scenario 2: A response selects a product but the specification remains unchanged

Create the record before the first follow-up. Capture Question and location, Referenced drawing or specification, Originator and responsible party, then move it through register the question and governing references and assign the decision owner and needed-by date. If the response changes cost, schedule, scope, or controlled documents, do not improvise in a private message; assign the exception, set a review date, and preserve the evidence needed for the next decision. Close with an explicit outcome and reason. ### Scenario 3: A field clarification is later superseded by an issued bulletin

Create the record before the first follow-up. Capture Referenced drawing or specification, Originator and responsible party, Needed-by date, then move it through register the question and governing references and assign the decision owner and needed-by date. If field conditions or a revision supersede the published response, do not improvise in a private message; assign the exception, set a review date, and preserve the evidence needed for the next decision. Close with an explicit outcome and reason.

Debrief each scenario

After running a scenario, ask:

• Did the record make every open rfi decision needs one owner and a next review time?
• Did the record make completion requires recorded evidence that every rfi response identifies the authoritative decision, impact, and required document updates before operational closure?
• Did the record make automated reminders stop after verified completion or a documented closed reason?
• Did the record make keep controlled drawing, specification, rfi, and submittal repository as the system of record; only necessary coordination data belongs here?

Also check whether a new teammate could identify the owner, next action, and finish condition without opening another system.

Convert scenarios into acceptance tests

Use the normal case, waiting case, and closed-without-completion case in every software demo. Require the vendor—or your own prototype—to show the full workflow rather than isolated feature screens. Export the resulting records and verify that the status history remains understandable.

Next step

Explore the RFI Decision Register workflow concept and record whether this is painful enough to justify a focused tool.

For the adjacent workflow, see Consultant Deliverable Board.