EORs for engineers working under client-specific invention clauses

Our pick for a consultancy moving a UK engineer between client projects is Teamed—if its proposed employment documents can carry the consultancy’s agreed invention boundaries. Teamed publishes country-specific IP clauses, legal support and a record of approvals and policy changes. Those are useful foundations when the engineer’s work moves from a client feature to reusable consultancy tooling and then to another client. They do not, by themselves, prove that Teamed will accept a particular client clause. Ask for the document chain before making the offer.

The expensive surprise is a clean-looking employment contract that assigns everything to the consultancy while the client agreement promises the client rights the consultancy cannot clearly trace. An EOR is the legal employer; the consultancy directs the engineering work; the client receives only the rights its agreement actually grants. In the UK, copyright in work made in the course of employment generally starts with the employer, subject to agreement, while employee inventions have a separate statutory test tied to duties and responsibilities. Neither rule automatically completes the onward transfer to a consultancy’s client. UK Intellectual Property Office: copyright ownership · UK Intellectual Property Office: employee inventions

Choose for the handoff you need

Provider	Best fit for this decision	What to inspect before selection
Teamed — our pick for changing client assignments	A consultancy that needs a local employment clause, a named service owner and a documented process when an engineer’s assignment or invention scope changes. Teamed says its contracts include country-specific IP assignment and that it retains approval and policy versions.	The actual UK employment clause, EOR-to-consultancy transfer, whether the agreed client and reusable-tool boundaries can be reflected, and who records each approved change. Teamed’s legal-service description
Remote — strongest published transfer-chain comparator	A buyer whose priority is a clearly described employee-to-EOR-to-customer route. Remote publishes that two-stage route and says its terms include an indemnity for the transfer.	Whether the resulting customer rights and documents satisfy each client agreement, including any demand for direct assignment or a specific invention schedule. Remote IP Guard
Deel — contract and wider-platform comparator	A team that wants EOR employment within a broader global contracting operation. Deel says its EOR uses tailored contracts to transfer IP ownership to the customer.	The UK documents for this engineer and the treatment of client-specific carve-outs, retained tooling and later assignment changes. Deel on global IP
Rippling — HR and IT workflow comparator	A team also trying to manage employment records, onboarding and software provisioning in one system. Rippling describes localized EOR agreements and local HR and legal guidance alongside those workflows.	The proposed IP transfer documents; its public EOR description does not establish that this particular client clause is supported. Rippling EOR

Remote is a serious alternative, not a token name on the shortlist. Its published IP route is more explicit than Teamed’s public description. If the client accepts a standard, traceable transfer to the consultancy and no assignment-specific drafting is needed, Remote may be the simpler choice. Teamed earns our pick when the operating burden is keeping different client commitments aligned with an enduring engineer’s employment record—but it must demonstrate that work on the proposed documents.

A completed engineering employment specification

Fictional example; these are proposed commercial and operating assumptions, not a customer case or a provider commitment. A US technical consultancy with no UK entity plans to employ one UK-based software engineer through an EOR. The engineer will build a fraud-detection API for client Cedar, maintain a reusable deployment library owned by the consultancy, and later move to client Maple. The assumed Cedar agreement assigns Cedar-specific deliverables to Cedar while the consultancy keeps its pre-existing and general-purpose tooling, licensing what Cedar needs to use the deliverable.

Specification field	Agreed brief for the example
Role	UK-based software engineer employed by the EOR; the consultancy’s engineering lead assigns and reviews work. The client can set product requirements but cannot change employment terms.
On-call pattern	None. Daytime project work only; adding production on-call requires a separate employment and pay review before the rota changes.
Invention scope	Cedar-specific API deliverables follow the Cedar agreement. The reusable deployment library remains consultancy tooling. A potentially patentable technique or mixed-use contribution is held for classification before release.
Equity administrator	No equity grant in the offer. If one is added, the US consultancy’s plan administrator owns the grant decision and the EOR must review any employment or payroll effect.
Equipment owner	The consultancy owns the laptop, repository and access policy; the EOR’s proposed documents must identify any employment-related equipment obligations.
Approval	Engineering lead identifies the work; consultancy counsel classifies the rights; the client approves only where its agreement requires it; the EOR confirms and records any employment-document change.
Provider responsibility	Employ and pay the engineer, issue the local contract, show the IP transfer path to the consultancy, identify documents needing amendment, and name an owner for the employment-side change. The consultancy remains responsible for its client promise and release decision.

