How Robotic Patent Drafting (RPD) Helped Me Reduce Patent Delivery Time From Weeks Or Months To Days

Schweiger & Partners

Contributor

founded his firm's strategic Asian branch office in Singapore, which has become a major hub for IP matters in Asia. Martin Schweiger has his own blog, IP Lawyer Tools, that produces materials in helping to guide bright young people through the mine fields that the intellectual property (IP) profession has. It shows you specific solutions that can save you time and increase your productivity.
My journey as a patent attorney began at a time when software patents were just emerging. That era laid the foundation for what is now a significant shift in patent drafting – the advent of Robotic
Singapore Intellectual Property
To print this article, all you need is to be registered or login on Mondaq.com.

My journey as a patent attorney began at a time when software patents were just emerging. That era laid the foundation for what is now a significant shift in patent drafting – the advent of Robotic Patent Drafting (RPD).

The transformation of patent drafting through technology

When I began my career in patent law, the very idea of patents for software was innovative. Traditionally, patents were granted for tangible inventions, and the inclusion of software in this realm was a significant development. I was an active part of this movement. Google "T1227/05" to name just one of the many software patent cases I have been personally involved in over the past 30 years.

The evolution from the 1990s to the present is remarkable. The legal landscape has changed dramatically with RPD. In the past, drafting a patent was a labor-intensive process that often took several weeks or even months. Now, RPD has made it possible to deliver complete and accurate patent drafts in just a few days. And modern RPD bots helped me get a new approach to patent drafting: I rediscovered the original joy of patent drafting, because all the monotonous drafting work is gone, and the quality of the patents has gone up. Please let me explain this to you.

How RPD works – important: the input data

In short, a patent drafting bot works like any other piece of software: the user provides input data and information about the desired output data. Once this data is provided, the software generates the output data, which can and should be reviewed and modified by a human. In the case of RPD, the input data often includes not only information about the invention, but also data about the structure of that information, such as which figures show which elements of the invention. My very first patent drafting robot generated pictorial descriptions of gear variations that were stored in a spreadsheet file, and that saved me a lot of time in writing the enabling patent specification.

Some RPDs go beyond this traditional way of working and would provide additional features such as automatic detection of substructures and sections of devices, often from interpreting patent claims after they have been entered into an online form or text document intended to be sent to a server. This can be used to automatically generate figures illustrating claims.

Of course, all modern RPDs have features that highlight quality problems in the input data and issue warnings if common error patterns are found. Building a set of patent claims in a good online tool can be an instructive lesson for beginners and a therapeutically refreshing experience for experienced patent drafters.

To be more specific, depending on the required quality of the resulting patent application, I spend about 45 minutes (for an economy class patent application) to 8 hours (for a litigation grade patent application) generating the input data for each robotic patent drafting tool.

To cut a long story short, each RPD bot generates an output text file that needs to be carefully reviewed, because auto-generated texts can contain incredible nonsense wrapped in flawless language, similar to what MBA students, management consultants, and politicians often produce. In my case, it takes about two to three times as much effort to correct and modify the output text file as it does to generate the input data. What I often do is to check the output text file for language inconsistencies and logical errors, and then re-run the RPD generation after making changes. The total effort is still only 20% to 30% of the time I used to invest in writing patent applications the conventional way, and with much higher quality.

How to get started with RPD today

There are two ways to start using patent drafting automation tools:

a) read articles, books, and watch videos until you feel comfortable with your needs, followed by trying a few patent drafting bots yourself, or

b) hire a professional trainer (me) to help you shorten the learning curve (click here).

I would recommend option b) because that trainer will also help you choose the right patent drafting robot. As I write this article, there are seventeen (17) commercially available bots, and a new one comes out every month or so.

If you're inclined to start with self-education, I've compiled an overview of current resources on my "IP-Lawyer-Tools" blog (click here).

Conclusion

I recall times when drafting a patent for a wireless car alarm system was a significant undertaking. Today, using RPD tools, I can create a draft for an 'Economy-Class' patent in about 45 minutes and a 'Litigation-Grade' patent in about 8 hours. The subsequent review and amendment process are swift, ensuring the final patent application is of high quality.

Do not delay. Embrace RPD and rediscover the efficiency and joy of patent drafting.

Check out this landing page: https://trademarks-patents.com/service/assisted-patent-drafting/

You will like it. I promise.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

See More Popular Content From

Mondaq uses cookies on this website. By using our website you agree to our use of cookies as set out in our Privacy Policy.

Learn More