Before a company can decide whether to patent an invention, it needs to understand exactly what its engineers have developed. That means gathering enough technical information to evaluate the invention for patentability and eventually turn it into a patent application.
Traditionally, that information is collected through an invention disclosure. But engineers aren't always sure what to include or how much technical detail is necessary. And even after completing a lengthy disclosure form, they may still need to walk a patent attorney through the invention in a follow-up meeting.
So what should a good invention disclosure actually include? And does it need to be a formal document in the first place?
What is an invention disclosure?
An invention disclosure is a record that describes a potentially patentable invention. It typically explains the technical problem the inventors were trying to solve, how their solution works, and what distinguishes it from existing approaches.
In a typical corporate patent process, an engineer or technical team submits the disclosure to an internal IP manager, legal team, or outside patent counsel. They then use the information to evaluate the invention's patentability and commercial relevance before deciding whether to proceed with a patent application.
An invention disclosure is not itself a patent application, and submitting one does not establish a filing date with the United States Patent and Trademark Office (USPTO). It's an internal step that helps companies decide what to patent and gives patent practitioners a starting point for preparing an application.
The format can vary. Some companies require detailed questionnaires, while others use inventor interviews or more structured invention review workflows. Regardless of the approach, the goal is to capture the technical information needed to make an informed filing decision and support the subsequent patent work.
What should a good invention disclosure include?
A useful invention disclosure should explain what the invention does, how it works, and why it matters. While the exact requirements vary by company and type of invention, several key pieces of information should be captured in almost every invention disclosure. Here are the main elements to include.
1. The technical problem the invention addresses
Start by explaining what problem prompted the invention and why existing approaches weren't sufficient. Try to be specific about the technical challenge rather than describing only the broader business objective.
For instance, "improve application performance" doesn't tell a patent practitioner very much. On the other hand, explaining that an existing processing architecture introduces unacceptable latency under certain workloads provides a much clearer starting point.
2. The proposed technical solution
Next, describe what the team developed to address the problem and how it works. This is typically the most substantive part of an invention disclosure.
The explanation should cover the invention's main components or steps and how they work together to produce the intended result. Focus on the actual technical approach rather than just what it accomplishes. Saying that a system "uses AI to optimize resource allocation," for example, doesn't explain how the system makes those decisions or what makes its approach potentially inventive.
3. What makes the invention different from existing approaches
Explain what the inventors believe is new about their approach. It may help to compare the invention with the company's previous implementation or other solutions the team considered.
What specifically changed? Was there a limitation that existing methods couldn't overcome? Does the new approach work differently, or does it achieve a result that wasn't previously possible?
Inventors don't need to establish that their invention is legally patentable. That requires a separate assessment of the prior art. They should, however, explain what they believe distinguishes their work so the patent practitioner knows what to investigate.
4. Important implementation details
Beyond the general explanation of the solution, include the technical details needed to understand how it can be implemented. The relevant information will depend on the invention:
- Software inventions: Explain the logic behind the software and how the relevant parts of the system work together. This might involve describing how data is processed, how decisions are made, or what happens at different stages of an operation.
- Hardware inventions: Describe how the physical components are arranged and interact with one another. Pay particular attention to any design features or mechanisms that are important to how the invention functions.
- Manufacturing inventions: Walk through the manufacturing process, explaining what happens at each stage and which conditions or techniques are important to achieving the intended result.
The objective is to explain the mechanisms that make the invention work, rather than simply describing what the finished system or process achieves.
And if certain details are still being developed, make that clear. The disclosure can still be useful before every engineering decision has been finalized.
5. Alternative implementations
A good invention disclosure should also consider whether the underlying idea could be implemented in other ways.
For instance, an invention might currently use a particular communication protocol even though the technical approach could work with other protocols. That distinction matters because the patent practitioner may be able to pursue broader protection than the specific implementation the team has built.
Identifying alternatives helps patent practitioners understand which parts of the invention are necessary for it to work and which could be changed. This can help them draft a patent application that protects the underlying invention more broadly, rather than limiting protection to the specific version the team has built.
Engineers don't need to speculate about every possible variation. But any known alternatives worth protecting should be documented.
6. Supporting technical documentation
Engineers don't necessarily need to rewrite information that's already documented elsewhere. Existing technical materials can help explain the invention and provide context for patent practitioners.
Useful materials may include:
- Architecture diagrams, flowcharts, or schematics
- Engineering design documents and technical specifications
- Relevant code references or repository files
- Prototype documentation and test results
- Internal presentations describing the technical approach
Be selective about what to provide. A diagram showing the relevant system architecture may be more useful than an entire folder of engineering documents, particularly if the reviewer would have to spend hours identifying which portions matter.
7. Known prior art and related technologies
Include any existing technologies or publications the inventors know about that address a similar problem. These might be competing products, open-source implementations, published patents, or earlier approaches developed within the company.
If the team evaluated existing solutions before developing its own, briefly explain what it found and why those approaches weren't sufficient.
Engineers aren't expected to conduct a comprehensive patent search as part of the disclosure. The purpose is to capture what they already know, providing useful context for the patent practitioner who will investigate the relevant prior art.
8. Inventor contributions and relevant disclosure dates
Beyond the technical information, companies should also capture two important administrative details:
- Inventor contributions: Identify who contributed to developing the potentially inventive concepts and what each person contributed. The initial list of inventors may change as the patent claims are developed, since legal inventorship depends on the claimed subject matter.
- Relevant disclosure dates: Note whether the invention has already been shared publicly through a presentation, publication, product release, or other external communication. Include any upcoming disclosures as well.
Disclosure dates are particularly important because publicly revealing an invention before filing can jeopardize patent rights, especially in countries with strict novelty requirements.
If an invention has already been disclosed or is about to be shared externally, flag it for patent counsel as soon as possible rather than waiting for the normal review process.
What are the different formats for invention disclosures?
If you're setting up an invention disclosure process for your company, you'll also need to decide how employees should submit their ideas. There's no required format for an internal invention disclosure, and you don't necessarily need dedicated software to get started. Here are a few common approaches.
Invention disclosure forms and templates
The simplest option is a standardized invention disclosure form, usually created in Word, Google Docs, or a similar tool. You can use the questions covered above to build a template that employees complete whenever they identify a potentially patentable invention. Once submitted, the document can be reviewed by your internal IP team or forwarded to outside patent counsel.
This approach is relatively easy to implement and works well for companies that only receive a handful of disclosures each year. However, it puts most of the responsibility on inventors to prepare a detailed technical explanation, and managing multiple submissions through documents and email can become cumbersome as filing activity grows.
Inventor interviews and disclosure meetings
Some companies rely on direct conversations between inventors and patent professionals rather than requiring a detailed written submission. During an inventor interview, a patent attorney or other qualified reviewer asks questions about the invention and documents the relevant technical information.
This approach lets the interviewer explore potentially important details that might not come up in a standard questionnaire. However, scheduling interviews takes time, particularly when multiple inventors or engineering teams are involved. It can also be expensive to collect preliminary information if outside counsel attends every meeting.
AI invention capture platforms
More recently, AI-powered invention capture tools have introduced a different approach to collecting technical information. Rather than having engineers complete a lengthy form or schedule a disclosure meeting, these platforms can guide inventors through a conversation about their work, asking follow-up questions to develop the technical details needed for patent evaluation and drafting.
For example, Patentext lets engineers describe their inventions in their own words and develop the technical information through a guided conversation. Teams can also bring existing engineering materials into the process, reducing the need to recreate information that's already documented elsewhere.
Instead of producing a standalone disclosure document that gets passed along to counsel, Patentext keeps the invention record connected to subsequent prior art review, evaluation, and patent drafting. Companies can also work with USPTO-registered practitioners through Patentext Services when they're ready to proceed with an application.
This can be particularly useful for organizations that want to encourage more invention submissions without adding another substantial documentation task to engineers' workloads.
This article is for informational purposes only and doesn't constitute legal advice. Patent laws are complex and vary by jurisdiction. For personalized guidance, consult a qualified patent attorney or registered patent agent.
