Skip to main content
For AI agents: a documentation index is available at https://docs.coverbase.com/llms.txt. This page is also available in markdown by appending .md to the URL.
This guide is part of the User Guides collection. It covers the intake template settings under Configuration → Portal Templates, the vendor status settings on its Intake Approval tab, and the Review Stages section of an intake request. It sits beside Requesting a new vendor, which covers the requester’s side, the Analyst and reviewer guide, which covers working the queue, and Reviews, approvals and gates, which covers review gates after intake.
By default one reviewer decides each intake request. Review stages let several teams review it in turn. For example, a category manager approves the business need first, and the third-party risk team reviews the vendor after that. Each stage can approve, and you choose whether it can also send the request back or deny it. The mistake people make most often is editing the stages and expecting requests already in review to follow. A request keeps the stages it started with. Only requests submitted after you save use the new ones.

Before you start

You need permission to edit portal templates. Admins have it. Decide these with the teams involved:
  • The stages, in order, and a name for each that the requester will understand. The requester sees stage names and team names.
  • Who reviews each stage: named people or groups, a role on the vendor, or reviewers routed by the requester’s answers.
  • Which stages may send a request back for changes, and which may deny it.

Add review stages

  1. Open Configuration → Portal Templates and open your intake template.
  2. Find Review Stages. With no stages, it reads One reviewer decides each request. Add a stage to have more people review it in turn.
  3. Click New stage for each stage. A template can have up to 10 stages.
  4. For each stage, fill in:
    • Name, for example “Category manager approval” or “TPRM review”. Each stage needs its own name.
    • Reviewed By: who reviews it. See Who reviews a stage.
    • Reviewers Can: Approve is always on. On the last stage it reads Accept, because approving there accepts the request. Tick Send back for changes and Deny for the stages that may do those.
  5. Put the stages in order. Drag a stage, or use Move up and Move down in its actions menu. Remove stage deletes one.
  6. Save the template.
With two or more stages the section reads Requests go through these in order. Approval at the last stage accepts the request.
A stage that is missing a name or a reviewer is flagged, and the template says how many stages to fix before it saves. If a saved template’s stages stop being valid, for example because the questionnaire a stage routes on was taken off the template, requesters cannot submit the form until you fix them.

A two-stage example

The request goes to category management first. When they approve it, it moves to the third-party risk team, who accept it, send it back or deny it. If category management sends it back, the requester’s resubmission goes straight back to them.

Who reviews a stage

The reviewer is worked out when the request reaches the stage, not when it is submitted. The person who submitted the request is never a reviewer of their own request. If nobody can be found, for example because the matrix has no entry for those answers or the group is empty, the stage goes to the template’s default intake reviewers, and otherwise to your organization’s admins. The stage shows them as the fallback reviewers.

Decide a request at your stage

Open the request. Review Stages shows every stage with its status (Not started, In review, Sent back, Approved or Denied) and a line naming who it is waiting on and at which stage. When the current stage is yours, the buttons are: Reassign moves the stage to another reviewer. They get it in their work queue and by email. Only the current stage’s reviewers, or an admin, can decide a stage. An admin’s decision on a stage they do not review is recorded as made as an admin. If two people act on the same stage at once, the first decision counts and the second person is told Someone already acted on this stage. Here is where the request is now. A stage that is waiting on the requester can still deny the request, if the stage allows denying.

Decide on the request, not its questionnaire

An intake request is decided on the request page, whether or not it has review stages. Only there do its stages, the Intake Approval settings and its checks run. If you open one of its questionnaires from Questionnaires instead, the submission shows Decide on request in place of Accept and Deny, or Open request once there is nothing left to decide. Both take you to the request.

What a resubmission does

When the requester resubmits a request that was sent back, it goes straight back to the stage that sent it, with the same reviewer if one had taken it. The history says how many answers changed. There is one exception. If the requester changed an answer that decides who reviews an earlier stage (an answer the reviewer matrix reads), the request restarts at that earlier stage.

The intake list

The intake list has Review Stage, Waiting On and In Stage For columns, and a Waiting on me filter for the requests at a stage you review.
A request with review stages has to go through them. Bulk deny skips it and asks you to deny it from its page so you can give a reason. A Finalize intake workflow action skips it, and deciding its questionnaire submission directly is refused.

