When the site needs an answer from the engineer, architect or client, Kai raises the RFI, chases it and posts the reply back to the chat.
Text, email, a call, a meeting. Nobody knows which question is still open.
The answer comes after the pour, not before it.
It lands in the PM’s inbox and stays there.
Every RFI follows the same 5 steps. Kai does the paperwork; people make the calls.
Anyone on site asks the question.
Numbers it, attaches photos and drawings, proposes who it goes to.
Sent with a required-by date. Kai chases before it’s due.
The reply is filed against the RFI, with any cost or time impact.
The crew sees the answer where they asked the question.
Every RFI is a task with a type. Pick the RFIs tab to filter, group by project and open any record, with the message it came from.
Add the crew, keep chatting the way you already do, and let Kai turn it into the record.