Information Requests (RFI)

What it is

An Information Request (RFI) is a structured ask: a set of typed custom fields and/or supporting documents that one or more people fill out. Instead of chasing answers over email, you send a request, the fulfiller answers a clean form, and you see exactly what's outstanding and what's been provided.

RFIs are deliberately generic so they apply across the platform — collect new-hire details during onboarding, exit information during offboarding, vendor security documents for TPRM, audit evidence from a control owner, or any one-off information ask. Each request carries a snapshot of its fields, the response, a status, optional due date, and a deep link back to whatever it's attached to.

Field types

Build a request from typed fields, each optionally required:

• text / textarea — short or long free text
• number, date, email, phone, boolean (yes/no)
• select / multiselect — choose from a fixed option list
• file — the fulfiller uploads a supporting document (stored securely in TATER)

Save a recurring field set as a template (e.g. "New Hire Information", "Vendor Security Docs") so you can re-send it in one click. Templates are managed from TATER Ops → Knowledge → Information Requests → Templates (Admin role).

Internal vs. external fulfillment

Every request is one of two modes:

• Internal — sent to one or more staff fulfillers, who answer from My TATER → My Requests. No extra access needed; the request appears in their queue with a badge.
• External — sent to someone outside TATER (a new hire's personal email, a vendor contact) via a secure tokenized link. They open a clean public page, fill in the fields, upload any documents, and submit — no login required. The link is single-purpose and scoped to that one request.

Creating & tracking requests

Create and track requests in TATER Ops → Knowledge → Information Requests (Auditor+ to create, Admin to manage templates):

• Pick a template or build fields inline, choose internal/external, set fulfiller(s), an optional due date, and reminder cadence.
• The roster shows every request with its status, mode, fulfiller, due date, and age. Send a reminder on anything still outstanding.
• When a response comes in, open it to see the answers and download any documents, then Accept it or Request changes (which re-opens it for the fulfiller with your note).

Status flows open → submitted → accepted, or open → submitted → changes-requested → submitted on a revision. Reminders go out automatically on the cadence you set, and a request past its due date with no response is marked expired.

Fulfilling a request (for fulfillers)

If a request is assigned to you, it appears in My TATER → My Requests with a badge count. Open it, answer each field, upload any required documents, and submit. If the requester asks for changes, the request returns to your queue with their note so you can revise and resubmit. External fulfillers do the same on the secure link they were emailed.

In onboarding & offboarding

RFIs plug directly into the personnel lifecycle. When you onboard a new hire, you can attach an RFI template to collect their information up front — sent externally to the new hire before their start date, or internally to a manager/HR. Offboarding can collect exit information the same way. The request is linked to the People record and tracked alongside the provision/deprovision checklist, access review, and (offboard) the vault recovery task. Trigger it from TATER Manage, the personnel endpoints, or the trigger_onboarding / trigger_offboarding MCP tools (pass rfi_template_id).

MCP / AI access

An AI assistant connected to TATER (via MCP) can manage RFIs end-to-end:

• list_rfi_templates — list reusable templates
• create_rfi — create & dispatch a request (from a template or inline fields; internal or external)
• list_rfis — the request roster, optionally by status
• list_my_rfis — requests awaiting the caller's response
• review_rfi — accept or request changes on a submitted response

This lets an agent, say, "send the new-hire information request to jordan@example.com" or "review the vendor's submitted security docs and accept if complete."

Reporting

TATER Insights → Information Requests (RFI) reports volume and status, completion rate, average time-to-submit and time-to-accept, and the oldest still-open requests — so you can see where information is stuck.

Related

• Document Reviews — post documents for staff to review & sign off (acknowledgement, not data collection)
• Surveys — structured questionnaires & CSAT
• Approvals — the Universal Approval Engine for decisions
• MCP setup — connecting Claude Desktop / API to TATER