An RFI — a request for information — is a formal question to the design team, and the record of its answer. Unlike an issue, an RFI has a workflow: it is raised, it sits with somebody, it is answered, and it is closed.
This topic includes:
The RFI list
RFIs, with the number, status, manager and who currently holds the ball.
The people on an RFI
- Creator — who raised it.
- Manager — who is accountable for getting it answered.
- Reviewer — who provides the answer.
- Ball in court — who it is sitting with now. This is the field to look at when an RFI has gone quiet.
- Distribution — people kept informed as it progresses, without being asked to answer.
Statuses
draft → open → answered → closed, with void for one raised in error.
The steps are guarded, so the record stays honest:
- Only the creator may move an RFI from draft to open.
- Opening an RFI requires a question and a manager — an open RFI with no question is not a question.
- Closing requires a response.
- Only the member who currently holds the ball may edit the RFI.
Note: if a transition is refused, the reason appears on the form. The status shown always reflects what was actually saved.