What the requester sees

The requester follows the request under Your request. It shows each stage by name and With the team reviewing it now, and says We’ll email you when it moves on or if they need something.
  • When a stage sends it back, the request shows Waiting on you since the date and Make changes. Nothing moves until you resubmit.
  • When a stage denies it, the requester sees Your request was denied at that stage, with the note written for them.
  • When the last stage accepts it, the vendor is approved for use.
The requester sees stage names, team names and notes written to them. They never see a reviewer’s internal reason or a Note for Later Stages.

Set the vendor’s status as a request moves

An intake request can move its vendor’s lifecycle status when it is submitted, approved and denied. Set this once for your organization:
  1. Open Configuration → Portal Templates and go to the Intake Approval tab.
  2. On the Vendor Status card, choose a status for each of these:
Submitting and denying leave alone a vendor that was already in review or active before the request. In practice:
  • When submitted moves a vendor only while its status is in the Unstarted or Canceled group, such as Created or Denied. A request for a vendor you already use, or a second request while one is in review, leaves the vendor where it is.
  • When denied moves a vendor only while it is still at the When submitted status or in the Unstarted group. A vendor in the Completed group, such as Active, always keeps its status, so a denied request to add a service to an active vendor does not demote it.
  • When approved never moves an active vendor, or one already past the approved status in your organization’s status order. A vendor at Created, at the submitted status, or in a canceled status such as Denied moves to the approved status.
Status groups are explained under Statuses and lifecycle. Every move is recorded on the vendor’s Activity tab as a change made by the person who submitted, approved or denied the request. If you tick Also update the vendor’s status while denying, the status you pick there is applied after the denial, so it is where the vendor ends up.
If a status chosen here is later archived or deleted, choose another. Until you do, approving or denying a request is refused with a message saying so. Submitting is never blocked: the vendor just stays where it is.

Change the stages later

You can edit stages at any time. Requests already in review finish on the stages they started with, and the editor tells you how many there are. New submissions use the new stages.

Require a vendor contact

To make requesters name someone at the vendor:
  1. In the intake template, under Step 2: Additional information, turn on Ask for the relationship owner and vendor contacts.
  2. Turn on Require a vendor contact beneath it.
The requester cannot continue past Additional Information until they add at least one vendor contact with an email. The form says Add at least one vendor contact with an email before continuing.

Block requests for existing vendors

To stop requesters starting a second request for a vendor you already have, turn on Block requests for existing vendors under Step 1: Select vendor in the intake template. With it on, a requester cannot start a request for a vendor that is:
  • Already approved: its last assessment outcome approved it. A vendor whose last outcome did not approve it can be requested again.
  • Already being onboarded: another request for it is open past pre-qualification or waiting for review, or one of its assessments is still running.
The requester sees the vendor’s status in the search results with a lock line saying why it cannot be chosen, and, where the vendor has owners, who to ask. See What the labels on a vendor mean. Coverbase also refuses to link or submit a request for that vendor, so the block holds even when the vendor is named some other way.

Check answers before submission

An intake template checks each request’s answers against what the requester wrote, before the requester submits. The check is on for every intake template.
  1. Open Configuration → Portal Templates and open your intake template.
  2. Under the intake questionnaires, find Check answers before submission. To stop the check, switch it off.
  3. To add your own standards, write them under Answer check rules, one per line. For example: “Names, emails and employee IDs count as PII, including for our own staff.”
  4. Click Save changes.
A rule changes how Coverbase reads an answer. It never creates a flag alone: a flag still needs words the requester wrote. Leave Answer check rules empty to use the standard check. On the request’s Summary tab, Answers checked before submission lists each flagged answer and how the requester settled it. A changed answer shows the old and new answer. A kept answer shows the requester’s reason and the words it disagrees with. To change a kept answer, edit it on the Review Questionnaire tab. For what the requester sees, see The answer check before you submit.

Troubleshooting

Requesting a new vendor

The requester’s side, including the vendor labels and what happens after submitting.

Analyst and reviewer guide

Working the intake queue day to day.

Reviews, approvals and gates

Review gates after intake, with outcomes, quorums and rework.

Permissions and roles

Who can edit templates and decide requests.