š Overview
Sending the question is the easy part. The hard part is getting the answer back where your team can see it. When an engineer replies to whoever happened to email them, the answer sits in one person's inbox, the superintendent never sees it, and the crew builds from an old drawing.
When you send an RFI, each recipient gets an email with a VIEW RFI button. It opens the RFI in their browser with no Structur login, and they type their answer under RESPONSE. Their answer lands on the RFI for your whole team. When the primary contact answers, Ball in Court moves to your side so you know it's your turn.
This article covers what recipients receive and how answers flow back. For creating and sending RFIs, see RFIs.
š Understanding RFI Emails and Responses
ā” What It Does
RFI emails and responses allow you and your team to:
Email every recipient a personal link -- vendors and additional recipients each get their own
Let recipients answer without an account -- on the RFI page in their browser
Answer from inside Structur -- your reply goes to every recipient
Keep every answer in one thread -- oldest first, with the name and time on each
See whose turn it is -- Ball in Court moves when the primary contact or your team answers
Tell recipients when you close the RFI -- with an automatic email
š When to Use It
This is most useful when you need to:
Get an answer from a vendor, architect or engineer who doesn't use Structur
Keep several people on the same question and the same answers
Follow up on an RFI that hasn't been answered
Work out why a recipient says they never got the RFI
š Step-by-Step Instructions
1. Who Gets the RFI Email
When you click Send RFI and Send, Structur emails:
Every vendor and client under RECIPIENTS, including the project's client when Include Client is on
Every email address you typed under ADDITIONAL RECIPIENTS
The Send RFI window lists the addresses under Recipients before you click Send.
Important: A team member you pick under ADDITIONAL RECIPIENTS is only emailed if they've turned on RFI sent to client/vendor in their own Settings > Notifications. It's off unless they've changed it. If a teammate needs the email, ask them to turn it on, or type their email address as an outside address instead.
Note: Other contacts on that vendor who have Send notifications turned on also get the email, even though the Send RFI window doesn't list them.
2. What the Email Looks Like
The email comes from [email protected] with your company logo. The subject reads like "Your Company: RFI #023 - Door swing at Unit 2B".
It opens with "Hey" and the recipient's name, then your Message. If you left the message empty, it says "You have a new RFI for" the project name, and asks them to open it with the button. The VIEW RFI button opens that recipient's personal link.
Structur doesn't show whether an RFI email was delivered or opened.
3. How a Recipient Answers
The VIEW RFI button opens the RFI page. The recipient sees the RFI number, title and status, REQUESTED BY, RFI DETAILS with the due date, RECIPIENTS, ADDITIONAL RECIPIENTS, the QUESTION, earlier RESPONSES and the ACTIVITY.
To answer:
Type the answer in the RESPONSE box
Add files with Click To Upload or drag and drop if needed
Click Send Response
They see Response submitted successfully! and the answer appears under RESPONSES with their name and the time. Additional recipients can answer the same way.
Note: Only a recipient's personal link can answer: the VIEW RFI button in their email, or the link from Copy Recipient Link on their row in the recipients table. The Copy Link button at the top of the RFI gives a read-only link, where Send Response stays greyed out. View As Recipient shows you their page, but an answer you send there while signed in is posted under your own name.
4. Find Out a Recipient Answered
When a recipient answers:
If they're the primary contact, Ball in Court moves to the team member who requested the RFI, on the list and on the RFI. Answers from other recipients don't move it
An RFI Answered notification appears in your bell. Click it, then Open in RFIs
The answer appears under RESPONSES on the RFI
If you already had the RFI open, reload the page to see the new answer. To hand the RFI to a different recipient, open the three-dot menu on their row and click Set Ball In Court.
Note: Currently, you aren't emailed when a vendor or additional recipient answers, even with RFI answered emails turned on. Watch the bell and the BALL IN COURT column so you don't miss an answer.
5. Answer from Inside Structur
Open the Submitted RFI
Type your reply in the RESPONSE box under the question
Click Send Response
Your reply shows under RESPONSES with your name. Every recipient gets an email saying you answered, with a VIEW RFI button. So do the project's owner, the team members assigned to the project and the person who requested the RFI, if they have RFI answered emails turned on (it's on unless they've changed it). Ball in Court moves back to the primary contact.
6. What Recipients See After You Edit, Close or Reopen
After Edit: the RFI is back in Draft. Recipients can open their link and read the responses, but there's no response box until you send it again.
After Mark as Closed: recipients get an email saying you closed the RFI. Their page shows Closed and is read-only.
After Reopen RFI: the RFI is Submitted again and recipients can answer. They aren't emailed, so let them know it's open.
ā Best Practices
Tell recipients to answer with the VIEW RFI button -- an answer on the RFI page reaches your whole team and moves Ball in Court.
Send personal links, not the header Copy Link -- only a personal link lets the recipient answer.
Add a short Message -- a line on what you need and by when reads better than the default text.
Check the bell and Ball in Court daily -- recipient answers don't arrive by email.
Reply on the RFI, not by email -- your reply then goes to every recipient and stays on record.
Tell recipients when you reopen -- Reopen RFI doesn't email anyone.
ā Common Questions
Q: Does the recipient need a Structur account?
A: No. The VIEW RFI button opens the RFI in their browser, and they answer there.
Q: My vendor says they never got the RFI. What can I do?
A: Check the vendor's email address and contacts, and ask them to check spam for an email from [email protected]. You can also send them their personal link yourself. Open the three-dot menu on their row in the recipients table and click Copy Recipient Link. It's there on Draft and Submitted RFIs, so you don't need to edit the RFI first.
Q: I sent someone the link, but Send Response is greyed out. Why?
A: They're on the read-only link from Copy Link. Ask them to use the VIEW RFI button in their email, or send them their personal link from Copy Recipient Link on their row.
Q: Can additional recipients answer the RFI?
A: Yes. Each additional recipient gets their own VIEW RFI link and can answer from it.
Q: I added a teammate as an additional recipient and they didn't get the email. Why?
A: Team members only get the RFI email if they've turned on RFI sent to client/vendor in their own Settings > Notifications. It's off unless they've changed it. Ask them to turn it on and send the RFI again, or add their email address as an outside address.
Q: Why didn't I get an email when the vendor answered?
A: Currently, answers from vendors and additional recipients don't send an email to anyone. You'll see them as RFI Answered in your bell. The BALL IN COURT column also moves to your side when the primary contact answers.
Q: Can I see if the recipient opened the email?
A: No. Structur doesn't show delivery or open status for RFIs. Check Ball in Court, or ask the recipient directly.
ā ļø Common Mistakes to Avoid
ā Don't | ā Do |
Paste the header Copy Link for someone to answer from | Send their Copy Recipient Link |
Wait for an email when a vendor answers | Watch the bell and Ball in Court |
Answer a vendor's question outside Structur | Reply in the RESPONSE box so everyone sees it |
Leave an RFI in Draft after Edit | Click Send RFI again so recipients can answer |
Reopen an RFI without telling anyone | Let recipients know it's open again |
