Securing a patent is often seen as the ultimate recognition and an aspirational milestone of an inventor’s hard work, creativity, insight, and risk that led to a new solution, which is worthy of limited exclusivity, and yet the reality of the patent system is far more complex than simply submitting a form and waiting for approval. Many inventors, whether individuals, startups, or large corporations, encounter rejection when their applications are examined by the United States Patent and Trademark Office (USPTO). Understanding why these rejections occur is not only essential for improving your chances of eventual approval but also for avoiding costly mistakes, saving valuable time, and ensuring that your intellectual property strategy remains strong.

In fact, for the vast majority of applicants, the road to a granted patent is neither linear nor swift, and instead reads like an iterative dialogue with the USPTO in which rejections, amendments, arguments, and strategic shifts are the norm rather than the exception. Indeed, modern USPTO data and recurring practitioner experience show that receiving at least one substantive office action is expected rather than surprising, which means that an inventor who treats the patent process as a one-and-done paperwork exercise is almost certain to meet frustration unless they prepare for a process that demands technical clarity, legal precision, and strategic narrative.

Patent rejections are thus not rare or unusual; they are, in fact, the norm. Statistics reveal that between 86% and 90% of patent applications initially receive some form of rejection before being allowed. While this may sound discouraging, it is important to remember that most rejections are not the end of the road. Instead, as aforesaid, they are part of an iterative process in which inventors and patent examiners work through the legal and technical requirements that determine whether an idea deserves protection.

With that in mind, it is important to understand the primary reasons why a patent application might be rejected, ranging from substantive issues of patentability to procedural mistakes in the application itself.

Why Rejections Matter and What a “Rejection” Really Is?

When an examiner issues a rejection, they are not, as a rule, pronouncing the death of your idea; they are identifying deficiencies in meeting statutory requirements or pointing to prior disclosures that undermine your claims. The USPTO typically issues an examiner’s report, often called an office action, in which rejections are categorized and explained, most commonly under 35 U.S.C. §§ 102 (novelty), 103 (obviousness), 101 (subject matter eligibility), and 112 (written description, enablement, indefiniteness), and the applicant is given an opportunity to amend claims, present arguments, or supply additional evidence before final refusal, abandonment, or allowance. The statistics are instructive here, which show that a very large fraction of applications receive at least one non-final rejection, a type of office action, and patent practitioners budget time and resources accordingly because the typical path to allowance involves multiple rounds of examination.

Lack of Novelty

At the heart of every patent system lies the requirement of novelty. For an invention to be patentable, it must be new in every meaningful sense of the word. If the patent examiner finds that the claimed invention, or every essential element of it, has already been disclosed in prior art, your application will face a rejection under 35 U.S.C. §102 of the U.S. patent law.

Prior art encompasses a wide array of sources, including earlier patents, published applications, academic journals, conference papers, existing products, and even public demonstrations. A single piece of prior art that fully anticipates your invention is enough to deny novelty. This is why thorough prior art searches before filing are critical, as they allow inventors to understand the competitive and technical landscape into which their idea fits.

What the examiner looks for: A novelty rejection (35 U.S.C. § 102) is issued when a single prior art reference, which can be a patent, published patent application, journal article, product brochure, public demonstration, or any other public disclosure, discloses every element of a claimed invention as arranged in the claim. The examiner’s claim chart will typically show the reference and map each claim element to language or teaching in the reference; if the map is complete, the claimed subject matter is anticipated and fails the novelty requirement.

Why novelty rejections are deceptively simple: On the surface, novelty rejections feel straightforward; either the exact arrangement appears in the prior art or it does not. But the devil is in the details: claim phraseology, functional language, means-plus-function claims, and claim dependencies all affect whether a reference anticipates. A carefully drafted claim that emphasizes a non-trivial structural or functional difference, and that is supported by examples in the specification, can survive a §102 challenge even where superficially similar references exist.

How applicants respond: Responses typically fall into two categories: (i) amend the claims to recite distinguishing structural or functional elements that are not found in the cited reference, or (ii) argue that the reference does not in fact disclose the claimed combination (for example, because a limitation is missing, the reference requires an inventive modification, or the reference’s disclosure is ambiguous or non-enabling as to the limitation in question). Sometimes, applicants submit evidence showing the reference postdates a priority date.

The novelty requirement is an important check that protects the integrity of the system by ensuring that patents reward true innovation rather than granting monopolies on old or well-known knowledge.

Obviousness

