Skip to content
English
  • There are no suggestions because the search field is empty.

06.09 Vendor Findings and Offboarding

Record what a vendor review turned up as findings with a likelihood, an impact, an owner and a due date, follow them on the vendor's Findings tab and the Manage Findings page, send one to the risk register or link it to an existing risk, and take a vendor you're leaving through its offboarding checklist to Terminated.

Requires: Vendor Risk Management Extra

A vendor's Findings and Offboarding tabs and the Manage Findings page come with the Vendor Risk Management Extra. Without it, the Findings tab and the menu entry show as locked, and there's no Offboarding tab: a vendor moves from Offboarding to Terminated with Able to Edit Vendors alone.

Why this matters

A review that finds nothing is rare. The SOC 2 report has an exception, the questionnaire admits there's no MFA on the support portal, the penetration test summary lists two highs that "will be fixed next quarter". Each of those is something you've agreed to chase, and most of them get chased in an email thread that nobody can find six months later, when the auditor asks what you did about the exception.

Leaving a vendor has the opposite problem. Everyone remembers the contract end date, and nobody remembers to check that the vendor's accounts were closed and your data came back or was destroyed. A service account or VPN credential that outlives the contract is a classic audit finding, and an easy one to avoid.

The NIST Cybersecurity Framework (CSF) 2.0 asks you to respond to and monitor the risks your suppliers pose, and its supply chain category (GV.SC-10) expects your plans to cover what happens after a relationship ends. The supplier controls in ISO/IEC 27001:2022 Annex A ask the same of supplier agreements and of changes to supplier services. The Vendor Risk Management Extra gives both a home on the vendor. A finding is a tracked issue with a likelihood, an impact, an owner and a due date, and a serious one becomes a normal risk in your risk register. The offboarding checklist is the list of things that must be true before a vendor can be marked Terminated, and SimpleRisk won't let anyone skip it.

Before you start

  • The right permissions. Every part of this article needs Allow Access to "Vendor Risk" Menu and Able to View Vendors, or a permission that includes viewing (Able to Manage Vendors or Able to Configure Vendor Risk Management). On top of that:
  • Able to Run Vendor Due Diligence lets you read findings, on the vendor's Findings tab and on the Manage Findings page, without changing them.
  • Able to Manage Vendor Findings lets you read, add, edit and delete findings, and unlink them from a risk.
  • Create risk also needs Able to Submit New Risks and Allow Access to "Risk Management" Menu. Link existing risk needs Allow Access to "Risk Management" Menu and Able to Modify Risk Details.
  • Able to Manage Vendors lets you work through an offboarding checklist and start one.
  • Moving a vendor to Offboarding needs Able to Edit Vendors. Terminating it at the end of offboarding needs Able to Edit Vendors and Able to Approve Vendors.
  • To choose a finding's owner, nothing more. With Able to Manage Vendor Findings, the Owner list holds every enabled user you can see. If the list can't be loaded, it's greyed out with No users are available to choose as owner. An owner already set is kept., and saving leaves the finding's owner as it was.

Encryption availability. In this release, finding descriptions, remediation notes and offboarding notes are stored as entered, not encrypted. They will be encrypted once SimpleRisk's built-in encryption is available; the Vendor Risk Management Extra does not use the Encrypted Database Extra. Until then, don't put secrets in these fields. After encryption arrives, saving or reading them also needs a working encryption key, and your administrator restores it if it goes missing.

Step-by-step

1. Know what a finding holds

A finding is one issue you found with a vendor and intend to see through. It has:

  • Title: up to 255 characters, and it stays readable in lists even after encryption arrives. It appears in lists, in reminder emails and, if you send the finding to the risk register, as the risk's subject. Keep secrets out of it.
  • Likelihood and Impact: both required, chosen from the same Classic scales you use for risks. SimpleRisk works out the finding's risk score and risk level from them, with the same level names and colors as the risk register.
  • Status: Open, In Progress, Resolved, Accepted or Closed.
  • Source: Assessment, Monitoring or Manual, saying where the finding came from.
  • Owner and Due Date: the person who chases it and when it should be done. Both are optional. A finding with no due date never produces a reminder, and one with no owner reminds the vendor's business owner instead.
  • Description and Remediation notes: up to 20,000 characters each.

Open and In Progress are the open statuses. The other three close the finding, and they mean different things, so pick the one an auditor would expect:

  • Resolved: the vendor fixed it.
  • Accepted: you've decided to live with it. SimpleRisk refuses to save Accepted without Remediation notes, because "we accepted it" with no reason is the first thing an auditor pulls on. The form says Required when the status is Accepted: explain why the risk is accepted.
  • Closed: nothing to do after all, such as a duplicate or a finding that turned out not to apply.

