Source selection
Identify the appropriate official USPTO source for discovery, current status or document evidence.
Methodology
From Public USPTO Records to Qualified Trademark Intelligence
Our methodology separates discovery, qualification, verification and delivery. The goal is not to collect the largest possible raw dump; it is to produce a dataset whose inclusion rules and important fields can be explained.
Data provenance process
- 1Official source record
- 2Normalize with provenance
- 3Review source conflicts
Data company workflowNormalize / qualify / verify / deliver
On this page
Direct answer
The core quality principle
A record should enter a professional dataset because it matched a defined qualification profile and the inclusion fields were checked against the appropriate source—not simply because a search query returned it.
Data pipeline
Record binding
Bind the row to the correct application or registration identifier.
Normalization
Convert relevant source fields into a consistent schema without collapsing distinct legal/data roles.
Qualification
Apply the product/customer rules for status, event, date, representation, geography, class or contact availability.
Verification
Check the time-sensitive fields that determine inclusion at the required point in the workflow.
Deduplication
Apply batch/global/prior-delivery rules appropriate to the use case.
Evidence / provenance
Retain enough context to explain the qualification result where the workflow supports it.
Delivery QA
Validate the requested columns, encoding and file structure before delivery.
Direct answer
How serial-level customer exclusivity works
Every accepted USPTO application serial is allocated in a private order ledger before delivery. A delivered serial remains assigned to that customer and is suppressed from later orders, even if the same trademark record later changes status or appears in a different product cohort.
A new order is checked against current reservations and permanent deliveries. Requests cannot be fulfilled with ambiguous attorney representation or insufficient available qualified inventory; we confirm any shortage before collecting full payment. This rule applies to dead/abandoned and both age tiers of status 641.
Important interpretation rules
| Data distinction | Quality rule |
|---|---|
| Case status vs goods/services status | Do not substitute a goods/services code for the case-level application status when the product is defined by case status. |
| Applicant attorney vs examining attorney | The USPTO examining attorney is not the applicant’s representation attorney. |
| Domestic Representative vs attorney | These are separate roles and should not be collapsed into one representation flag. |
| Public correspondence email | A public correspondence field is not automatically an independently verified owner-business email. |
| Dead vs abandoned | Dead is a broad state; abandonment is one specific application lifecycle outcome. |
| Counted vs mailed status | Historic counted/not-mailed codes must not be marketed as if the corresponding action had already been mailed. |
Fail-closed handling
Clear match
Include when the required source fields support the qualification decision.
Clear non-match
Reject when the profile criteria are not met.
Ambiguous / incomplete evidence
Prefer exclusion, separate labeling or manual review over guessing.
Quality dimensions we separate instead of blending together
| Dimension | What it controls |
|---|---|
| Identity | Whether the data belongs to the intended serial/registration record. |
| Source provenance | Where a field came from and whether it is a status, event, representation or correspondence value. |
| Qualification | Whether the record satisfies the agreed inclusion/exclusion rules. |
| Freshness | When the relevant event occurred and when the current source was checked. |
| Deduplication | How repeated serials or prior-delivery records are handled. |
| Delivery integrity | Whether the output schema preserves the fields needed to interpret and audit the row. |
Why fail-closed handling is part of quality
A data pipeline should not turn missing or conflicting evidence into a positive classification simply to increase row count. When a qualification rule depends on representation, event identity or another critical field, ambiguity should be excluded or surfaced according to the profile.
This is especially important for trademark lead data because similar-looking fields can represent different roles. Applicant attorney, USPTO examining attorney, Domestic Representative and correspondence information should remain distinct in both qualification logic and delivered explanations.
Methodology questions
Does “verified” mean every field is independently investigated?
No. Verification is scoped to the record, source and qualification fields defined by the workflow. Separate enrichment requires a separate process.
Can trademark data change after delivery?
Yes. Trademark records evolve. A delivery should be understood as a verified snapshot/cohort at the stated time unless recurring monitoring is part of the service.
Do you use official USPTO sources?
Official USPTO systems and documentation are the primary authority for current status, procedure and public record behavior.
Need provenance columns in your order?
Ask for verification timestamps, source references, profile labels or other supported audit fields when we define the dataset.