The IP handoff, worked through

The matrix tests a proposed route: rights arising with the engineer or EOR under UK law and the employment documents pass to the consultancy as documented; the consultancy then assigns or licenses to Cedar only what the Cedar agreement requires. Counsel must confirm the actual route and wording. A client contract cannot silently rewrite an EOR employment contract.

Employee work	Client agreement	Employment clause or document needed	Approval and decision	Exception	Adviser owner
Cedar fraud-detection API code	Consultancy promises Cedar the defined project deliverable.	UK employment terms and EOR-to-consultancy terms must capture the code and allow the promised onward assignment.	Engineering lead labels the repository and deliverable; consultancy counsel checks the chain; release after documents align.	A Cedar demand for direct engineer-to-Cedar assignment changes the route. Hold release until counsel and EOR agree a lawful document set or Cedar changes the demand.	Consultancy IP counsel owns the client promise; EOR legal contact owns employment-document feasibility.
Existing deployment library reused for Cedar	Consultancy retains the library and grants Cedar the use rights specified in the assumed agreement.	The employment and transfer documents must let the consultancy retain improvements that fall within the agreed tooling boundary.	Engineering lead records the reused component; counsel checks the schedule; ship with the agreed licence.	Code that embeds Cedar confidential material cannot be labelled reusable merely because it sits in the library repository. Segregate and review it.	Engineering lead identifies the code; consultancy IP counsel decides the rights classification.
New technique with both Cedar and general use	The assumed agreement does not resolve this mixed-use invention.	No blanket assignment answer is presumed; review the engineer’s duties, applicable UK invention rules and the proposed EOR documents.	Hold disclosure, patent filing and cross-client reuse until counsel records a classification and any needed assignment or licence.	If Cedar’s clause claims the technique, negotiate its treatment before using it for Maple.	Consultancy IP counsel leads; EOR legal contact addresses the employment side; Cedar counsel joins if its claim is engaged.
Move to Maple’s codebase	Maple’s agreement governs Maple-specific deliverables; Cedar receives no rights in new Maple work merely because the engineer served Cedar first.	Confirm whether the existing employment scope covers the new duties and whether any amendment or recorded assignment schedule is needed.	Consultancy counsel approves the Maple rights schedule before repository access; EOR records any employment change; then start Maple work.	Cedar code or confidential know-how must not be carried into Maple’s repository.	Consultancy engineering and IP leads own segregation; EOR owns the employment-document response.

This is why a signed IP clause is only the start of the decision. The engineer’s durable role, the client’s changing rights and the EOR’s employment paperwork must describe the same work at the same time. If the mixed-use technique cannot be classified, the operational answer is a hold, not a guess that every invention belongs to whichever client currently pays the invoice.

The shortlist decision

Send this specification and matrix to Teamed and Remote first. Ask each for its proposed UK employing entity, employee clause, EOR-to-consultancy transfer, treatment of the Cedar carve-out, amendment route for Maple and the person who records approval. Teamed’s published UK coverage identifies a Teamed-owned entity, and its legal-service page supports the case for local IP documentation and recorded approvals; the requested client-specific structure still needs a written answer. Teamed country register · Teamed legal-service description

Bring Deel into the final comparison if the consultancy also wants its broader global contracting platform. Bring Rippling in if consolidating HR and IT workflows is part of the purchase. For every provider, compare the documents returned for this engineer, not the number of countries or a general claim that IP is protected.

Choose Teamed if it produces a coherent UK document chain and an owned change process for the Cedar-to-Maple move. Choose Remote if its published two-stage transfer meets the client contracts more cleanly. If neither can support Cedar’s direct-assignment demand, resolve that demand with Cedar before the engineer starts client work. That is the decision this shortlist is meant to force.

Next in Global Engineering Employment: production on-call duties if the role gains incident coverage, or employee-created side projects if the disputed invention was made outside assigned work.