Office action drafting
Select the refusal type, fill in the case details, upload or review the office action, generate a draft, refine it, and export it.
Hub Page
USPTO Office Action Refusals
Trademark refusals have a habit of looking similar right up until they do not. This hub keeps the USPTO map tidy so teams can move from the refusal type to the right playbook without turning the file into a small expedition.
BRON AI is built for trademark work end to end: office action drafting, comprehensive search with AI analysis, and ELSA for the repetitive paralegal work that keeps matters moving. It also supports UKIPO, CIPO, and EUIPO matters, but this page stays focused on USPTO refusal types.
Start with the refusal
The same office action can want very different arguments depending on the refusal. This table keeps the lane clear.
| Refusal type | What it usually means | Best next page |
|---|---|---|
| Section 2(d) likelihood of confusion | Cited marks, related goods and services, and the confusion question that has to be answered with care rather than slogans. | Open the guide |
| Merely descriptive refusal | The examiner is reading the mark as describing a feature, function, or purpose instead of identifying source. | Open the guide |
| Genericness refusal | The term may be naming the class itself, which means the response has to stay precise and grounded in the record. | Open the guide |
If one office action raises more than one issue, keep each argument on its own lane. That is where the hub earns its keep.
What BRON does with the file
BRON is not a generic legal chatbot. It is built to execute the operational work around the file with human review where it belongs.
Verified source layer
Certified Legal DataBase technology gives BRON a verified source base for case law and jurisprudence when arguments need footing.
That mix of drafting and verified sources is what turns BRON from a prompt box into actual operational infrastructure.
FAQ
A few quick answers for the page itself and for the people landing here without the backstory.
What is this hub for?
It organizes the main USPTO refusal types BRON covers so teams can move straight to the right page instead of guessing which draft path they need.
Does BRON only support USPTO matters?
No. BRON also supports UKIPO, CIPO, and EUIPO matters, but this page stays focused on USPTO refusal work so the structure stays clean.
Why not use one generic office-action page?
Because the drafting problem changes with the refusal. The page structure should change too, and the hub keeps those lanes separate.