Source: https://www.quantumsteeldesign.com/rfi-log/ Your browser. Your workspace. # Steel RFI Builder and Response Log Prepare numbered steel-detailing requests for information, record drawing references and responses, track open questions, and print a project RFI log. Saved only in this browser. Use a complete project package to back up the project and its attached tool records. No files or private project fields are uploaded. ProjectLoading projects… Saved recordNew record [Create or edit a project](https://www.quantumsteeldesign.com/project-workspaces/) · [Project dashboard](https://www.quantumsteeldesign.com/project-dashboard/) ## Project requests and answers Show requestsAll requestsOpenAnsweredClosed Prepared RFI text — copy into your normal correspondence Printing includes the visible filtered requests. Up to 500 requests. Copying checklist questions creates independent RFIs. This tool prepares records locally; it does not send correspondence or establish project approval. ## Write a question that can be answered and followed up The RFI builder prepares a local record and copyable correspondence text. Start by choosing the project and the RFI log you intend to maintain. A useful request identifies the source, the uncertainty, and the clarification needed. ### Prepare the request - Check the suggested RFI number, give the request a specific subject, and identify the drawing or specification reference. - Describe one clear question and the information needed to resolve it. Record the responsible team and response-needed date when known. - Save the RFI, then choose Prepare correspondence to copy its formatted text into your normal project communication process. No message is sent by this tool. ### Example: resolve an inconsistent piece reference For a fictional request, use subject “Piece reference at grid C/4,” reference “S201 revision B; detail 3/S501,” and question: “The plan identifies the member as B12, while the referenced detail identifies B21. Please confirm the governing piece mark and the drawing issue that should be used for coordination.” This states the conflict and asks for a traceable answer without inventing the answer. ### Keep the response and status together Record the response or disposition before changing the request to answered or closed; the tool requires response text for those states. Include the source and date of the response in that text when you need to trace it later. Status is your log entry, not proof that correspondence was transmitted or that a release was authorized. Copying unresolved workspace items creates independent open RFIs. The tool avoids recopying the same source item into that log, but later changes do not synchronize between the RFI and the original follow-up item. Update both records when that is appropriate for your workflow. Filter open requests to prepare a focused follow-up printout. Printing respects the current status filter, while CSV includes all requests. Use a [complete project package](https://www.quantumsteeldesign.com/project-dashboard/) for an editable backup; the CSV export is a readable record, not an RFI-import format. Include the relevant log in a [handoff package](https://www.quantumsteeldesign.com/project-handoff/) when unresolved questions need to remain visible. A few practical answers ## Frequently asked questions Does saving an RFI send it to the project team? No. It creates a local record. Review the question and use the project's agreed communication process to submit it. What makes a useful question? Identify the exact sheet, detail, revision, and location; explain the conflict or missing information; and state the decision needed. Keep assumptions separate from confirmed requirements. Does marking an RFI answered release the affected work? Not by itself. Record the authorized answer, affected drawings, required revisions, and release decision under the project's procedures.