Third-party risk management

Third-party risk starts at intake

Procurement sees a new vendor first. Opstream uses that moment to set the risk tier, run the right assessment and bring the result back to the people who approve the purchase.

Book a meetingSee how it works

Why should third-party risk start at procurement intake?

Procurement starts when someone plans to buy. Third-party risk often starts later, when someone already knows which vendor they want. When the two are separate, risk teams hear about vendors after the decision is made. Intake closes that gap: the request carries the risk data from the first question to the final approval.

When risk work starts late, three things happen. Assessments run on vendors that were never going to be approved. Urgent purchases skip the assessment. Results sit in a separate tool and never reach the approver.

  • Every new vendor request reaches the risk team, not only the ones someone remembers to forward
  • Low-risk purchases move fast because they skip checks they do not need
  • Approvers see risk results next to cost, contract and owner

Procurement leaders responsible for supplier risk often struggle to gain approval for a technology investment business case because they find it difficult to demonstrate a persuasive financial ROI.

Source: Gartner, “Create a Compelling Business Case for Supplier Risk Technology,” Cian Curtin, Martin Shreffler, 18 February 2026. GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally and is used herein with permission. All rights reserved.

Starting at intake helps with that business case. The risk check becomes part of a process the business already uses, and the time saved shows up in procurement cycle time.

How does Opstream run third-party risk at intake?

Opstream turns intake answers into a risk tier, then uses that tier to decide which assessments run. Results return to the request before anyone approves.

  1. Ask the right intake questions. The request form asks about data access, systems touched, spend and category. Answers change the next questions, so requesters only see what applies.
  2. Set the risk tier automatically. A computed attribute turns the answers into a risk tier. You own the formula and the thresholds.
  3. Run only the checks the tier needs. Conditions add a security review, a vendor questionnaire, SOC 2 report collection, a ServiceNow ticket or an Archer record. Low-risk vendors skip what they do not need.
  4. Bring the results back to the request. Assessment status and fields return to the task, so approvers see the outcome next to the contract and the spend.
  5. Keep watching after approval. Reminders and agentic workflows track document expiry and can ask for updated reports from high-risk vendors.

What changes when risk checks move to intake?

QuestionRisk check after contractRisk check at intake
When does the risk team hear about the vendor?After the business picks it, often after signatureWhen the request is submitted
Which vendors get assessed?The ones someone forwardsEvery vendor, at the depth its tier needs
Where do results live?In the TPRM tool onlyIn the TPRM tool and on the request and vendor record
Who approves with the result in view?Nobody, unless they askEvery approver on the request
What happens at renewal?A new manual check, if anyone remembersA reminder or workflow before the date, with the last result attached

Which tools does it connect to?

TPRM and GRC

Native connectors for OneTrust and AuditBoard. An Archer step can create or update a record and read chosen fields back onto the task.

IT service management

Create a ServiceNow ticket from a review task, sync its status and show the ticket number and link on the request.

ERP, CLM and HRIS

Vendor master data, contracts and owners come from the systems you run today, with bi-directional sync.

Opstream connects to 120+ enterprise systems and is SOC 2 Type 2 audited. See all integrations →

Does a person stay in the loop?

Yes. Automation decides which checks run and collects the evidence. People decide whether the vendor is acceptable, and the audit log records each decision.

  • Pre-filled questionnaire answers show their source, and the vendor confirms before submitting
  • Agent findings show what they are based on, so reviewers can check the reasoning
  • Admins choose which steps can approve on their own and which always need a person
  • Audit logs are filterable by date, user and action, and can be exported

This is the rule-based rung of the trust ladder. You can move single steps to hands-off when the results earn it.

Vendor risk checklist for intake

Use these questions on your intake form to set the risk tier before the purchase is approved:

  • Will the vendor access personal, customer or financial data?
  • Will the vendor connect to our systems or hold credentials?
  • What is the expected annual spend and contract term?
  • Is the vendor critical to a regulated process or to revenue?
  • Where is the vendor based, and where will it process data?
  • Do we already have a current SOC 2 report or assessment on file?

Download the full vendor risk assessment checklist →

Third-party risk is one of five use cases that run on the same data model. See all procurement use cases, or read how vendor onboarding picks up where the risk check ends.

Frequently asked questions

What does third-party risk at intake mean?

It means the risk check starts when someone asks to buy, not after the contract is signed. The intake form collects what the risk team needs, such as data access, spend and category. Opstream uses those answers to set a risk tier and run only the assessments that tier needs, before the approval.

How is this different from a TPRM platform?

A TPRM platform runs and stores the assessment. Intake decides when an assessment is needed and makes sure its result reaches the people who approve the purchase. Opstream connects to TPRM and GRC tools such as OneTrust, AuditBoard and Archer, so each tool does its job and the request carries the result.

How does Opstream decide the risk tier of a vendor?

You define it. Intake answers and vendor attributes feed a computed risk score, for example a weighted mix of compliance, security and business criticality. Conditions on that score decide which steps run. A low-risk vendor gets a short path. A high-risk vendor gets security review, a questionnaire and document collection.

Can vendors fill in security questionnaires faster?

Yes. Opstream sends the vendor questionnaire at the right step and can pre-fill answers from the documents the vendor uploads, such as a SOC 2 report or a policy. Each pre-filled answer shows its source, the vendor can edit any answer and nothing is submitted until the vendor confirms.

Does a person still approve high-risk vendors?

Yes. Opstream routes a high-risk vendor to the reviewers you choose and records every decision in the audit log. Automation decides which checks run and collects the evidence. People decide whether the vendor is acceptable. That is the human-in-the-loop control regulated buyers ask for.

What happens after the vendor is approved?

Risk work continues. Agentic workflows watch document expiry dates and can ask high-risk vendors for an updated SOC 2 report. Reminders can run a set number of days before a certificate or contract ends. The risk tier stays on the vendor record, so the next request for that vendor starts with current data.

See third-party risk start at intake

Show us your current risk process. We will map it to intake questions, tiers and the tools you already use.

Book a meeting