A Contractor Owned Our Core Module for 14 Months and Nobody Noticed: the 7 Steps I Use for Developer IP Assignment in Singapore

Two people reviewing a signed document at a desk, illustrating the seven steps for getting developer intellectual property assignment right when hiring engineers and contractors in Singapore
Bryan

Bryan

Delivery & Offshore Teams Expert · November 12, 2026 · 11 min read

TL;DR

  • •The method: 7 steps. Audit what you own today, treat employees, contractors and agencies as three separate problems, make the assignment automatic rather than a promise, write the background carve-out early, list the deliverables that are not code, make signature a condition of repository access, and run a quarterly chain of title check.
  • •The one phrase that matters most: “assigns” rather than “agrees to assign”. One is an asset, the other is a claim you have to enforce against someone who no longer answers your messages.
  • •The gap nobody checks: agency and vendor staff. Your contract with the agency means nothing if the agency never got the rights from its own engineers.
  • •Not legal advice. This is the commercial and engineering side: what to ask for, in what order, and how to verify it held. Have your own counsel draft and review the documents.

We found it during a diligence exercise, which is the worst possible way to find it. A contractor had built a pricing module fourteen months earlier, invoiced for it, been paid, and left on perfectly good terms. His contract was two pages long and contained the word “deliverables” exactly once, in a payment clause. Nothing in it moved ownership of anything to us. The module was by then load bearing.

He was, thankfully, a reasonable person who signed a confirmatory assignment over a coffee. The cost was two weeks of distraction during a process where we had no spare attention, and a question from the other side that I did not enjoy answering. What follows is the order I do this in now.

Step 1: Audit What You Own Today, Before You Draft Anything

The instinct when you discover this problem is to go and fix the template. That is step three. If you start there you will produce a very good document that protects you from this month onwards and tells you nothing about the two years already in your repository.

Pull the contributor list for your main repositories over the last 24 months and sort every name into three buckets:

  • Employees, with an employment agreement you can produce
  • Individual contractors, engaged directly
  • Agency or vendor staff, who worked through a company

Then find the signed paperwork for each one and mark where it is missing or silent on ownership. The gap between the contributor list and the paperwork register is your real exposure, and in every audit I have run it has been larger than the person who asked for the audit expected. Rank what you find by how central the code is, not alphabetically and not by date. A missing assignment on a build script matters considerably less than one on the module that prices your product.

A note on scope: include anyone who touched design files, data or infrastructure, not just people who pushed code. The contributor graph is a convenient starting point, not the boundary of the problem.

Our expert take

Do this audit while the relationships are still warm. That is the entire strategic point of doing it voluntarily rather than under pressure. A confirmatory signature from someone who left on good terms is a friendly message and a document. The identical request, arriving during a dispute or forwarded by an acquirer’s lawyer, is a negotiation in which the other party has just discovered they hold something you need. Nothing about the legal position changes between those two conversations. Everything about the price does.

Step 2: Treat the Three Relationships as Three Different Problems

One template applied to everyone is how most of these gaps are created. The starting position is genuinely different depending on how the person is engaged, and the strength of your position runs in a clear order.

RelationshipDefault positionWhat you must get in writing
Employee, work in the course of employmentStrongest for the employerConfirm it anyway, and cover work created outside stated duties
Individual contractorWeakest, and the most common surpriseA present tense assignment, signed before access is granted
Agency or vendor staffDepends on a chain you cannot seeA warranty that the agency holds rights from its own people, plus the right to evidence it

That third row is the one almost nobody checks, and it is where I would look first in any company that outsources. Your contract with an agency can promise you full ownership of everything its team produces. If the agency never obtained those rights from the engineers who actually wrote the code, the agency cannot pass to you what it does not hold, and your remedy is a claim against the agency rather than ownership of your own product.

Ask for the warranty, and ask for the right to see evidence of the upstream assignments on request. You will rarely exercise it. Asking tells you quickly whether the vendor has thought about this, and the ones who have will answer in a sentence. We go deeper on assessing vendors in technical due diligence on a software vendor.

Step 3: Make the Assignment Automatic, Not a Promise

This is one phrase, and it is the highest value change most companies can make to their developer paperwork.

A clause where someone agrees to assign rights in future leaves you holding a promise. If they later refuse, become unreachable, move country or simply fall out with you, what you have is a contractual claim, not the asset. You find this out during a funding round or an acquisition, when somebody is specifically looking for clean title and has every incentive to flag it.

A clause that assigns present and future rights in the work as it is created needs no further action from the contributor for you to own it. Three components belong together:

  1. The present assignment itself, covering work as created rather than on some later date or trigger
  2. A further assurance obligation, requiring them to sign any confirmatory document you reasonably need afterwards
  3. A fallback letting you execute those confirmatory documents if the person genuinely cannot be reached

This drafting is entirely routine for any competent counsel, costs nothing extra over a weaker clause, and is the difference between an asset on your balance sheet and a lawsuit you would rather not run.

