What kind of written descriptions work best?

You'll get better results when you start from a well-written invention description

As a rule of thumb, a well-written description includes the background of technology, problem you are solving, the technical solution, and what makes your solution unique. In other words, enough information that another person could understand the invention without requiring additional explanation.

  • Descriptions can be any length but the longer they are the better your results will be
  • Write the way you would explain to another person
  • You do not need to write using legal language, a thorough technical explanation is sufficient

Amplified uses your invention description to prioritize relevant patents. It does this by comparing your entire description against the full text of every patent in our database. Since this happens in real-time, you can experiment to see how different descriptions impact results. Just click Update results after making changes and in a few secondsyou'll get a re-sorted list.

Try our invention disclosure guide to improve your descriptions

From your Amplified dashboard click on Invention Disclosure.

This will open the Invention Disclosure guide which starts with an explanation of what an invention disclosure is and why it's useful. Click on Get Started.

On the left side of the screen you'll see a series of questions which help you to think through the invention and draft a high quality description. To help you fill these in we've also included pre-written best practice examples on the right side. To see the examples in different technical areas such as Telecommunications or Mechanics, just click on the bubble at the top.

Invention disclosures are important documents that begin the process of turning an idea into a patent. Using this form as a guide you'll be able to write high quality invention descriptions that give you better results in Amplified and lead to more valuable patents.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us