Consultant RFI chasing
Structural have not come back and it has been nine days.
- HUMAN STEPS
- 1
- AUTOMATED
- 4
- RECLAIMED
- ~5 hrs/month
WF-06 — Consultant RFI chasing. 1 human step, 4 automated steps, about 5 hours a month reclaimed.
- Step 1. RFI raised (REGISTER)
- Step 2. Log against the project
- Step 3. Set the response date
- Step 4. Follow up, politely, on a schedule (EMAIL)
- Step 5. RFI register updated (REGISTER)
Risk points in this workflow:
- RFI gone quiet. An unanswered RFI stops being a coordination problem and starts being a programme problem.
Steps you still do:
- Escalate to the lead
What it actually does
- 01RFI raised
- 02Log against the project
- 03Set the response date
- 04Follow up, politely, on a schedule
- 05RFI register updated
The risk this covers
RFI gone quiet
An unanswered RFI stops being a coordination problem and starts being a programme problem.
What you still do
- Escalate to the leadWhen chasing stops working
Everything else runs without you.
- WORKFLOW
- WF-06
- BAND
- ENTRY
- REV
- 01