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

Gemini Links 11/01/2026: Scott Morgan and 'The Unix Way'
Links for the day
IBM to Be 'Reorganised'
The rich look for ways to 'monetise' what's left IBM
Dr. Andy Farnell Explains Why He'll Stop Sending E-mail to Microsoft and Gmail Users
The article is long and well worth reading
GNOME Foundation's Microsoft Developer Account
"Lately they're teaming up with Mozilla to eliminate middle click paste - something which I use continuously."
Links 10/01/2026: "Abolish ICE or GTFO", Calls to Ban X/Twitter From Apple/Google App Stores (or Implement National Blocks) Over MElon Turning It Into Non-consensual Deepfake Porn Site
Links for the day
EPO People Power - Part XXX - New Year Starts, Cocainegate Still Discussed a Lot, António Campinos Desperate for Distraction From It
Why the sudden change or 'generosity'? [...] Actual cocaine addicts caused nervous breakdowns among sober people
 
Links 11/01/2026: Bob Weir and Stewart Cheifet Perish
Links for the day
Higher Adoption Rates of GNU/Linux in Cyprus in Recent Years
there are some Cypriots who are championing Free software
Microsoft's linkedin.com is Shrinking, Expect LinkedIn Layoffs to Carry on in 2026
Expect the mass layoffs and office closures to carry on there, maybe as early as next week
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, January 10, 2026
IRC logs for Saturday, January 10, 2026
Monday, January 12, Red Hat Layoffs Allegedly Planned
We'll update this post or follow up if or when we get more information
Slop Still Becoming Rare as Another Week Ends
Generally speaking, calm and quiet is desirable, it's what we hope for (an absence of slop, a lack of need to keep abreast of it, ultimately)
Links 10/01/2026: Iran Offline, Venezuelans Decry Civilian Casualties
Links for the day
GAFAM Wants War
Go war! Go bailouts! Go debt! Go Wall Street!
GNU/Linux and Chromebooks Rose to Almost 10% in Haiti
What's noteworthy is that this month GNU/Linux is measured at around 8% and ChromeOS at about 2%
2026 Might be the Year Microsoft Replaces Layoffs With Mass Firings (No Severance Payments to Dismissed Staff)
It's hard to "see" PIPs unless insiders blow the whistle
IBM and Microsoft Hiding Layoffs in Similar, Overlapping Ways
Performance Improvement Plans aplenty
IBM is a Cancer That Attaches Itself to Everything
Red Hat should have remained an independent company
Links 10/01/2026: STV Layoffs (Scottish TV), “CBS Evening News” in Chaos (Culls and Censorship by the US Regime)
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, January 09, 2026
IRC logs for Friday, January 09, 2026
Gemini Links 10/01/2026: Blackout, E-Waste, and Secondary Smartphone
Links for the day
Plot Twist: Microsoft MSN Relays Articles Hinting at or Pointing to Mass Layoffs Soon, Other Gossip
the narrative from Microsoft's "PR bunny" (Shaw) is showing mold already
Links 09/01/2026: Google and Character.AI Implicitly Accept Chatbots Kill Kids and GLP-1 ‘Slimming Pens’ Turn Out to be a Lot Worse Than Advertised
Links for the day
'Vibe Coding' is Not "AI", It's a Sewer, It is Junk
Linus Torvalds was wrong. 'Vibe coding' isn't good for anything.
GNU/Linux May be Approaching 10% "Market Share" in Montenegro
The surge started around 2021
At IBM, "Employee Reviews" (or Appraisals in the UK) Are a "Trojan Horse" for RAs (Mass Layoffs), a Waste of Time
comments from IBMer serve to suggest that appraisals can be precursors
Links 09/01/2026: Technical Blogging Lessons Learned and Google's Gmail Getting a Lot Worse
Links for the day
More IBM Layoffs in India
If IBM cannot afford to retain workers in India, then something is truly "out of control" at IBM
Escaping GAFAM Colonialism Requires Homegrown Free Software
GNU/Linux now measured at 3% in Zambia
Dr. Richard Stallman Has Done No Harm to the GNU Project or the FSF (He Had Benefited Both, Always, Even After the Attacks on Him Began)
Some people try to prevent Dr. Stallman from speaking or having a platform where many people can hear him
GNU/Linux at 4% in Saudi Arabia, Says statCounter
Some years ago Windows fell to a "market share" of just 11% there
Microsoft Isn't Denying the Mass Layoffs
Still silence from Microsoft
In Western Africa GNU/Linux Flirts With 5% Market Share
there's a gradual increase in GNU/Linux usage there
Gemini Links 09/01/2026: Pro1 X Repair and the Mercury Protocol
Links for the day
Links 09/01/2026: Cambodia and China Extradition, "NATO’s High-risk Patrols Near Ukraine"
Links for the day
No, Microsoft Did Not Deny the Q1 Mass Layoffs (Microsoft Can Delay These)
Maybe they disperse or delay the layoffs (changing plans), but the layoffs are going to happen
Only One Person in Charge of Fedora is Not IBM Staff
This is not a community project, it's just a way for IBM to onboard unpaid volunteers
This Is Not a Drill, GNU/Linux is Really Going 'Mainstream' on Laptops (and Desktops)
It is important to explain to people software freedom
IBM Albany Layoffs
not only did many in the site lose their job; there's more to come "and likely another one in February" (weeks from now)
EPO Workers' Industrial Action to Include Many Strikes, to Last Several Months
In some ways, The Hague and Bavaria are becoming almost indistinguishable from Moscow
EPO People Power - Part XXIX - Getting DER SPIEGEL, FAZ, Deutschlandfunk and Sueddeutsche Zeitung (SZ) to Cover EPO Scandals
We kindly ask our readers to contact their local media and urge it to cover the scandals
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, January 08, 2026
IRC logs for Thursday, January 08, 2026