RFI follow-up without the spreadsheet

The RFI spreadsheet works until two people edit it, or nobody does. Here is a cleaner way to keep questions answered on time.

← All posts

Write RFIs that can be answered

One question per RFI, with the drawing or spec reference, a photo or sketch if it helps, and a suggested answer when you have one. Clear questions come back faster.

Always include a needed-by date

Tie the date to the work it affects. "Needed by" tells the design team what is at stake and gives you a fair basis for following up.

Keep one source of truth

RFIs scattered across email threads and a spreadsheet copy on someone's laptop are how answers get lost. Keep every RFI, its status and its answer in one shared place.

Review open RFIs every week

Sort by needed-by date. Anything close or past due gets a written follow-up. Note when you sent it.

Close the loop when the answer comes back

An answer is not the end. Make sure it reaches the field, and check whether it changes cost or schedule before you mark it closed.

Where Arise Crew fits

Arise Crew tracks RFIs as items on your project board, flags what is getting close to its needed-by date, and drafts follow-ups that wait in your approval queue. Nothing sends without your OK. See RFI tracking for GCs.