What’s in this guide
Each part stands on its own, so you can jump to the stage you need.Part 1: Get the vendor into Coverbase
Part 2: Create the assessment
Part 3: Collect the evidence
Part 4: Find your way around
Part 5: Work the issues
Part 6: Run follow-up cycles
Part 7: Reviews and quality control
Part 8: Complete and export
Before you start
You will move faster with these to hand:- The vendor name, website, and a security contact email address.
- Any evidence you already hold: SOC 2 report, policies, pen test results, certificates of insurance.
- The vendor’s Trust Center URL if they publish one. Adding it to the vendor record lets Coverbase pull documents straight from the trust center later, saving a round trip.
- An Assessment Plan that matches the depth of review you need. Plans bundle the control sets, questionnaires, and collection method, so choosing the right one is most of the setup.
- Permission to create vendors and assessments. If a button described here is missing, check your role with an administrator.
Two terms worth pinning down
Inherent risk vs residual risk
Inherent risk vs residual risk
Assessment Plan
Assessment Plan
Part 1: Get the vendor into Coverbase
An assessment attaches to a vendor record, so the vendor has to exist first. There are two ways to get one in.- The Intake module: the standard path. A requester submits the vendor through a portal, answers a short set of questions, and Coverbase produces an inherent risk score as a by-product. You end up with a vendor record and a risk profile in one pass.
- Manual creation: the New Vendor wizard in the dashboard. Faster if you only need the record, but it does not establish inherent risk on its own.
Path 1 (recommended): through the Intake module
Intake determines how much risk a vendor introduces before anyone looks at their documentation. It answers two questions: what is the use case, and what is the scope? Why this is the better path. The inherent risk result drives which control sets apply and how deep the assessment goes. A consulting vendor with no system access should not be assessed like a core processor, and intake is what tells Coverbase the difference. Intake is completed by the requester (the business owner asking for the vendor) through a portal separate from the main dashboard. It runs in three steps: Select Vendor, Additional Information, Review Questionnaires.Name the vendor and describe the use case

1 Use cases tailor the questions that follow. 2 Pre-Qualification catches duplicates before you onboard.
Scope it to services, if relevant

Optional scoping, with the Confirm section beneath it.
Answer the clarification questions

Clarification questions, generated for this vendor and limited to what public sources cannot answer.
Review the autofilled questionnaire
- A confidence badge: green High confidence where the evidence was clear, amber Review this response where it was not.
- Reasoning: why Coverbase chose that answer, with links to the sources it used. Expand it with Read more.
- Answered / Reviewed checkboxes: track your way through the list.
- Select supporting documents: optionally attach evidence to a response.

1 Tabs split answered from flagged. 2 Amber means low confidence, so read these. 3 Reasoning shows the sources behind the answer.
Submit

1 Submit when ready. 2 Responses cannot be edited afterwards, so review first.
Path 2 (alternative): creating the vendor manually
Use this when you only need the record: a vendor being logged for administrative reasons, a supplier inherited from elsewhere, or a case where you already know the risk profile and will set it yourself.Open the Vendors page and click New Vendor

The + New Vendor button sits at the top right of the Vendors page.
Search for the vendor (step 1 of 3)
Create vendor from scratch: "{your vendor}". Click it or press Enter.
Selecting a match pre-fills the vendor. The arrow marks the create-from-scratch option, used when nothing matches.
Fill in the details (step 2 of 3)

1 AI Autofill populates the record from public sources. Only Vendor Name is required.
- Website, Description, HQ Location, Use Cases: context the AI draws on during assessment.
- Security Contact Email: used when Coverbase contacts the vendor.
- Trust Center URL: enables Retrieve from Trust Center in Part 3.
- Services: you can then assess a single service rather than the whole vendor, which keeps scope tight.
- Vendor Contacts: these pre-fill every document request and follow-up you send.
- Tags: tags can drive which control sets apply, so if you tag by tier, do it now.
- Risk Analysts, Relationship Owners, Watchers: ownership and notification.

2 Add Service. 3 Add Contact. 4 Add Tags. Then Next, bottom right.
Custom fields and create (step 3 of 3)

Custom fields vary by organization. Create Vendor finishes the wizard.
Part 2: Create the assessment
Open the Assessments page and click New Assessment

If the list looks empty, clear the filters or switch back to All assessments. Filters you add persist between visits.
Add the vendors and any services

1 Add as many vendors as you need. 2 The plan summary tells you what you are about to run.
Choose the Assessment Plan

