Master Services Agreement in Poland: Template, Key Clauses and Local Law (2026)

A master services agreement (MSA) sets the standing terms between a supplier and a customer so each new project only needs a short statement of work. In Poland the framework is the Civil Code, which gives wide freedom of contract but also supplies default rules when the parties stay silent. This guide covers the law, the key clauses and a working skeleton. It is general information, not legal advice; confirm a live deal with a Polish lawyer. ## What law governs an MSA in Poland? There is no dedicated master services statute. An MSA rests on the Polish Civil Code (Kodeks cywilny) of 23 April 1964. The starting point is the freedom of contract in Article 353(1): parties may shape the relationship as they wish, as long as its content and purpose do not conflict with the nature of the relationship, the law, or the principles of social coexistence. Beyond that, several Civil Code rules matter for a services framework: - Service contracts. Where the services are not a specific named contract, Article 750 applies the rules on mandate (umowa zlecenia, Articles 734 and following) by analogy. A project that is really a defined deliverable may instead be a contract for specific work (umowa o dzielo, Article 627), which carries a result obligation and statutory warranty for defects. The classification drives the warranty and the liability.

• Form. Contracts are generally valid without special form, but Article 77 governs how an agreement is amended or terminated when it was made in writing, and some clauses (for example certain penalty or assignment terms) are safer in documentary or written form for proof.
• Sole traders. Since 1 January 2021, some consumer protections in the Civil Code extend to individual entrepreneurs (one-person businesses) where the contract is not of a professional character for them. Keep this in mind if a counterparty is a sole trader. ## Key clauses in a Polish MSA - Structure and precedence: the MSA sets the framework; each statement of work (SOW) covers one project; state which document prevails on conflict.
• Services and classification: describe the services and whether a given engagement is a service contract (mandate rules by analogy) or a contract for specific work with a result obligation.
• Charges and payment: rates, invoicing, and interest for late payment under the Act on counteracting excessive delays in commercial transactions.
• Contractual penalties (kara umowna): Polish contracts often use contractual penalties under Articles 483 and 484; they can only secure non-monetary obligations, and a court may reduce a grossly excessive penalty.
• Intellectual property: copyright transfer or licence must specify the fields of exploitation (pola eksploatacji) under the Copyright Act; a bare assignment without them does not transfer those uses.
• Confidentiality and data protection: GDPR and the Polish Act of 10 May 2018 on Personal Data Protection where personal data is processed, with a separate Article 28 data processing agreement.
• Liability: caps and exclusions, remembering liability for intentional harm cannot be excluded in advance (Article 473).
• Term and termination: duration, renewal, and notice.
• Governing law and forum: Polish law and a chosen court or arbitration. ## A simple drafting skeleton 1. Parties and date

2. Definitions
3. Structure: MSA, SOWs and order of precedence
4. Services and their classification
5. Customer responsibilities
6. Charges, invoicing and late-payment interest
7. Change control
8. Contractual penalties
9. Intellectual property and fields of exploitation
10. Confidentiality
11. Data protection and the linked DPA
12. Limitation of liability (Article 473 limit respected)
13. Term, renewal and termination
14. Governing law (Polish) and dispute resolution
15. Signatures ## Common mistakes - Transferring copyright without listing the fields of exploitation, so key uses are not actually assigned.

• Trying to exclude liability for intentional harm, which Article 473 forbids.
• Setting a contractual penalty on a monetary obligation, where it does not work.
• Ignoring whether an engagement is a mandate or a contract for specific work, which changes the warranty.
• Forgetting the Article 28 data processing agreement when services touch personal data. ## Keeping a services contract portfolio under control If you run many SOWs under one MSA, the hard part is not the first draft. It is tracking which SOW is live, when each renews, and whether a penalty or IP clause is consistent and enforceable. That work (drafting from a tuned template, flagging risky clauses, tracking renewals and keeping versions straight) is what an AI contract workspace can hold in one place. Adira is built for this, with per-clause risk review and plain-English clause editing; it is India-first today with other jurisdictions on its roadmap, so verify local depth before relying on it for Polish law. More at Adira. The law above stands on its own. ## Bottom line A Polish MSA is built on freedom of contract in Article 353(1) of the Civil Code, but the Code's default rules on service contracts, contractual penalties, intellectual property and liability shape what you can safely write. Classify each engagement, list the fields of exploitation for any IP, keep penalties and liability within the Code, and get Polish advice before signing a real deal.