Even if your invention is technically new, it may still fail the obviousness test, which is codified under 35 U.S.C. § 103 of the U.S. patent law. Obviousness asks whether the claimed invention would have been obvious to a person having ordinary skill in the art (often referred to as PHOSITA or POSITA) at the time of invention.

Unlike novelty rejections, which require a single reference, an obviousness rejection often involves a combination of prior art references. If the examiner determines that two or more existing technologies could reasonably be combined to create your invention, they may conclude that your contribution lacks the inventive step required for patentability.

The governing standard: Obviousness under §103 is often the toughest obstacle for applicants because it allows the examiner to use multiple references, combined by logic, to reach a conclusion that the claimed invention is an expected or routine aggregation of known elements, rather than a true inventive step. The controlling judicial standard for how to analyze obviousness was significantly clarified by the U.S. Supreme Court in KSR International Co. v. Teleflex, Inc. (referred to as “KSR”), which rejected a rigid “teaching, suggestion, or motivation” (TSM) test in favor of a more flexible analysis that considers the creativity that would be expected from a person of ordinary skill in the art, common sense, and whether the combination is a predictable use of prior art elements. Post-KSR, examiners and courts may find an invention obvious where the combination of references would have been “obvious to try” or where the prior art provided a reasonable expectation of success in combining elements.

Why §103 rejections are so frequent: Because obviousness looks at the prior art holistically, even genuinely useful and novel tweaks to existing technology can be rejected if the examiner believes the tweak would have been an ordinary engineering or design choice. Technologies where incremental innovation is the norm (electronics, mechanical assemblies, chemical process parameters, software design patterns) routinely see §103 rejections because many permutations of known elements exist in the literature.

Tactics to overcome obviousness: Applicants respond to §103 rejections by: (a) narrowing the claims to claim the actual inventive core, (b) submitting evidence of unexpected results or improved performance compared to prior art, (c) presenting long-felt unsolved needs and explaining why others failed (secondary considerations/evidence of non-obviousness), (d) using expert declarations that explain why the combination was not routine and required skillful ingenuity, and (e) arguing that the prior art references are non-analogous or cannot be combined for technical reasons. When the patent examiner’s combination relies on impermissible hindsight, that is, using the invention as the blueprint to piece together references, counterarguments often stress the lack of motivation to combine the references absent the applicant’s insight.

Overcoming obviousness rejections often requires showing that your invention provides unexpected results, solves a long-felt but unmet need, or offers a unique technical advantage not suggested by the prior art. Expert testimony, detailed technical evidence, and precise claim drafting can all strengthen your argument.

Patent-Eligible and Non-Patentable Subject Matter

Whether an invention is the kind of thing that falls within the statutory categories of patentable subject matter is governed by 35 U.S.C. § 103 of the U.S. patent law, but modern doctrine, shaped heavily by Supreme Court decisions in the U.S., has made that analysis particularly important and, at times, unpredictable, especially for software, diagnostics, and biotechnology claims.

Two landmark Supreme Court decisions in the U.S. frame the current §101 landscape: (i) Mayo Collaborative Services v. Prometheus Laboratories, Inc. (2012) (referred to as “Mayo”), which held that claims directed to laws of nature cannot be salvaged simply by adding routine steps, and (ii) Alice Corp. v. CLS Bank International (2014) (referred to as “Alice”), which articulated a two-step framework for determining whether claims are directed to an abstract idea and, if so, whether they contain an “inventive concept” sufficient to transform the abstract idea into patent-eligible subject matter. These cases have had a profound impact on the patentability of software, business methods, and diagnostics.

More importantly, not all ideas are eligible for patent protection, regardless of how novel or non-obvious they might be. Under 35 U.S.C. § 103 of the U.S. patent law, certain categories are deemed non-patentable subject matter, which include (i) laws of nature (e.g., gravity or natural principles); (ii) abstract ideas (such as mathematical formulas or basic algorithms); (iii) natural products (like unmodified genes or minerals found in nature); and certain business methods or mental processes that can be carried out solely in the human mind.

This type of rejection is particularly common in fields such as software, biotechnology, and financial technologies, where the boundary between abstract concepts and practical applications can be blurry. To overcome such challenges, inventors must show that their claims apply these abstract or natural concepts in a concrete, technical, and inventive way.

Examples that illustrate the problem: (a) Software/business method claims that merely automate a known human activity or apply well-known accounting/financial techniques on a generic computer are frequently rejected under Alice unless the claims recite a novel computer implementation that produces a technical improvement beyond mere automation. (b) Diagnostic claims that simply correlate a biomarker to a disease state may be invalid under Mayo if the claimed steps are conventional laboratory techniques that merely apply the natural correlation.

