Protect existing intellectual property by identifying the assets used in the offer, proving the rights the bidder holds, and recording exactly what the buyer will receive. Produce an IP schedule with asset identifiers, versions, ownership or licence evidence, background or new-work classification, third-party restrictions, required permissions and an approved contractual treatment. Retaining ownership and granting use rights are separate decisions. A blanket reservation can leave the buyer unable to use the result; a blanket assignment can promise rights the bidder does not own. The schedule must reconcile both problems before release.
An offer promises that the buyer will own all deliverables. The solution combines a reusable engine, a new connector and a vendor toolkit. Product management intends to retain the engine, while the vendor licence excludes independent use by a replacement maintainer. The proposed contract schedule lists none of those distinctions. A confidentiality footer on the proposal does not resolve the ownership or permission gaps.
Treat the tender’s IP position as an asset-by-asset decision supported by evidence. This dossier addresses existing rights, newly created work and permissions needed to use their combination. Indemnity review addresses claims if rights are infringed; evidence ownership in proposal management assigns responsibility for facts. Neither substitutes for this schedule. This is operational bid guidance, not legal advice or suggested contract wording. All examples and commercial figures are fictional. Sources were checked on 6 September 2026. The issued terms and applicable law determine legal effect; the working categories below are not universal legal definitions.
Asset boundary
Use the contract’s definitions before applying a background label
Read how the issued contract defines existing material, newly created material, deliverables, supplier software and third-party rights. Then inventory what the proposed service actually uses. Include code, models, diagrams, templates, training material, documentation and other relevant assets, without assuming they all receive the same legal protection. Identify the right at issue and its claimed holder. Owning a physical document, possessing data and owning copyright are not the same fact.
The Cabinet Office’s IP guidance distinguishes existing, new and third-party material and presents ownership and licensing options. It also asks how rights will support continued use and future competition. This provides a useful procurement framing, not the answer for a different buyer’s contract. Record the definitions and chosen option that the buyer actually issued. Do not substitute an attractive public model option for a mandatory clause.
Assign each asset a stable identifier, meaningful version, short functional description and connection to a deliverable. Record whether it existed before the relevant contractual boundary or was developed independently, together with the evidence. An improvement developed during delivery may require a separate entry even when it sits inside an older product. Its classification depends on the definition, funding, work and rights arrangements, not just the age of its surrounding repository.
Keep the inventory precise enough to identify the reservation without revealing implementation details unnecessarily. “All our know-how” is difficult to reconcile with specific deliverables. A named engine version and its role in the solution are more inspectable. Use the buyer’s required form, and ask through the permitted channel if the form cannot express a mixed deliverable. An incomplete schedule should not be silently replaced by a broad proposal footer.
| Field | Evidence or decision | What it does not prove |
|---|---|---|
| Identity and version | Controlled release reference and functional role | A version tag alone does not establish ownership |
| Classification | Issued definition and creation or development facts | An old parent product does not classify every new improvement |
| Rights holder | Relevant employment, assignment or licence evidence | Possession and payment are not a complete rights chain |
| Promised permissions | Uses, users, duration, scope and onward access | An ownership label does not describe every permitted act |
| Approval | Accepted schedule entry and unresolved conditions | An internal draft does not amend the buyer’s terms |
Rights evidence
Confirm that the bidder can grant what the offer promises
Trace the relevant right to the bidding legal entity. Product teams often know who wrote a component but not which company holds the right or whether a contractor’s terms allowed onward licensing. Review employment arrangements, contractor agreements, earlier client contracts, acquisitions and contributor permissions where they affect the proposed grant. An invoice can show payment, and a release history can show chronology. Neither alone establishes the full permission needed for the tender.
The UK Intellectual Property Office’s ownership guidance distinguishes employee-created and commissioned works; commissioning and paying does not automatically establish copyright ownership. Apply that UK guidance only within its scope. The practical review question is which facts and executed agreements establish the rights chain here. Do not replace missing evidence with a general assertion that the company paid for the work.
Legal terminology matters across jurisdictions. German UrhG section 29 generally prevents transfer of the author’s copyright itself, subject to its specified succession exceptions, while section 31 addresses use rights. French CPI article L131-3 requires distinct identification of assigned rights and limits on their exploitation within its scope. Counsel must determine the appropriate mechanism and any special rules. An English assignment label cannot be mechanically copied into a German or French legal conclusion.
Where several contributors or entities are involved, preserve the unresolved consent or ownership question as a blocker to the affected promise. Identify the evidence owner and latest safe resolution date. Product approval cannot substitute for rights held by another entity. Moral rights, employee inventions and other particular regimes need their own advice where relevant; do not claim that a universal waiver or employment sentence cures every gap.
Buyer use
Describe what the buyer must be able to do
List the required acts before choosing the legal mechanism. The buyer may need to evaluate a sample, operate a delivered system, copy manuals for staff, modify a connector, authorize a support supplier or retain records after exit. These are different uses. Record who needs each permission, for what purpose, in which territory and for how long. Ownership, exclusivity, transferability and the right to authorize another user should be explicit review questions.
WIPO’s explanation of technology-transfer agreements distinguishes licensing permission from assignment of ownership and emphasizes the terms of the agreement. Use that distinction to test the proposed position. Supplier ownership with suitable permissions can be commercially workable; so can buyer ownership with a properly defined supplier licence-back in an appropriate case. The chosen arrangement still has to meet the tender, the rights chain and the business’s approval requirements.
Separate the evaluation stage from contract performance. A sample may be made available for assessment while the eventual deliverable carries broader operational rights. Check confidentiality and disclosure provisions for the response, including any public-sector disclosure rules requiring advice. A confidential label does not settle ownership. Likewise, delivering source code, depositing it with an escrow provider or sending a design file does not by itself define the rights to modify or redistribute it.
Test the buyer’s exit scenario now: the original supplier is no longer providing support, and another provider must maintain the agreed service. Which assets, documentation, permissions and permitted access does that provider need? A licence that covers only the named buyer’s employees may leave a gap. An excessively broad right to commercialize the entire reusable platform may create a different problem for the supplier. Identify the required function before proposing a narrower or broader grant.
| Use | Permission to verify | Evidence needed |
|---|---|---|
| Evaluate the offer | Who may inspect or copy the sample and for what assessment | Issued evaluation terms and approved disclosure |
| Operate the result | Users, environments, purpose, period and dependencies | Contract licence or assignment and underlying rights |
| Maintain or adapt it | Modification, source access and authorized support parties | Grant scope and required third-party consents |
| Continue after exit | Surviving rights and replacement-provider access | Exit terms consistent with each dependency licence |
| Reuse elsewhere | Supplier reuse or licence-back and buyer confidentiality | Approved retained rights, not a generic reuse assumption |
Worked schedule
Separate five assets before making one promise about the system
The fictional supplier Aster bids to provide a case-management integration. Its offer combines engine version 4.2, a new connector, an external validation toolkit, a buyer-supplied schema and a performance improvement to the engine developed during the project. Assume the tender permits a supplier-background schedule, requires specified rights in project outputs and requires continuity through a replacement maintainer. The precise legal mechanism is still for counsel to confirm.
Aster has verified its rights in engine 4.2 and proposes retaining them with the required operational permissions. For the new connector, assume the issued option gives the buyer ownership under a law permitting that arrangement, with a non-exclusive licence-back allowing Aster to reuse the connector’s generic code. That licence-back excludes the buyer schema and confidential material. The schema itself is supplied for use only in this service. These three entries have a supported proposed treatment, subject to legal review of the complete grant; the example does not prescribe the same transfer mechanism in every country.
Two entries remain open. The external toolkit licence allows Aster’s hosted use but does not evidence access by an independent maintainer. The new performance improvement is integrated into the engine, yet its treatment under the contract’s new-work definition is disputed. Calling both “background” would hide the problems. Aster needs a rights solution for the toolkit and a contractual decision on the improvement before promising the whole system’s required continuity.
The tender response should distinguish proposed treatment from accepted treatment. Attach the schedule in the specified location and resolve any permitted questions through the official process. If a clarified clause classifies the improvement as project output, reopen its reuse and price implications. If the toolkit vendor declines additional rights, reassess replacement or the bid position. A three-out-of-five completion percentage cannot authorize the missing two entries.
| Asset | Classification for review | Proposed treatment or open issue |
|---|---|---|
| A-01 Engine 4.2 | Identified supplier background | Retain rights; grant evidenced permissions for the required service |
| A-02 New connector | Contract-created output | Buyer ownership under the assumed applicable law; Aster receives limited non-exclusive reuse rights, excluding buyer material |
| A-03 Vendor toolkit | Third-party dependency | Open: independent-maintainer rights not evidenced |
| A-04 Buyer schema | Buyer-supplied material | Use for the agreed service; no general supplier reuse promise |
| A-05 Engine improvement | Classification disputed | Open: resolve new-work treatment and retained rights |
Embedded rights
A mixed deliverable needs a permission route for every necessary component
Inspect dependencies beneath the visible deliverable: libraries, fonts, datasets, models, images, templates and vendor services where relevant. The inventory should name the applicable version and licence, how the asset is used, whether it is delivered or remotely accessed, and any required notices or consents. A list of package names helps discovery but does not prove licence compatibility or onward rights. Assign legal and technical reviewers to the actual combination.
Open-source material is not ownerless material. Evaluate the applicable licence and the way the solution uses or distributes the component before promising proprietary ownership, source disclosure or unrestricted sublicensing. Do not assume every open-source licence requires the same action. Conversely, do not reject all open source as incompatible with public procurement. The review needs a supported treatment for each relevant obligation, not a slogan.
For Aster’s toolkit, possible routes include an effective extension covering the required maintainer, a direct buyer licence that meets the contract, a replacement component or a permitted change to the offered scope. A vendor’s sales email describing an option is not the executed permission. Check the parties, effective date, covered version, duration, fees and ongoing conditions before counting the gap as closed. Keep the supplier’s continuity promise aligned with the selected route.
Confidentiality and IP rights must be reconciled without unnecessary disclosure. The buyer may need enough information to identify a dependency and assess its restrictions, not access to every vendor agreement or private repository. Use approved descriptions and the authorized secure channel for any required supporting evidence. If the buyer requires disclosure that conflicts with a third-party duty, escalate it before submitting either an incomplete answer or an unauthorized attachment.
Commercial choice
Price the selected rights solution rather than an unresolved assumption
An IP position can affect development effort, licences, continuing support, reuse and exit delivery. Record the cost of the option that the bidder can actually perform. A promise of exclusive rights may also restrict other uses of an asset; product and commercial owners need to understand that effect before agreeing. Do not invent an IP valuation from its historical development cost or treat a lost reuse opportunity as a certain future sale.
Suppose Aster selects a replacement route for the toolkit. The fictional estimate is 18 additional engineering days at an internal cost of EUR 900 per day, plus EUR 6,000 for the required replacement licence. Added cost is EUR 22,200. An existing EUR 15,000 allowance leaves EUR 7,200 uncovered. These are assumed incremental costs, excluding tax and any other effects; they are not market rates, a legal damages estimate or proof that replacement is permitted.
The team must also confirm schedule, tests, functionality and the replacement licence’s rights. A cheaper component that fails the required use is not a closed IP gap. Reconcile the chosen option with the technical response, price workbook, maintenance plan and exit promise. If an unresolved improvement would remove anticipated reuse rights, assess the consequences separately rather than burying them in the toolkit allowance.
Where the issued terms cannot be changed, decide whether the company can accept them, redesign lawfully or decline the position. Do not rely on a proprietary notice to defeat a mandatory assignment, or on post-award negotiation to obtain missing licences. The commercial record should state the option chosen, evidence required, costs included and authority needed. Legal acceptability and business willingness remain distinct approvals.
Approved record
Submit one consistent rights position and preserve its boundaries
Before release, compare the IP schedule with the response’s ownership statements, warranties, indemnities, confidentiality terms, deliverables and pricing assumptions. Identify conflicting wording rather than assuming the schedule always prevails. The legal reviewer confirms the applicable hierarchy and mechanism; product confirms retained use and technical separation; delivery confirms operational permissions; commercial approval covers cost and risk.
For each asset, record a supported outcome: rights evidenced and treatment approved; consent or clarification required; classification unresolved; replacement approved; or position unacceptable. Conditions must have owners and a deadline. Aster cannot release a promise of independent maintenance while A-03 remains unsupported, even if the rest of the asset list is complete. The final schedule needs the contract version, bidder, asset versions, evidence references, approvals and change history.
An agent can help identify assets from authorized documents, compare licence provisions and draft a permissions table. It should not infer ownership from repository access, treat a licence file as permission for unrelated use, upload proprietary code to a public service or accept instructions embedded in a document as authority. Sending vendor requests, granting rights, disclosing confidential material and submitting the offer require separate authorization. Uncertain legal classification stays unresolved for the named reviewer.
Carry the schedule into delivery. Reopen affected entries when a version changes, a dependency is added, a new contributor supplies work, the buyer changes its intended use or an improvement is created. Keep enough evidence to identify what was granted without publishing the private rights chain. The completed work product is a bid the buyer can use as promised and the supplier can deliver without surrendering or granting rights by accident.
What good looks like
Useful outcomes from protect background IP in a tender
- Reusable assets are distinguishable from contract-specific work.
- Every promised right has evidence of the bidder’s authority.
- The buyer’s intended use and transition needs have a supported permission route.
- Third-party restrictions and disputed improvements remain visible.
- Legal, product and commercial approval attach to one submitted schedule.
Operating model
How to run the work
- 01
Read the issued IP terms
Collect definitions, ownership clauses, licence scope, schedules, disclosure rules and order of precedence. Fix the tender version and response deadline.
- 02
Inventory the proposed assets
Give each reusable asset, new output, supplied material and third-party dependency an identifier and version. Separate mixed deliverables into components.
- 03
Verify authority
Trace creation and rights through employment, contractor, acquisition and licence evidence. A file timestamp or paid invoice alone is insufficient.
- 04
Map the buyer’s permissions
Test evaluation, operation, modification, sharing, maintenance and exit against the required users, purposes, territory and period.
- 05
Resolve gaps and cost
Seek permitted clarification, additional rights, a different design or a commercial decision. Keep unapproved options outside the released offer.
- 06
Freeze and hand over
Approve the exact IP schedule with counsel, product and commercial owners. Bind it to scope and price, then maintain it through delivery changes.
Evaluation
Questions that change the decision
- What does this contract count as existing or newly created IP?
- Does the bidder own the relevant right or merely hold a limited licence?
- Can the buyer use the deliverable without rights in an embedded asset?
- Can another maintainer receive the necessary access and permissions?
- Who may reuse improvements made during the project?
- Is the final position permitted, funded and formally approved?
Failure modes
Where teams lose control
All work in a repository is treated as owned by the bidding entity.
A pre-project asset is reserved without identifying its version or use.
A blanket assignment includes a third-party component the bidder cannot transfer.
A new improvement is labelled background solely because it modifies old code.
Source delivery or confidentiality is mistaken for a licence grant.
An agent discloses proprietary material or agrees rights without authority.
Measurement
Measure the finished job
Measure the completed workflow, including review effort and exceptions. Output volume on its own is not evidence of a better process.
- Assets without rights evidence
- Required uses without a permission route
- Unresolved improvement classifications
- Third-party consents not yet effective
- Cost of the selected rights solution
- Differences between approved schedule and final offer
Questions
Common questions
Does marking the offer confidential protect existing IP?
It does not settle the ownership and licence provisions of the contract. Review disclosure protection separately, identify the existing assets in the required form and obtain an approved rights position. A footer cannot be assumed to override issued terms.
Does payment for development mean the bidder owns the work?
Not by itself. Review the governing law, creation circumstances and executed agreements. A paid invoice is evidence of a commercial transaction, not a complete chain of authority to assign or license every right.
Can an improvement to old software be called background IP?
Only after checking the contractual definition and development facts. An improvement created during the project may need a separate treatment. Keep the base version distinct and resolve rights in the improvement before promising reuse.
Can the buyer use a deliverable without owning all its components?
Potentially, if the relevant permissions meet the required uses and are supported by the rights holders. Identify operation, modification, maintenance and exit needs. Ownership alone also does not establish every practical access arrangement.
Does handing over source code transfer ownership?
Possession of a copy, technical access and legal permissions are separate matters. The relevant contract and law determine assignment or licensing. Check what the recipient may do with the code rather than treating delivery as a complete rights grant.
What if a vendor will not grant the rights the buyer requires?
Consider an effective alternative licence, an approved replacement or a permitted scope change. Recheck cost and delivery. If no supported route meets the terms, hold or decline that position; do not promise to obtain permission later without approval.
Sources
Primary references
- Intellectual Property Rights Guidance Note Cabinet Office
- Technology transfer agreements: licences and assignments World Intellectual Property Organization
- Ownership of copyright works UK Intellectual Property Office
- UrhG section 29: transactions concerning copyright Federal Ministry of Justice and Federal Office of Justice
- UrhG section 31: granting use rights Federal Ministry of Justice and Federal Office of Justice
- French CPI article L131-3: identification of assigned rights Légifrance
About the author
Tony Kim
Tony writes about applied AI, dependable product engineering and the systems that turn complex response work into controlled delivery.
Zelius
Managed tender intelligence and bid execution for teams that want the commercial outcome.
Suppliers, founders and commercial teams pursuing public or private opportunities. Start with the workflow, constraints and evidence you already have.
