Ready To File Means Nothing Outstanding

There is a sentence that shows up in every submission week, and it means two different things depending on who says it. "It is ready to file." Said at 16:00 on a Thursday with one budget line still carrying a placeholder, it means the document is written. Said against a compliance floor of 50 rules, it means something narrower and harder. Rule 2 of that floor is the only one of the fifty that defines a state rather than an action. A document is ready to file when every mandatory field carries data verified from a primary source. A document with outstanding fields is a working draft, and it is never labelled anything else. Not nearly ready. Not ready pending 1 confirmation. Ready, or a draft.

Rule 1 sits directly above it. Every figure, whether it is a budget line, an FTE count, a revenue number, a market size or a test hour, has to originate from a verified primary source. If the number does not exist yet, the field stays blank and it is marked outstanding. That is not caution. A fabricated number inside a federal application is a false statement, and the sentence that describes the risk in the playbook is 10 words long: no exception. The floor is specific about what counts as a source. A market size claim traces to Destatis, the BMBF, Creditreform or a published industry report. "Approximately X companies" without attribution is not a validated figure, and it does not enter the document. The same standard applies to technical maturity. Rule 6: a TRL assessment is a factual claim about what has actually been built and tested. Assigning TRL 3 to a concept that exists on paper in 2026 is a misrepresentation, not optimism. A technology readiness level is a description. Not an aspiration.

Internal documents are allowed to contain estimates, projections and design choices. They have to be labelled as such. Rule 8 is the point where that permission ends. Once a number enters the application, the project carrier treats it as a statement of fact. The probability that a single unvalidated figure passes unnoticed is not zero. Most applicants price it at zero, and the arithmetic on that bet is bad: 1 field, 1 repayment. The floor then pushes the same logic into every field that looks administrative. The Projekttitel in the portal must be letter for letter identical to the title in the Skizze, because Rule 7 says a discrepancy is grounds for formal rejection. The applicant's name must be copied character for character from the current Handelsregister extract, never from the brand. Under Rule 33 that extract has to be no more than 3 months old at submission, because an older one may not carry the current managing director, address or share structure. And the small-enterprise self-declaration has to use the most recent completed fiscal year. Under Rule 34, not the current year's projection. Not an estimate from 2 quarters of trading. The last approved annual accounts, headcount and revenue and balance sheet total. Anything else is a number you cannot stand behind 18 months later.

Budget architecture is not a reflection of what the applicant already spends. It is designed on behalf of the client, and the floor gives it fixed edges. Personnel costs are capped at 20 per cent of the applicant's total budget, and Rule 24 requires that cap to be calculated before any other line is designed. External services and third-party work must represent at least 80 per cent of the budget. The funding rate for a small enterprise under AGVO Article 25 for standard industrial research is 60 per cent, and Rule 29 says it is not negotiable: regional supplements and modifiers do not move it. Every subcontract needs 3 independent market-rate offers, where independent means no personal, financial or corporate relationship between applicant and offeror, and they must be documented before the award rather than reconstructed afterwards. Arms length is broken by role overlap as much as by ownership. Rule 27: if the managing director of the applicant holds any substantive role at the subcontractor, as employee, advisor, partner or director, the principle is violated whatever the share register says. Then the column totals have to reconcile to the euro. Rounding drift between the work packages and the consolidated total is a recurring completeness-check failure, and it is the cheapest one on the list to catch. Design the budget to win. Then audit it as if it will be read line by line. It will be.

A working draft with one unvalidated field is not nearly ready. It is not ready.

The written layer carries its own hard edges. The Skizze must not exceed 12 pages, counting tables and figures, and Rule 40 sets it in Arial 11 point with minimum margins of 1.5 centimetres and 1.15 line spacing. Format compliance is checked before content review, so a strong concept on 13 pages is a rejected one. Inside those 12 pages, novelty has to be proven rather than claimed. "Our approach is novel" is not an argument. The closest prior art has to be cited, papers, patents, competing products, and the difference at the technical level stated precisely, for a reviewer who is a domain expert. Milestones follow the same discipline. "Complete development" is not a milestone. Rule 44: a system prototype validated with 3 pilot clients at or above 80 per cent accuracy by month 18 is. Every work package needs at least 1 of those. Additionalität is argued rather than assumed. The specific financial or technical barrier that public funding addresses is named and quantified, because a generic statement about research risk is not sufficient. Then the words the reviewer is looking for: DSGVO and explainable AI, addressed explicitly for any system touching personal or business data, which the floor treats as a maturity signal.

Rule 47 sets the standard that everything above depends on. If a figure or a claim cannot be traced to a primary source within 48 hours of a query, it should not be in the application. The bar is not whether it can be explained. The bar is whether it can be proved. That is why the file matters. For every submission, the extract, the entity source documents, all correspondence with the project carrier, all partner confirmations, all budget source documents and the submitted PDF are kept, and Rule 48 keeps them for a minimum of 10 years after the project ends. Every invoice issued from project start carries the funding reference number, because Rule 31 says an invoice without it is not reimbursable whatever the underlying work was. And the reporting obligations, half-yearly interim reports, time records, change notifications, are legal obligations rather than administrative ones. Rule 49: each one gets a named owner before the project begins. An obligation without an owner does not get met. The timeline then closes the argument. Rule 18 files 24 to 48 hours before the window shuts, because portal overload on the final day is a recurring systemic failure. Rule 19 needs 48 hours for a qualified signature. Rule 10: a new research partner takes 4 to 8 weeks, and Rule 11 says under 21 days it is operationally impossible. Rule 20: collecting missing entity data takes 2 to 10 working days, with 5 as the baseline. Rule 21: a 12-page Skizze written from scratch needs 5 working days of quality writing, before concept development. Which leaves the last rule, and it is the cheapest of the 50. When in doubt, ask. The cost of a clarifying question is seconds. The cost of a false statement in a public funding application is repayment, reputation and exclusion from the next round. Every rule above was written after somebody assumed something at 23:59. The blank field costs you 1 question. The filled-in guess costs you the application.