How to draft for §101 robustness: To survive a §101 challenge, applicants should (a) draft claims that tie the abstract concept or natural law to a particular, concrete technological solution (e.g., a specialized data structure, sensor configuration, hardware/software partitioning, or physical transformation), (b) include detailed specification passages showing how the claimed steps are implemented in practice and why those implementations are unconventional, and (c) where appropriate, emphasize technical advantages and improved functioning of a technological system rather than claiming business goals or mere data organization. For instance, in practice, many applicants move from high-level software claims to method and system claims that recite specific improvements to computer functionality.

Insufficient Disclosure: Enablement and Written Description

Another frequent reason for rejection lies in insufficient disclosure under 35 U.S.C. § 112(a) of the U.S. patent law. This section contains multiple requirements, namely (a) a written description that shows the inventor was in possession of the invention as claimed, and (b) an enablement requirement that the specification teach a PHOSITA or POSITA how to make and use the invention without undue experimentation, and (c) a definiteness requirement (related but distinct) that the claims particularly point out and distinctly claim the subject matter. If your description is vague, incomplete, or leaves out critical steps, the examiner may reject your application. Similarly, failure to disclose the best mode of practicing the invention, the inventor’s preferred way of carrying it out, may also lead to problems, even if the requirement is less strictly enforced today. Drawings, detailed examples, and multiple embodiments are often essential for satisfying enablement. These not only strengthen the application but also make it more defensible in litigation or licensing negotiations.

Courts and examiners scrutinize the specification, examples, and drawings to ensure the disclosure is commensurate with the breadth of the claims. A powerful Federal Circuit decision that shaped the written description analysis is Ariad Pharmaceuticals, Inc. v. Eli Lilly and Co. (referred to as “Ariad”), which clarified that written description is a separate requirement from enablement. Ariad provides that broad functional language without sufficient supporting examples can fail the written description test because it does not prove possession of the claimed invention. Ariad thus reinforces that a specification must include concrete embodiments or representative structures to support broad claim language.

In contrast, enablement interrogates whether the specification provides enough information so that someone skilled in the art can practice the invention across the full scope claimed without undue experimentation. The courts have developed Wands factors, a checklist of eight non-exhaustive considerations, including the breadth of the claims, the nature and predictability of the art, the presence of working examples, and the amount of guidance provided, which are the practical yardstick examiners and courts use to determine undue experimentation. When an art is unpredictable (for example, certain areas of biotechnology or chemistry), patents typically require more detailed examples, working data, and parameter ranges to satisfy enablement.

To avoid § 112(a) rejections: (a) Include multiple detailed examples and working embodiments. (b) Provide experimental data, parameter ranges, and “recipe-style” instructions in unpredictable arts. (c) Use claim differentiation prudently: do not claim enormously broader subject matter than your examples support. (d) Explicitly define key terms used in the claims to reduce ambiguity and support the written description.

Indefiniteness and the Clarity Requirement

Patent claims are the heart of a patent, defining the legal boundaries of what is protected. If your claims are too broad, too vague, inconsistent, or indefinite, the USPTO may reject them under 35 U.S.C. § 112(b) of the U.S. patent law. This represents another requirement, where a § 112(b) rejection for indefiniteness arises when claims fail to particularly point out the invention’s scope. The U.S. Supreme Court’s decision in Nautilus, Inc. v. Biosig Instruments, Inc. tightened the standard for indefiniteness by requiring that claims inform, with reasonable certainty, those skilled in the art (PHOSITA or POSITA) about the scope of the invention; vague or insolubly ambiguous claim terms invite indefiniteness findings. Where the claim uses subjective terms without objective anchors (e.g., “large”, “sufficient”, “substantially”), the specification should contain definitions, objective thresholds, or test methods so that a person skilled in the art can apply the claims with reasonable certainty.  

If a claim might invite indefiniteness, provide explicit numerical ranges, concrete test protocols, or algorithmic boundaries in the specification; include dependent claims that crystallize the preferred embodiments, and avoid purely functional claim language unless it is supported by corresponding structure or steps in the specification.

Thus, claims must be drafted with precision, balancing breadth with clarity to ensure enforceability while avoiding overlap with prior art. Indefiniteness is a particularly dangerous problem, as it renders the scope of the patent unclear. Courts and examiners alike insist that claims must be sufficiently clear to inform the public of what is and is not covered by the patent. Poorly drafted claims can not only lead to rejection but also make the patent vulnerable to invalidation later.

Lack of Utility

