Nonfinal
Raises a legal problem for the first time. Under current USPTO guidance, most non-Madrid applications have a three-month response period with an optional paid three-month extension.
Trademark Lifecycle
Trademark Office Actions: What They Mean and What Happens Next
An Office Action is an official USPTO letter in which an examining attorney identifies legal problems or requirements in a trademark application. Some issues are requirements that may be corrected; others are refusals that must be addressed before registration can proceed.
Office Action review
- 1Official examiner notice
- 2Applicant response + dates
- 3Current case status
Data company workflowNormalize / qualify / verify / deliver
On this page
Direct answer
What is a trademark Office Action?
USPTO describes an Office Action as an official letter from an examining attorney listing legal problems with the mark or application. The applicant must resolve the relevant problems before the mark can register. Some Office Actions require a written response, some issues may be resolved through examiner communication, and some communications may not require a response.
Nonfinal vs final Office Action
Final
Raises a legal problem for the last time during examination after the issue was previously raised. Current USPTO guidance also describes a three-month response period with an optional paid three-month extension for most non-Madrid applications.
Madrid Section 66(a)
USPTO states that Office Action response timing differs for Section 66(a) applications: six months and no extension option.
Common issue families
Likelihood of confusion
A refusal based on conflict with earlier marks under Section 2(d).
Descriptiveness
A refusal that the mark merely describes the goods/services under Section 2(e)(1).
Specimen / use issues
Problems with evidence of use or the relationship between the mark, specimen and identified goods/services.
Identification / classification
Requirements involving goods/services wording or classification.
Domicile / representation
Procedural requirements involving applicant information or counsel where applicable.
Other substantive / procedural issues
The exact Office Action should be read because different actions can contain multiple refusals and requirements.
How to research an Office Action record
Confirm the application
Use the serial number and mark to identify the correct case.
Check TSDR status
Review current status and the event timeline.
Open the document
Read the actual Office Action in the Documents tab rather than inferring the issue from one status code.
Check response timing
Use the current USPTO instructions and the actual action because deadlines can depend on application type and event.
Retrieve and verify the original Office Action
For evidence-based Office Action research, read the source document and confirm its date and current case context before interpreting a status event.
TSDR API Document Retrieval
Learn how supported Office Actions, PDFs and original ZIP files are accessed.
Learn more →TSDR API Status Codes
Separate an historic Office Action code from today's case status.
Learn more →An Office Action event and an Office Action issue are different data layers
The event tells you that an Office Action occurred. The document tells you what the examining attorney actually raised. This distinction is central to professional data work: a status/event filter can identify a cohort, while issue-level products require document evidence or a separate classification process.
That means a dataset described as “Office Action leads” should say whether it is event-qualified only or whether the documents were also classified by refusal/requirement type. The two products can be useful for different buyers, but they should not be described as if they carry the same evidence.
Office Action data layers
| Layer | What it can support |
|---|---|
| Application identity | Serial number, mark and other identifiers bind all later events to the correct record. |
| Office Action event/date | Supports event-driven cohorts and freshness filters. |
| Current status | Shows the later record state at verification and should be kept separate from the historical event. |
| Office Action document | Supports classification of refusals and requirements when reviewed or parsed appropriately. |
| Representation/contact fields | Support separate business qualification rules with provenance and role distinctions. |
| Verification metadata | Documents when the event/current record was checked and which profile produced the inclusion decision. |
Official Office Action sources
Office Action questions
Does every Office Action mean the application will be refused permanently?
No. Nonfinal actions can identify issues that may be addressed. A final action has a different procedural posture, but the actual options depend on the application and issues.
Is status 641 the same thing as every nonfinal Office Action?
641 is a historic case-status code for “Non-final action — Mailed.” The actual Office Action document contains the substantive refusals/requirements.
Can a data provider identify the exact refusal reason from 641 alone?
No. The status code identifies the mailed nonfinal-action event, not every issue in the document. Document-level parsing/review is needed to classify refusal types reliably.
Need current Office Action lead data?
Request a qualified 641 cohort with freshness, representation, class, geography and supported contact-field filters.