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 worksProcurement 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.
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.
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.
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.
| Question | Risk check after contract | Risk check at intake |
|---|---|---|
| When does the risk team hear about the vendor? | After the business picks it, often after signature | When the request is submitted |
| Which vendors get assessed? | The ones someone forwards | Every vendor, at the depth its tier needs |
| Where do results live? | In the TPRM tool only | In the TPRM tool and on the request and vendor record |
| Who approves with the result in view? | Nobody, unless they ask | Every approver on the request |
| What happens at renewal? | A new manual check, if anyone remembers | A reminder or workflow before the date, with the last result attached |
Native connectors for OneTrust and AuditBoard. An Archer step can create or update a record and read chosen fields back onto the task.
Create a ServiceNow ticket from a review task, sync its status and show the ticket number and link on the request.
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 →
Yes. Automation decides which checks run and collects the evidence. People decide whether the vendor is acceptable, and the audit log records each decision.
This is the rule-based rung of the trust ladder. You can move single steps to hands-off when the results earn it.
Use these questions on your intake form to set the risk tier before the purchase is approved:
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.
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.
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.
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.
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.
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.
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.
Show us your current risk process. We will map it to intake questions, tiers and the tools you already use.