One Phrase, Two Very Different OutcomesTested on the day the contributor stops answering“agrees to assign”You hold: a promiseNeeds: their signature, laterIf unreachable: you own a claimdiscovered during diligence, at the worst moment“assigns”You hold: the rightsNeeds: nothing further from themIf unreachable: you still own itfurther assurance and fallback cover the paperworkIllustrative contrast between two drafting approaches. Have counsel draft the actual wording for your jurisdiction and relationship type.

Step 4: Write the Background IP Carve-Out Before They Ask

Strong engineers arrive with their own libraries, tooling, scaffolding and accumulated templates. They will not sign a document that appears to hand you their career, and the ones who read carefully enough to notice are usually the ones you most want to hire. An overreaching clause costs you candidates, and it does so silently, because nobody tells you they declined over paragraph eleven.

So define it yourself, first:

  • Background IP is anything they created before the engagement, or outside its scope, and it remains theirs
  • You take a broad, irrevocable, royalty free licence to use, modify and sublicense whatever background IP they embed in your deliverables
  • They list what they intend to bring, in a schedule, at the start of the engagement
  • Anything not listed but embedded is covered by the licence anyway, so an omission is not a weapon either way

That schedule is the part people skip and the part that does the work. It converts a vague future argument into a short conversation on day one, when everyone is cheerful and nothing is at stake. It also occasionally surfaces something useful, like a dependency on a library the engineer maintains personally, which is a thing you would rather know before it is in production than after.

Step 5: List the Deliverables That Are Not Source Code

Most clauses cover code and quietly omit everything else. The phrase “all work product” feels comprehensive and performs poorly in an argument. Name things:

  • Designs and design source files, including anything in a collaborative design tool
  • Database schemas, migrations and seed data
  • Infrastructure definitions and deployment configuration
  • Test suites and fixtures
  • Documentation and operational runbooks
  • Training data and labelled datasets, which can be worth more than the model trained on them
  • Model artefacts, weights where applicable, and evaluation sets
  • Prompt libraries and agent configurations, a real asset in 2026 and almost never named in a contract written before it
  • Ownership of third party accounts and the right to have them transferred

The two that bite hardest in practice are design files and third party accounts. Design files live in tools under personal logins with distressing frequency and leave with the person. Third party accounts are worse: an engineer registers a monitoring or messaging service under their own email during a busy week, it becomes load bearing, and eighteen months later the only person who can reset that password works somewhere else.

The test I use is blunt. List everything you would need to keep operating if this person disappeared tomorrow, then check each item appears in the agreement. Anything on the first list and absent from the second is a gap, regardless of how comprehensive the clause sounds.

Our expert take

Prompt libraries and agent configurations are where I expect the next wave of these arguments to come from, and almost every contract signed before this year is silent on them. If a contractor has spent four months tuning the orchestration and evaluation harness that makes your AI feature actually work, that artefact is a substantial part of what you paid for, and “source code” may not obviously cover a directory of configuration and prompts. It costs one line to name it. Add the line.

Want a second pair of eyes on your contributor list

Tell us how your engineering team is made up today, employees, contractors and agency staff. We will tell you where the gaps usually sit in a setup like yours and which ones to close first.

Get started

Step 6: Make Signature a Condition of Repository Access

Paperwork chased after work has started is paperwork that does not get signed. Not through bad faith, but because the project is live, the person is useful, and nobody wants to be the one slowing things down over a document.

So make the control mechanical rather than a reminder. No signed agreement, no repository access. It is a single gate, it needs no diligence from anyone, and it cannot be forgotten in a busy week.

Apply it to all three relationship types, and in particular to the case that leaks most:

  • New agency or vendor staff joining a team mid engagement. The master agreement was signed eight months ago, three new engineers joined the vendor team last month, and nobody checked whether the upstream assignments cover them.
  • Short engagements. A two week specialist fix is exactly the engagement nobody papers properly, and exactly the kind of work that ends up somewhere critical.
  • People who start as advisers and drift into contributing. The relationship changed and the paperwork did not.

Keep a register: name, relationship type, date signed, document reference. A spreadsheet is fine. The register is what makes step 7 take an hour instead of a week, and it is the artefact a buyer or investor will actually ask to see. For the contractor relationship specifically, we cover the surrounding terms in engaging a developer as an independent contractor in Singapore.

Step 7: Run a Quarterly Chain of Title Check

Everything above describes a state. This step is the only one that keeps it true, because contributor lists change continuously and registers do not update themselves.

Once a quarter, do three things:

  1. Generate the list of everyone who has contributed to your repositories since the last check
  2. Diff it against the signed paperwork register
  3. Investigate every name in one list and not the other, and close it within the quarter

A short script and under an hour. The output is usually boring, which is the point, and occasionally it catches something: a contractor brought in for a fortnight, a vendor engineer who joined mid engagement, a designer who pushed a change directly. Each of those is trivial to fix in the quarter it happens and genuinely awkward to fix three years later.

Keep a dated record of each check. This is the part whose value arrives years later. Being able to show a buyer, an investor or an acquirer a quarterly chain of title process with records going back is worth considerably more than being able to say you have good templates, and it shortens the diligence conversation from an investigation to a review.

