What TradeDesk does
TradeDesk collects covered source records, matches them to company and relationship context, groups related evidence and keeps the source trail visible.
METHODOLOGY GUIDE
How TradeDesk turns source records into review-ready evidence
How TradeDesk turns scattered company records into review-ready evidence while keeping the source trail inspectable.
Search is the entry point.Review is the outcome.
01What this page explainsHow records are collected, matched, grouped and kept inspectable.
02Who it is forReviewers, data buyers and product evaluators who need to understand what counts as evidence.
03After readingYou should be able to distinguish source rows, evidence groups, coverage gaps and review prompts.
Quick answer
At a glance
The short version reviewers should understand before reading the detailed methodology.
What it does not do
TradeDesk does not treat every mention as equal evidence, hide weak coverage or turn review prompts into facts.
What users should verify
Open source rows, check dates, review match context and separate observed facts from gaps or prompts.
Method
How it works
Simple steps first, with the detailed source and caveat text below.
- 01
Collect source records
Bring together company filings, ownership records, people links, footprint evidence and connected public records.
- 02
Match and group evidence
Use company numbers first, then names, people, addresses and relationship context where needed.
- 03
Separate facts from prompts
Keep source-backed facts, coverage gaps and review prompts visibly distinct.
- 04
Keep the trail inspectable
Link summaries back to source rows, evidence groups, coverage notes and review checks.
Product surfaces
What users see in the product
The methodology connects directly to surfaces where users inspect evidence or record review work.
Company OverviewThe starting view for identity, filings, status, source coverage and profile context.Ownership and peopleDirectors, PSCs, controlled entities and relationship evidence that explain who is connected.Operational FootprintMapped and unmapped location evidence, address/place context and operational signals where covered.Review WorkspaceThe workflow area for review cases, checks, owners, notes, monitoring and evidence links.Evidence modeA company-profile view for inspecting source-backed rows, grouped evidence and coverage notes.
Labels
What the labels mean
Short definitions for terms that appear across evidence, footprint and review views.
| Label | Meaning for reviewers |
|---|---|
| Evidence group | A review-friendly cluster of related source rows, such as a location, relationship, filing pattern or source family. |
| Source row | The underlying record that supports a displayed item. |
| Address/place evidence | Evidence that an address or place appears in covered records. It is not automatically operating evidence. |
| Operating evidence | Source-backed context that may support real-world activity where coverage supports it. |
| Group scope | Evidence shown through explicit parent, subsidiary, control or relationship metadata. |
| Coverage gap | A source returned no match, is unavailable, is not loaded or is outside the visible plan. |
| Review prompt | A suggested review action or focus area based on available evidence. |
| No match | No matched record was observed in the covered source and current view. |
Detail
Method detail and caveats
Use these sections when you need the source-level detail behind the quick answer.
From scattered records to evidence groups
Company review usually starts across filings, ownership records, address data, people links, footprint evidence and internal notes. TradeDesk brings those records into one review path while keeping the source trail visible.
The methodology is evidence-led: collect records, match them to the right company or group context, group related items, separate what is known from what is missing, then keep source rows and coverage notes available for inspection.
Collect source records
TradeDesk brings together source families that can help a reviewer understand a company view. Coverage depends on source availability, plan access, jurisdiction and matching confidence.
| Source family | Examples | How it supports review |
|---|---|---|
| Company filings | Registry identity, filing dates, officers, PSCs and statutory events. | Frames the company profile and basic source context. |
| Ownership and control | People, controlled entities, parent relationships and control paths where available. | Helps reviewers understand structure before relying on a company view. |
| People links | Directors, PSCs and connected roles found in covered records. | Supports continuity and relationship checks. |
| IP and connected public records | Public-sector records, intellectual property records and other source-linked records where covered. | Adds external context when source coverage supports it. |
| Footprint evidence | Mapped locations, address/place evidence and group-derived footprint signals. | Helps reviewers inspect operational footprint without treating every address as operating evidence. |
Match identifiers, names and relationships
TradeDesk matches records using structured identifiers first, then supporting context such as names, addresses, people and relationship evidence. Matching confidence can vary by source and record quality.
A matched item should remain inspectable. Where a match is weak, unavailable or not observed, the product should make that limit visible instead of filling the gap by assumption.
- Company numbers and registry identifiers are preferred where available.
- Names and trading labels can help, but they need context because names can change or overlap.
- Addresses and places can support grouping, but an address match is not always operating evidence.
- People and relationship records help connect company-only and group views.
Separate facts, gaps and prompts
TradeDesk keeps three things separate: source-backed facts, coverage gaps and review prompts.
A source-backed fact should connect back to source context. A coverage gap explains what was not observed, unavailable or not included in the current plan. A review prompt helps the team decide what to inspect next.
| Item type | Meaning | How to read it |
|---|---|---|
| Source-backed fact | A displayed item supported by source context or a linked record. | Open the source row or evidence group for detail and dates. |
| Coverage gap | A source family returned no match, is unavailable, is not covered or is plan-gated. | Do not infer the missing item exists or does not exist outside the covered view. |
| Review prompt | A suggested review action or focus area based on available evidence. | Use it to prioritise human review, not as an automated outcome. |
Keep the trail inspectable
Every summary should remain connected to evidence, source rows, coverage notes or review checks. The aim is to make the review faster without hiding how the view was assembled.
When coverage is limited, the inspectable trail is especially important. It helps reviewers understand whether the view is supported by multiple source families or by a narrower set of records.
Limits and caveats
What the view cannot prove on its own
These limits keep methodology pages readable without hiding uncertainty.
Coverage varies by source, jurisdiction, company type, plan access and matching confidence.
No match means no matched record was observed in the covered source and current view. It is not proof of absence.
Source rows and evidence groups support review. They are not certification, recommendation or final assurance.
TradeDesk helps teams organise and inspect evidence. The customer team owns the review purpose, policy context and recorded decision.
FAQ
Common questions
What does a no match message mean?
It means the covered source did not return a matched record for that source family in the current view.
Does no match mean the underlying record cannot exist elsewhere?
No. It means no matched record was observed in the covered source and current view.
Why group evidence instead of showing only source rows?
Groups help reviewers navigate repeated or related records, while source rows remain available for inspection.
Can review prompts be treated as facts?
No. Prompts are workflow aids. Reviewers should inspect the linked evidence and coverage notes.
Related pages
Keep reading by review question
How TradeDesk WorksThe product model, evidence links and review workflow.Operational Footprint MethodologyHow to read mapped locations, source rows, evidence groups and footprint caveats.Data Sources & CoverageWhat sources are covered, what no match means and why recency varies.Review WorkspaceHow to read the workspace and run the review workflow.Corrections & DisputesHow to ask TradeDesk to review something that appears wrong or incomplete.Trust CentreSecurity, AI transparency, legal and governance resources.