Most contracts with external software teams are drafted carefully. Most reclassification risk is created afterwards, in the ticket system, the stand-up and the team chat. German law distinguishes between instructions that relate to the work product (werkbezogene Weisungen), which a client may give, and instructions that relate to how, when and where individual people work (arbeitsbezogene or personenbezogene Weisungen), which belong to the employer. If the second type moves to the client, the engagement starts to look like Arbeitnehmerüberlassung, regardless of the contract title. This note translates that distinction into the tools engineering teams use every day.

Why daily practice is where the risk sits

German authorities assess the lived reality of an engagement, and they do so at volume. German customs reported that the Finanzkontrolle Schwarzarbeit checked 25,800 employers in 2025, opened around 98,200 criminal proceedings across all sectors and put the damage caused by undeclared work at about EUR 675 million. The Deutsche Rentenversicherung carried out 23,052 status determination procedures in 2024. In both settings, what counts is not only what the contract says, but how work is actually assigned.

The benchmark for legitimate labour leasing is substantial: the Bundesagentur für Arbeit recorded around 622,000 temporary agency workers on 30 June 2025, all within a licensed regime. Integrating external engineers into your own ticket flow without that regime is exactly the scenario this field note helps you avoid. With Bitkom still counting 79,000 unfilled IT positions in Germany in 2026, many engineering organisations will rely on external teams for years, which makes a stable working routine more valuable than a one-off contract review.

The legal anchor

§106 GewO gives the employer the right to determine the content, place and time of work. §1 Abs. 1 Satz 2 AÜG describes Überlassung as integration into the client's work organisation combined with subjection to the client's instructions. §611a Abs. 1 Satz 6 BGB makes the actual performance decisive over the contract wording. A client in a Werk- or Dienstvertrag may specify what is to be built and may give instructions concerning the work product. It should not take over the steering of individuals: assigning tasks to named engineers, setting their hours, approving their absences or evaluating their personal performance.

No single factor decides. Courts and authorities form an overall picture. The aim is therefore not to avoid every contact between client staff and vendor engineers, but to make sure the overall pattern shows the vendor organising its own people.

Traffic-light guide for daily tools

PracticeAssessmentSafer pattern
Client writes epics and user stories with acceptance criteriaGreen: describes the work productKeep stories outcome-oriented, not person-oriented
Client assigns Jira tickets to named vendor engineersRed: direct tasking of individualsAssign to the vendor team or the vendor lead, who distributes internally
Client product owner prioritises the backlogAmber: acceptable if the vendor plans the sprintPriorities feed into a sprint plan the vendor lead commits to
Vendor engineers attend the client's daily stand-up and report individually to client managersRed: integration into the client's organisationVendor runs its own stand-up, the vendor lead joins a sync with the client
Joint sprint review and demoGreen: acceptance of resultsFrame as review of increments against acceptance criteria
Client sets core hours for named engineersRed: control of working timeAgree service windows for the team, staffed by the vendor
Client approves leave or replacements of individualsRed: personnel managementVendor guarantees capacity and qualification, staffs autonomously
Client gives code review comments on pull requestsAmber: work-product related, but can driftReview comments address the code and acceptance criteria, rework is scheduled by the vendor
Vendor engineers in the client's org chart, email domain or HR toolsRed: visible integrationSeparate accounts or clearly marked external accounts, no HR system access
Client gives individual performance feedbackRed: employer functionFeedback on deliverables goes to the vendor lead

Jira configuration that supports the boundary

  • Create a dedicated project or board for the vendor team. Client staff create and prioritise issues, the vendor lead moves them into sprints.
  • Use a team assignee or the vendor lead as default assignee for new issues. Internal distribution is the vendor's decision.
  • Separate the backlog (client influence) from the sprint (vendor commitment). Changes to a running sprint go through the vendor lead.
  • Map acceptance criteria into a field or checklist on each story, so that review and Abnahme refer to the issue, not to a person.
  • Avoid time tracking dashboards per engineer for the client. Report at team or deliverable level.

Meetings and communication

Stand-ups

A daily stand-up where vendor engineers report to the client's engineering manager, receive tasks and are asked about their availability is one of the clearest signs of integration. A workable alternative: the vendor team runs its own stand-up, and a short client sync (daily or a few times per week) between the client's product owner or tech lead and the vendor lead covers blockers, priorities and clarifications.

Chat channels

Shared Slack or Teams channels are normal and useful for technical clarification. The risk lies in using them for direct tasking (can you quickly do X today) or for checking presence. A simple rule helps: technical questions in shared channels, new work and priority changes through the vendor lead.

Pair work and incidents

Pair programming, architecture workshops and incident response require direct contact. They are compatible with a Werk- or Dienstvertrag when they serve the work product and are not used to direct individuals beyond that purpose. For on-call or incident work, define the service in the contract (response times, escalation path) and let the vendor staff it.

A ten-question self-check

  1. Does anyone on your side assign tickets to named vendor engineers?
  2. Do vendor engineers attend your internal stand-ups as participants?
  3. Do you set or monitor working hours of individuals?
  4. Do you approve leave, sick notes or replacements?
  5. Do you give individual performance feedback or ratings?
  6. Are vendor engineers listed in your org chart or HR tools?
  7. Do vendor engineers use your hardware or internal accounts without external marking?
  8. Can the vendor replace a team member without your consent?
  9. Is there a named vendor lead through whom work flows?
  10. Is acceptance based on deliverables rather than hours?

Questions 1 to 7 should be answered no, questions 8 to 10 yes. Each deviation is not automatically fatal, but several together form the overall picture that authorities and courts evaluate.

Make it a routine

Drift happens gradually. A new engineering manager joins, a deadline approaches, and direct tasking feels faster. A quarterly check against the list above, documented briefly, keeps the operating model aligned with the contract. Onboarding for new client staff should include a short explanation of how to work with the external team.

This article is general information and does not constitute legal advice for your specific situation.

A boundary that depends on everyone remembering the rules will drift; one that is built into roles and tools tends to hold. In a niogod™ pod, the German-speaking Projektleiter is the defined channel for requirements and priorities, so your team steers the work product while the vendor directs the engineers, as outlined on the compliance page. If an external team is about to join your Jira board, setting up that channel before the first sprint is far easier than correcting habits later.

Talk to niogod™

Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.

Book consultation
← All insights