Bonum Certa Men Certa

Leaked: Letter to Quality Support (DQS) at the European Patent Office (EPO)

One has to wonder how many more letters like this are being suppressed (never seen by the outside world) and how widespread these problems really are

Letters



Summary: Example of abysmal service at the EPO, where high staff turnover and unreasonable pressure from above may be leading to communication issues that harm stakeholders the most

THE FOLLOWING IS AN anonymised letter to senior EPO staff, bemoaning what was a horrible (and possibly not exceptional) service from the EPO, which caused enormous financial loss and the loss of many years (stuck in a limbo).



⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆ ⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆ Director, Directorate 2.5.2 Quality Support (DQS) Principal Directorate Quality Management I DG2 European Patent Office 80298 Munich Germany

Application No: ⬆ ⬆ ⬆ ⬆ ⬆

Dear Mr. ⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆,

Re Letter of ⬆⬆ & ⬆⬆ ⬆⬆⬆

Under rule 71 (2): -

‘Any communication under Article 94, paragraph 3, shall contain a reasoned statement covering, where appropriate, all the grounds against the grant of the European patent.’

At the first oral hearing the EPO stated that Claim 1 as set out in document ⬆⬆ met the EPC criteria for grant. It was recognised that dependent claims along with possible additional IP that could be added. The directions of the chairman were that these small outstanding matters were to be addressed by email. This resulted in submission of ⬆⬆⬆⬆⬆⬆. This provided 4 areas for discussion and detailed mark-up of the changes. There was no separate response to this communication. The response that was given was added by way of an addendum to the intention to grant Rule 71 (3) of ⬆⬆⬆⬆.

In contravention of Rule 71 (2) the response did not include a reasoned response on all grounds. There was no way of telling which mark-up was acceptable and which wasn’t. Had a full response been provided I would have known those part that may have been acceptable or not could have been addressed or incorporated into any further revision. In fact this failure to provide a full response is confirmed by the fact that no sooner than the initial objections were met than further grounds of objection by the EPO were added (see EPO’s later correspondence). The last such revision of objection being set out in the examining divisions letter of ⬆⬆⬆. Not only have I been subject to a grossly incomplete first response but further objections have been drip fed over months greatly adding to delay. The last of these objections I haven’t even been given an opportunity to contest because the examining division has refused the application in its entirety; not withstanding that the EPO has stated that a patent could be granted. It would appear that if you challenge the EPO you simply lose the IP that is rightly yours. Why was Rule 71 (2) not followed and why am I not given the opportunity to respond and possibly correct objections before my application is refused?

In your letter you state: “A grant can only be given on the basis of text approved by the applicant.” This would suggest that Rule 71 (3) (the intention to grant) is only instigated when agreement has been reached. I am left confused by the approach of the EPO on this front. The first letter of intent to grant was made under Rule 71 (3) on ⬆⬆⬆. This was later withdrawn. The exact same approach was then adopted on ⬆⬆⬆⬆. In your letter of ⬆⬆⬆ you state that the text was not approved by me. The text in both instances was the same. As the text was not approved I do not understand why the EPO moved to issuing a letter of intention to grant. What had changed between the withdrawal of the intention to grant of ⬆⬆ and later resubmission of the same words in ⬆⬆? As detailed in the previous paragraph it is clear from the changing grounds of the EPO that discussions with the EPO were ongoing as at ⬆⬆⬆. Why are applications refused when discussions are ongoing? Does the applicant have no right of reply? Why was the intention to grant issued when clearly agreement had not been reached? The evidence suggests that this approach has simply been used as a procedural move to refuse the application and curtail criticism.

From paragraph 7 of your letter of ⬆⬆⬆ it would appear that under Rule 71 (3) applicants are allowed to contest wording but if they do so they run the risk of a complete refusal of your application! The right to contest looks more like Russian Roulette. It would appear that the applicant is being restricted from contesting his case. At the point applicants are offered the prospect of contesting wording, the consequences of doing so should be set out in BOLD print. This they are not. In fact the insight in your letter is the first I have heard of this position and it came precisely at the same moment that this action was taken. You have previously provided a full set of references to substantiate the legal basis for the actions of the EPO but alas there are none here. Please could you supply me with the legal basis for this and references as you have done previously. I think it is critical that all applicants should understand when they are genuinely allowed to contest points and clearly when they are not.

