The EU platform work directive has to be German law by 2 December 2026, and as of mid-October Berlin has not published a draft. For an IT freelancer the first question is whether the agency or marketplace you get projects through is a "digital labour platform" at all. It is one only if it meets four conditions at once, including organising your work and using automated monitoring or decision systems. A job board that only lists projects is out. An agency that matches you by algorithm, runs the contract chain and rates you may be in.
Many German IT contracts run through an agency, and my current one does too. So I read the directive, the Bundestag papers and the industry positions to answer one practical question: what changes for people like us on 2 December, and what should we check before then?
What is the platform work directive?
Directive (EU) 2024/2831 of 23 October 2024 improves working conditions in platform work. It does two things. It creates a legal presumption that a person working through a platform is an employee when there are facts indicating control, and it sets EU rules for algorithmic management: what a platform may track, what it must disclose, and which decisions a human must take. Article 29 obliges member states to bring the rules into force "by 2 December 2026".
The Commission's case for it was misclassification. In its December 2021 proposal it estimated that over 28 million people in the EU worked through digital labour platforms and that 5.5 million of them were "incorrectly classified as self-employed". In my reading those figures were about food delivery and ride-hailing far more than about IT consulting. The definition is not limited to those sectors.
Is my agency a "digital labour platform"?
It is a digital labour platform only if all four conditions of Article 2(1)(a) apply. The service is provided at least partly at a distance by electronic means, such as a website or app. It is provided at the request of a recipient, the client. It involves, "as a necessary and essential component, the organisation of work performed by individuals in return for payment". And it "involves the use of automated monitoring systems or automated decision-making systems".
Recital 20 draws the line that matters for us. Platforms that "merely provide the means by which service providers can reach the end-user", for example by advertising offers or listing available providers, "should not be considered to be digital labour platforms". Organising work requires "a significant role in matching the demand for the service with the supply of work". So the test is whether the intermediary organises the work and uses automated systems to do it, whatever its website looks like.
| How you get the project | Organises the work? | Automated systems? | My reading |
|---|---|---|---|
| Project board where you apply and contract the client directly | No, it only lists | Maybe, for search ranking | Out, per recital 20 |
| Agency where a recruiter matches you by hand and the agency holds both contracts | Yes, it matches and contracts | Often only CRM and e-mail | Grey zone, depends on the automation |
| Agency or marketplace with algorithmic matching, ratings, timesheets and payment in its portal | Yes | Yes | Likely in scope |
| The client's own procurement or supplier portal | The client runs it for its own suppliers | Often | Industry wants it excluded, not settled |
The last row is not my invention. In its September 2024 position paper, Bitkom warned that the definition is "zu weit gefasst" and could even catch a "Ticketing-System für IT-Support". It asked the legislator to clarify that platforms serve to make contact between clients and contractors, not to run supply relationships that exist without them. That clarification has not been written yet.
What does the employment presumption mean for an IT freelancer?
The presumption shifts the burden of proof onto the platform, not onto you. Under Article 5(1), the contract between a platform and a person working through it is "legally presumed to be an employment relationship where facts indicating direction and control" are found under national law. If the platform wants to rebut it, the platform has to prove there is no employment relationship. The IW Köln pointed out in its May 2026 short report that the presumption would apply even if both sides agree the work is self-employed.
For the German contractor the important sentence comes next. Article 5(3) says the presumption "shall not apply to proceedings which concern tax, criminal or social security matters", although member states may apply it there. Our real risk, the status check by the Deutsche Rentenversicherung, is a social security proceeding. Unless the German law extends the presumption, the DRV keeps deciding status under § 7 SGB IV, where "eine Tätigkeit nach Weisungen und eine Eingliederung in die Arbeitsorganisation des Weisungsgebers" are the indicators of employment. Article 5(6) adds that for contracts already running on 2 December 2026, the presumption applies only from that date.
The agency triangle is covered on both sides. Article 3 says people working through an intermediary must get the same protection, with joint and several liability "where appropriate". German law already knows the triangle: § 7a Abs. 2 SGB IV lets the DRV decide whether an employment relationship exists with the third party the work is done for, which in our world is the end client. The details of how I see the status rules moving are in my note on the Statusfeststellung reform.
Where does Germany stand on 2 December?
Germany has no published draft for the directive. In April 2026 the government told the Bundestag that the labour ministry is drafting the bill (Drucksache 21/5454), and eight days later that widening the scope beyond the directive is "nach aktuellem Stand nicht vorgesehen" (Drucksache 21/5577). On 25 September 2026 the Bundesrat called on the government to present a draft "zeitnah", with its attention on food delivery (Drucksache 399/26).
With seven weeks left, Germany will in my view miss the deadline. That does not make the date irrelevant. Agencies with EU-wide operations will, I expect, prepare for it anyway. Expect their contract templates to change before the German law does.
What rights do self-employed contractors get?
This is the part most coverage misses, and it is the useful part for us. Article 1(2) extends the algorithmic management rules to persons performing platform work "including those who do not have an employment contract or employment relationship". If your agency or marketplace qualifies, these rights apply to you as a genuine freelancer:
- No tracking outside work. Article 7 bans platforms from using automated systems to process data on your emotional or psychological state or your private conversations, and collecting data while you are not offering or performing platform work. It applies "from the start of the recruitment or selection procedure".
- Transparency. Under Article 9 the platform must tell you that it uses automated monitoring or decision systems.
- Portability of your ratings. Article 9(6) gives you the right to take personal data generated by your work, "including ratings and reviews", to another provider.
- A human decides on your account. Article 10(5): any decision to restrict, suspend or terminate the contract or your account "shall be taken by a human being".
One catch: the right to an explanation of automated decisions in Article 11 does not apply to people who are business users under the EU platform-to-business regulation, which many B2B freelancers on a marketplace will be. The human-decision rule in Article 10(5) still applies.
What should IT freelancers check before 2 December 2026?
Five checks take an evening and will save an argument later:
- List your channels. Every agency, marketplace and portal you got a project through in the last two years, and which of them hold the contract with you.
- Run the four conditions per channel. Does it only list, or does it match and organise? Does it use automated matching, scoring, timesheet monitoring or ratings? Write down the answer and the date.
- Read the next contract template line by line. I expect new clauses on independence, indemnities and data. A clause that makes you carry the agency's reclassification risk deserves a counter-offer, not a signature.
- Keep your independence evidence current. Bitkom suggests using the criteria from the EU Court's Yodel case: freedom to use substitutes, to accept or refuse tasks, to work for competitors and to set your own hours. They overlap with what the DRV looks at, so document them per project.
- Export your profile and ratings now. The portability right will help once it is law. Until then, a copy you already hold is worth more.
None of this replaces a status check. If a project looks like integration into the client's organisation, the route is still the Statusfeststellungsverfahren under § 7a SGB IV, as described in my guide on becoming an IT freelancer in Germany.
My take
For most German IT contractors the directive will not turn agency work into employment overnight. The presumption is optional in social security proceedings, and the government has said that, as things stand, it does not plan to widen the scope. In my view the real effect comes through the agencies. Their compliance teams will read "digital labour platform" more broadly than the courts eventually will, and they will push the cost into contracts, documentation duties and rate pressure. The contractors who know which of their channels actually qualify will negotiate those clauses. The rest will sign them.
Related field notes:
- Statusfeststellung reform: certainty at 16.74% of the fee
- NIS2 supplier clauses for freelance contractors
- E-Rechnung for IT freelancers: what to do by 2027 and 2028
- Freelancer-Kompass 2026: why projects stall on the client side
- AI discounts in time-and-material contracts
- The German consulting market is sorting itself in 2026