Overview
This article explains all the setup steps for the example RFI introduced in RFI Example: Overview.
It covers the configuration of all the fields, additional settings and required permissions, assuming that you know how the related features work. Find more detailed explanations in the linked HelpCenter articles under each step.
Once completed, you can use this RFI form to create and process RFI tickets, as described in RFI Example: Workflow in Practice.
1. Prepare User Roles
You can create new roles as suggested here or adjust the existing roles of involved users if required.
Read more in Create & Manage Roles.
A single user cannot hold multiple roles within the same project. Each user must be assigned exactly one role.
The example roles shown in use-case articles may not match the roles and permissions configured in your account. Ensure that each user’s assigned role aligns with their responsibilities. In some situations, you may need to create an additional role for a user whose responsibilities are unique or do not fit an existing role.
For example, if a user has the role “Project Manager” and is expected to coordinate RFIs and request Submittals, you must either update the “Project Manager” role to include the necessary permissions or create a new role, such as “RFI & Project Manager.”
Role: Requester
Requesters need a role with the following ticket permissions:
- Create: checked
- View: Tickets that are created by or assigned to the user or a group they belong to
- Edit: All tickets that the user can view
Roles: Responder (Designer) + (Investor)
Responder (Designer) + Responder (Investor) need the same ticket permissions, but separate roles to manage different field edit permissions:
- View: Tickets that are assigned to the user or a group they belong to
- Edit: All tickets that the user can view
Role: RFI Coordinator
The RFI Coordinator doesn't need a specific role, because the coordinator is assumed to have full permissions.
Here we use the Coordinator role only for field permissions in the next step, but we also suggest that the coordinator has full view and edit permission for all fields.
2. Prepare User Groups
Create User Groups
Create two user groups to be able to ask a team of responders to reply to RFIs.
Name the groups and add the responsible users:
- Designers
- Investors
Read more in Create & Manage Groups.
Add User Groups to Projects
Add the groups to any project where you want to use RFI tickets.
Read more in Manage Groups of a Project.
3. Create a List
Create a list for the 'Discipline' list field with values for each discipline e.g. Architechtural, Electric, Plumbing.
Read more in Create & Edit Lists.
4. Create the Form
Create a new form in your PlanRadar account with the name 'RFI'.
Read more in Create & Edit Forms.
5. Configure Form Options
- Keep the default form options for Attachments, Comments and Plan position enabled.
- Enable the Locking form option to allow the ticket to get locked once the RFI is done, to prevent editing of any field values.
- Enable the Numbering sequence form option with 'RFI' as prefix to automatically get a number for each RFI ticket e.g. RFI-1, RFI-2.
Read more in Form Options.
6. Add Fields & Field Groups
Add all the predefined fields, custom fields and groups as listed in the following table:
| Field name | Field type |
| Title | Default |
| Discipline | List (select prepared default list 'Discipline') Optional: Allow multi-selection |
| RFI Coordinator | User |
| Assignee | Default |
| Due date | Default |
| Status | Default |
| Request details | Group |
| Description of request | Long text |
| Document references | Long text |
| Reference files | Long text |
| Cost impact | Checkbox |
| Time impact | Checkbox |
| Safety impact | Checkbox |
| Answer fields for designer | Group |
| Answered by | User |
| Answer | Long text |
| Reference files | Long text |
| Answer fields for investor | Group |
| Answered by | User |
| Answer | Long text |
| Reference files | Long text |
Read more in:
Create & Edit Forms > Add a Predefined Field
Create & Edit Forms > Create & Add a Custom Field
Create & Edit Forms > Layout Elements > Ticket Field Groups
7. Configure Field Permissions
Configure all field view and edit permissions as follows.
All involved roles have view permission for all fields.
Limited editing permissions just prevent users from filling in fields that are not in their responsibility and to make it easier for them to see which fields they should fill in.
| Field name | Edited by |
| Title | Requester |
| Discipline | Requester |
| RFI Coordinator | Requester |
| Assignee | All |
| Due date | Coordinator |
| Status | Coordinator |
| Request details | Requester |
| Description of request | Requester |
| Document references | Requester |
| Reference files | Requester |
| Cost impact | Requester |
| Time impact | Requester |
| Safety impact | Requester |
| Answer fields for designer | Responder (designer) |
| Answered by | Responder (designer) |
| Answer | Responder (designer) |
| Reference files | Responder (designer) |
| Answer fields for investor | Responder (investor) |
| Answered by | Responder (investor) |
| Answer | Responder (investor) |
| Reference files | Responder (investor) |
The Coordinator has edit permission for all fields, but should not edit the request or answer fields.
Read more in Field Permissions.
8. Add the Form to Projects
Add the RFI form to any project where you want to use it for RFI tickets.
Read more in Manage Forms of a Project.
9. (Optional:) Add the Form to Favorites
This step is optional but recommended, as it lets users quickly filter for the RFI form.
Add the RFI form to your PlanRadar account's favorite forms.
Read more in Manage Favourite Forms for the Quick Access Menu.
Comments
0 comments
Please sign in to leave a comment.