In your letter of ⬆⬆⬆⬆ paragraph ⬆⬆⬆ you have still failed to address the contradiction that the EPO is claiming inventive step and no inventive step on identical wording. You claim that my suggestion that the division contradicts itself may simply be due to a misinterpretation of the communication of the division (para 11). Please could you tell me what this misinterpretation is because I haven’t clue and you haven’t stated what it is? In para ⬆⬆ you state that ⬆⬆⬆ has been deemed inventive with regard to the document ⬆⬆. This issue concerning contradiction can readily be resolved if you or your examining division simply tell me what this inventive step is. Currently the examiner is complaining about the metal pipes of the heat exchanged as not being inventive, yet the wording concerning the metal pipes is the same in all documents ⬆⬆, ⬆⬆ and ⬆⬆. You have asserted that ⬆⬆ shows inventive step over ⬆⬆⬆, please can you tell me what it is? I bet this cannot answered honestly without agreeing with my assertion about contradiction is correct. Why is the inventive step not documented in the minutes of the oral hearings?

In para ⬆⬆ of your letter ⬆⬆⬆ you claim that; “the EPO has taken all possible steps to support your constituent (me)”. I ask you then: -

1. Why did the EPO not suggest I seek, or they themselves seek, an adjournment to the oral proceedings when they knew I could not attend due to being on my honeymoon? 2. Why did the EPO not tell me that I may lose my patent all together if I contested the EPO’s wording or lack of dependent claims? 3. Why has the EPO steadfastly refused to address the issue that the EPO contradicts itself? 4. Is the median turn around for applications greater than 6.5 years? 5. Is it normal to simply refuse an application on which the EPO asserts a patent can be granted without first consulting the applicant? 6. Why has the examining division not followed the order of priority for reviewing claims as set out in correspondence? This would have prevented the refusal letter from being submitted. 7. How are my interests served by being forced into an appeals process that will costs a minimum of 1,860 euros for the appeal, probable a further circa 3,500 euros on renewal fees and a further wait of 3 years when it is accepted by invention is patentable!?

In paras ⬆⬆⬆, ⬆⬆⬆ and ⬆⬆⬆ you suggest that I should employ the services of a competent professional. Setting aside the inference that I am not competent and setting aside all possible steps of support that the EPO has given me I have to ask what happens when the lack of competence lies with the EPO?

In the letter of refusal of ⬆⬆⬆ the examiners claim there is no ⬆⬆⬆ document on file. Is there little wonder then that I, and probably many others too, lose all faith in the EPO as an organisation when one realises that not only does the document exist on file but it has historically been replied to. This statement that the document does not exist on file has been signed by three of your examiners! What legal options for redress are there available to applicants who find their applications so evidently mistreated? What actions will you be taking to ensure this does not happen again?

In accordance with the spirit of Rule 71 (2) please could I have a full response to all points raised in this letter. May I suggest a response by email will significantly save time.

Regards

⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆ ⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆


Have you encountered similarly bad service? If so, please get in touch with us.

Recent Techrights' Posts

The Week to Come
Planning ahead
LLM Slop Has Only Been a Boon for Misinformation Online
The very same companies that were supposed to maintain quality (again, not limited to Google with PageRank) are now actively participating in generating and spreading slop
When They Tell You It's Free, Does That Mean No Charges (If So, Who's Paying and Why)?
there's "no free lunch"
 
