[IT Litigation] Core Guide for Software Service Contracts: Management and Utilization of Deliverables
Article posted in 2025-04-29 15:18:41 | VEAT
Today, businesses and institutions require various software for business operations and innovation. Accordingly, the number of cases in which software service contracts are concluded with external developers or experts to develop software tailored to specific purposes is steadily increasing.
A software service contract is more than just developing a program; it's an important legal act that clarifies the rights and responsibilities regarding the development process and deliverables. A particularly important aspect to pay attention to in this process is the utilization plan for ‘deliverables’.
|
[What are ‘deliverables’ in a software service contract?] In a software service contract, ‘deliverables’ refer to all forms of results produced by the developer during the service execution, including not only completed software but also design documents, source code, database structures, test result reports, and other materials produced during the development process. Deliverables go beyond simple work results; they are core assets that can be used for subsequent maintenance, further development, and service transfer. Therefore, when entering into a service contract for software development, it's important to clearly agree on how ownership and usage rights of the deliverables will be established, and whether to allow third parties to utilize the deliverables, and reflect this in the contract. |
The utilization relationship of deliverables between the client, the developer, and third parties
There may be conflicting interests between the client who commissions software development and the developer who executes it regarding the utilization of deliverables.
Considering these complex interests, simply settling ownership rights between the client and developer is not sufficient. The contract should clearly stipulate whether to allow and to what extent third parties can utilize the deliverables.
Key items to be stipulated in a software service contract
When entering into a software service contract, it is desirable to include the following items related to deliverables in the contract.
1. Definition and list of deliverables
Because the term ‘deliverables’ is comprehensive, you must specifically stipulate in the contract what is considered ‘deliverables’ under that contract. For example, it is necessary to clearly determine whether it includes items such as program executable files, source code, design documents, and user manuals, as well as database structure documents.
- Scope of utilization of deliverables
It must be clearly stipulated whether the client will only use the deliverables for internal purposes, or whether they can be recycled for commercial services, and whether to allow third parties to use the deliverables for system maintenance or additional feature development. It is also desirable to set conditions such as requiring a separate additional license contract or developer's additional approval when providing deliverables to third parties.
- Developer’s right of reuse
It must be clearly agreed whether the developer can reuse some of the technology or code from the deliverables in other projects. For example, the contract can be structured so that while the client can exclusively use the completed software, the developer can freely recycle general libraries or algorithms.
- Delivery timing and format of deliverables
Clearly stipulate when and how the deliverables must be delivered. For the source code, it must be delivered along with the executable files, design documents, and test results, and must be accompanied by documented instructions.
Reference to the ‘Ministry of Science and ICT Software Standard Contract’
In practice, you can refer to the 『Information System Development and Construction Project Standard Contract』 distributed by the Ministry of Science and ICT on December 4, 2020.
This standard contract stipulates that, as a general rule, ownership of the intellectual property rights related to the deliverables generated through the contract is transferred to the client, and the developer cannot utilize the deliverables or provide them to third parties without the prior consent of the client. However, the contracting parties can stipulate that the developer can have the usage rights for some or all of the deliverables through separate agreements.
The standard contract is merely a reference and cannot be applied to all contracts. Depending on the size, purpose, technical characteristics, and future business plans of the software development project, the expected utilization method for deliverables can vary greatly, so it is necessary for the client and developer to have sufficient discussions and coordinate their respective requirements and priorities.
Law firm Bit has systematically resolved complex legal issues such as the definition of deliverables, ownership of intellectual property rights, and permission to use by third parties, based on its experience in providing advice on numerous IT projects and software development service contracts. In particular, it goes beyond the basic framework of the standard contract, analyzes potential utilization risks of deliverables in advance, and proposes specific and effective clauses that reflect the project characteristics and business strategy, thereby providing support for sustainable business operations and rights protection after software development.
If you are about to enter into a software development contract or need a review of your deliverables utilization strategy, please feel free to contact Law firm Bit.
Thank you.
Law firm Bit