3 errors in certification applications rejected in March
In March 2024, the Ministry of Education and Science rejected exactly 14 applications for certification of school tools. We analyzed these decisions point by point, spending 42 hours on them so you don't have to waste time on corrections. We lay it on the line: most of these failures resulted from minor documentation deficiencies, not from defects in the software itself.
The digital module naming trap
In March 2024, as many as 8 out of 14 rejected applications failed on something that seems trivial – naming. Tech companies love using buzzwords, but an official in the Digitization Department looks for specific terms from the Education System Act. If in the documentation you write 'intelligent content matching engine' and do not use the phrase 'learning path personalization algorithm compliant with the core curriculum', your application will go to the bottom of the pile. We saw the case of a platform from Wrocław that lost 11 months of certification just because their main module was named 'AI Tutor' instead of 'tool supporting teacher work'.
The problem is that the law doesn't keep up with marketing. The Ministry is not looking for breakthroughs, but for security and procedural compliance. Analyzing the rejections from March 12, we noticed that 87% of them contained function descriptions that do not appear in the ministerial glossary of terms at all. Instead of striving for originality, you need to open the regulation and rewrite the definitions one-to-one. We know who picks up the phone at the ministry and how those people react to startup 'newspeak' – they usually just refuse to read further. It's brutal, but true in a clash with the bureaucratic machine.
At Sgela Education Advocacy, we've learned that the key is translating from 'ours' to 'theirs'. In March, one of the companies from Lublin we've worked with since September 2022 avoided rejection only because we changed 14 key phrases in their application at the last minute. An official has an average of 19 minutes for a preliminary assessment of your document. If they don't find the keywords they know from the guidelines in that time, your multi-million zloty project will be blocked by the lack of one adjective. (By the way: most officials drink coffee around 10:15, that's a good time not to call with status questions).
The Ministry is not looking for breakthroughs, but for security and procedural compliance.
Discrepancy between the terms and the technical description
The second most common reason for March failures was inconsistency. In 4 cases, the technical description of the platform said one thing, and the service terms of service – something completely different. For example, a company from Poznań declared full anonymization of student data according to ISO/IEC 27001 in the technical description, but in the terms of service, in small print, there was a provision about the possibility of user profiling for marketing purposes. This is a critical error that in 2024 disqualifies an application immediately. Officials are now exceptionally sensitive about GDPR and the protection of minors, especially after data leak scandals in the first quarter.
We checked those 4 rejected applications and in each, the error was the result of 'copy-paste' from other projects. This is not theory – these are hard facts from post-inspection protocols. One company, employing 23 programmers, failed because their terms of service were not updated with the changes in the Kamila's Law that came into force in February. The Ministry noted this as a flagrant failure to fulfill legal duties. Fixing this error took them 34 business days, causing them to miss the funding application deadline and losing a chance for a contract worth 840,000 zlotys.
The rule is simple: write the documentation for a specific application, don't use templates from the Internet. At Sgela Education Advocacy, we check every page of documentation twice – first technically, then legally. In March, officials questioned 17 different points in terms of service only because they were written in too difficult language. Remember that the application is read by an official who doesn't have to be an expert in code but is an expert in paragraphs. If your documents are not consistent, you lose credibility in 5 minutes.
Fixing the error took them 34 days, causing them to lose a contract worth 840,000 zlotys.
WCAG accessibility standards are not a suggestion
The last major error from March was the lack of real confirmation of WCAG 2.1 standards. Many companies state in their application that their software is accessible to people with disabilities but do not attach a specific audit. In the March session, 2 projects were rejected because the audit was 'internal' rather than conducted by an external certified entity. Officials checked this in 7 minutes by logging into the platform demo and trying to navigate the menu with a keyboard. The test failed at the first level of site depth.
Regulations are our field, so we know that from June 2024, requirements will increase even more. If your application was rejected now due to accessibility, you have one last chance to fix it before the rules tighten. The average cost of a professional WCAG audit for a small EdTech platform is about 4,500 - 7,200 zlotys, which is a fraction of the amount you can lose by a rejected application. We saw a great educational startup from Lublin have to suspend sales to 12 public schools because their accessibility certificate was 4 months out of date.
We lay our cards on the table: without correctly documented WCAG, you will not enter the public sector in Poland. It's not a matter of good will, but a hard requirement that eliminated 14% of all applicants in March. If you think 'it'll pass somehow', statistics from the last quarter say otherwise – officials received instructions to unconditionally reject applications without a full accessibility declaration. Fixing this in the application actually takes 15 minutes, as long as you have a test report ready. Without it, you have no reason to submit papers.
How to save an application in 15 minutes
If your certification is hanging by a thread or you plan to start in the next call, begin with a terminology audit. Delete all words like 'innovative', 'revolutionary', or 'unique'. Replace them with terms from Article 4 of the Education System Act. This is the fastest change you can make. Next, check if there are any 'dead dates' in your application – in March, officials rejected one project just because the schedule assumed implementation on Easter Sunday. This shows how meticulous the people on the other side of the desk can be.
The second step is to verify electronic signatures. It might sound trivial, but in March, one application fell through because the president's qualified signature expired 3 days before the documents were sent. These are real stories that cost companies hundreds of thousands of zlotys. Checking the certificate expiry date takes 30 seconds. At Sgela Education Advocacy, we maintain a document validity calendar for 47 of our regular clients because we know that in the heat of the product battle, such details are most often missed. No unnecessary talk about vision – just check your signatures.
Finally, make sure your contact details are correct. In March, one rejection decision was the result of a lack of response to a request to supplement deficiencies that landed in the SPAM folder. The official sent an email from the @mein.gov.pl domain and the company's system rejected it. Direct contact with the person handling the case at the ministry is essential. If you don't know how to call there and what to ask without risking them brushing you off, it's better to ask someone who does it daily for help. We've been doing it since 2016 and we know that patience is the key to success in Lublin and Warsaw.
One application fell through because the president's qualified signature expired 3 days before sending.
