Answers · Invention & Disclosures
How do we get engineers to actually submit invention disclosures?
Updated June 2026
The short answer
Stop relying on engineers to write disclosures on their own, and capture inventions through a facilitated funnel instead: gather a large pool of raw ideas broadly, let legal, consultants, and business leaders identify the ones with real patentable and business value, then go back to the engineers for a targeted interview on those. Published commentary commonly suggests only about a third of engineers ever submit a disclosure on their own initiative.
The pattern behind almost every low-submission program is the same. The system asks busy engineers to recognize that their work is patentable, document it at a level a patent attorney can use, and then wait months for a verdict. Each of those steps loses people. Fixing the process recovers far more inventions than incentive tweaks do.
Why submission rates stay low
Three failure points account for most of the gap. First, recognition: engineers are trained to solve problems, and a solved problem feels like ordinary engineering. The clever workaround that took an afternoon rarely strikes its author as an invention, even when it is one. Second, the writing burden: a useful disclosure takes hours of careful documentation, and that time competes directly with sprint deadlines and ship dates. Third, the feedback void: in many programs a submitted disclosure disappears into a review queue for months and comes back, if it comes back at all, with no explanation. Engineers talk to each other. A program that ignored the last submission has already lost the next one.
None of these are motivation problems, which is why incentive programs alone so often disappoint. Cash does little for the engineer who never realized there was anything to submit.
Flip the model from pull to push
The highest-leverage change is to remove the writing step from the engineer entirely. In a facilitated invention session, a trained facilitator interviews a group of engineers about recent problems, workarounds, and design choices, recognizes the patentable material in real time, and captures it on the spot. The engineers spend a few hours talking about work they are proud of. The facilitator and scribe do the documentation, and the inventors review the drafts. Submission volume stops depending on whether engineers enjoy paperwork.
Our ipScan engagements run exactly this way, capturing a large pool of invention concepts in a short, focused engagement and then triaging them for business value. One Fortune 500 engagement produced roughly 150 invention concepts and more than 80 patent applications, with a 98 percent issuance rate. Those inventions were already in the building. The capture process was the missing piece.
Repairs for the standing program
Sessions surface the backlog; a few process repairs keep organic submissions flowing between them. Commit to a decision on every disclosure within weeks, with a reason attached. Recognize inventors visibly: filing announcements, plaques, a named line in the engineering all-hands. Give managers explicit cover to allow disclosure time, because an incentive the manager resents is a dead incentive. And lower the recognition threshold by telling engineers the rule that actually works: you do not decide whether it is patentable, you just flag it, and the review process decides.
Cash awards have a real but secondary effect on top of all this. We cover typical structures and amounts in a separate answer on inventor award programs, linked below.
Related questions
Do cash incentives alone fix low submission rates?
Rarely. Incentives reward engineers who already recognize and document their inventions. The larger losses happen earlier, when inventions are never recognized or the documentation burden wins. Process changes recover those; cash by itself does not.
Should we make disclosure submission mandatory?
Mandates produce volume with poor signal: thin disclosures written to satisfy a quota. Facilitated sessions reach the same engineers through structure instead of compulsion, and the engineers leave feeling interviewed rather than taxed.
How fast should the review committee respond to a disclosure?
Weeks, not months. Two to six weeks from submission to a decision with a stated reason is achievable for most committees and is the single cheapest trust-builder available. Slow, silent review is the most common way programs lose their best inventors.
What does a facilitated capture program cost?
ipScan sessions are scoped as fixed-price engagements, and the business-grade disclosures that follow typically run about $7,000 each, closer to $5,000 in volume programs, excluding attorney and filing fees. Our answer on invention disclosure cost has the full breakdown.
Surface the inventions you already have
A facilitated session turns a quiet engineering team into a large pool of documented disclosures, triaged for business value. Tell us about your team and we will scope a program. 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.