What should an R&D team do when the patent committee decides not to file?
A committee's decision not to file does not make the invention public, and it does not stop someone else from patenting it later. If the company has decided not to patent it, does not need to keep it confidential and is authorised to disclose it, defensive publication may be an alternative: publish a sufficiently detailed technical description before anyone files a relevant application, so that it may serve as prior art, to the extent of what it actually describes. This is especially relevant for improvements that are useful but too incremental, too narrow or not commercially important enough to justify the cost of a patent. Publication is public and permanent, and it may prevent the company from patenting the disclosed subject matter itself. This guide is about an internal decision not to file; a patent office refusing an application that was already filed is a different situation.
Why a patent committee may decline an invention
Patent committees weigh technical merit, patentability, commercial relevance, cost and the wider portfolio. The reason for the decision matters, because defensive publication is not the right answer every time.
Useful, but the cost isn't justified. An improvement can have value but be too narrow to justify drafting, filing, prosecuting and maintaining a patent family. For example, an engineer improves the adjustment mechanism of an industrial component: assembly gets easier, but not enough to set the product apart. Possible alternative: if the company is comfortable letting others use it, publish the technical details so the solution is available as prior art.
Too incremental for the patent strategy. The budget goes to core platforms and features that give a real competitive advantage; smaller improvements stay unpatented, even though competitors or suppliers could use them. Possible alternative: publish the specific improvement and its relevant technical variants, to keep them available to the industry.
Not new or inventive enough. An internal review may find earlier patents, publications or products. First understand what is already public: republishing it adds little. There may still be undisclosed technical details or alternative implementations worth documenting, if they are authorised for disclosure. Describing something as "obvious" in a publication doesn't make it unpatentable; the effect depends on the actual technical disclosure, its date and the applicable law.
The company doesn't want exclusivity. It may want suppliers, customers, partners or even competitors to use a defined solution without the risk of a later patent on it. Possible alternative: a deliberate defensive publication records the technical teaching publicly, to keep it available.
When defensive publication makes sense
| Situation | Is publication worth considering? |
|---|---|
| The committee declined because the expected benefit doesn't justify the cost. | Yes, if the company wants the solution to remain available to others. |
| The improvement is useful but too incremental for the patent strategy. | Yes, provided the details and variants are not already adequately disclosed elsewhere. |
| The committee found prior art that already describes the same solution. | First assess what is already public. Republishing the same information may add little. |
| The company still wants to keep the process or know-how secret. | No. Public disclosure undermines confidentiality and may destroy trade-secret protection. |
| A related patent application is still being considered or may be filed later. | Not yet. Don't publish until the patent strategy has been reviewed and approved. |
| Ownership, employee-invention rights or third-party confidentiality are unresolved. | Not yet. Don't publish until authority to disclose is established. |
The key question is not "Can we get a patent?" but: "Now that we have decided not to patent this solution, do we want it kept confidential, or available for others to use?" If the answer is "available", defensive publication is one route.
A practical example: a sensor mount the committee didn't approve
A fictional example to illustrate the decision. It is not a real company case or a technically validated invention.
The situation. An industrial equipment manufacturer develops an improved mounting for vibration sensors on production machinery. Today an engineer has to loosen several fasteners, reposition the sensor and retighten everything. The R&D team develops a mount that lets the sensor be repositioned and locked much faster, and submits an invention disclosure. The committee decides not to file: useful, but its commercial impact is too limited for the patent budget. The team asks: what happens to the mount now?
Option A: do nothing. The details stay in internal files. They may later surface in a product, a service manual or supplier documents, but nobody deliberately publishes the complete technical teaching. Another company could independently develop a similar mechanism and patent it. Internal records can prove when the idea was developed, but they are not public prior art just because they exist.
Option B: keep it a trade secret. This suits know-how that gives a lasting advantage and can realistically stay secret. But it conflicts with the wish to let other manufacturers use the mount freely, and it doesn't stop someone else from independently developing and patenting it.
Option C: publish a defensive disclosure. Suppose the company confirms that the decision is final, no related application is being prepared, it owns the information and is authorised to publish it, nothing needs to stay secret, and it is prepared to let others use the solution. It can then publish a detailed technical disclosure.
What the disclosure should describe. Not "an adjustable sensor mounting bracket", but the actual implementation:
- The base: how it attaches to the machine frame and supports the adjustment mechanism.
- The guide: the shape and arrangement of the rail along which the sensor carrier moves.
- The locking mechanism: how a locking element engages the guide or a set of indexed positions.
- The sensor interface: how the sensor attaches to the carrier, and how vibration coupling or isolation is arranged.
- The operating sequence: release, move, select a position, lock again.
- The implementation: dimensions, materials, tolerances and operating conditions where known.
- The alternatives: other mechanisms or configurations the team actually developed or considered and may disclose.
Drawings would show the assembly, the components, the lock and the adjustment sequence. The disclosure should describe what the team actually knows, not invent details or add vague lines meant to cover every possibility.
What publication can achieve. If it is public and detailed enough, the disclosure may become prior art against later applications covering what it discloses. A later application still needs individual assessment by the patent office or court. Publication gives the company no exclusive right, and does not establish that it is free to use every implementation, because other patents may cover different or broader features. The aim is narrower: a public technical record that may help prevent later patent claims from restricting the disclosed solution.
What a useful technical disclosure should contain
A disclosure intended to serve as prior art must do more than show that an idea existed. It must explain the technical teaching clearly enough for a skilled person to understand and carry it out: the enablement standard. The exact requirements depend on the applicable law; as a practical starting point, document:
- The technical problem: the limitation or inefficiency of the existing solution, the context of use, and why the change was made.
- The technical solution: components, steps, relationships and operating principles, and how they work together. Don't rely on the outcome ("faster assembly") without the mechanism that achieves it.
- A concrete example: at least one actual implementation, with dimensions, ranges, materials, parameters or operating conditions where relevant and known.
- Drawings and component relationships: clear, original drawings with labelled parts, referred to consistently in the text.
- Technical variants: specific alternatives the company developed or wants in the public domain, each described clearly enough. Merely listing possibilities doesn't necessarily disclose how to implement them.
- Related references: relevant patents, papers or products, and what this disclosure adds.
More detail: how to write a disclosure that counts.
A company checklist before publishing
- Confirm the decision. The committee has decided not to file for this subject matter, not merely postponed or asked for more information.
- Confirm ownership and authority. Check employment and invention-assignment terms, joint-development agreements, funding conditions and customer commitments. An individual employee should not assume they may publish a company invention.
- Check related patent plans. Could the same invention, an improvement, a variant or a broader platform still be filed? Disclosure can jeopardise those options.
- Separate public information from secrets. Remove confidential production parameters, customer information, personal data and unrelated know-how.
- Decide what the company is willing to make public. Others may reproduce and commercially use what is published. Read the publishing terms and licence first.
- Prepare a sufficiently detailed disclosure: problem, mechanism, worked example, drawings, variants; no marketing claims or unsupported generalisations.
- Record approval according to company procedures.
- Publish and keep the evidence: the final disclosure, publication details and evidence of the publication date.
Publication should be a deliberate, authorised release, not an automatic administrative step whenever a committee declines an invention.
How Open Prior Art can help
Open Prior Art is a free public registry where inventors, researchers and authorised company representatives publish technical disclosures. For a company that has decided not to patent an improvement and wants it publicly available, it gives a structured form for recording the technical teaching and its date. Entries get a permanent number, independent timestamps, an Internet Archive copy and a Certificate of Publication. These document what was published and when; they don't guarantee that an examiner will find the entry, or that it will be effective against every later claim.
Entries are public, permanent and published under CC BY 4.0, which allows reuse with attribution, so the company must be comfortable with both. If it is still weighing patent protection, confidentiality or ownership, resolve those first. Entries can show the company name or stay anonymous.
Questions
Does a patent committee rejecting an invention disclosure mean the invention is now public?
No. An internal decision not to file does not publish anything. The information may remain confidential. A separate, authorised act of public disclosure is needed.
Can a company publish an invention after deciding not to patent it?
Yes, if it owns or is authorised to disclose the information and has considered confidentiality, contracts and related patent plans. The publication should contain enough technical detail to explain the subject matter, not just a title or general idea.
Can defensive publication help if the committee says the invention is not worth patenting?
Yes, this is one situation where it is worth considering. If the company doesn't need exclusive rights but wants the solution to stay available, a public technical disclosure may serve as prior art against later applications. First understand why the committee declined.
What if the committee says the invention is obvious or already known?
First identify the prior art and what it discloses. Republishing an already public solution adds little, but additional variants or details that are not yet public may still be worth publishing, if the company authorises it.
Does defensive publication guarantee that nobody can patent the invention?
No. Its effect depends on the publication date, the technical detail actually disclosed, the claims of a later application and the applicable law. It may be overlooked during examination, and a later application may contain features that were not disclosed.
Does publishing the invention give the company the right to use it?
No. Publication is not a licence under other patents and does not establish freedom to operate. Separate patents may still restrict particular implementations.
Can an employee publish the invention if the company declines to file?
Not necessarily. Ownership and the authority to disclose depend on the applicable law, employment terms, agreements and company policy. The employee needs the company's approval before submitting employer-owned or confidential information.
What if the company might patent a related improvement later?
Don't publish until that has been reviewed. Public disclosure can impair protection for the disclosed subject matter and may affect related filings.
Is this the same as a patent office rejecting a patent application?
No. This guide is about an internal decision not to file. If an application was filed and later refused, withdrawn or abandoned, the dates, published documents, remaining rights and future filings need to be assessed separately.
How detailed should the publication be?
Detailed enough for a skilled person to carry it out: how the parts or steps work together, a concrete example, and drawings or variants where useful. A vague description has limited value as prior art.