What TradeDesk does
TradeDesk organises covered public, licensed and source-derived records into source-backed product views.
SOURCE GUIDE
What TradeDesk covers and how to read coverage
What TradeDesk can cover, what unavailable or no-match states mean, and how coverage should be used in evidence-led company review.
Search is the entry point.Review is the outcome.
01What this page explainsWhich source categories can support TradeDesk views and what no-match, not-loaded or unavailable states mean.
02Who it is forBuyers, reviewers and support teams comparing coverage across company, footprint and Review Workspace views.
03After readingYou should know what coverage can say, what it cannot say and how to route corrections.
Quick answer
At a glance
The short version reviewers should understand before reading the detailed methodology.
What it does not do
TradeDesk does not guarantee every source will return a matched record for every company or plan.
What users should verify
Check the source category, coverage state, plan access, freshness context and linked source detail before relying on a summary.
Method
How it works
Simple steps first, with the detailed source and caveat text below.
- 01
Identify the source family
Read whether the evidence comes from registry, ownership, people, footprint, benchmark or review workflow records.
- 02
Match to the company view
Check whether records are matched directly to the company or connected through group relationship evidence.
- 03
Read the coverage state
Separate matched, no-match, not-loaded, unavailable and plan-gated states.
- 04
Check freshness
Use source dates and freshness labels because source families update on different timetables.
- 05
Route corrections
Use Corrections & Disputes when something appears wrong, duplicated, stale or misattributed.
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 |
|---|---|
| Source family | A category of records such as filings, ownership, footprint, benchmark or review workflow records. |
| No match | The covered source did not return a matched record in the current view. |
| Not loaded | The source family has not been loaded into the current product view or pipeline. |
| Unavailable | The field or source family is outside the current view, jurisdiction or source pipeline. |
| Plan-gated | The source or deeper detail may require a different plan or enabled module. |
| Snapshot | A source-defined extract or point-in-time view rather than a live register. |
| Coverage gap | A visible limit explaining what was not observed or not available. |
Detail
Method detail and caveats
Use these sections when you need the source-level detail behind the quick answer.
What TradeDesk can cover
TradeDesk organises source-backed records into company profile, ownership, people, operational footprint, benchmark context and Review Workspace views. Coverage depends on the source family, jurisdiction, source availability, plan access and matching confidence.
A source can be covered generally while still returning no matched record for a specific company or evidence family. Coverage language should describe what is visible in the current view without filling gaps by assumption.
| Source family | What it can support | Review use |
|---|---|---|
| Company registry and filings | Identity, status, filings, officers, PSCs and statutory events. | Confirm the company record and frame the review. |
| Ownership and people records | Directors, PSCs, controlled entities and relationship evidence where available. | Understand control, people context and group relationships before review work moves on. |
| Operational footprint sources | Mapped locations, address/place evidence and environmental signals where covered sources support them. | Inspect operational context while keeping source rows and caveats visible. |
| Review Workspace records | Checks, notes, owners, monitoring and evidence links created by the team. | Keep workflow context attached to the company evidence trail. |
Coverage states
TradeDesk uses coverage states to prevent users from treating absence of evidence as a final conclusion. Read the label, open the source context where available, and keep important decisions tied to evidence the team has inspected.
| State | Meaning | How to use it |
|---|---|---|
| No match | The covered source did not return a matched record in the current view. | Do not infer the record exists or does not exist outside the covered source. |
| Unavailable | The source family or field is not available in the current product view, jurisdiction or pipeline. | Treat that area as outside the current view and use other checks where needed. |
| Plan-gated | The source family or deeper detail may be available only on another plan or enabled module. | Use visible coverage notes to understand what is included in the current plan. |
| Not yet review-ready | A source or derived field exists but is not presented as a stable review field. | Use only the source context the product exposes and keep caveats visible. |
How to interpret no-match results
A no-match result means no matched record was observed in the covered source and current view. It is not a judgement about the company and it is not a guarantee that no relevant record exists elsewhere.
For important review work, combine no-match labels with source dates, company identity checks, footprint scope and any internal review notes before deciding what to inspect next.
Coverage-aware review
- Use source-backed evidence where it is available.
- Treat coverage gaps separately from observed facts.
- Open source rows and coverage notes before relying on a summary.
- Use Review Workspace to capture follow-up checks, decision notes and unresolved evidence questions.
Coverage shows how much relevant evidence is available. Freshness shows recency, not certainty.
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
Does covered source mean every company will have data?
No. A source can be covered while a specific company still has no matched record in that source or view.
Does no match mean there is nothing to review?
No. It means no matched record was observed in the covered source and current view.
Why does coverage vary between companies?
Coverage varies by source, jurisdiction, company type, public disclosure, plan access and matching confidence.
Related pages
Keep reading by review question
Evidence MethodologyHow scattered records are collected, matched, grouped and kept inspectable.Data Freshness & LimitationsHow source timetables, freshness labels and evidence limits should be read.Operational Footprint MethodologyHow to read mapped locations, source rows, evidence groups and footprint caveats.Corrections & DisputesHow to ask TradeDesk to review an issue or data concern.Review Workspace GuideHow reviews, checks, owners, notes and evidence links work together.Trust CentreSecurity, AI transparency, legal and governance resources.