Before you start
You need the Admin role, or a role that can change organization settings, to change the Front Door settings. Triage itself needs permission to review intake requests. Decide three things with your team first:- Which user group is the TPRM Office and which is Supply Chain. Each disposition needs one sign-off from each, by two different people.
- How old a completed assessment can be and still be reused. The default is 12 months.
- Whether an IRQ is required by default, and which intake answers should change that.
Step 1: Configure the Front Door
Open Configuration and choose Front Door.
Configuration → Front Door, with the reuse window, the two sign-off groups and the IRQ scoping rules.
Reuse and Sign-off
IRQ Scoping Rules
Save
Step 2: Mark vendors you must not use
Open the vendor, find the Do Not Use card on the overview, and click Mark Do Not Use. Give a Reason, then click Add to Do Not Use. To take the vendor off the list, click Remove from Do Not Use. The confirmation asks for a Reason for removing, and Coverbase refuses the removal without one. Both reasons are capped at 2,000 characters, and a counter under the field shows how many you have used. Every change, on or off, is recorded in the vendor’s activity with who made it and why. A Do Not Use vendor can still be requested. The requester is warned that a reviewer must approve an exception, and approving the request needs an override rationale (step 6).Step 3: Open a request
Open Intake in the left navigation and choose the request. The request opens on the Front Door tab. Submission shows the requester’s answers. If the request started as a purchase requisition in a connected procurement system, a Started From Procurement card shows the Source, Value, Category and when it was Synced. See Integration Hub.Step 4: Is this new?
The Is This New? card compares the request with your vendors.Check the IRQ answers
The IRQ answer check flags each inherent risk questionnaire answer that the request itself contradicts, so a wrong answer does not lower the tier. Coverbase runs it in the background when the request is submitted. The card sits on the request’s Summary tab, above Suggested Inherent Risk Profile, and the Front Door review shows a count such as 2 to review that opens it. The check reads the request’s description, use case, products and services, intake context, answers to follow-up questions and the descriptions of the services in scope. It compares them with every answer picked from a list on the request’s IRQs. It flags an answer only when a source states a fact that makes the answer wrong. A source that says nothing about a question is not evidence.
The IRQ answer check with two flagged answers. The first raises the Cybersecurity tier; the second leaves the tier unchanged.
- The question, what was Answered and what the Description suggests.
- One or more quotes, each with the source it came from. Coverbase discards a flag whose quote is not word for word in its source.
- The effect on the tier, for example Cybersecurity: High → Critical, or Tier unchanged.
- Use “Yes” (the suggested answer) changes the answer. The IRQ is scored again, and the tier impact of the other open flags on that questionnaire is worked out again.
- Keep “No” (the given answer) asks Why keep “No”?. Write what the description gets wrong, or why the answer still holds, and click Confirm. The reason is required.
Step 5: Decide reuse and record the disposition
When a similar engagement has completed due diligence, Proposed Reuse by Domain lists each risk domain with its Prior Result and a Proposal: Reuse prior due diligence, Abbreviated review or New due diligence. Change any proposal you disagree with. Then pick the Disposition:- Add as new engagement, reuse due diligence reuses the domains you marked for reuse.
- Extend the existing engagement treats the request as an amendment. No new engagement is created.
- Full new due diligence ignores prior results.

A recorded disposition awaiting sign-off. The TPRM Office has signed, and Decline sits beside Approve triage for the Supply Chain group.
Decline a disposition
To send a disposition back instead of signing it, click Decline beside Approve triage. Only a member of a sign-off group that has not signed yet can decline, and only before the disposition is decided. Write the Reason (what needs to change before your group can sign off) and click Decline and send back. The reason is required. What a decline does:- The disposition goes back to the TPRM Office as a draft, labeled Back with the TPRM Office. Any sign-off already given is cleared.
- The disposition shows who declined, for which group, and why. The Audit Trail records the same.
- The TPRM Office and whoever recorded the disposition are notified with the reason. The requester is told that the TPRM Office is revising the decision.
- Nobody can sign off or decline until the disposition is recorded again.