The Chain of Title, and Where It Usually BreaksA chain is exactly as strong as the link nobody checkedVendor engineerwrites the codeThe agencyweakest linkdoes it hold rights upstreamYour companyholds the contractlink you cannot seelink you negotiatedAsk for the warranty, and for the right to see evidence of upstream assignments on requestQuarterlycheckkeeps it trueIf the agency never obtained rights from its own engineers, it cannot pass to you what it does not hold, and your remedy is a claimagainst the agency rather than ownership of your own product.

The 3 Things IP Assignment Does Not Solve

Assignment is a narrow instrument and it gets sold as a general answer to ownership risk.

  1. Open source obligations. A perfect assignment of your developer’s work says nothing about the licence terms of the components inside it. If something copyleft is embedded in a product you intend to distribute, no assignment fixes that. Keep a dependency and licence inventory as a separate discipline.
  2. Knowledge and continuity. Owning the artefact is not the same as being able to maintain it. The defence is documentation and more than one person touching each area during the engagement, not paperwork. If a vendor relationship is ending, the operational side is in transitioning an engineering vendor in house.
  3. Confidentiality. Ownership and secrecy are different obligations with different remedies, and a strong assignment with a weak confidentiality clause leaves you owning something your former contractor is free to describe in detail. They belong in the same document and they are not the same clause.

How to Fix Gaps You Have Already Found

Quietly, in order of importance, and before anyone outside the company needs to look.

Rank by centrality, then approach people while the relationship is warm. Most of these conversations are genuinely easy: a short, friendly message explaining you are tidying up records, and a one page confirmatory assignment. In my experience the large majority of former contractors sign without hesitation, because there is nothing in it for them not to and they generally liked working with you.

Where someone cannot be reached or declines, record what you attempted, identify precisely what they wrote, and take advice on the residual position rather than hoping nobody asks. The one thing not to do is wait for a transaction to force the conversation. That is when the cost is highest and your room to move is smallest, and it is exactly the mistake I made with the pricing module.

For the wider picture on structuring engagements in the first place, our guides to contract management systems in Singapore and enterprise software development in Singapore cover the surrounding decisions.

Frequently Asked Questions

Does paying a contractor mean my company owns the code in Singapore?
Not reliably, and this is the most expensive assumption in software hiring. Paying an invoice buys delivery of work. It does not automatically move ownership of the intellectual property in that work, which is why a written assignment exists at all. The position differs by relationship: employee work created in the course of employment is the strongest default for an employer, while an individual contractor is the weakest and the most common source of unpleasant discoveries years later. Agency staff add a further link, because the agency must hold rights from its own people before passing anything to you, and that upstream link is rarely checked. Never rely on a default: get a written, present tense assignment signed before repository access, for every category of contributor, and keep a register of who signed what. This is not legal advice, and your counsel should draft the documents.
What is the difference between agreeing to assign and assigning?
It is the difference between a remedy and an asset, and it is one phrase. A clause where someone agrees to assign rights in future gives you a promise: if they later refuse, are unreachable, have moved countries or fallen out with you, you hold a contractual claim rather than the thing itself, and you discover this during a funding round or acquisition when a buyer looks for clean title. A present tense assignment transfers rights in the work as it is created, so nothing further is needed from the contributor for you to own it. Pair it with a further assurance obligation requiring confirmatory signatures later, and a fallback for when they cannot be reached. The drafting is routine, costs nothing extra, and is the highest value single change most companies can make to their developer paperwork.
What do most IP assignment clauses forget to cover?
Everything that is not source code. The usual omissions, roughly in order of how often they cause problems: design files, which often live in a tool under a personal account and leave with the person; infrastructure definitions and deployment configuration; training data and labelled datasets, which can be worth more than the model; model artefacts and evaluation sets; prompt libraries and agent configurations, now a real asset and almost never named; documentation and runbooks; and ownership of third party accounts registered under an engineer personal email that are now load bearing. Naming these explicitly costs no more than writing all work product. The test: list everything you would need to keep operating if this person left tomorrow, then check each item appears in the agreement.
How do I fix IP assignment gaps I have already discovered?
Quietly, in order of importance, and before anyone outside the company needs to look. Rank gaps by how central the code is rather than by date, then approach people while the relationship is still warm, which is the whole game. A confirmatory assignment from someone who left on good terms eighteen months ago is usually a short conversation and a signature. The same request during a dispute, or forwarded by a buyer lawyer during diligence, is a negotiation with leverage on the other side. If someone cannot be reached or declines, record what you tried, isolate what they wrote, and have counsel advise on the residual position rather than hoping nobody asks. Do not wait for a transaction to force the conversation: that is when it costs most and you have least room to move.

Lance-toi: start with the contributor diff

Step 1 takes an afternoon and tells you whether the rest of this applies to you. If you would rather hire engineers who arrive with the paperwork already handled, we shortlist pre-vetted developers for Singapore employers against your scope.

Get started