A company signs an R&D contract focusing mainly on price and deadlines, and six months later it turns out that the text does not state who owns the rights to the technical solution that was developed, while the contractor has already filed a patent application in its own name. Or another situation: the customer expected to receive a working prototype, but under the contract the contractor was obliged to provide only a report on the research results. Both situations arise not from bad faith on the part of the parties, but because the contract was drawn up formally, without working out the details that play a decisive role in R&D.
In this article, we will look at which work needs to be set out in the contract, how to formulate the purpose of R&D and the rights to the results, how to delineate the project stages, and what the customer needs to analyze even before signing the contract.
R&D activities: what work must be set out in the contract
A contract for research and experimental design work is governed by Chapter 38 of the Civil Code of the Russian Federation, but the Code itself sets only a general framework: the specific content of R&D activities must be written out by the parties themselves, and it is precisely this level of detail that standard contracts downloaded from the internet most often lack.
In the subject matter of the contract, it is important to record not a general wording such as “the contractor undertakes to carry out research work,” but a specific list of actions: which studies are carried out, whether design documentation is developed, whether a prototype is manufactured, whether tests are conducted and by what method. The more specifically the scope of work is described, the less room there is for dispute at the acceptance stage: the customer will not be able to demand what was not provided for, and the contractor will not be able to limit itself to the minimum by referring to a vague wording.
The contract should separately state what exactly is considered the result of the work: a research work report, a set of design documentation, a prototype, a patent research report. Confusing these concepts is the source of most conflicts between the customer and the R&D contractor, because the parties’ expectations regarding the “result” often diverge as early as the start of the project.
Innovative R&D activities and rights to the results created
Innovative R&D activity (that is, bringing the research result to practical implementation) requires separate attention to intellectual property rights, because it is this section of the contract that determines who will be able to use, patent and commercialize the technical solution obtained.
By default, the Civil Code vests the exclusive right to an R&D result in the customer, unless the contract provides otherwise, but in practice the parties often agree on other terms: joint ownership of the rights, transfer of the right to patent to the contractor with subsequent licensing to the customer, the contractor retaining the right to use the developments in its own projects that do not overlap with the customer’s interests. Any of these options is permissible, but it must be set out explicitly. The contract’s silence on this issue almost inevitably leads to a dispute at exactly the moment when the result turns out to be commercially valuable.
The contract should also provide for who files the patent application and in what order if the R&D result proves patentable, who bears the patenting costs, and how rights are allocated if several co-contractors with their own prior developments took part in the development.
The purpose of R&D: how to record the expected result
A vaguely formulated purpose of R&D is one of the most common causes of protracted disputes over the acceptance of work. A wording such as “develop an effective technical solution” gives neither the contractor nor the customer an objective criterion for judging whether the purpose has been achieved.
In the contract and in the technical specification attached to it, the purpose should be recorded through measurable indicators: the specific technical characteristics that the final solution must demonstrate, the conditions under which these characteristics are verified, and the method by which their achievement is confirmed. For example, instead of “improve equipment performance,” write “improve performance by at least 20% while maintaining the current dimensions and energy consumption, confirmed by a test report.”
Such a wording protects both parties: the contractor gets a clear criterion by which it can prove that the work has been performed, and the customer gets a guarantee that the result it paid for really meets expectations, rather than amounting to a report with general conclusions and no measurable indicators.
R&D and technological work: how to delineate the project stages
The relationship between R&D and technological work is another point that the contract must delineate explicitly. The research part of the project (experiments, hypothesis testing, laboratory tests) and the subsequent technological development (development of production technology, preparation for serial production) often require different competencies, different timelines and different amounts of funding, and combining them in one stage of the contract without separation makes both planning and monitoring of the work more difficult.
A sensible practice is to divide the contract into stages, each with its own acceptance: for example, the first stage is patent and scientific-technical research with a report on its results, the second is the development of design documentation, the third is the manufacture and testing of a prototype, and the fourth is the development of technology for serial production. Such a division allows the customer to control the project stage by stage and, if necessary, to adjust or stop the work after any of the stages without losing the result already paid for and accepted.
For each stage, the contract should specify the completion deadlines, the composition of the documentation to be delivered and the acceptance procedure: an acceptance certificate, a report or a test report, depending on the content of the stage. This turns an abstract “R&D completion deadline” into a concrete schedule with checkpoints by which both parties can track progress.
R&D analysis before concluding the contract: what data the customer should collect
Before signing the contract, it makes sense for the customer to carry out its own R&D analysis, without waiting for it to become the contractor’s obligation under the contract. Such a preliminary analysis reduces the risk of commissioning the development of something that already exists on the market or is protected by someone else’s patent, and makes it possible to formulate a more precise technical specification that will form the basis of the contract.
The minimum set of data worth collecting before signing the contract includes: an overview of existing technical solutions in this field, patent information on related developments, an assessment of the technological readiness of the field, and an approximate market analysis for the future product.
This data is useful in several respects at once.
First, it helps the customer formulate a realistic technical specification rather than a description based on general wishes.
Second, it becomes the basis for negotiations with the contractor on the content and cost of the work: knowing which solutions already exist, the customer can more accurately assess what exactly it is paying for.
Third, a preliminary patent analysis reduces the risk that the money invested under the contract will be spent on developing a solution that then turns out to be impossible either to patent or to bring to market without a conflict with the existing patents of competitors.
Conduct a patent analysis even before signing the R&D contract
It is easier to commission a development than to check whether the planned solution has real novelty, which is why many companies skip this step and rely on the contractor’s expertise, which may discover a problem only after the contract has been signed and the first stage paid for. Manual patent search takes weeks, and without it the decision to commission costly R&D is made almost blindly.
The AI engineer “POSINT” helps you carry out such a check on your own, before negotiations with the contractor:
- processes a natural-language description of the planned development, so there is no need to understand patent terminology in advance;
- analyzes the global state of the art, checking relevant patents and applications in Russian and foreign databases;
- finds the closest analogues and shows where the potential novelty of the future solution lies;
- generates a structured report that can be used when preparing the technical specification and discussing the contract terms with the contractor.
Conduct a patent search with “POSINT” before you sign an R&D contract. It will take hours instead of weeks and will help you formulate the technical specification and the contract terms with the contractor more precisely.
Conclusion
An R&D contract must record not only the cost and timeline of the project, but also the specific scope of work, the measurable expected result, the stages and the acceptance procedure, the composition of the documentation to be delivered, and the terms for allocating rights to the results of intellectual activity created. The more precisely these issues are defined before the work begins, the lower the risk of receiving a result that formally complies with the contract but does not solve the customer’s problem.
It is especially important to understand the initial state of the art even before concluding the contract. If a similar solution already exists or individual technical features are protected by valid patents, this may affect the technical specification, the scope of R&D and the subsequent patenting strategy. Therefore, it is advisable to carry out patent analysis not after the development is completed, but at the stage of forming requirements and negotiating with the contractor.
Conduct a patent search with «POSINT» before signing the R&D contract, so that you make the development decision based on the existing state of the art, rather than discovering critical restrictions after the project has already been launched and paid for.