Most BSFZ rejections have a few, recurring causes. Almost always the issue is the presentation: the project is described like a product or a development project instead of like research. Anyone who knows the typical mistakes can avoid them – and that is exactly what an application prepared in line with the review guidelines aims for.
The most common reasons for rejection
Product description instead of research
"Our product can do X, Y and Z" sounds like sales. Better: describe the knowledge gap and the research approaches used to close it.
Novelty too vague
"The novel element is the systematic approach" describes methodology, not technology. It must become clear WHAT is novel and what technical benefit it provides.
Economic instead of technical risk
"Whether customers will buy it" is not an R&D risk. Only scientific and technical uncertainties count – for example "whether the algorithm converges under these conditions".
Routine activities declared as research
According to the review guidelines, testing, debugging, configuration, porting, commissioning following instructions, or certifying existing products are not eligible.
Missing time reference for the novelty
The state of the art changes over time. Without a year ("market analysis 2022: …"), the novelty cannot be substantiated.
Character limits underestimated
The portal fields are tightly limited (e.g. 500 characters for novelty). Anyone writing without watching the limit loses their strongest arguments.
The common thread: prove research, don't sell products
The BSFZ assesses against the Frascati criteria. What matters is that the knowledge gap, the technical risk and the methodology are clearly recognisable – and that non-eligible routine work is cleanly delineated. Which activities count as eligible or not eligible in your industry is shown by our sector pages, for example mechanical engineering or software & AI.
More on getting the wording right: Research language instead of development language.
Frequently asked questions about rejections
What is the most common reason for a BSFZ rejection?
The description reads like a product or project description instead of research. If the knowledge gap does not become clear and the technical-scientific risk is missing, the BSFZ has no basis on which to assess eligibility.
What happens after a rejection?
If a criterion is clearly not met, the rejection is issued without any further inquiry. That leaves an objection or a lawsuit. It is far better to set up the initial application in line with the review guidelines from the outset.
Can I avoid a rejection with an application review?
Often, yes. In the application review we check the application you prepared yourself for research language, delineation and character limits – before it is submitted.