What TradeDesk does
Review Workspace keeps review cases, owners, checks, notes, decision notes, monitoring and linked evidence in one workflow.
REVIEWER GUIDE
Understand reviews, checks, notes, owners, evidence links and monitoring in one workspace.
Quick answer
The short version reviewers should understand before reading the detailed methodology.
What TradeDesk does
Review Workspace keeps review cases, owners, checks, notes, decision notes, monitoring and linked evidence in one workflow.
What it does not do
Review Workspace does not make the final decision, replace team policy or convert benchmark context into an outcome.
What users should verify
Check the evidence behind each review prompt, assign owners for open checks and record the reasoning behind decisions.
Method
Simple steps first, with the detailed source and caveat text below.
Use the company record as the container for supplier, customer, prospect or portfolio review work.
Make responsibility clear at review or check level.
Capture the evidence tasks that need inspection, follow-up or monitoring.
Use overview, ownership, timeline, footprint and benchmark context to decide what needs review.
Keep reviewer reasoning attached to the company and current review purpose.
Use review history and monitoring to return to the same evidence trail as records change.
Product surfaces
The methodology connects directly to surfaces where users inspect evidence or record review work.
Labels
Short definitions for terms that appear across evidence, footprint and review views.
| Label | Meaning for reviewers |
|---|---|
| Review case | The company review record for the current purpose. |
| Owner | The person responsible for a review or check. |
| Active check | A task or evidence item that still needs attention. |
| Note | Reviewer context captured during review work. |
| Decision note | The recorded reasoning for the current review view or next step. |
| Evidence check | A workflow item linked to source rows, evidence groups or product views. |
| Review history | The activity trail showing what changed, who changed it and when. |
| Monitoring | A way to keep the company in view after the first review. |
| Benchmark | A Review Workspace aid for comparing observed signals with a selected reference group. |
Detail
Use these sections when you need the source-level detail behind the quick answer.
Review Workspace helps teams review companies they care about. It brings together the company overview, ownership and control evidence, timeline events, operational benchmark signals, notes, actions and review activity in one place.
It is designed to help reviewers answer four practical questions: what is the current review view, what evidence supports that view, who owns the next action and what still needs to be checked.
Review Workspace is a review aid. It does not make a formal rating, approval decision, legal conclusion or assurance.
A review is the container for the current company review purpose, status, owner and decision trail. It keeps the team working against the same company context.
Checks are the specific evidence tasks that need attention. Notes capture reviewer context. Owners make accountability clear. Evidence links connect the review back to source rows, evidence groups, coverage notes or specialist views.
| Workspace concept | What it means | How to use it |
|---|---|---|
| Review | The company review record for a supplier, customer, prospect, portfolio or monitoring purpose. | Use it to keep status, owner, notes and decision context together. |
| Check | A task or evidence item that needs inspection or follow-up. | Assign it, update status and link it to relevant evidence where possible. |
| Note | A human reviewer comment or explanation. | Use notes to record context, decisions, caveats and follow-up reasoning. |
| Owner | The person responsible for the review or check. | Use owners to make next steps accountable. |
| Evidence link | A link from the review to source rows, evidence groups, coverage notes or product views. | Use it to keep the trail inspectable after the review moves on. |
The queue shows companies that have been added for review. You can switch between review types such as supplier, customer or prospect, then select a company to inspect.
Overview gives the short executive summary. It shows the review status, owner, decision summary, what is known and what needs action.
Use this section first when you need a quick answer.
Ownership & Control explains who appears to control the company and whether the structure is straightforward, layered or needs review.
Layered ownership does not mean wrongdoing. It means the ownership and control structure may need more context.
Evidence Timeline shows source events in date order. It is the evidence layer behind the review.
Timeline events help you understand what happened, when, from which source and why it may matter.
Operational Benchmark appears inside Review Workspace as a review aid. It compares the company's observed operational signals with a selected reference group.
Use it to decide what to inspect next, then open the evidence timeline, footprint evidence and coverage notes before recording a review view.
Workflow is where review work is managed. It includes actions, notes and review activity.
Actions are tasks that need doing. Notes are human review comments. Review Activity is the audit trail of what changed, who changed it and when.
The Overview is designed to show what matters first.
Use the deeper tabs when you need to inspect the evidence behind the summary.
Ownership & Control helps you understand whether the company's control structure is explainable from available evidence.
If ownership is described as layered or needing review, that does not mean wrongdoing. It means the structure may require more context.
Evidence Timeline helps reviewers move from summary to evidence.
A "No records observed" message means the covered source did not return records for that source family in the current view.
A "Not available" message means that source family is not yet available in the Review Workspace view.
Operational Benchmark is a Review Workspace-only review aid. It uses available source signals to compare the selected company with a reference group.
Changing the reference view changes the comparison group. It does not change the company's observed signal.
The observed signal for the company on that dimension.
The group of companies used for comparison.
The midpoint of the selected reference group.
The middle range of the reference group.
How much source data supports the signal. A strong signal with limited evidence coverage should be treated carefully.
Source events that may require human review, such as court records, Gazette notices, regulatory records, insolvency indicators or filing irregularity signals.
Reference views let you compare the company in different contexts.
Broader reference views are useful for direction. They should not be read as direct peer comparisons.
Reference group examples show the kind of companies used in the comparison. They are not necessarily direct competitors and are not necessarily trading counterparties.
The closest available reference group with enough companies.
Companies with the same SIC, region and size band.
Companies with the same SIC and region.
Companies with the same SIC across the UK.
Companies in the same size band nationally.
Support dimensions group observed source signals into practical areas that help reviewers decide what to inspect next.
Shows whether statutory filing and company-change activity appears current and regular.
Shows whether available filed accounts support an operational profile. Coverage varies by filing type and disclosure level.
Shows whether external sources support real-world operational activity beyond statutory registration. This may include web or domain evidence, public-sector records, IP records, charity or social-impact evidence and organisational scale signals.
Shows how broad the available source coverage is across independent evidence families. Higher evidence density can make the review easier to support. Lower evidence density means the view should be treated with more caution.
Shows whether ownership and control appear explainable from available records. Use Ownership & Control to inspect the underlying evidence.
Shows whether the company's observed structural and filing-change pattern appears stable.
Shows whether financial, filing and external evidence broadly tell a coherent story.
Shows whether covered sources contain events that may require human review. A higher review-event signal means there may be source events to inspect; it does not mean stronger operational support.
Workflow is where the team manages review work.
Actions are tasks assigned to a reviewer or team member. Actions may have an owner, status, due date, notes and activity history.
Notes are human review comments. Use them to record observations, context or review decisions.
Review Activity records workflow changes. It is an audit trail and should explain what changed, who changed it and when.
Monitoring keeps a company in view after the first review. It helps teams return to the same review record when ownership, filings, footprint evidence, source events or internal checks change.
Evidence links keep the workflow attached to source context. A review check can point to a source row, evidence group, coverage note, ownership view, footprint view or benchmark context so the reason for the check remains inspectable.
Completing a review means the reviewer is satisfied that the evidence, notes and actions are sufficient for the current review purpose.
It does not mean the company has been approved or accepted for every purpose.
Review Workspace does not make a final approval, rejection, legal or policy decision about a company.
It does not establish the absence of issues.
It helps reviewers organise evidence, compare observed signals and manage the review workflow.
Limits and caveats
These limits keep methodology pages readable without hiding uncertainty.
Review Workspace is a review aid and does not make final approval, rejection, legal or policy decisions.
Benchmark context should be used to decide what to inspect next, not as a standalone outcome.
A completed review means the workflow was completed for the current purpose only.
Owners, checks and notes are only as complete as the team keeps them.
Evidence links should be inspected before relying on summaries or prompts.
FAQ
No. Review Workspace is a review aid based on available evidence and observed source signals.
No. It means the observed signal is below the selected reference group for that dimension. It should prompt review, not an automatic conclusion.
Not necessarily. They are selected for comparison based on available attributes such as SIC, region or size band.
Not unless TradeDesk has actual relationship data showing that. In Operational Benchmark they should be read as reference examples, not trading relationships.
It means no records were observed in covered sources for that source family in the current view.
Evidence coverage shows how much source data supports the signal. Lower coverage means the view should be treated with more caution.
Review Events are source events that may require human review, such as court records, Gazette notices, regulatory records, insolvency indicators or filing irregularity signals.
No. Use the benchmark as a prompt, then inspect the Evidence Timeline, Ownership & Control and workflow notes.
Check the review focus areas, inspect the Evidence Timeline, review Ownership & Control evidence and complete or assign the required actions.
No. It means the review workflow has been completed for the current purpose.
Related pages