Every patentable invention must demonstrate specific, substantial, and credible utility, i.e., the invention has a practical use. If the examiner concludes that the invention lacks a practical application or that the claimed utility is not supported by evidence, the application may be rejected. Claims that lack a real-world application, or that promise speculative or implausible effects, may be rejected.

Utility rejections are less common than novelty or obviousness rejections, but can arise in emerging fields where the usefulness of a technology is uncertain or poorly documented. Further, although less frequent, these can be fatal in certain contexts.

This issue commonly arises in early-stage inventions where efficacy has not been demonstrated (e.g., unvalidated therapeutic compounds claiming broad therapeutic benefits without data) or where the use is inherently non-practical.

Providing experimental results, data, prototypes, working examples, concrete use cases, or credible theoretical reasons showing the claimed invention performs the intended function can help overcome such challenges. Even modest data or clear descriptions of a demonstrated, plausible utility can convert a speculative claim into one that satisfies the utility standard.

Problems with Drawings

Patent drawings are not mere illustrations; they are an integral part of the disclosure. They serve as a visual complement to the written description and can be critical when the invention has spatial or structural aspects. Poorly executed drawings, those that are blurry, incomplete, or fail to comply with USPTO formatting rules, can lead to rejection. In some cases, unclear drawings can also undermine the sufficiency of disclosure. Alternatively, inadequate drawings that fail to show essential elements, are ambiguous, or fail to adhere to USPTO formatting rules and can prompt rejections or requests for replacement drawings.

Additionally, Applicants must ensure that drawings are black-and-white, free of shading or colors, and clear enough to support both the written description and the claims. Investing in professional patent illustration services can avoid costly rejections and delays.

Formalities

Procedural mistakes such as missing fees, failure to file a declaration or oath, incorrect inventorship, or failure to reply to office actions in a timely manner can lead to abandonment or dismissal.

A practical checklist for avoiding formal rejections: (a) Use clear, high-contrast, black-and-white line art in the appropriate sizes and margins. (b) Include reference numerals in drawings that correspond to specification text. (c) File all required declarations, assignments, and fee transmittals. (d) Track reply deadlines carefully and use extensions or RCEs when strategically appropriate.

Provisional vs. Non-Provisional Applications

It is important to distinguish between provisional and non-provisional applications when discussing rejection. Provisional applications are useful tools to preserve a priority date while continuing development. A provisional application is not examined for patentability at the USPTO and therefore cannot be “rejected” in the traditional sense. However, it can fail to establish a proper priority date if it is incomplete, inaccurate, or fails to adequately disclose the invention. So, a defective provisional that lacks sufficient disclosure can fail in its crucial purpose, which is establishing a robust priority date that adequately supports later-filed non-provisional claims, and this means that when the later non-provisional application is filed, the earlier filing date may not be recognized by the USPTO.

Non-provisional applications, by contrast, are subject to full examination and may face rejection on any of the grounds outlined above. The USPTO, while examining the non-provisional application, may find that the non-provisional claims rely on matter not adequately outlined in the counterpart provisional from which it takes its priority filing date, and in this way, the USPTO may deem the earlier filing date as ineffective, exposing the applicant to intervening prior art and undermining the patentability of the subsequent non-provisional application. For inventors who use provisional filings, drafting the provisional with the same care as a non-provisional specification, i.e., with sufficient examples, figures, and enabling detail, pays dividends.

How to Reduce the Risk of Rejection

While rejection is common, it is not inevitable. Inventors can take several proactive steps to strengthen their applications: (i) Conduct a comprehensive prior art search to identify potential novelty or obviousness issues before filing. (ii) Work with a patent attorney who understands the complexities of drafting strong claims and complying with USPTO rules. (iii) Provide detailed and accurate disclosure, including examples, embodiments, and professional-quality drawings. (iv) Be responsive and timely when addressing office actions or examiner communications. (v) Develop a robust invention disclosure process within organizations to ensure that innovations are well-documented from the start.

Conclusion

Patent rejections are far from rare; they are a standard part of the process. Yet, understanding the reasons behind them, from lack of novelty and obviousness to insufficient disclosure, defective claims, and procedural errors, empowers inventors to approach the patent system strategically. A rejection is not necessarily a final defeat but rather an opportunity to refine, clarify, and strengthen your application.

By investing in thorough preparation, professional guidance, and careful attention to both substance and form, inventors can significantly improve their chances of success. Ultimately, the journey through patent rejections and office actions is not just about securing exclusive rights but also about contributing to the body of public knowledge that fuels future innovation. The key lies in persistence, preparation, and precision, qualities that transform the challenge of rejection into a stepping stone toward eventual protection and recognition.