1 Configure opens Assessment Settings, where plans live. 2 Plans are built and named by your team.
Check the name, then create

1 Expand to see the template. 2 Live example. 3 The template itself.
Part 3: Collect the evidence
Open the Documents tab. A Collection mode badge shows whether this assessment is collecting manually or automatically. In manual mode nothing is collected until you start it, and five routes are offered. They combine freely, and each card tells you how much is available before you click. In automatic mode the cards are replaced by the collection’s progress through its stages, with Pause and How collection works beside it and Switch to manual in its actions menu.
1 Existing vendor docs. 2 Request from vendor. 3 Switch to automatic. 4 Coverbase Library. 5 Trust Center. The badge shows the current collection mode.
- Import from existing vendor docs: anything already on the vendor profile. Fastest route for a reassessment.
- Request from vendor: manages the assessment portal, and shows the portal’s current status so you can see where the vendor has got to.
- Request automatic collection: switches this assessment to automatic collection.
- Import from Coverbase Library: documents Coverbase collected for this vendor itself, by requesting them from the vendor and retrieving what the vendor publishes on its trust center. Check the count; for well-known vendors it is often substantial. Nothing your organization uploads is ever part of this library. See Document library.
- Retrieve from Trust Center: pulls from the vendor’s public trust center. Only available with a Trust Center URL on the vendor record.
If you are using the portal, send the request

1 Upload area. 2 Each section the vendor must complete; Submit stays disabled until required items are done.
Wait for analysis

1 The stage tracker. This workspace has added a Quality Control stage of its own. 2 A shortcut to whatever the assessment needs next.
Part 4: Find your way around the assessment
There is a lot on this page. Three areas matter.The left panel
Current stage, what it is waiting for, and a shortcut into the work. Once results are ready it also offers an Export menu. Below that, Details holds the assignee, inherent risk, risk target, and services, followed by cards for the Plan the assessment came from, its Control Sets, its Questionnaires, and custom Properties. The Actions menu at the top right of the page holds Rerun, Clone, Cancel run, Export, and Archive.The tabs
Once results are in, eleven tabs run across the top. Most of the time you need the first two, Summary and Issues. The rest carry supporting detail and the audit trail: Controls, Findings, Emails, Work Queue, Documents, Activity, Notes, Properties, and SLAs.The Properties tab
Properties groups fields by the record they belong to. The Assessment tab holds the assessment’s custom fields, in their sections, and the assessment system fields selected for the view. The Vendor tab holds the vendor fields selected for the view, and each service the assessment covers gets a tab of its own with that service’s fields. Configure view chooses which vendor and service fields appear; the choice applies to every assessment in the organization. When no vendor or service field is selected, the tab shows the assessment fields alone.The Summary tab
Once an outcome or a recommendation has been recorded, Recommendation sits at the top: the human conclusion. It appears in exports, so write it properly rather than leaving it thin. Then a band showing the Score as a percentage with a compliance band, how many domain reviews are complete, and Complete Assessment. Then the risk domain table: a row per domain in scope, each with the assessment score for that domain, the assigned reviewer, and the review status. Domains vary by plan; a broad plan can produce nine or more, covering things like AI & Emerging Technology, Operational Resilience, Concentration & Fourth-Party Risk, and Reputational & ESG alongside the familiar Data Security and Privacy. Rows reading “Not started” or “Unassigned” have not been reviewed yet. Those are your gaps. The switch above the table changes whose profile it shows. Assessment is this assessment’s results. Vendor is the vendor’s current inherent and residual risk by domain, and each service the assessment covers has its own entry, so a relationship owner can see how the vendor-level assessment compares with their service. The vendor and service views are read-only here; edit those scores on the vendor or service page.
1 Recommendation. 2 Score, review progress, and completion. 3 Risk by domain. 'Not set' means not yet reviewed.
Relationship owner attestations
When relationship owner attestations are turned on for your organization, completing an assessment asks each relationship owner of a covered service to confirm its results. Each owner gets a work queue item naming the services they own. Opening it lands on the Summary tab with the Relationship Owner Attestations card highlighted. The owner reads the statement, selects the services the attestation covers, and chooses Acknowledge or Dispute. A dispute needs a reason, and it raises a work queue item for the assessment’s assignee. The card lists every owner’s standing per service: awaiting, acknowledged with the date, or disputed with the reason. On a disputed row the assignee chooses Request again, which asks that owner once more for that service, or Close dispute. The statement owners confirm is set under Assessment Settings, in the Relationship Owner Attestation section. Leave it empty to use the default.Part 5: Work the issues
The Issues tab holds one result for every control in the assessment. It opens filtered to the results raised as issues.Reading the top of the page
- Risk domain selector: narrow to a single domain.
- Control Score: the score out of 100%.
- Open Issues: open count against the total.
- Vendor Score (Service Score on a service-scoped assessment): inherent and residual risk.
Orient yourself in the list

