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 is for the person who wants to start using a new tool or vendor, not for the risk team reviewing the request. If you are on the reviewing side, see the Analyst and reviewer guide.
Before anyone signs anything, your organization needs to know who the vendor is, what data they will touch, and whether you already pay for something that does the same job. That is what a vendor intake request is for, and it takes a few minutes. Coverbase does most of the typing. You confirm, correct, and decide.

Read this part first

Submitting a request is not approval. It does not authorize you to buy, sign, expense, or deploy anything.
When you finish, your request goes to your security or due diligence team, and they decide it. A vendor record may appear in Coverbase with your request attached, but it sits in Created status. It is not an approved vendor until someone reviews and accepts it. A completed intake form means “asked”, not “allowed”. Wait for the decision before you commit spend or send data.

Two ways to file one

The portal

A three-step form: Select Vendor, Additional Information, Review Questionnaires. Use the link your admin gave you.

Chat

Ask an AI assistant connected to Coverbase. Same request, same queue, no form.
They produce the same thing. Pick whichever you are already using. To file in chat, say what you want in ordinary language. You do not need to use the word “intake”:
I want to start using Northwind Analytics for product analytics.
My team needs a load testing tool and we’re looking at Loadspin. Can we buy it?
Is Acme approved for us to use?
That last one checks first and offers to file a request only if there is not already an approved record.

What you’ll be asked

1

Which vendor, exactly

Coverbase researches the company and shows you what it found: what they do, their website, their headquarters, their trust center. Check it. Two companies called Acme is common, and a request filed against the wrong one is sent back to you. If it is wrong, say so and correct it.
2

Whether you already have something that does this

You are shown existing vendors in your portfolio that cover the same job, and any prior relationship with this vendor. Depending on how your admin configured things, you may also see alternatives found on the web.If an approved vendor already does what you need, using it means no review, no procurement cycle, and no new contract.
3

What you'll use it for

You get a short list of use cases this vendor is commonly bought for, rather than a blank box. Pick one, or type your own if none fit.
4

Which services are in scope

A list of candidate services. You can add one that is not listed.
5

The inherent risk questionnaire

Coverbase does most of this one for you. It answers what it can from public sources and whatever context you provided, then shows you each answer with the reasoning behind it.Check them. Answers Coverbase was confident about are marked as such; the ones it was not are flagged for you to look at first. Anything about your intended use, the data you will send, or your internal owner is yours to answer, because public research cannot find it.If none of a question’s options fit and it offers Other, choose Other and type your answer in the field that opens. When the question requires the text, choosing Other alone does not answer it. Your wording is saved with the request.
Behind the scenes, Coverbase also screens the vendor’s financial stability, security posture, and sanctions status, and checks whether the request duplicates something you already have. You do not have to ask for any of that. It runs as part of the flow, and you see the results.
Which of these steps you see depends on how your organization configured its intake portal. Some orgs turn off web alternatives, or pre-qualification, or prior assessment history. If a step described here does not appear for you, your admin turned it off.

What the labels on a vendor mean

When you search for the vendor, each result that is already in your organization’s records carries a label: Your organization can block new requests for vendors it already has. When it does, an approved vendor or one being onboarded shows a lock line under its label, Already approved, so you can’t start a new request for it or Already being onboarded, so you can’t start another request for it, and you cannot choose it. If you pick it anyway, the form explains why and, where it can, names the owner to ask. Use the vendor you already have, talk to its owner, or choose another vendor.

A vendor contact may be required

Your organization can ask you for at least one contact at the vendor, with an email address. If it does, you cannot continue past Additional Information until you add one, and the form says Add at least one vendor contact with an email before continuing.

Getting through it faster

Give context up front

Anything you already know: the use case, the data types involved, a link to their security page, the team that will own it. Coverbase feeds that into the drafting, so more context up front means fewer questions for you later.
Drafted answers come with a confidence signal. The low-confidence ones usually name what was missing, and they are where your knowledge adds the most. The high-confidence ones mostly need a glance.
A partially answered request is not in anyone’s queue. It sits open until you come back to it. If you do have to stop, you can pick it up later, in the portal or by asking the assistant where your request got to.
Questions about what customer data flows to the vendor drive the whole depth of the review. An optimistic answer here means a review scoped too shallow. If you do not know, say so.

The answer check before you submit

When you open the Submit tab, Coverbase compares each answer you picked from a list with what you wrote in the description, the use case, the follow-up questions and your written answers. This can take up to a minute. If an answer disagrees with what you wrote, you see answers don’t match what you told us, with one card per answer. Each card shows Your answer, the words you wrote under You wrote, and one sentence on why they disagree. For example, you answered No to a question about personal information and wrote that you share employee names and work emails. To settle a card, do one of these:
  • Click Change to and the suggested answer. Coverbase updates the answer for you.
  • Click Keep and your answer, write why your answer is right, then click Keep my answer. The reviewer reads your reason beside the answer.
