The IT Freelancer Compliance Checklist for German Companies

A practical pre-engagement checklist that consolidates the German compliance cluster, contract type, scoping, autonomy, integration limits, evidence, works-council notification and periodic review, with the reasoning behind each item. An educational overview, not legal advice.

Elena Voss·Head of AI Delivery, Aiporate··7 min read·Share on XLinkedIn

Key takeaways

  • Work the checklist before day one: contract type chosen deliberately, scope written outcome-based, autonomy safeguards agreed, integration limits set, evidence collected, works council informed where applicable, and a review rhythm scheduled.
  • Every item exists to keep the lived engagement matching a defensible paradigm, because German authorities classify by practice, not by the label on the contract.
  • The most frequently skipped items are the cheapest: written documentation of the working model, and calendar-scheduled reviews of lived practice at each extension.
  • Escalate honestly borderline cases to your own legal counsel or the Statusfeststellungsverfahren instead of resolving them by hope; no checklist, this one included, makes an engagement zero-risk.

The previous articles in this series covered the German compliance landscape for external tech talent piece by piece: false self-employment, the AÜG, the three contract paradigms, the works council. This one consolidates them into a single, practical pre-engagement checklist, the items a German company should work through before an IT freelancer's first day, each with the reasoning behind it. Two framing notes before the list. First, this is an educational overview, not legal advice; no checklist replaces an assessment of your specific case by your own legal counsel, and borderline items below are exactly the ones to escalate to them. Second, no checklist makes the risk zero: classification follows the lived engagement, which is why the last item, periodic review, is not optional garnish but the item that keeps all the others true.

The pre-engagement checklist

  1. 1Choose the contract type deliberately: decide Werkvertrag, Dienstvertrag or (licensed, openly declared) Arbeitnehmerüberlassung based on who will direct the work and what is owed, before drafting, not by defaulting to whatever template is nearest.
  2. 2Write the scope outcome-based: deliverables, milestones and acceptance or review criteria instead of undifferentiated weekly capacity, so the freelancer demonstrably owes results or defined services, not attendance.
  3. 3Agree autonomy safeguards in writing: the freelancer controls method, and where the work allows, time and place; the client steers through backlog, milestones and acceptance, not through daily task assignment.
  4. 4Set integration limits: no entry in the internal org chart as a team member, external identification in email and tools, no employee-only mechanics (vacation approval workflows, performance reviews, staff on-call rotas designed for employees).
  5. 5Collect the freelancer's entrepreneurial evidence: proper invoicing with the freelancer's business details, professional liability insurance, own equipment where feasible, and indications of multiple clients or an own market presence, filed with the engagement record.
  6. 6Verify the provider side where an agency is involved: is the model contracting or leasing, is leasing openly labeled and licensed (AÜG-Erlaubnis), and does the provider's operating model match the paper.
  7. 7Notify or involve the works council where applicable: consent process for leased workers under §99 BetrVG, proactive information for contractor engagements, before the start date, not after discovery.
  8. 8Document the working model: a short, dated record of who directs what, communication paths and review mechanics, the document you will be glad to have if anyone ever asks how the engagement was designed.
  9. 9Schedule periodic reviews of lived practice: at fixed intervals and at every extension, check the actual daily reality against items 1-8, and correct drift or escalate to counsel (or the status-determination procedure) when the honest answer is 'this has become something else.'

Why items 1-2 carry the most weight: paradigm and scope

The contract-type decision (item 1) is the keystone because every other obligation hangs on it: a Werkvertrag brings acceptance mechanics and contractor self-direction, a Dienstvertrag brings the duty to protect self-direction operationally, leasing brings the AÜG's license, labeling, duration and equal-treatment regime. Choosing by inertia, reusing whatever template the last project used, is how companies end up with paper that never matched the plan, let alone the practice. Outcome-based scoping (item 2) is the keystone's mirror in daily work: a freelancer who demonstrably owes deliverables looks different in every audit-relevant dimension, direction, risk, integration, from one who owes presence. These two items are also where a capable staffing partner adds the most structural value, and where your legal counsel should see the setup before signature.