1 Switch between all results and issues. 2 Grouping. 3 Status chips, weight, and result on every row.
Handle the straightforward ones in bulk

1 The bulk action bar appears once anything is selected. The arrow marks the row checkboxes.
Open an individual result

1 Correct the AI, Rerun, Preserve, Edit. 2 Actions available for this state.
Follow the citation to the source

1 The cited passage, highlighted in the source document. 2 Step through results without returning to the list.
Read what the vendor said about a control
Part 6: Run follow-up cycles
Follow-ups are drafted individually and sent together, so the vendor gets one consolidated request rather than a trickle of emails.Draft the follow-up

1 AI Autofill drafts the question. 2 Name the documents you need. 3 Save creates a draft, it does not send.
Send them

1 Manage what has been sent. The workbook and import options sit in Actions beside it. 2 How many follow-ups are out, and how many are still drafts.
Let the reanalysis run

1 Response received. 2 The score after reanalysis. 3 Preserved pins this result against future runs.
Part 7: Reviews and quality control
Each risk domain can carry its own reviewer, which is what lets several teams work one assessment: InfoSec on the security domains, Legal on the contractual ones, Compliance on regulatory. The Summary tab reports progress as a count of completed reviews. A reviewer opens their domain with Start review. Domains show Not started until someone does, and their residual risk stays “Not set”.
1 Start review. 2 'Not set' until reviewed. 3 Reviewer per domain. 4 Complete Assessment, next to the review count.
- Reviewers are set per domain or control set and can be changed until that domain’s review is complete.
- Reviewers are notified when results are ready for them.
- Risk analysts and administrators can resend reminders.
- Restrict assessment completion to risk analysts and admins, in Assessment Settings > Workflow, stops anyone else from completing assessments.
Part 8: Complete and export
Complete the assessment

Completion sits alongside the score and review progress.
- Action: approve, reject, or whichever outcomes your organization uses.
- Vendor Status: where this leaves the vendor in its lifecycle, for example Active. A service-scoped assessment asks for Service Status instead.
- Next Vendor Reassessment Date: set for you based on risk tier and the date you completed, typically a year out. Change it if this vendor needs watching sooner.
- Recommendation: the written conclusion that appears in exports.

1 The next reassessment date is set automatically. 2 Outcome and vendor status. 3 The recommendation carried into exports.
Export the results

1 Export Report. 2 The formats, chosen by audience. Word appears only with a custom report template.
Where a vendor’s score comes from
An assessment writes its residual risk to whatever it was scoped to. A vendor-scoped assessment moves the vendor’s score. A service-scoped assessment scores those services and, by default, leaves the vendor’s score unchanged. This is why a service assessment can come back high while the vendor profile still reads medium. Risk Roll-up carries the service score up to the vendor. Once an administrator turns it on for a risk type (see Step 5 of the admin setup guide), a vendor takes the highest score among its services instead of carrying its own. Services with an inactive, discontinued, or denied status are excluded. Risk domain rows roll up as well as the overall score. A vendor’s Data Security row follows the highest Data Security score among its services.Overriding it for one vendor
Open the score on the vendor’s Risk Profile and use Automatically infer from services. With it on, the services set the score. The Risk Score field is read-only and Clear risk score is hidden, because the next change to the services would overwrite anything you entered.
Following services. The score field is disabled and Clear risk score is absent.

Overridden. The score is editable, with Use organization default above it.
Run assessments from MCP or the API
You can create, follow, correct and close out assessments from an MCP client, and most of it with an API key. An MCP client reads withquery_assessments(kind=...) (search, detail, summary, evals, run_status, follow_up_sections). It writes with mutate(entity="assessment", action=...) (start, update, rerun, resume, complete), mutate(entity="eval", action=...) and mutate(entity="follow_up_section", action=...).
With an API key, create one with POST /v1/assessments and read it with GET /v1/assessments/{assessment_id} on the Assessments API. Documents go through the Documents API, and evals, follow-ups and reruns through the Assessment administration 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.
Completing an assessment and recording its outcome have no API route, so a person does them in the dashboard or through MCP. An API key cannot close an issue on evals. Accepting an eval rerun’s result works only through MCP.