Vendor onboarding
Onboard new vendors with a record from the first request
Onboarding goes wrong when a vendor is already in use before anyone in vendor management hears about it. VendorRisk starts the record at the request: an employee asks for a new vendor on a form, the request is approved, and the diligence, risk review and paperwork that follow are assigned to named owners with due dates.
How a new vendor comes on board
An employee requests the vendor
A task form collects the requested vendor's name, a description, and a contact's name and email, so the request itself is captured as a task.The request is approved
Send the task through a review committee. Members approve or reject, and each member's vote is kept on the record.The vendor record is created
The approved request copies straight into the Vendors module, so nobody retypes it.Reviews and documents follow
Send a due diligence questionnaire through the guest portal, complete a risk assessment, and request the documents you need on file.
One launch creates every onboarding step
A multi-step saved task bundles the steps of onboarding, each with its own owner, due date and form. Steps can start together or be released in stages as earlier ones are reached, and a saved scenario presets who owns each step, for example one set of owners for a critical vendor and another for a routine one.
Risk questions answered on the request form
A vendor request form can include the questions from a risk review form. Once the task is completed and the vendor has been added, a risk review can be created from those answers, already filled in, with its risk level calculated when the review is first saved.
Onboarding work and where it is done
| Work | How VendorRisk handles it |
|---|---|
| New vendor request | A task form with a vendor request section. An administrator chooses which standard vendor fields are displayed and which are required. |
| Approval | A review committee, with rules for how many members must approve and who must approve first or last. |
| Watchlist screening | Run watchlist checks from the vendor's page for a name you have just added, against the OFAC, SAM and SCP lists your site uses. |
| Due diligence | A scored questionnaire, filled in internally or sent to the vendor to complete through the guest portal. |
| Risk assessment | An internal review that scores the vendor and lands on a risk level. |
| Required documents | Document requests for items such as insurance certificates and SOC reports, uploaded by the vendor in the guest portal. |
| Signatures | With the Docusign integration, send a document for signature to vendor contacts and internal users, and track the request from the vendor record. |
| Contract | Enter the contract's dates, notice deadlines and provisions, with reminders ahead of the notice and end dates. |
Vendor onboarding: every feature
Request forms you design
Build the form's own questions as yes/no, dropdown, free text, date or file upload items, with skip logic for questions that do not apply.
Requests for services and software too
A task form can be set up as a vendor request, a service request or a software request.
A status for vendors in progress
Define vendor statuses such as Onboarding or In Review. Each status controls where its vendors show up and what can be done with them.
Committee routing by risk level
A risk review form can route to a different committee for each risk level it calculates, or to none at all.
Saved tasks limited by role
A saved task can be offered to everyone, limited to the user roles you choose, or kept to site administrators.
Step owners set automatically
A saved task raised against a vendor can assign its owner to the vendor's own owner instead of a fixed person.
Import the vendors you already have
Load vendors, contracts, contacts and mailing addresses from spreadsheets. A confirmation screen shows what will be added, updated or rejected before anything is saved.
Reviews launched in bulk
Create due diligence reviews for a whole filtered list at once, which suits onboarding waves.
No per-user fees
There are no per-user fees, so you can add as many users as you need.
Common questions
- Can employees outside the vendor management team request a new vendor?
- Yes. Employees request a new vendor through a task form with standard vendor fields, and the approved request copies into the Vendors module. There are no per-user fees.
- Can a new vendor request require approval?
- Yes. Tasks can be routed through a review committee so the request is approved before completion, and a full record shows how each member voted.
- Can different kinds of vendors follow different onboarding steps?
- Yes. You can create as many saved tasks and task forms as you need, and a multi-step saved task can carry scenarios that preset a different owner for each step.
- We already have a vendor list in a spreadsheet. Do we have to retype it?
- No. Download the import template, fill in one row per vendor and upload it. Nothing is written to your data until you approve the confirmation screen.
Related
Start every vendor relationship on the record
Take new vendor requests on a form, route them for approval, and assign each onboarding step to an owner.
Your Next Exam Starts Today
Build the vendor oversight program your regulators expect — before they ask for it.