German procurement processes are thorough for hardware suppliers and often surprisingly thin for engineering service providers. Yet an offshore engineering vendor will have access to source code, infrastructure and sometimes personal or export-controlled data. A structured due diligence process before signature costs a few days. Discovering a gap after go-live can cost months. This guide provides a checklist in eight sections that procurement, legal, information security and engineering can work through together.

How to use the checklist

Send sections 1 to 7 to the vendor as a written questionnaire and ask for evidence, not assertions. Use section 8 for your own internal assessment. Mark each item as fulfilled, partially fulfilled or missing. Decide in advance which items are knock-out criteria for your organisation; for most DACH companies, data protection and intellectual property belong in that category.

Why diligence matters in a crowded market

The pool of potential vendors is large and growing. NASSCOM estimates that India's technology industry generated USD 315 billion in revenue in fiscal year 2026 with about 5.95 million employees, and a 2024 NASSCOM and Zinnov study counted more than 1,700 Global Capability Centres in India. Breadth of supply means wide variation in maturity, from listed service firms to very young providers. Demand pressure in DACH adds urgency that can cut diligence short: Bitkom's 2025 survey counted about 109,000 unfilled IT positions in Germany and an average of 7.7 months to fill one, and ICT-Berufsbildung Schweiz projects a gap of about 54,400 ICT specialists in Switzerland by 2033. A structured checklist protects the process from the time pressure these numbers create.

1. Corporate identity and stability

  • Full legal name, registration number and registered address of the contracting entity.
  • For Indian entities: company registration details that can be verified in the public records of the Ministry of Corporate Affairs.
  • Ownership structure and ultimate beneficial owners.
  • Recent financial statements or, for younger companies, evidence of funding and runway.
  • Name and role of the person signing, and their authority to bind the company.
  • Local presence or contact in the DACH region, and the language of contract management.

2. Contract model and labour law

  • Is the engagement structured as Werkvertrag (BGB §631), Dienstvertrag (BGB §611) or Arbeitnehmerüberlassung?
  • If not Arbeitnehmerüberlassung: how does the vendor ensure that its engineers are not integrated into your organisation and do not receive instructions from your staff (§1 Abs. 1 Satz 2 AÜG)?
  • If Arbeitnehmerüberlassung is intended: does the vendor hold the required permission?
  • Who directs the engineers day to day, and how is that documented?
  • If the vendor is a single person or very small: has Scheinselbständigkeit risk under SGB IV §7 been considered, and would a Statusfeststellungsverfahren under SGB IV §7a be appropriate?
  • Are the vendor's engineers employees of the vendor, or subcontracted freelancers?

3. Data protection

  • Draft data processing agreement under DSGVO Art. 28, including technical and organisational measures.
  • Transfer mechanism for data leaving the EU under DSGVO Art. 44 ff., typically the EU Standardvertragsklauseln, and support for your transfer impact assessment.
  • List of sub-processors, including cloud providers.
  • The vendor's approach to India's Digital Personal Data Protection Act, 2023, where relevant to its own processing.
  • Process and timelines for reporting personal data breaches to you.

4. Information security

  • Certifications such as ISO/IEC 27001, with scope and validity, or a credible roadmap if not yet certified.
  • For automotive supply chains: whether a TISAX assessment is available or planned.
  • Device management: company-owned, encrypted, centrally managed endpoints.
  • Access model: least privilege, client-managed identities where possible, prompt revocation on exit.
  • Secure development practices: code review, dependency scanning, secrets management.
  • Physical security and remote-work policy at the delivery location.

5. Intellectual property and code ownership

  • Contractual grant of exclusive, unrestricted rights of use (Nutzungsrechte, §31 UrhG) in all work results.
  • Evidence that employment contracts with engineers assign rights to the vendor in writing.
  • Open-source policy and licence scanning; disclosure of pre-existing components.
  • Confidentiality obligations that bind every individual engineer, not only the company.

6. Export control and sector regulation

  • If your technology may fall under the EU dual-use regulation 2021/821: has the vendor understood that sharing controlled technology with a team outside the EU can require an export licence?
  • For medtech: experience with MDR documentation requirements and software lifecycle processes under IEC 62304.
  • For defence and dual-use clients: willingness to work within your export control and screening processes.

7. Delivery capability and continuity

  • Named delivery lead and their language skills for German-speaking stakeholders.
  • Seniority definitions and CVs for proposed team members.
  • Replacement process: notice period, maximum time to replace, overlap for knowledge transfer.
  • Bench depth: how many qualified engineers could step in if needed?
  • Exit plan: handover package, documentation standards, return or deletion of data.
  • References, or for younger vendors, willingness to start with a paid, scoped pilot sprint.
  • Professional indemnity and cyber insurance, with coverage amounts.

8. Internal assessment

  • Tax: will invoices be handled under the reverse charge mechanism of §13b UStG? Does any part of the contract involve licensing that could trigger withholding under §50a EStG?
  • Supply chain obligations: if your company falls within the scope of the Lieferkettensorgfaltspflichtengesetz (LkSG), has the vendor been included in your risk analysis?
  • Works council: does the engagement touch matters requiring Betriebsrat involvement, for example tools that monitor performance?
  • Internal ownership: who on your side is the product owner and contract owner?
  • Budget and approval: does the total contract value require additional internal approval levels?

Red flags

Some answers should stop a process or at least escalate it:

  • The vendor proposes that your managers direct its engineers directly but does not raise the AÜG question.
  • No data processing agreement or standard contractual clauses are offered.
  • Intellectual property is licensed rather than granted exclusively, or remains with the vendor until final payment of all invoices without limitation.
  • The contracting entity cannot be verified in public records.
  • CVs are anonymised and the vendor will not commit to named individuals.

Proportionality

Not every engagement needs every item at full depth. A two-person pilot on non-sensitive code needs less than a long-term team with production access. Scale the depth of review to the access the vendor will have and the impact of a failure. What should not be skipped, at any size, are the contract model, data protection and intellectual property sections.

This checklist is general information, not legal or tax advice.

A provider without a long public track record should expect to be examined against exactly this list, and niogod™ is no exception: our compliance approach, built on a Werkvertrag or Dienstvertrag with Abnahme rather than staff provision, is described on the security page. If a vendor review sits on your plan for next year, starting it early leaves room to do it properly.

Talk to niogod™

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

Book consultation
← All insights