Send formal, time-boxed Requests for Information to client contacts, with CCs, a threaded reply timeline, and an Open → Answered lifecycle.
Last updated: August 2026
RFIs are formal, time-boxed written questions from your engineering team to a named client contact. Each RFI carries CC'd client contacts and internal team members, a threaded reply timeline, and an explicit status lifecycle (Open → Answered).
RFI-{project no}-{001}.An RFI becomes Overdue automatically when it's still Open past its expected reply date.
| Issue | What to do |
|---|---|
| “RFIs require the M Module add-on.” | Upgrade the organisation's plan to include the M Module. |
| I need to change an RFI after sending | RFIs are permanent. Post a correction as a reply instead. |
| My Mark as Answered button is missing | Only the RFI author can mark it answered. |
| The expected reply date is rejected | The date must be in the future — RFIs can't be back-dated. |
How are RFIs numbered?
Automatically per project as RFI-{project no}-{001}, -002, and so on.
Who can reply to an RFI?
Anyone with access while the RFI is Open — team members and client contacts.
Can a client reply before registering?
No — they must register first using the signed Register Here link in the email.
Can I delete an RFI?
No — RFIs are permanent records once sent.