An open finding can move to any status. A resolved, accepted or closed one can only be reopened, to Open or In Progress; the form offers only the moves allowed.

Each open finding with a due date also carries a due state:

  • Overdue: the due date has passed.
  • Due soon: the due date is within the finding lead time your administrator set, 14 days unless they changed it. The boundary day counts.
  • On track: the due date is further out.

A resolved, accepted or closed finding, or one with no due date, has no due state.

2. Record a finding

Open Vendor Risk, then Manage Vendors, open the vendor and choose the Findings tab. With Able to Manage Vendor Findings, select Add finding and fill in the fields above. Title, Likelihood, Impact, Status and Source are required. A new finding starts as Open and its source as Manual. Select Save.

To change a finding, select the pencil button on its row. Only the fields you changed are sent. To remove one, select the trash button and confirm: Delete this finding? Its description and remediation notes are deleted with it. A risk created from it is not deleted. While a finding is being sent to the risk register, it can't be deleted.

The eye button opens Finding details with every field, including the description and notes. Anyone who can read findings can open it.

3. Create a finding from a due diligence review

Findings usually come out of a review. On the vendor's Assessments tab, each record in Assessment history has a Create finding button for users who hold Able to Manage Vendor Findings as well as Able to Run Vendor Due Diligence. It takes you to the Findings tab and opens Add finding with Source set to Assessment and the record named as the Source assessment record, for example Assessment record of 2026-10-15.

The link is kept with the finding. Finding details shows it to users who can run due diligence; to someone who reads findings with Able to Manage Vendor Findings alone, it isn't shown. If the record is deleted later, the finding stays and loses the link.

SimpleRisk doesn't turn questionnaire answers into findings by itself. The Assessments Extra already turns flagged answers into pending risks, and an answer carries no likelihood or impact. You decide what's worth tracking, and Create finding saves you the retyping. Vendor Due Diligence and Reassessment covers the Assessments tab.

4. Follow findings on the vendor and across vendors

The Findings tab shows the vendor's open findings, highest risk first, 25 to a page. Status switches between Open findings and All statuses, and Risk Level, Due Date (Overdue or Due soon) and Owner (All owners, Mine, or one person) narrow the list. Sort By orders it by Risk Level, Due Date, Status or Title. Findings with no due date come last whichever way you sort by date.

For the whole picture, select Vendor Risk, then Manage Findings. The page appears in the menu for anyone who can read findings. It lists open findings across every vendor you can see, highest risk first, with the Title, Vendor, Risk Level, Status, Owner, Due Date, Source and Risk columns. Overdue rows carry the Overdue label and a coloured stripe. Select anywhere on a row to open that finding's details in a window over the list, so your filters, sort and page stay as they are. The window has an Open vendor link to the finding on its vendor's Findings tab. If you can manage findings it also offers the same actions as the tab (Edit, Delete, Create risk, Link existing risk and Unlink risk, each shown only when your permissions allow it) and the list refreshes when you finish one; without that permission you get the details, Open vendor and Close. Filter with:

  • Search, on the title;
  • Status: Open findings (the default), All statuses, or one status;
  • Risk Level, Due Date and Source;
  • Owner: All owners, Mine for the findings you own, then the people in the list (findings managers always get it; readers get it when they can also add or edit vendors);
  • Vendor, with a Search vendors box when there are more vendors than fit in the list.

Select the Title, Vendor, Risk Level, Status or Due Date heading to sort by it. Show sets how many rows a page holds. The vendor's name opens that vendor's Findings tab with the finding's details already open, which is the link to send a colleague.

A Monday habit that works: open Manage Findings, set Owner to Mine and Due Date to Overdue, and clear that list before you add anything new.

5. Send a finding to the risk register

Some findings are big enough to be a risk in their own right: they need scoring against your other risks, a mitigation plan and the review cycle the risk register already runs. Create risk on a finding's row turns it into a normal SimpleRisk risk and links the two.

The dialog offers:

  • Subject: the finding's title, which you can change. The limit is your instance's maximum risk subject length, counted in bytes, so accented and non-Latin characters use up more than one each.
  • Likelihood and Impact: preset from the finding's own likelihood and impact. Choose other levels if the risk warrants it.

Select Create risk. The new risk:

  • has the subject you gave it and the status New;
  • is scored with the Classic method from the likelihood and impact you chose. The vendor's tier never raises the impact;
  • has the finding's owner as its owner, and the vendor's teams as its teams;
  • carries one line of notes, Created from vendor finding ID {id}., and nothing else from the finding. The description and remediation notes are never copied, and neither is the vendor's name;
  • is linked to the vendor, so it appears on the vendor's Risks tab.

