IP audit
We check authors, work-for-hire records, contractor agreements and the chain of title to the code.
DeliverableA map of rights and the gaps found
IP audit
We are heading into a deal
Due diligence rarely trips over missing patents; it trips over gaps in the chain of title — a contractor with no acceptance act, a developer with no work-for-hire record, a library under an incompatible licence. These are fixed in advance and almost never mid-deal.
Preparing for due diligence 3 steps
Closing the gaps
We complete the paperwork and register the missing programs, databases and signs.
DeliverableCertificates and signed documents
The buyer's pack
We assemble a set that survives review by the other side's lawyers.
DeliverableA ready due diligence pack
What backs this up
Experience running an IP function in a tech centreQualified for software, databases and trademarks
Experience building an IP function inside a technology centre: not only how to document the rights to the code, but how a buyer will test them.
Rights in code arise with the author by default, not with the company. The transfer has to be evidenced: an employment contract with a work assignment, an acceptance act under a contractor agreement, a licence for the components used. That chain is exactly what the reviewing side looks at.
This is probably you if
- You need to secure rights to source code, a database or a software module.
- You need a package for Rospatent, the CIS states or another jurisdiction.
- You need the registration to line up with contractual, corporate or litigation evidence.
How it runs
- We define the object of registration: a program, a database, a product version or a single module.
- We prepare the abstract, the deposited materials and the details of authors and rights holder.
- We file and see the registration through to the certificate.