# RFIs Cx Assistant help · platform: mobile · module: rfis · updated 2026-10-03 Canonical: https://cx-assistant.com/en/help/mobile/rfis ## What is an RFI An RFI (Request for Information) is a formal question raised on a project — for example a clarification about a design, a specification, or site conditions — that needs an official answer. Unlike an issue, an RFI is built around getting one authoritative response: it carries a question, a "response needed by" date, watchers who follow it, and an official response that a team member with the right permission promotes from the discussion. ## Opening the RFIs screen and browsing the list Open the drawer (hamburger icon or swipe right from the left edge) and tap RFIs. The list shows RFI cards with infinite scroll — more load automatically as you approach the bottom. The header shows the total count for the project. Pull down to refresh. The search and filter row tucks away as you scroll down and returns when you scroll up; the header with the title and the + button stays in place. ## Search, filter, and sort RFIs To find an RFI: - Type in the search bar; results update after a short pause. Search looks in the RFI title, description, and number. - Tap the Sort & filter button to open the filter sheet. You can multi-select Status, Priority, Type, Assigned to (people and groups), and Created by, and choose a sort order — including "Response needed (soonest first)". Tap Apply. Clear all resets the filters and the sort order. - Active filters appear as removable chips below the search bar — tap a chip to drop that filter. Search and filters combine. ## How to create an RFI Tap the + button on the RFIs screen (requires the rfis.create permission — Project Admins, Project Members, and Technicians have it by default). A create sheet slides up with these fields: - Title — required, up to 100 characters. Phrase it as the question you need answered. - Description — optional; the context and what you need answered. - Priority — required. Your project's default priority is pre-selected when it has one. - Type — optional; shown only if your project defines RFI types. - Response needed by — optional date, picked in a calendar. - Attachments — optional; take a photo, pick from the photo library, or pick a document. - Assigned to — optional; one person or one group, picked from a list (a search box appears on larger teams). - Watchers — optional; tap the members who should follow the RFI. Tap Create to raise the RFI. If you don't see the + button, your role lacks rfis.create — ask a project admin. ## Viewing an RFI — the detail sheet Tap any RFI card to open its detail sheet. It opens read-only first and shows the question, the official response card (if one has been set), properties like status, priority, type and assignee, the "response needed by" date, watchers, attachments, comments, and history. To edit, tap a field: select fields (status, priority, type, assignee) open a compact picker that slides up inside the sheet, and your choice is saved as soon as you tap it; title and description open an inline editor, one at a time — tap Save to keep the change or Cancel to discard it. Attachments: if you can edit the RFI, use the add tile in the Attachments section to take a photo, pick from the photo library, or pick a document. Tap an attachment to open it. ## The official response — setting and clearing it Each RFI can carry one official response — the authoritative answer to the question. It appears in a dedicated card between the question and the properties. To set it, promote an existing comment to be the official response. You can also clear the official response if it was set in error or superseded. Both actions require the rfis.respond permission (Project Admins and Project Members by default). Unlike other RFI edits, there is no shortcut for the creator or assignee here — only rfis.respond holders (or the project owner) can promote or clear the official response. ## Response needed by — due dates and overdue RFIs Each RFI can have a "Response needed by" date — the deadline for the official answer. Tap the date field in the detail sheet to pick it in a calendar sheet. When the date has passed and the RFI is not closed yet, the date turns red and is marked Overdue in the detail sheet, and the RFI shows a red clock icon in the list, so late RFIs stand out at a glance. An RFI stops counting as overdue once it reaches a closing status — setting the official response alone does not close it. ## Watchers — keeping people in the loop The watchers (CC) panel in the RFI detail sheet lets you add project members who should follow the RFI. Open the panel and multi-select the members to watch it. Use watchers for anyone who needs visibility of the question and its answer without being the assignee. ## Changing an RFI's status Tap the Status field in the detail sheet to open the status picker. It only offers the transitions your project's policy allows from the current status — statuses you cannot move to are not offered. Changing status requires rfis.status.update (Project Admins and Project Members by default). The RFI's creator, its assignee, and members of an assigned group can change status even without the permit. ## Commenting on an RFI Use the comments section in the RFI detail sheet to discuss the question — add context, propose answers, or ask follow-ups. Commenting requires rfis.comment, which all built-in roles (Project Admin, Project Member, Technician) hold by default. A comment can later be promoted to the RFI's official response by someone with the rfis.respond permission. ## Who can do what on RFIs — permissions RFI actions are controlled by your project role: - rfis.read — see the RFI list. Default: all roles (Admin, Member, Technician). - rfis.create — the + (New) button. Default: all roles. - rfis.update — edit RFI fields. Default: Admins and Members. - rfis.status.update — change status. Default: Admins and Members. - rfis.comment — comment. Default: all roles. - rfis.respond — promote or clear the official response. Default: Admins and Members; no creator/assignee shortcut. - rfis.delete — delete an RFI. Default: Admins only. Bypass rule: the RFI's creator, its assignee, or a member of the assigned group can edit and change status even without rfis.update / rfis.status.update. The project owner can always do everything. Actions you lack are hidden or disabled — ask a project admin if you need more access. ## RFIs not loading or missing actions — troubleshooting If the RFI list shows an error or stays empty: 1. Pull down to refresh. 2. Clear active search text and filter chips — a narrow filter can hide everything. 3. Check your internet connection, then close and reopen the app. If a button you expect is missing (New, edit fields, status, official response, delete), your role most likely lacks the matching permission — see "Who can do what on RFIs" and ask a project admin. If you have no project yet, join one first from the empty state. If the screen says "You're in My Workspace", open the menu and switch to a project — RFIs live inside a project.