A declined disposition, back with the TPRM Office, with the decline in the audit trail.
Decide from Microsoft Teams
With Teams approvals on, Coverbase posts one card for both sign-off groups, and each group can sign off or decline from it. Declining from Teams does the same as Decline in Coverbase. A card for a disposition that has since been revised is refused, so nobody signs a decision they did not see. A sign-off or decline made in Coverbase also updates the Teams card. The card then shows who signed and which group is still waiting, the decided disposition, or who declined and why, and it cannot record a second decision.What happens when it is decided
- The IRQ is sent once. If an IRQ is required, the templates go to the requester as soon as the second sign-off lands. If the request has no vendor or requester yet, the card says Required but not sent yet; click Send IRQ once it does.
- Reuse waits for the next assessment. The vendor’s next assessment launched from an assessment plan drops the control sets for reused domains and copies the prior scores for them, labeled with their source. Zero Touch assessments do not use it.
Step 6: Handle a Do Not Use vendor
When the vendor is on the list, a banner names it and shows the reason. Enter an Override rationale and click Record override before approving the request. Approval without one is refused. The override applies to this request only, and is kept in the audit trail.Step 7: Ask the requester
Click Send back with questions, write one or more questions, and Send. The requester is notified and answers inside their request, including an anonymous requester on a public portal. Questions and answers stay under Questions for the Requester and in the Audit Trail.Budget and material change
Two more cards appear when the requester filled in the matching intake steps.- Budget. Shows the request amount, its amortization and First year’s draw against the synced budget line’s remaining balance, with Within budget or Exceeds budget. Coverbase works this out from the synced line, not from figures the requester typed. A line the procurement system reports no committed figure for shows Unknown. If the requester asked for a budget exception, Approve exception or Decline exception, with an optional Decision rationale.
- Material Change. For an existing vendor, lists what the requester flagged as changed, such as a new offshore location, a new AI use case or a new subprocessor, with Needs IRQ refresh. Refresh IRQ opens an IRQ refresh on the engagement’s monitoring plan for its Transaction Owner to answer. See IRQ refresh.
Close requests that do not meet your criteria
A Front Door rule can close a request as Closed: Criteria Not Met the moment it is submitted, before anyone reviews it. Use it for requests that belong in another process, for example small purchases that go through a purchasing card. To add one, open Configuration → Front Door, click New rule, and add the Conditions as for any IRQ scoping rule. Set the Outcome to Close: Criteria Not Met and write the Reason the requester sees. The reason is required, because the requester reads it. Click Update rule, then Save.
An IRQ scoping rule with the Close: Criteria Not Met outcome, listed with the rules that require the IRQ.
- The request’s status is Closed: Criteria Not Met. The Front Door tab shows the reason and Closed by the rule with the rule’s name.
- The requester is notified with the reason. A requester who filed through a public portal without signing in gets it by email.
- The request is still screened (see Screen for countries of concern and free email domains), but no review stage starts and no extra reviewer gets a task while it is closed.
- The Audit Trail records the close with the rule and the reason.

A request a closing rule closed, with the reason the requester sees and the Reopen button.
Reopen a closed request
To put a closed request back into review, click Reopen on the callout. Give a Reason for reopening if you want one (it is optional), then click Reopen request. You need permission to update intake requests across the organization. Admins have it.
The reopen confirmation. The reason is optional and goes into the audit trail.
- The portal’s configured review stages start, or resume where an earlier submission left them, so the request still needs every sign-off.
- If the screening found a country of concern, the extra reviewer group gets its review task and notification.
- When the Front Door is turned on for your organization, the IRQ answer check is queued.
Screen for countries of concern and free email domains
Coverbase screens every submitted request against your organization’s reference lists. It flags a vendor, data location or entity in a country of concern, and a contact on a free email domain. The requester sees the same notice while filling in the form, and can still submit. To set it up, open Configuration → Front Door and go to Screening.
Screening settings: the country list and extra reviewer, the location questions, and the free email list.
What reviewers see
On a flagged request, the Front Door tab opens with a notice that names each country and where it was found, the list it matched, and the group asked to review it. That group gets a work queue task, Country of concern review, once per request.
A country of concern notice, routed to the extra reviewer group.

The Screening card on a flagged request.
Return fields to the requester
To ask the requester to correct specific answers, return those fields instead of sending a question. The requester edits only the fields you mark, and you see each value before and after.- On the request, click Return fields.
- Under Request details and Intake answers, tick each field that needs to change. You can return up to 30 fields at once.
- For each field, write What needs to change. A comment is required on every field.
- Click Return to requester.

Return fields to the requester. Request details are listed above the intake answers, each with its current value.

Two returned fields after the requester resubmitted, with each value before and after.
Run the Front Door from MCP
You can work the Front Door from an MCP client, as well as in the dashboard. An MCP client reads withquery_questionnaires(kind="intake_triage") and query_questionnaires(kind="intake_triage_config"). It writes with mutate(entity="intake_triage", action=...) (set_identifiers, set_disposition, sign_off, decline_signoff, override_block, send_irqs and the rest) and mutate(entity="intake_triage_config", action="update").
Before an MCP client sends a write, it shows you the change and waits for you to confirm it. The MCP tool reference lists every field.
The public API has no Front Door routes, so an API key cannot do any of this.