Review RFI response page wording
Review and validate the wording that external designers see when responding to an RFI, ensuring it is clear, plain English and project-specific.
This guide is designed for project manager.
Steps
Step 1: Open the shared RFI response link
Open the public RFI response link that has been shared with the external designer to see exactly what they will see when they access the page.
Step 2: Confirm project, drawing and requester details are clear
Check that the page clearly states which project, which drawing and which organisation is asking the question, so the responder knows the full context.
Step 3: Check the verification screen wording
Review the verification screen text to ensure it uses plain English, avoids internal PlanOps terminology and makes the purpose of the RFI clear.
Step 4: Review the RFI question and answer instructions
On the answer page, confirm that the RFI question is stated clearly, and that any instructions for providing an answer are simple and unambiguous.
Step 5: Ensure banned terms and symbols are not present
Scan the page copy to confirm there are no em or en dashes and no internal vocabulary such as "lifecycle", "workspace", "metadata", "stage", "endpoint", "null", "page_type" or "RAMS".
Step 6: Check confirmation screen clarity
After a test submission, review the confirmation page and ensure it clearly explains that the response has been received and what will happen next, in non-technical language.
Last updated: 2026-08-21