The short answer
A good software development contract answers five questions. What exactly is being built, and how will scope changes be handled? How will you prove the work is done? Who owns the code, and on what terms can you use the supplier's own components and open-source libraries? What happens after go-live, meaning warranty, maintenance and the SLA? And how do you leave if the relationship ends? If the contract is silent on any of these, the answer will eventually come from a dispute or from the default rules of the Lithuanian Civil Code, which don't always fit software well.
The SLA (service level agreement) is a separate schedule that turns "support" into measurable numbers: severity levels, response and resolution times, availability, how each is measured, and what happens when targets are missed. One rule matters more than the rest: if a metric can't be checked against monitoring or ticketing data, it won't work in practice.
This guide is written for the buyer: a medium or large company or a public body in Lithuania commissioning custom software or its maintenance. We checked the legal references on 19 November 2026. It is a practical guide, not legal advice, so have a lawyer review the final wording.
How this guide fits with our other articles
Before you sign, ask the supplier the right questions. We covered those in How to choose a software development partner: 12 questions to ask before signing. The cybersecurity clauses that NIS2 entities must have in supplier contracts are broken down in NIS2 and your software supplier. This article is about the contract itself: how to structure it, the clauses that cause most disputes, and how to write an SLA that actually gets enforced.
Contract structure: which documents you need
For a long-running project, a layered structure works best. A framework agreement sets the rules that don't change, and each piece of work is ordered separately. You then don't have to rewrite the whole contract for every new phase.
| Document | What it covers | How often it changes |
|---|---|---|
| Framework agreement | Parties, pricing principles, IP rights, confidentiality, liability, termination, disputes | Rarely, and only by mutual agreement |
| Technical specification | What the system must do, non-functional requirements, integrations, acceptance criteria | Per phase |
| Order or statement of work | Specific scope, deadlines, price or budget, named contacts | Per phase or block of sprints |
| SLA schedule | Scope of support, severity levels, response and resolution times, availability, reporting | Yearly, or when the system changes |
| Data processing agreement | The terms required by GDPR Article 28 if the supplier will access personal data | When sub-processors or data scope change |
| Security schedule | Access, logging, incident notification, audit rights | When requirements change |
| Exit plan | What you receive, and how fast, when the contract ends | Reviewed yearly |
We explained how to write a specification that can actually be tested in Technical specification for a software project. The contract should also say which document prevails if they conflict. The usual order is framework agreement first, then the order, then the specification.
Contract for work or contract for services
The Lithuanian Civil Code distinguishes a contract for work (rangos sutartis), where the contractor performs work at its own risk and hands over the result (Article 6.644), from a contract for services (paslaugų sutartis), covering intangible services not linked to creating a material object (Article 6.716). Building a system with a defined result tends to look like a contract for work, while maintenance and consulting look more like services. How a given contract is classified depends on its content, not its title, so that question belongs with your lawyer. What the buyer needs to know is that the default rules differ:
- Acceptance. Under a contract for work, acceptance is recorded in a signed act, and a customer who accepts work without checking it loses the right to rely on obvious defects that a normal inspection would have revealed (Article 6.662(1) and (3)).
- Time limit for defects. If no warranty period is set, defects must be identified within a reasonable time, and no later than two years after handover (Article 6.666(2)). Claims for defects are subject to a one-year limitation period (Article 6.667).
- Termination. Under a services contract, the client may terminate at any time by paying for services already provided and reasonable costs (Article 6.721(1)). Under a contract for work, the customer may withdraw before the work is finished if there are important reasons, paying for the completed part and compensating losses (Article 6.658(4)).
The practical takeaway: don't count on the default rules to protect you. Write acceptance, warranty and termination into the contract yourself.
Pricing and change control
The pricing model decides who carries the scope risk. No model is always better, but each one needs different clauses.
| Model | Works well for | What the contract must say |
|---|---|---|
| Fixed price | A clear, approved scope: discovery, a first version, a specific module | Exact scope, what is excluded, acceptance criteria, change procedure |
| Time and materials | Ongoing development where priorities shift | Rates per role, monthly budget, timesheets, right to pause work |
| Time and materials with a cap | Scope that is only partly clear | The cap, written approval to exceed it, and what happens when it is reached |
| Fixed monthly fee | Maintenance and SLA | What the fee covers, hours for small changes, how extra work is billed |
The most common source of disputes isn't price. It is the blurry line between a bug and a new request. A simple contractual rule helps: a defect is system behaviour that doesn't match the approved specification or acceptance criteria. Everything else is a change. Change control then needs four steps: the customer describes the request, the supplier estimates effort and impact on deadlines within an agreed time, the customer approves or rejects in writing, and an approved change becomes part of the order. For how phasing and contract model affect project cost, see How much does custom software development cost.
Acceptance: how you prove the work is done
Acceptance is usually the point where the warranty starts, payment becomes due and, if agreed, IP rights transfer. It needs precise wording.
- Acceptance criteria for every phase, agreed in advance and testable: specific scenarios, performance requirements, integration checks with test data.
- A testing period for the customer to check the result. Make it realistic: a single module with a handful of users and a system with five integrations need very different amounts of time.
- Defect categories. For example: a critical defect (the system or a core process doesn't work) blocks acceptance; major defects block it above an agreed number; minor defects are listed in the acceptance record and fixed within an agreed time.
- Retesting after fixes, and how many rounds are allowed before the customer can use other remedies.
- Deemed acceptance. The supplier reasonably needs protection from a customer who never signs. The customer needs protection from a deadline that is too short. A clause that works for both: the result is deemed accepted if no reasoned defect list is submitted within the agreed testing period.
- Production use. Agree whether using the system in live operation counts as acceptance. A common compromise is that it doesn't, provided the defect list was submitted on time.
Rights in the code and licences
In Lithuania, computer programs are protected by copyright (Law on Copyright and Related Rights, Article 4(2)(1)). Under Article 10(2) of the same law, the economic rights in a program written by an employee in the course of their duties belong to the employer unless a contract says otherwise. For the buyer, that means that without a clear agreement, the rights to the code stay with the development company whose staff wrote it.
Several statutory rules shape the contract text directly:
- Copyright contracts transferring economic rights, licence contracts and contracts commissioning a work must be in writing (Article 42(1)).
- The contract must state the rights transferred (the ways the work may be used), the licence type, territory, term and fee. If no territory is stated, the rights are deemed transferred for Lithuania only. If no term is stated, either party may terminate with one year's written notice (Article 40(1) and (2)).
- If the ways of use aren't specified, the contract is deemed to cover only those needed for its purpose (Article 40(3)).
- Rights to all future or unidentified works can't be transferred (Article 38(3)). A framework agreement should therefore say that rights pass for each result created and accepted under an order.
- Moral rights stay with the author, but for computer programs they can't be used in a way that unreasonably restricts the rightholder's freedom to adapt, modify and distribute the program (Article 14(3)).
Not all of the code is "your code"
Nearly every system contains three kinds of code, and each needs a different clause:
| Type of code | Usual arrangement | What to check |
|---|---|---|
| Code written specifically for you | Economic rights transfer to the customer | Ways of use (reproduce, modify, adapt, distribute, pass to third parties), territory, term, when the rights pass |
| Supplier's pre-existing components (frameworks, modules) | Non-exclusive, perpetual licence | Whether the licence survives termination, and whether another supplier may modify the system |
| Open-source libraries | Their own licences apply | A list of components and licences at each handover, especially copyleft licences |
Ask for a dependency and licence list at the end of each phase. For example, section 13 of the GNU AGPLv3 requires that users interacting with a modified version over a network be offered its source code. For most internal systems this is not an issue, but you want to know before you open the system to customers.
What you should physically receive
Rights to the code mean little if you don't have the code. List the deliverables in the contract: source code in a repository you control, the database schema and migrations, deployment instructions or automated deployment scripts, configuration without secrets, technical documentation, and all accounts (domain, servers, cloud accounts, third-party API keys) in your name. Ideally the repository and cloud account belong to the customer from day one, with the supplier working inside them under granted permissions.
Warranty and maintenance are two different things
A common mistake is assuming the monthly maintenance fee also covers fixing the supplier's own bugs. Warranty and maintenance solve different problems:
- Warranty: the supplier fixes defects free of charge, meaning places where the system doesn't match what was agreed and accepted. Put the length and start of the warranty period (usually the acceptance date) in the contract. If none is set, the Civil Code Article 6.666 rules mentioned above apply.
- Maintenance: a paid service covering what isn't the supplier's fault: monitoring, security and version updates, adapting integrations when an external system changes its API, backups and restore tests, user support and small changes.
It is worth agreeing that warranty defects are fixed under the same SLA response times as maintenance incidents. Otherwise a warranty bug can wait a week while a paid incident gets fixed within hours.
The SLA: how to write one you can check
An SLA has to answer three questions: what we measure, how we measure it, and what happens when a target is missed. Start with severity levels, because every other number depends on them.
Severity levels and timings
The table below is an example of how an SLA can be structured. It is not a market standard: the right numbers depend on what an outage costs your process and how much you are willing to pay for on-call cover.
| Level | Definition | Response time (example) | Resolution or workaround (example) | Coverage |
|---|---|---|---|---|
| P1 critical | System down, or a core process stopped for all users | 1 hour | 8 hours | 24/7 or business hours, as agreed |
| P2 high | Important function broken, but a workaround exists or only some users are affected | 4 business hours | 2 business days | Business hours |
| P3 medium | A bug that doesn't stop work | 1 business day | Next scheduled release | Business hours |
| P4 low | Question or minor request | 2 business days | As agreed | Business hours |
Three details decide whether this table works:
- Who sets the level. Usually the customer sets the initial level and the supplier can reasonably change it. In a dispute, the definition in the table decides, so make it specific to your system: what counts as a "core process" (order intake, invoicing, login, for example).
- When the clock starts. From the moment a ticket is logged in the agreed channel, not from an email to a particular developer. For P1, you also need a phone number.
- Response and resolution are different. Response means a qualified person has started working on the problem, not an auto-reply. Resolution time can be a target rather than a commitment, especially when the cause is an external system. Say so explicitly.
Availability: convert percentages into minutes
An availability commitment sounds good, but only once you know how much downtime it allows. A 30-day month has 43,200 minutes:
| Monthly availability | Downtime allowed in 30 days |
|---|---|
| 99% | about 7.2 hours |
| 99.5% | about 3.6 hours |
| 99.9% | about 43 minutes |
Alongside the percentage, set out how availability is measured (for example, independent monitoring checks the home page and login every minute), what counts as downtime, which planned maintenance windows are excluded and how much notice is given, and what is excluded because it is outside the supplier's control. If the system runs on your own or a third party's infrastructure, the supplier can't commit to server availability, only to its own response times.
Reporting and review
Each month the supplier should send a short report: tickets by severity, how many were resolved on time, availability, updates applied, hours used. Once a quarter or every six months, check whether the levels and timings still match your processes. An SLA that nobody measures is just text.
What happens when the SLA is missed
The most common mechanism is a service credit, a reduction of the monthly fee, for example a set percentage for each missed P1 deadline with an overall monthly cap. Under Lithuanian law this is essentially a contractual penalty (netesybos). Two Civil Code rules are worth knowing. First, when damages are claimed, penalties count towards the damages (Article 6.258(2)). Second, a court may reduce an unreasonably high penalty, but not below the actual loss (Articles 6.258(3) and 6.73(2)). So very large penalties are often less effective than a moderate credit that applies automatically. For repeated failures, a different clause is more useful: a right to terminate if P1 deadlines are missed, say, for several months in a row.
For NIS2 entities, service levels are one of the mandatory elements of supplier contracts (point 34.7 of Lithuania's Cybersecurity Requirements Description). We covered how to align it with the other security clauses in our NIS2 article.
Liability and its limits
Almost every supplier will propose a liability cap, usually the contract value or the fees paid over a set period. That is normal and not a problem in itself, but the buyer should know what can't be limited and what is worth carving out:
- An agreement excluding or limiting liability for losses caused intentionally or through gross negligence is void (Civil Code Article 6.252(1)).
- A business is liable only for losses it foresaw or could reasonably have foreseen when the contract was signed (Article 6.258(4)). If an hour of downtime costs you a specific amount, it helps to state that in the contract or a schedule.
- Breaches of confidentiality, data protection and intellectual property are often carved out of the cap. The Public Procurement Office's standard services contract terms do the same (more on them below).
From 9 December 2026, Civil Code amendments (Law No XV-1080) take effect that transpose the new EU Product Liability Directive (EU) 2024/2853. Under the directive, software counts as a product, and the new rules apply to damage suffered by natural persons from products placed on the market or put into service from that date. For most internal business systems this changes little. If you are building a system or app that consumers or other individuals will use, discuss with your lawyer how the contract should allocate responsibility for updates and potential claims.
Termination and handover
Exit terms are easiest to agree while the relationship is still good. The exit plan should cover:
- what the supplier hands over (code, documentation, a database copy, accounts) and within how many days of a termination notice;
- transition support for a new supplier or your own team: how many hours, at what rate, for how long;
- that maintenance continues under the same SLA throughout the notice period;
- return of data and deletion from the supplier's environments, with confirmation, as the data processing agreement also requires.
If part of the solution is the supplier's SaaS platform, the EU Data Act switching rules apply on top. We covered those, and when custom-built services are exempt, in Leaving a SaaS platform with your data.
Public sector: what the Public Procurement Law changes
For contracting authorities, much of the contract is shaped by the Law on Public Procurement (VPĮ) and the standard terms approved by the Public Procurement Office (VPT). The points that matter most for IT projects:
- Standard terms are mandatory. Procurement contracts must use the VPT's standard terms unless they are not applicable or can't be adapted and the authority justifies this (VPĮ Article 87(1)). The standard terms for public services contracts apply to procedures started from 1 March 2025 (VPT Director's Order No 1S-209). A contract consists of general and special conditions, and the special conditions can amend or supplement the general ones.
- Intellectual property. Under point 15.1 of the general conditions, results and intellectual property rights, except moral rights, pass to the buyer when the acceptance act is signed, unless the special conditions say otherwise. For software, the special conditions should still describe licences for the supplier's pre-existing components and open-source code, since those can't be transferred outright. The technical specification may state whether IP rights must be transferred (VPĮ Article 37(1)).
- Acceptance window. Under the general conditions, the buyer accepts the result or issues a defect report within 5 business days, and if no defect report is issued in time the services are deemed accepted (points 6.2.3 and 6.2.6). For a complex system that is often too short, so set out the testing period and acceptance criteria clearly in the special conditions and the technical specification.
- Warranty. Once defects are fixed, the warranty period for that result starts again from the handover of the properly delivered services (point 7.3.4).
- Liability cap. Losses are compensated up to the initial contract value, but the cap doesn't apply to breaches of confidentiality, data protection or intellectual property (point 17.2).
- Changes. The scope for changing a contract is limited (VPĮ Article 89). A services contract can be changed without a new procurement, for example, where the change was clearly and precisely provided for in the procurement documents, or where the total value of such changes stays within 10% of the initial value and below the international procurement thresholds. Further development phases, extra hours and maintenance extensions therefore need to be built in as options in the procurement documents from the start.
- Price review. If services run for more than 6 months including extensions, the contract must include a price review clause not linked to tax changes, unless the pricing method makes recalculation impossible (VPĮ Article 87(2)(7)).
Example: what this can look like in practice
Vetrunge Logistics is a fictional company, and the figures are illustrative. A company with 180 employees commissions an order management system integrated with its accounting software and courier systems.
- Structure. A three-year framework agreement and three orders: fixed-price discovery, a fixed-price first version based on the specification approved during discovery, and further development on time and materials with a monthly budget.
- Acceptance. A 10-business-day testing period per phase. Any critical defect, or more than five major ones, blocks acceptance. If no reasoned list is submitted in time, the result is deemed accepted.
- Rights. Economic rights in the custom code pass to the company once each accepted phase is paid, worldwide and with no time limit, including the right to modify it and hand it to another supplier. The supplier's reporting module is used under a non-exclusive perpetual licence.
- SLA. P1 response within 1 hour on business days, 7:00 to 20:00. No availability commitment, because the servers sit in the company's own cloud account. Credit: 5% of the monthly fee for each missed P1 deadline, capped at 25% a month. Three consecutive months with missed P1 deadlines give a right to terminate.
- Exit. The repository and cloud account belong to the company from the start, and transition support is capped at 40 hours at the agreed rate.
Pre-signing checklist
- Is it clear which document prevails if they conflict?
- Does every phase have testable acceptance criteria and a realistic testing period?
- Have you agreed what counts as a defect and what counts as a change, and how changes are approved?
- Are the ways of use, territory, term and timing of the rights transfer stated?
- Are the supplier's pre-existing components and their licence listed, and does the licence survive termination?
- Will the supplier provide a list of open-source dependencies and licences?
- Do the repository, domain and cloud accounts belong to you?
- Are the warranty period, its start and fix times written separately from maintenance?
- Are the SLA severity levels defined for your system rather than in general terms?
- Is it clear when the response clock starts and which channel tickets go through?
- Has availability been converted into minutes, and is it clear how it is measured?
- Are monthly reports and consequences for missed SLAs in place?
- Does the liability cap leave out intent, gross negligence, data protection and confidentiality breaches?
- Is there a data processing agreement if the supplier will see personal data?
- Is there an exit plan with deadlines and transition support?
Common mistakes
- Signing the supplier's standard template with no schedules. Templates usually contain general terms but not what matters most for your project: acceptance criteria, SLA levels and an exit plan.
- "All rights pass to the customer" with no detail. Without ways of use, territory and term, the phrase may mean less than you expect (Copyright Law Article 40).
- An SLA without measurement. A "99.9%" commitment with no monitoring or reports is practically unverifiable.
- Mixing up warranty and maintenance. The customer ends up paying maintenance hours for the supplier's own bugs.
- No options in a public tender. After launch it turns out that development or maintenance needs a new procurement.
FAQ
Can we do without a separate SLA?
For a small system whose downtime doesn't cause major losses, a few maintenance clauses in the main contract can be enough. When the system matters for daily operations, keep the SLA as a separate schedule: it changes more often than the contract and is easy to review each year.
When should the rights to the code transfer?
The most common compromise is transfer upon payment for each accepted phase. The supplier is protected against non-payment, and the customer avoids a situation where rights pass only at the end of a multi-year project.
Can the supplier reuse our project code for other clients?
If the economic rights are transferred to you, not without your permission. Shared components the supplier owned before the project, however, it will normally keep using. That is why the contract should clearly separate code written specifically for you.
How long should the warranty be?
The law doesn't set a length, and the parties can agree on one. If no warranty period is set, under a contract for work defects must be identified within a reasonable time and no later than two years (Civil Code Article 6.666(2)). More important than the length is how quickly defects are fixed and what counts as a defect.
Does an SLA credit stop us from claiming damages?
No, but penalties already paid count towards the damages (Civil Code Article 6.258(2)). In the public procurement standard terms, penalties are treated as minimum losses that don't need to be proven, and greater losses can be claimed up to the agreed cap.
What to do next
If you are drafting a contract now, start with the two schedules most often left out: acceptance criteria and an SLA table with severity levels defined for your system. If the contract is already signed, run through the checklist and mark the three biggest gaps. These can usually be closed with an annex to the existing contract.
DESAmedia helps buyers prepare technical specifications, acceptance criteria and support terms through IT consulting and system design, builds web applications and business management systems, and works with public bodies within procurement rules through our public sector services. Our phased approach is described on the process page. To discuss your situation, get in touch.
Sources
- Law on Copyright and Related Rights of the Republic of Lithuania (e-tar.lt, consolidated text, in Lithuanian)
- Copyright Law Article 10, copyright in computer programs (unofficial text, atviri-teises-aktai.lt, in Lithuanian)
- Copyright Law Article 40, terms of copyright contracts (unofficial text, atviri-teises-aktai.lt, in Lithuanian)
- Copyright Law Article 14, moral rights (unofficial text, atviri-teises-aktai.lt, in Lithuanian)
- Civil Code Article 6.662, acceptance of completed work (unofficial text, atviri-teises-aktai.lt, in Lithuanian)
- Civil Code Article 6.666, time limit for identifying defects (unofficial text, atviri-teises-aktai.lt, in Lithuanian)
- Civil Code Article 6.252, agreements excluding or limiting liability (unofficial text, atviri-teises-aktai.lt, in Lithuanian)
- Civil Code Article 6.258, penalties and damages (unofficial text, atviri-teises-aktai.lt, in Lithuanian)
- Civil Code Article 6.721, unilateral termination of a services contract (unofficial text, atviri-teises-aktai.lt, in Lithuanian)
- Law on Public Procurement Article 87, content of the procurement contract (unofficial text, atviri-teises-aktai.lt, in Lithuanian)
- Law on Public Procurement Article 89, changes to contracts during their term (unofficial text, atviri-teises-aktai.lt, in Lithuanian)
- VPT Director's Order No 1S-209 of 30 December 2024 on standard terms for public services contracts (e-tar.lt, in Lithuanian)
- Public Procurement Office: mandatory documents and standard contract terms (in Lithuanian)
- Civil Code amending Law No XV-1080 on liability for defective products (e-tar.lt, in Lithuanian)
- Directive (EU) 2024/2853 on liability for defective products (EUR-Lex)
- GNU Affero General Public License v3 (gnu.org)