Why the annex matters more than the quote
Software intellectual property is the part of a development contract most people skim. The price is on page one, and the rights annex for software intellectual property sits at the back where nobody argues about it. Then, two or three years later, the system needs rebuilding after the original supplier has moved on, and someone asks a question nobody can answer: are we allowed to do this?
That question has a cost. Not a dramatic one. It's weeks of delay while lawyers read old contracts and a new team tries to work out what it's permitted to touch. The seven questions below are the ones worth asking while you still have leverage, which is before you sign anything. None of this is legal advice, and your own counsel should read the actual words in your actual agreement.
Define the legal context
Start with who is actually contracting. The supplier's trading name and the legal entity on the signature page may differ, and you'll struggle to enforce software intellectual property rights assigned to a dormant holding company. Write down both entities, the governing law clause, and where the people writing your code are physically based.
Jurisdiction decides the default. Under section 11 of the Copyright, Designs and Patents Act 1988, an employer is the first owner of copyright in work made by an employee in the course of their employment. Spain reaches a similar result for software through Article 97.4 of the Ley de Propiedad Intelectual, which gives the employer the exploitation rights in both source and object code unless the contract says otherwise. Neither rule helps you when the code is written by a contractor rather than an employee.
Guidance from the UK Intellectual Property Office and Business.gov.uk describes UK law. It isn't evidence of what happens in Madrid or Austin, and a contract naming English law doesn't automatically decide how an assignment signed by a developer abroad will be treated there. If contributors sit in more than one country, your counsel needs to know that before drafting. Keep the assignment or licence wording visible from the start, because that single clause does most of the work in any discussion of software ownership.
Separate rights from access
Three different things get muddled in these conversations. There's who has source code ownership, and there's what permissions attach to the components inside the build. There's also whether you can actually get at the repository on a Tuesday morning without emailing someone. You need all three. Having one doesn't give you the others.
Payment doesn't settle it. The IPO's own guidance on commissioned works states that the first legal owner is the person or organisation that created the work, not the commissioner, unless you agree otherwise in writing. And section 90 of the same Act requires an assignment to be in writing and signed. A handover of files proves you have the files without proving you have the software intellectual property.
One small mercy for software specifically: section 79 disapplies the attribution moral right to computer programs, so you won't be arguing about credit lines in your codebase. Everything else needs reading by someone qualified in the relevant jurisdiction. Source code ownership is a legal conclusion drawn from documents.
Software intellectual property questions
Our position at Evolved Ideas is straightforward. If you commissioned bespoke work and paid for it, you should own it, and our contracts are written on that basis. Treat that as a starting point, because the honest answer in any specific build is shaped by the agreed terms and by the rights attached to components nobody wrote for you.
Here's how we'd put the same point less comfortably. A promise to assign everything is only as good as the chain of paperwork behind it, and no supplier can assign rights in a library it merely licenses. The seven questions that follow are designed to find where the promise and the paperwork diverge. Run them past your counsel, then run them past whoever is quoting for the build, because software intellectual property clauses are negotiable and most suppliers expect you to ask.