From then on it's an ordinary risk. Rescore it, plan its mitigation and review it in Risk Management like any other. Everything that reacts to a new risk on your instance reacts to this one too, the same as for a risk submitted by hand: the new-risk email if the Notification Extra is set up for it, and a Jira issue if you use the Jira integration.

Back on the finding, the Risk column shows Risk {id} with the risk's status, linking to the risk, for anyone with risk access who can see it. Step 6 covers what everyone else sees.

A few things can go differently:

  • Two people press Create risk at once, or someone double-clicks. Only one risk is created. The other gets This finding is being sent to the risk register. Try again in a few minutes. or This finding is already linked to a risk.
  • The risk register refuses the risk. You see The risk could not be created. The finding was not changed. Usually no risk was created. If your Jira integration or another hook failed after the risk was saved, though, a New risk with this subject may exist. Check the risk register before you try again, and if it's there, connect it with Link existing risk instead of pressing Create risk a second time.
  • Your risk form has a required custom field. That doesn't stop Create risk. The finding sends no custom fields, so the risk is created without them; open the risk and fill them in on its form.
  • The risk was created but its scoring or the new-risk email didn't complete. The finding is linked and you see The risk was created and linked, but its scoring or the new risk notification did not complete. Check the risk. Open the risk and check its score. If the score you chose couldn't be saved, the risk gets SimpleRisk's default score instead, and you see The risk was created and linked, but the requested score could not be saved, so it has SimpleRisk's default score. Rescore the risk. Rescore it before anyone works from the register.
  • The risk was created but couldn't be linked. You see Risk ID {id} was created, but it could not be linked to this finding. Use Link existing risk to link it. The risk is kept. Don't press Create risk again; link the risk named in the message.
  • The risk was created but you can't see it. Under team separation, a risk created with the vendor's teams may be outside yours. The finding is linked, and you see Risk ID {id} was created and linked to this finding, but your risk access does not let you see it. Ask a risk manager who can see it to review it. When a link fails as well, the dialog adds If you cannot open or link risk ID {id}, ask a risk manager who can see it to link it to this finding.

6. Link an existing risk, unlink, and repair a broken link

If the risk already exists, perhaps because someone raised it before the review, select Link existing risk and enter its Risk ID. It must be a risk you can see. The risk is linked to this vendor as well, and its links to other vendors are left as they are. Several findings can share one risk.

Unlink risk clears the finding's link and nothing else. The confirmation says so: Unlink this finding from its risk? The risk is not changed or deleted, and it stays linked to the vendor until the vendor is removed on the risk's own form. To take the vendor off the risk, edit the risk's Vendors field.

A link can break without anyone touching the finding. When the risk is deleted, or the vendor is removed from the risk, the finding shows Link broken, and Create risk and Link existing risk come back so you can replace it.

What you see of a linked risk depends on your risk access. The risk's ID, status and link appear only if you hold Allow Access to "Risk Management" Menu and the risk is one you can see. Otherwise the finding says Linked to a risk and nothing more, so a due diligence analyst without risk access learns that a risk exists, not what it is.

7. Know who gets reminded

Unless your administrator has turned vendor notifications off, SimpleRisk emails the finding's Owner once when an open finding comes within the finding lead time (Vendor finding due soon: {title} ({vendor})) and once when its due date passes (Vendor finding overdue: {title} ({vendor})). A finding with no owner goes to the vendor's Business Owner instead.

Each email goes once per finding, due date and person. Move the due date or change the owner and the reminders start again for the new date or owner. The recipient must be able to open the finding: an enabled account with an email address, the Vendor Risk menu, a view permission, Able to Run Vendor Due Diligence or Able to Manage Vendor Findings, and, under team separation, a team that can see the vendor. An owner who can't read findings gets nothing, and the email doesn't fall back to the business owner.

Reminders cover findings of vendors that are Prospect, Onboarding, Active or Offboarding. Resolved, accepted and closed findings, findings without a due date and findings of Terminated vendors never produce one.

8. Offboard a vendor

