Bind the record
Use the trademark identifier and relevant official source to anchor the row to the correct case.
Verification Framework
How We Define Verified Trademark Data
“Verified” means the record and the fields that determine inclusion were checked against the agreed source and qualification profile at a known point in time. It does not mean every public field has been independently validated outside the USPTO record.
Data provenance process
- 1Official source record
- 2Normalize with provenance
- 3Review source conflicts
Data company workflowNormalize / qualify / verify / deliver
On this page
Direct answer
What “verified” means here
A source-verified trademark record is tied to the relevant public USPTO record and checked for the fields that matter to the selected dataset. A qualification-verified record also matched the defined inclusion rules at the verification time.
Verification is therefore a documented data-quality statement, not a promise about legal outcome, future status or the independent identity of every public contact field.
Verification pipeline
Extract and normalize
Map the source fields required by the product into a consistent internal/output schema.
Apply qualification rules
Test status, event, date, representation, geography, class or other agreed conditions.
Check freshness
Verify time-sensitive inclusion fields at the point required by the workflow.
Control duplicates
Apply serial-level, batch-level or prior-delivery rules defined by the order.
Retain provenance
Keep enough source/evidence context to explain why a row was included where the workflow supports it.
Direct answer
Source timestamp is not event freshness
The applicable USPTO status code, date of the qualifying event, and date/time we verified the current case are recorded separately. A 641 event from 30 days ago may not still be the case's current status today; do not market a progressed application as currently in 641 without an explicitly different historical-event scope.
We check applicant-attorney evidence independently from USPTO examining attorney and distinguish Domestic Representative indications. Ambiguous cases fail the strict no-attorney profile until resolved. Cross-customer serial allocations are checked before payment and before delivery.
Verification labels we use
| Label | Meaning |
|---|---|
| Source-verified record | Bound to and checked against the applicable USPTO/TSDR source. |
| Qualification-verified | Matched the explicit dataset inclusion profile at the verification timestamp. |
| Public contact available | A public correspondence/contact field was present in the source used. |
| Enriched contact | Additional contact information obtained through a separately defined enrichment step; not implied by public correspondence data. |
| Verification timestamp | The date/time at which the relevant qualification fields were checked. |
Why timestamps matter
Trademark records can change. A record that qualifies today may have a different status, representation field or lifecycle position later. Time-sensitive datasets should therefore be understood as verified snapshots or defined event cohorts, not permanent facts.
Trademark records can change. A record that qualifies today may have a different status, representation field or lifecycle position later. Time-sensitive datasets should therefore be understood as verified snapshots or defined event cohorts, not permanent facts.
What verification does and does not establish
It establishes
That the record matched the agreed data criteria when checked, subject to the source and workflow used.
It does not establish
That a trademark is legally available, that a person is eligible for a particular legal remedy, or that a future event will occur.
For contact fields
It establishes provenance/availability under the selected workflow; it does not automatically turn a public correspondence field into a verified commercial owner contact.
Verification is field-specific
| Field category | Verification question |
|---|---|
| Record identity | Did we bind the row to the intended USPTO serial/registration record? |
| Lifecycle/status | Did the relevant status or event match the agreed profile at the verification point? |
| Representation | Do the selected applicant-attorney fields support the classification without confusing other roles? |
| Public contact | Was the contact/correspondence field present in the source, and is its provenance preserved? |
| Freshness | Are both the relevant event/date and the verification time clear enough for the order? |
| Qualification result | Can another reviewer understand why the row was included or excluded under the stated rules? |
Source verification is not the same as enrichment
Source verification checks what the relevant official/public trademark record supports. Enrichment is a separate process that may add or independently validate information outside the original source. The website should not collapse those two concepts.
For example, a public correspondence email can be accurately extracted and provenance-tagged without being independently confirmed as the applicant owner’s current commercial email. If a customer needs separately enriched contact data, that requirement should be defined as a different scope.
Need audit-friendly output?
Tell us whether you need verification timestamps, profile labels, source URLs or additional provenance columns in the delivery.