Answers · Invention & Disclosures
How many invention disclosures per engineer per year is normal?
Updated June 2026
The short answer
Commonly cited benchmarks run from roughly one disclosure per ten R&D engineers per year at typical companies to one or more per engineer per year at the most patent-active firms in dense sectors like semiconductors and pharmaceuticals. Treat any single number with suspicion: sector, IP maturity, and how a company counts its engineers all move the figure substantially.
The average also hides the real pattern. Published commentary commonly suggests only about a third of engineers ever submit a disclosure, so a small group of repeat inventors usually carries the per-capita number while most of the organization submits nothing at all.
Why the benchmark range is so wide
Disclosure rates track patent intensity, and patent intensity varies by an order of magnitude across industries. Hardware, semiconductor, and life science companies file along every product cycle; software, services, and integration businesses file far less per engineer even when the engineering is excellent. Definitions blur the picture further: one company counts only R&D engineers, another counts all technical staff, and the same disclosure volume produces very different per-capita rates.
For that reason, the most useful comparison is your own trailing years rather than another company's ratio. A rate that doubled after a process change tells you something. A rate that trails a semiconductor benchmark tells a software company almost nothing.
The metrics that beat the average
If you can only track a few numbers, track these instead of the per-engineer average. Participation rate: what share of engineers submitted at least one disclosure this year. A rising participation rate means the program is reaching new inventors rather than squeezing the usual five. Time to decision: how long a disclosure waits for a verdict, because slow review quietly kills next year's volume. Conversion rate: what share of disclosures become filings, where a 20 to 40 percent disclosure-to-filing conversion is a commonly cited triage band. And roadmap coverage: whether disclosures are arriving from the products that matter, not just the teams that enjoy patents.
Each of these is diagnosable and actionable. An average disclosure count is neither: it cannot tell you whether the problem is recognition, writing burden, or review speed.
What facilitation reveals about the true rate
The strongest evidence that organic submission undercounts invention is what happens when capture is facilitated. Our ipScan sessions reliably surface disclosures in volume, from the same engineers who were submitting little or nothing organically. One Fortune 500 engagement produced roughly 150 invention concepts and more than 80 patent applications with a 98 percent issuance rate.
The gap between your organic rate and a facilitated rate is the size of your capture problem, not your talent ceiling. That reframing matters when leadership reads a low disclosure count as evidence the team is not inventive. In our experience the inventions exist; the pipeline loses them.
Related questions
Is a low disclosure rate a sign our engineers are not inventive?
Almost never. Low rates are usually a process symptom: inventions go unrecognized, the writing burden wins, or past submissions vanished into a slow committee. Facilitated sessions reliably surface inventions from teams with near-zero organic submission.
Should we set disclosure quotas per engineer?
We advise against it. Quotas generate thin disclosures written to hit a number, which clogs review and teaches the committee to skim. Participation rate and time to decision are better levers and have no gaming downside.
How do we benchmark against competitors?
Their disclosures are private, but their filings usually publish within about 18 months of filing. A landscape analysis of competitor filing volume and direction, normalized for company size, is the honest comparison. We run these as part of our analytics practice.
What rate should a 100-engineer organization plan for?
Plan capacity rather than predicting a rate. Size the review committee and disclosure budget for the volume you intend to create through capture practices, then use participation and conversion to tune. A facilitated program can outproduce years of organic submission in days, so capture method dominates headcount math.
Find out what your real rate is
One facilitated session shows you the gap between what your team invents and what your pipeline captures. The discovery call is free.
Talk with Our TeamRelated
ipCapital Group is a consultancy, not a law firm, and nothing on this page is legal advice. Dollar figures on this page are typical market ranges for professional IP services, drawn from published sources and industry experience across a variety of providers. They are not an ipCG quote or rate card; every ipCG engagement is individually scoped and priced. See how our pricing works.