Submit turns on when every card is settled. Undo reopens a card until you submit. Coverbase flags an answer only when your own words contradict it, and it quotes those words. It does not flag a question your request says nothing about. If the check cannot finish, you can still submit, and a reviewer checks the answers. Your organization can turn the check off.

After you submit

Your request lands in the risk team’s review queue with everything attached: your answers, the enrichment, the screening results, and the duplicate check. Your organization may also move the vendor’s status when you submit, for example to show it is being onboarded. A vendor that was already in review or active keeps its status. See Set the vendor’s status as a request moves. From there one of three things happens:
  • Approved. Onboarding starts and an assessment is created against the right control set, sized to the risk your answers indicated.
  • Sent back. A reviewer needs something clarified. You get a specific question rather than a rejection.
  • Rejected. Usually because an approved vendor already covers the need, or the screening surfaced something disqualifying.
Once you submit, your answers are read-only to you, whatever your role, even if you could otherwise edit questionnaires. The questionnaire says You submitted this request, so its answers are read-only. Reviewers can still see and change answers while they review. If something needs to change on your side, a reviewer sends the request back to you, and only then can you edit your answers again. A reviewer can also return just the fields that need fixing (see If a reviewer returns fields).

Following a request through review stages

Your organization may have your request reviewed by several teams in turn, for example a category manager first and then the risk team. If so, the request shows Your request with each stage by name:
  • With a team means that team is reviewing it. You are emailed when it moves on or if they need something.
  • Waiting on you since a date means a stage sent it back. Click Make changes, update your answers and resubmit. Nothing moves until you do. Your resubmission goes straight back to the stage that sent it, and earlier approvals stand unless you change an answer they depend on.
  • Denied at a stage means the request ended there. Any note the reviewer wrote for you is shown.
  • Accepted means the vendor is approved for use.
You see stage and team names and notes written to you, not reviewers’ internal notes.

Notices while you fill it in

The form warns you as you type when your organization screens requests:
  • A country of concern. The vendor’s headquarters, or an answer about where data is stored or where an entity sits, names a country on your organization’s list. You can still submit. The request gets an extra review.
  • A free email provider. A vendor contact’s address is on a free email domain, such as Gmail. Use the vendor’s company address if they have one. You can still submit, and the reviewer sees the warning.
Two warning notices: Russia is on your organization's list of countries of concern, from High-risk countries, and gmail.com is a free email provider

The two screening notices on the request form.

If your request is closed: Criteria Not Met

Some requests belong in another process, for example small purchases. Your organization can set rules that close those requests as soon as you submit them. You are notified with the reason, and the request shows Closed: Criteria Not Met with the same reason.
Red notice: Closed: Criteria Not Met. Purchases under $1,000 go through the P-card process instead. If you think this is wrong, contact your third-party risk team. They can reopen it.

A request closed by a rule, as the requester sees it.

If you think the close is wrong, contact your third-party risk team. They can reopen the request, and it goes into review without you filing it again.

If a reviewer returns fields

A reviewer can return specific fields for you to correct, each with a comment. You are notified, and the request shows A reviewer returned with the number of fields.
  1. Open the request. Each returned field is highlighted with the reviewer’s comment.
  2. Correct each field. A field that needs an answer cannot be left empty.
  3. Click Resubmit.
Notice: A reviewer returned 2 fields. Vendor website with the comment This is a reseller domain, use the vendor company website, and a text box; Will the vendor process personal data? with a comment and a dropdown; and a Resubmit button

Two returned fields, each with the reviewer's comment, ready to correct and resubmit.

The reviewer sees each value before and after your change. Your request cannot be approved until you resubmit the returned fields.

File a request from MCP or the API

You can file a request from an MCP client by describing what you need. The assistant opens it with mutate(entity="intake_session", action="create"), records your answers with mutate(entity="intake_session", action=...) and submits it with mutate(entity="intake_session", action="submit"). See Vendor intake through MCP. An integration files one with an API key through POST /v1/intake/api/sessions and reads its status with GET /v1/intake/api/sessions/{session_id}. See the Intake API. 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. Approving or rejecting a request stays with a reviewer.

Troubleshooting

Vendor intake in chat

The full conversational flow, step by step, including what your assistant will and will not do on its own.

Analyst and reviewer guide

What happens to your request on the other side, and what reviewers are looking for.