How to manage intellectual property right for different clients from a consultancy
<p>let's say company A is a consultancy in field XX and develops software solutions for client B. Client B clearly retains the IP of the work done. Then company A will have 2 more clients C and D. Now, company A has clearly the expertise to do a similar work for company C and D (without copying or reusing the same software of course). Is there any infringement of IPR of company A just has other clients and do similar jobs? Especially in software clearly there are pieces that can be repeated in different project but they are not representative of the IP. How the company A can handle the legal situation: it has to give the IP to client B , C and D without infringing all of them. Otherwise company A will get out of business because they cannot have multiple clients.</p>

<blockquote>
  <p>Is there any infringement of IPR of company A just has other clients and do similar jobs?</p>
</blockquote>

<p>Typically no, especially if that knowledge is gained independently. For example if Client A provided the company with a specific algorithm and asked for that algorithm to be implemented, the company could not use that algorithm (even if the code is different) for Client B. However if Client A came to the company and said "we want software that does X, Y, Z" and the company developed the algorithm to do that, it would be free to use that with Client B.</p>

<blockquote>
  <p>How the company A can handle the legal situation [...]</p>
</blockquote>

<p>Technically speaking this is done in a number of ways depending on how the company wants to implement it. It may have a well-documented development process which documents where these methods come from and a source control system that can show that the code is independently written. Separation of data (for example, completely unrelated source repositories) and even having different individuals working on the projects. </p>

<p>Usually though there is some kind of documentation exchanged between the contractor and the client at the beginning of the project that outlines very carefully where the intellectual property belongs (and clearly defining the scope of work and any intellectual property output). This may include such provisions as:</p>

<ul>
<li>Assignment of any patents</li>
<li>Documentation and assignment of algorithms</li>
<li>Non-disclosure agreements</li>
<li>Release and removal of all documentation/source/notes/etc from the contractors system related to the developed system via signed affidavit</li>
<li>Documentation of trade secrets</li>
<li>Marking sensitive documents as such (Confidential/Internal use only, etc)</li>
</ul>

<p>Another important step from the client side is an indemnification agreement, which basically would say that if Client A were to sue Client B for an IP violation arising from work produced by the contractor, that the contractor would be the one to pay for that particular violation (and court costs/lawyer fees, etc). This is a huge incentive for the contractor to clearly demonstrate that while the output is similar, it was developed independently.</p>

<p>The important thing here is to remember that Intellectual Property and Expertise are two different legal concepts. Intellectual Property is something that can be legally protected, while expertise is general knowledge that cannot.</p>

united-kingdom intellectual-property software