When engineering duties change, follow the rights through both contracts
By Global Engineering Employment editorial desk · Publication editorial desk
Updated
Choose the arrangement that can document the required rights, and keep the incumbent if it can do so. “IP included” does not establish rights to a personal library, a client-funded invention or a new use of old code. For an England-based engineer moving into reliability design, the useful output is a clause-and-materials record the employer and company counsel can resolve.
Follow the work before drafting the clause
IPO copyright guidance describes the general employer-first rule for employee works made in the course of employment, subject to contrary agreement. With an EOR, the legal employer and the product company are different entities. Trace the employee-to-employer and employer-to-client documents together; do not jump from “employee wrote it” to “our company owns it.”
An invention requires a different analysis. The IPO’s employee-invention guidance makes duties, expected invention and particular responsibilities relevant, with territorial conditions. Expanding a role from operating a release system to designing a new recovery mechanism can change the facts that counsel needs. A generic “all IP” sentence is not a substitute for that assessment.
Completed rights schedule for the role-change example
The following assets are fictional. No ownership conclusion about a real engineer is implied.
| Item | New or earlier work | Proposed disposition | Evidence required before use |
|---|---|---|---|
| Release-check script | New work in proposed D3 duties | Include in employment/client assignment review | Current and amended duty description; employee and client IP clauses |
| Recovery mechanism | New inventive work may arise | Refer for invention assessment separately from code copyright | Assignment instructions, inventor record and applicable statutory analysis |
| Personal latency library | Created before the role change; ownership unknown | Exclude from production build for now | Creator/owner history, licence and permission for intended commercial use |
| Incident runbook | New internal documentation | Internal access; approved disclosure route | Work scope, confidentiality and client entitlement |
| Customer production logs | Third-party/confidential input, not employee-created code | Use only approved environment and recipients | Customer terms, access policy and retention/deletion decision |
The library exclusion is a completed engineering decision while rights remain unresolved. If the feature can work without it, ship the permitted work. If it is indispensable, hold that feature until permission or a replacement exists. A new employment contract cannot assign rights that the engineer does not own.
Put the clauses beside the decision
Record the exact employee agreement, client services/IP agreement, background-material schedule and any customer or university agreement. For each, capture version, relevant clause number, parties and scope; then write the precise change needed. “Protect our IP” cannot be accepted or rejected meaningfully. “Exclude library L from assignment but permit its licensed use in component C” is a concrete proposal for review, not ready-to-sign wording.
Confidentiality needs its own boundary: which logs, security details and customer information may be accessed, stored and shared, and who handles a request to publish an incident account? Preserve lawful disclosures. Government whistleblowing guidance explains that confidentiality clauses cannot validly prevent protected disclosures. Security restrictions and employment obligations must be coordinated without turning every concern into a secrecy breach.
Which provider evidence can decide this?
Teamed’s legal-team offering supports localised contracts and IP assignment. It is relevant for a team wanting specialist employment support, but that published scope does not establish acceptance of a particular bespoke clause. Make the actual marked-up documents the condition of selection.
Remote’s IP Guard description expressly explains the two-stage transfer chain. That is useful when the standard documents satisfy counsel. Its linked employment-agreement policy currently requires customer sign-in. Confirm the current amendment restrictions for the actual account; this edition does not treat a saved restriction as a newly verified policy or assume that every exception is available.
Deel’s published redlining process and custom-review guidance make it a meaningful bespoke-document alternative. Confirm applicability to this existing employee, review fees and the final accepted wording. Its public guidance does not promise acceptance either. Rippling or G-P should face the same document test if they already employ the engineer or meet a separate operating need.
Our selection rule is decisive: prefer an acceptable existing chain; negotiate an identified gap; exclude unusable material; change provider only when the indispensable requirement cannot be met and a different eligible arrangement can meet it. There is no supported unconditional bespoke-IP winner from the public material retrieved for this edition.
Do not transplant the English result
For Sweden, PRV’s agreements guidance supports resolving employment-related intangible assets in the relevant contracts. Use the Swedish AI rights inventory and the applicable local rules. For the Netherlands, start from Dutch copyright guidance and the existing-materials brief. These are distinct local assessments, not translations of the English invention test.
Return the closed rights items to the role-change decision record. Reopen it when a new repository, customer, research partner or publication plan changes the proposed use.