The anatomy of a report
Reports differ by purpose, but the structure is consistent. Identity information establishes who the file belongs to. Findings carry the substantive items. Sources document where each finding came from. Status flags show what is verified, what is disputed, and what was rejected.
- Identity block: legal name, known variations, and the verified identifier the file is keyed to.
- Findings: court records, regulatory actions, filings, licenses, and authenticated firsthand reports.
- Evidence citations: the specific source document behind every single item.
- Review status: verified, pending review, disputed, or rejected and excluded.
- Score context: how the findings translate into a standardized measure.
What never appears
Unverified allegations do not appear. Anonymous claims do not appear. Items a reviewer could not confirm against a source are rejected outright and never reach the report, and the person who submitted them is told.
Hub or Dub does not sell or disclose file contents to outside parties. Information leaves the platform only through a report to a user with a certified permissible purpose, or under a lawful court order signed by a judge and verified through the proper channels.
Reading a report without misreading it
Start with the date on each item, then the source, then the status. An old, resolved matter and an active, verified one look similar at a glance and mean very different things.
If an item looks wrong, do not argue with the conclusion. Challenge the evidence. A dispute that names the specific item and explains why the source does not support it resolves far faster than a general complaint.