Why items 3-4 decide most real cases: autonomy and integration

When authorities examine an engagement, the questions that decide most real cases are the ones items 3 and 4 address: who assigned this person's tasks, who controlled their hours, and how distinguishable were they from employees. Autonomy safeguards fail silently, a well-meaning team lead starts assigning tickets to the freelancer like everyone else, and integration creeps, the external gets the same badge, the same standing meetings, the same review cycle, because that is operationally convenient. Neither is malicious; both re-shape the lived engagement toward employment or leasing. Writing the safeguards down (item 8) and reviewing them (item 9) is what turns good intentions at signing into a defensible pattern over time.

Why items 5-6 exist: evidence and provider verification

Item 5 is about the overall picture: entrepreneurial indicators, own invoicing, insurance, equipment, multiple clients, do not individually decide a status question, but they are the context in which the decisive factors are read, and collecting them at the start costs minutes while reconstructing them years later during an audit costs weeks. Item 6 extends the same diligence to agencies: the riskiest configurations in German staffing are not solo freelancers but provider constructs whose label and reality diverge, a services frame over leasing behavior, or leasing without a valid license. A provider that answers the license and direction questions crisply is signaling operational maturity; one that waves them off is telling you where its risk will land, on you.

Why items 7-9 protect the whole engagement: council, documentation, review

Works-council involvement (item 7) protects the timeline and the relationship: legally required for leased workers, and cheap insurance as proactive information for contractor models, because councils resist what they discover far more than what they were told. Documentation (item 8) is the quiet hero of every contested case: a dated working-model record shows the engagement was designed, not improvised. And the review rhythm (item 9) is the item that keeps the checklist honest, because German classification follows lived practice, and lived practice drifts. A quarterly half-hour against this list, plus a fixed check at every extension, is the cheapest compliance instrument in this entire series. When a review finds real drift, the responsible moves are to restructure the engagement, convert it honestly (to employment or declared leasing), or put the question to counsel or the status-determination procedure, not to extend and hope.

Frequently asked questions

If we tick every item, are we safe from reclassification?

Safer, not safe. The checklist aligns the engagement with defensible paradigms and creates the evidence trail, but classification always turns on the overall picture of the lived case, and authorities decide it, not checklists. That is precisely why the review item exists and why borderline cases belong with your counsel or the Statusfeststellungsverfahren.

Who inside the company should own this checklist?

In practice it works best with one accountable owner per engagement, often the hiring manager or a procurement/HR partner role, with legal counsel involved at setup and for escalations, and the review appointments in a real calendar rather than a policy document. Diffuse ownership is how the review item silently dies.

How often should the periodic review happen?

A common, practical rhythm is quarterly for active engagements plus a mandatory check at every extension or scope change. The review is short if the engagement is clean, a half hour against the checklist, and its value is precisely that it catches drift while it is still cheap to correct.

Does this checklist replace involving a lawyer?

No, and it is not meant to. It structures the operational side so that your legal counsel reviews a well-designed engagement instead of untangling an improvised one, and it flags the escalation points, contract-type choice, borderline autonomy or integration findings, provider constructs, where their judgment is exactly what you are paying for.

Head of AI Delivery, Aiporate

Elena has spent 12 years building and embedding AI and data teams inside B2B SaaS companies, from first pilot to enterprise-wide platform. At Aiporate she leads how forward-deployed talent is matched, onboarded and shipped to production.

Need the team to make this real?

Describe your need in plain English, get the exact hire, forward-deployed talent or a fractional leader, vetted and matched in 72 hours.

Scope your need →

Keep reading

The Weekly Brief

Intelligence for building AI-native organizations.

One email a week: the sharpest thinking on AI hiring, infrastructure, teams and strategy, for the people building the future of work.

Join operators, founders and CTOs. No spam, unsubscribe anytime.