Links 28/07/2025: COVID-19 Sped up Brain Aging, "Circumvention is More Popular Than Compliance"
Links for the day
Richard Stallman is Usually Right Because He Thinks "Outside the Box"
he is able to observe society (mores and norms) as somewhat of an outsider
LWN Has Been Down for a Long Time, Another Casualty of LLM Bots?
Time will tell. How much time though?
Slopfarms Versus 'Linux' (and Against People Who Write Real Articles About GNU/Linux)
LLM slop in slopfarms by Brian Fagioli and Redazione RHC
Gemini Links 28/07/2025: Bila Yarrudhanggalangdhuray and Running pkgsrc in a FreeBSD Jail
Links for the day
Microsoft Turns News Sites Into Spamfarms
Is the site The Register MS the next IDG?
The Register MS/The Register US
On Saturday I contacted them for a comment (before issuing criticism)
Hacking revelations at Vatican Jubilee of Digital Missionaries
Reprinted with permission from Daniel Pocock
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Sunday, July 27, 2025
IRC logs for Sunday, July 27, 2025
We're Going to Focus Less on the Molotov Cocktail-Throwing Microsofters and More on Patents
We can get back to focusing on what we wanted to focus on all along
Just Trying to Keep Web Sites Honest (Journalistic Integrity)
the latest articles in LinuxIac are real
Links 27/07/2025: Political Affairs, Data Breaches, Attacks on Freedom of the Press
Links for the day
Gemini Links 27/07/2025: Hot in Japan and Terminal Escape Codes
Links for the day
Links 27/07/2025: More Microsoft Layoffs Coming, Science and Hardware News
Links for the day
Links 27/07/2025: FSF Hackathon and "Hulk Hogan Was a Very Bad Man"
Links for the day
Gemini Links 27/07/2025: DAW Mixer Chains and Simple Software
Links for the day
The Register MS is Inventing or Giving Air Time to New Conspiracy Theories so as to Distort the Narrative As High-Profile Agencies Fall Prey to Microsoft Holes
But the problem is holes, i.e. Microsoft making bad products; the problem is Microsoft
Most Editors at The Register Are American, Including the Editor in Chief, a Decade-Long Microsoft Stenographer (Writing Prose to Sell Microsoft)
It's not easy to tell where the site is based (we tried) because it's hiding behind ClownFlare and CrimeFlare hasn't been well lately
Pushers of systemd Rewrite History (Richard Stallman Said UNIX "Was Portable and Seemed Fairly Clean")
Unlike systemd
"New Techrights" Soon Turns 2 (A Few Days Before the FSF Turns 40)
We have a lot more to say about LLM bots
When Silence Says So Much
Garrett, a 'secure' boot pusher, will need to defend himself in the UK High Court
The Register in Trouble
There is not much that can be done at this point
Trajectory of The Register: From News Site/s Into "B2B"... and Into Microsoft Salespeople
Something isn't right at The Register
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, July 26, 2025
IRC logs for Saturday, July 26, 2025
Misinformation in Social Control Media
Social control media passes around all sorts of tropes
Slopwatch: Fake Linux 'Articles' and Slopfarms With "Linux" in Their Names/Domains
throwing bots at "Linux" to make some fake articles
Links 26/07/2025: Amazon Shutdown in China, Russian Economy Slows
Links for the day
Gemini Links 26/07/2025: History of Time (1988) and Gemini Games
Links for the day
Links 26/07/2025: 50 Percent Tariffs in Amazon, Dying Intel Offloads Network and Edge Group (NEX)
Links for the day
Doing My Share to Tackle Online Slop and SPAM
Trying my best to 'fix' the Web
Blaming Programming Languages for Users' and Developers' Bad Practices
That's like blaming cars for drivers who crash into things
Slopwatch: Fakes, FUD, Duplicates, and Charlatans Galore
The Web as we once know it is collapsing. Some opportunists try to replace it with low-quality slop.
The Register UK Seems to Have Become American and Management is Changing (Microsofter as Editor in Chief)
The Register 'UK' is now controlled by the Directions on Microsoft guy
Many People Still Read Techrights Because It Says the Truth, Produces Evidence, and Does Not Self-Censor
Unlike so many other sites
The Register is Desperate for Money, According to The Register
I decided to check how they're doing as a business
Microsoft Finally Finds a Use Case for Slop?
Create low-quality chaff to shift the media's attention?
Microsoft Windows Lost 400 Million Users in a Few Years, Why Does The Register Double Down on Windows With New US Editor?
days ago they hired a new US editor
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, July 25, 2025
IRC logs for Friday, July 25, 2025
For Libel Reform One Must First Bring (or Raise) Awareness to the Issues and Their Magnitude
I myself know, from personal experience
Links 26/07/2025: Rationed Meals in the US and TikTok Repels Investments (Too Toxic)
Links for the day
Gemini Links 26/07/2025: "Bloody Google" and New People in Geminispace
Links for the day
Response to Solderpunk (Father of Gemini Protocol) About the Gemini Community
Solderpunk responds to non-sequitur
HTML and the Web Used to be Something a Child Could Learn, "Modern" Web is a Puzzle of Frameworks, Bloat, and Worse
When the Web was more like Gemini Protocol