Nonfinal
Issue raised for the first time; a satisfactory response can move the application forward.
A final Office Action raises an unresolved legal problem for the last time during the USPTO examination process. It follows earlier consideration of the issue and places the application in a different procedural posture from a nonfinal action.
USPTO explains that a final Office Action is issued after the examining attorney has previously raised the legal problems. It is the applicant’s last opportunity to respond during examination, subject to the procedures available for the particular case.
As verified September 28, 2026, USPTO guidance states that most non-Madrid final Office Actions have a three-month response period with an optional paid three-month extension. Section 66(a) Madrid applications use a six-month response period. Applicants may also need to consider appeal or reconsideration procedures depending on the case.
As verified September 28, 2026, USPTO guidance states that most non-Madrid final Office Actions have a three-month response period with an optional paid three-month extension. Section 66(a) Madrid applications use a six-month response period. Applicants may also need to consider appeal or reconsideration procedures depending on the case.
Issue raised for the first time; a satisfactory response can move the application forward.
Previously raised issue remains unresolved; the procedural options are different and time-sensitive.
A final-event dataset should be based on the relevant final-action status/event and verification rules, not inferred from a nonfinal code.
A final Office Action should be read together with the earlier prosecution history. The word “final” does not mean the application is instantly dead on the issue date; it describes the procedural posture of the examining attorney’s action. The applicant still has the response/appeal options and deadlines described by current USPTO rules and the specific action.
For data products, a final-action cohort is therefore different from a 641 nonfinal cohort. It should be qualified using the correct final-action event/status and a fresh verification point. Do not infer a final action merely because an application previously received a nonfinal action.
No. A final Office Action is a procedural event during examination. If the applicant does not take a permitted timely step, abandonment may follow, but the events should not be collapsed into one status.
USPTO guidance discusses appeal to the TTAB and requests for reconsideration in appropriate circumstances. The specific options are case-dependent and legal advice should come from qualified counsel.
No. 641 is the historic nonfinal-action-mailed status. Final-action cohorts require the relevant final-action event/status.
A final Office Action is not simply a stronger label for the same event. It reflects a different point in the prosecution sequence because the issue has already been raised and remains unresolved. For research or lead qualification, final and nonfinal cohorts should therefore be represented as distinct lifecycle events.
A current-status field should also be kept separate from the historical final-action event. A case can move again after the action, so a dataset should state whether it is built around the event itself, the current posture at verification, or both.
| Field | Why it matters |
|---|---|
| Serial number | Binds the event and later verification to the correct application. |
| Final-action event / date | Defines the cohort and its freshness. |
| Current case status | Shows what the record looks like at the later verification point. |
| Office Action document | Contains the actual refusals, requirements and instructions. |
| Representation fields | Allows applicant-attorney criteria to be applied separately from examining-attorney information. |
| Qualification timestamp | Makes it clear when the inclusion decision was checked. |
No. They are different lifecycle concepts. A final action can precede later events, while abandonment is a separate application outcome.
Not reliably. The Office Action document is the evidence source for the actual refusals and requirements.
The event date defines when the final action occurred; the current status shows what happened by the later verification point.
Yes when the requested workflow and source data support the qualification criteria. Custom orders should define the event, date window and additional filters explicitly.
Send the target event and date window. We can confirm whether the current data workflow supports the required qualification profile.