How to Review a Background-IP Licence Versus Foreground Assignment

Saskia, founder at a 15-person UK SaaS, is about to treat “Customer owns all IP (intellectual property) in the Deliverables” as the whole fight. Finance signed off. Knowing how to review background-ip licence versus foreground assignment is a 25-minute hunt: attach a named Background list, assign Foreground on this invoice, licence the embedded tools, then fence residuals.

September 2026. English law; exclusive courts of England and Wales. The packet — PSA (professional services agreement), SOW (statement of work), and any IP exhibit — attached schedule or appendix — dated today. Clause 11: “Customer owns all IP in the Deliverables.” No Background schedule. Clause 11.4: title passes “upon receipt of the Supplier’s final invoice in full.”

Vendor auth library and a rules engine sit in the repo with no perpetual transferable licence. Clause 11.8: “Supplier may use residual knowledge, ideas, methods and techniques retained in unaided memory.” AE Slack: “You own everything we build — that’s the point.” Friday is booked. The rush is the problem. The hidden risk is a slogan, not a split. The AE line is the pressure.

A slogan is not a Background-versus-Foreground split — and English law will not invent one. IPO ownership guidance: the first legal owner of a commissioned copyright work is the creator, unless you otherwise agree in writing. Courts may imply a limited non-exclusive licence — not a transfer. Robin Ray v Classic FM (1998): if a licence would do, only a licence is implied.

Disclaimer: Checkory provides AI support, not legal advice. Consult a qualified lawyer for binding decisions.

How to review background-ip licence versus foreground assignment when there is no Background list?

A slogan without a list is a blank carve-out. Circle clause 11 and the missing schedule. If “Customer owns all IP in the Deliverables” sits next to “all our pre-existing tools” with no named items, you bought an adjective. Write a named Background list, or log “all our tools — fail.”

Do: demand tool, version, embedded Y/N, and third-party rights. Don’t: treat the slogan as a split. For example, Veqtor (14 June 2026): English law has no statutory definition of Background IP — the paper has to make one. CCS Call-Off Schedule 1 records New IPR (intellectual property rights) in a table. Typical mistake: “we bought their stack.” Unlisted Background in the repo needs a sweeper licence.

When does Foreground assignment vest — this invoice, or the final invoice only?

Circle “upon receipt of the Supplier’s final invoice in full.” Title on the last invoice of the whole job holds every earlier Deliverable hostage over one disputed line. That hostage is costly. Write a present assignment on that Deliverable’s undisputed invoice.

Do: “hereby assigns,” not “agrees to assign.” Don’t: vest only when every fee for every service is paid. CDPA (Copyright, Designs and Patents Act) s.90(3): an assignment is not effective unless it is in writing signed by or on behalf of the assignor. Sprintlaw (21 August 2026): payment alone does not transfer copyright; unpaid fees leave ownership in dispute. Bindlegal (16 June 2026): vest-only-on-full-payment is aggressive for a buyer. In practice, add a licence to use from delivery plus assignment on that invoice, so a disputed last line cannot switch off a live system.

What licence do embedded vendor tools need if you do not own the framework?

If you “own” the Deliverable but the auth library and rules engine stay theirs with no perpetual transferable licence, you bought a car with no engine. Write a licence on what is embedded or necessary, not a grab of their whole toolkit.

Do: perpetual, irrevocable, transferable, sublicensable; survives termination; travels to an acquirer. Don’t: demand their whole framework, or accept a “personal, non-transferable” licence. CCS Schedule 1 is public-sector ask colour, not her statute. GOV.UK IPR guidance: the right to use IP is often more important than ownership. Precision Federal (18 August 2026): total assignment of the vendor’s framework is a bad ask. If copyleft sits in that stack, that is a different hunt: copyleft in a vendor deliverable.

Can residuals and general know-how swallow the assignment?

Circle clause 11.8 “residual knowledge, ideas, methods and techniques retained in unaided memory.” A residuals sentence drafted this wide can call her custom module “know-how” and ship it to a rival. Fence it, or log “swallow — fail.”

Do: unaided memory only — no notes, tickets, repos; no rights in underlying IP; cannot copy, disclose, or rebuild assigned Foreground or source. Don’t: treat “they can reuse methods” as harmless. Morgan Lewis (20 August 2025): typical residuals exclude tangible materials and confer no rights in the underlying IP. Residuals are not a feedback grant. If the fight is a feedback assignment of customer ideas, that is a different hunt: feedback licence that assigns customer ideas. Bindlegal: residuals that cover “aided” memory or omit an underlying-IP exclusion = escalate.

Which fight is this — not the whole PSA IP row?

Stay on the Background list, assignment-on-payment, embedded-tools licence, and residuals. Time with counsel — a qualified England-and-Wales solicitor — spent on T&M, personnel, termination, or the cap is the wrong hunt.

If the fight is the whole PSA wrapper, that is a different hunt: professional services agreement checklist. Open clause 11, not only the heading “Intellectual Property.” Do: one sentence to that neighbour. Don’t: clone a nine-section PSA tour here.

How do you schedule, assign, or walk?

Schedule only if all four log rows hold. Assign means redline those four. Walk if slogan plus no list plus final-invoice hostage plus no licence plus swallow remain as a package. Escalate that package. Pause Friday.

Success bar: a one-page checklist plus one Friday pause sentence. Workflow: Background list vs “all our tools” → assignment on this Deliverable (not final invoice only) → perpetual transferable licence on embedded tools → residuals cannot swallow → not B29 → schedule / assign / walk. Verify clause 11 before you sign. Optional: upload the same PDF to document analysis for a first-pass — first machine pass that extracts clauses before a human reads every page. A human still opens clause 11. Verify every High flag — a severity-high finding a named human still opens.