The Offboarding tab is on every vendor for users who can view the Extra's data. While the vendor isn't in Offboarding, it says When an active vendor moves to Offboarding, its offboarding checklist appears here, and the vendor can then be terminated only once every required step is done.

  1. Start offboarding. With Able to Edit Vendors, an Active vendor's tab has Start offboarding. Confirm, and the vendor moves to Offboarding. Moving it on the Profile tab's Change Status card does the same. Only an Active vendor can move to Offboarding.
  2. Work through the checklist. Moving to Offboarding starts a fresh checklist from the items your administrator has set up. Out of the box there are three, all required: Access revoked, Data returned or destroyed and Final attestation received. Each step has a Done box, a Required marker, who ticked it and when, and Notes of up to 5,000 characters. With Able to Manage Vendors, tick a step when it's done and use the pencil button to record how you know: the ticket number for the access removal, the date of the destruction certificate. Steps can be changed only while the vendor is in Offboarding.
  3. Check the open findings. When you can read findings, the tab says how many the vendor still has, as Open findings: {n}, with a link to its Findings tab. Open findings don't block termination, so decide what happens to them first: resolve them, accept them, or close them.
  4. Terminate the vendor. Terminate vendor appears for users with Able to Approve Vendors and Able to Edit Vendors, and it's enabled once every required step is done. Until then it says This vendor cannot be terminated until its offboarding checklist is started and every required step is done. Confirm: Terminate this vendor? Terminated is final: the vendor cannot be moved to another status afterwards. Anyone else sees Once every required step is done, a user who can approve vendors and edit vendors terminates the vendor here.

The same rule holds wherever the status changes. On the Change Status card, or through the API, terminating an Offboarding vendor is refused without Able to Approve Vendors (Only a user who can approve vendors can terminate a vendor at the end of offboarding.) and while a required step is open. A Prospect or Onboarding vendor you never worked with can still be terminated as before, with no checklist.

If the vendor goes back to Active, its checklist is set aside. Offboard it again later and it gets a new checklist with every step undone, so last year's "access revoked" doesn't count for this year's exit.

A vendor that was already in Offboarding when your administrator turned the Extra on, or upgraded it to this release, has no checklist. Its tab says This vendor is in Offboarding but has no offboarding checklist yet, so it cannot be terminated. Start the checklist to work through the offboarding steps. With Able to Manage Vendors, select Start checklist.

Once a vendor is Terminated, the tab shows its checklist read-only, or This vendor was terminated without an offboarding checklist. Its findings stay listed, but nobody is reminded about them any more.

9. Know who sees what

Nothing more

  • Findings tab and Manage Findings page: Not shown
  • Offboarding tab: The checklist, read-only

Able to Run Vendor Due Diligence

  • Findings tab and Manage Findings page: Read-only, with each finding's source record
  • Offboarding tab: The checklist with the open findings count

Able to Manage Vendor Findings

  • Findings tab and Manage Findings page: Add, edit, delete and unlink; Create risk and Link existing risk with the risk permissions above
  • Offboarding tab: The checklist with the open findings count

Able to Manage Vendors

  • Findings tab and Manage Findings page: Not shown, unless you hold one of the two above
  • Offboarding tab: Tick steps, edit notes and Start checklist

Able to Approve Vendors with Able to Edit Vendors

  • Findings tab and Manage Findings page: As for your other permissions
  • Offboarding tab: Terminate vendor

The evidence and contract permissions show no findings. Team visibility applies throughout: a vendor you can't see contributes nothing to the Manage Findings page, and its findings and checklist don't exist as far as you're concerned.

Things to know

  • A finding's score isn't a risk's score. The level on a finding comes from its likelihood and impact alone. If it matters enough to track against everything else, send it to the risk register, where it's scored and compared with your other risks.
  • The title travels. It's the risk subject when you create a risk, so a risk viewer who can't see the vendor still reads it. Write "Support portal lacks MFA", not "Acme's support portal lacks MFA".
  • Changing the risk doesn't change the finding. Closing the risk leaves the finding open, and the other way round. Close both when the work is done.
  • A checklist keeps the steps it started with. When your administrator adds, renames or deletes a checklist item, vendors already in Offboarding keep their steps. The change applies to the next vendor that enters Offboarding.

Common pitfalls

  • Accepting a finding with a one-word note. The notes are why the risk was accepted. Say who decided, on what basis, and until when.
  • Pressing Create risk again after a link failure. The first press already created a risk. Link the risk the message names instead.
  • Leaving findings without an owner. A finding with no owner reminds the vendor's business owner, or nobody when there isn't one. Pick the person who will actually chase the vendor.
  • Assigning a finding to someone who can't read findings. They're never reminded, and nobody else is either.
  • Terminating with findings open. SimpleRisk lets you, and the reminders stop. Close or accept them first, so the record shows what you decided.
  • Ticking steps without notes. The tick says who and when; the note is the evidence. An auditor will ask how you know the data was destroyed.

Related