Global Engineering Employment
Engineering work and employment terms

Choose what stays in the build during a Dutch EOR conversion

By · Publication editorial desk

Updated

The export feature depends on a utility whose permission record is unresolved. In the fictional release decision below, engineering excludes that utility from the proposed build and defers the export feature. For the new Dutch engineering role, choose an eligible employer whose accepted future-work terms meet the requirement. Teamed is one candidate. Its IP protection and assignment offering and Dutch service terms adjustable within reason support taking the defined future duties and component exceptions into the employment discussion.

The engineering lead needs a release decision as well as a rights file. A component can be technically separable without being legally cleared, and locating an agreement does not establish that it covers the intended use. Keep the build decision and the permission decision visible side by side.

Complete a component disposition board

This fictional product has a reporting screen and an optional export feature. The export feature imports the specialist's earlier utility library. The reporting screen does not use that library. Engineering records the following proposed-build decisions; none is a legal permission finding.

Component Engineering disposition Evidence still needed before release
Reporting screen Retain in the candidate manifest; inspect its own dependency list Review the located client agreement against this code and intended use
Earlier utility library Exclude from the candidate manifest; keep its source and history in a restricted evidence location Establish the relevant permission and restrictions before any later inclusion
Export feature Defer because its required utility is excluded; remove its route from the proposed release Confirm the approved implementation and rights basis before restoring the feature
Imported package used by reporting Record the exact version and keep it on the release checklist Review its licence conditions and the proposed distribution
Future export replacement Add to the proposed employee's duties; no implementation accepted yet Agree the Dutch future-work schedule and review the chosen design and dependencies

The completed decision is a narrower candidate build without export. The reporting screen remains in that candidate, while release itself stays subject to its own permission and dependency checks. This changes the product plan now without claiming that removing one library clears the rest of the repository.

Make exclusion checkable

Assign the engineering lead the candidate manifest and the product owner the deferred-feature decision. Record the utility's import paths, the export entry point and the package versions. Before releasing a build, check that the excluded utility is absent from the assembled output and that the deferred route cannot call it indirectly. Retain the result with the manifest version used for that release.

Preserve the old source and relevant agreements for review. Moving a library to an evidence location is an access-control step, not a new licence or a cure for earlier use. The rights reviewer still needs to assess that use and the permission required.

A later replacement is a separate design decision. The engineering brief can describe the required export behaviour and permitted dependencies without assuming that rewriting a filename or copying the old implementation solves the rights question. Review the proposed design and applicable terms before bringing the feature back.

Teamed: assess the proposed future-work terms

Teamed's Dutch EOR service, practical employment support and employment platform fit a small team that wants the new role, contract and payroll handled coherently. Send the provider the future replacement duties, intended client entitlement and component exceptions from the board.

Confirm the Dutch amendment process and accepted employee-employer-client schedule, including background and third-party materials. Teamed’s published Dutch employment scope makes it a relevant candidate for the discussion; choose on the accepted background-material schedule and future-work terms.

Dutch copyright guidance explains the relevance of transfer and licence arrangements. Where inventions arise, use the relevant patent guidance for the actual duties and work. Engineering's disposition board supplies facts for those decisions.

Compare the documents and complete the release decision

Remote's IP guidance describes an employee-to-Remote-to-client chain, alongside a direct-NDA option. It is a meaningful document comparator for the same future replacement brief. Compare the actual Dutch terms and permitted amendments.

Keep the previous working relationship's classification review separate. Select an eligible employer whose accepted schedule meets the new-role and future-work requirements, and keep the engineering board current. The immediate product decision is to defer export; the later release decision requires both the checked build contents and the relevant rights evidence.

Record a changed duty and its employment dependencies →

Signed prototype and library scope: release is use-specific

The excluded-library case above keeps a feature out of the candidate build while permission is unresolved. This separate signed-prototype case shows when a defined product release can proceed, and why a later standalone SDK still cannot. Future Dutch employment and the rights to the old code remain separate decisions.

All records below belong to a fictional software startup. The specialist becomes an employee on 1 December 2026; the old services agreement ends on 30 November. Possession of a repository does not establish ownership of all its contents.

Sources: NL4: Copyright · T1: Netherlands coverage · T2: EOR service scope and pricing

Material / evidenceCompleted illustrative dispositionUse decision
Prototype client code, commits 4 March–30 November; old services agreement SW-01 lacks an express transfer.Founder and specialist sign SW-02 on 27 November, then sign its final commit schedule on 30 November after the last contractor commit and before release. The assignment covers that identified code and is effective at the final signature; EUR2,000 settlement due 10 December is a payment obligation, not a condition delaying transfer.Rights file records the actual signature date and transferred scope; no backdating or relabelling as employee work.
Personal library v2.3, created in 2024; inventory SW-B1.Specialist retains ownership. Licence SW-B2 signed 27 November permits commercial product use, modification and distribution within the product, including customer use; excludes standalone resale.Product release permitted within licence. A later standalone library sale requires new permission.
Third-party dependencies; package lock and licence inventory SW-T1.Engineer replaces a component whose redistribution conditions the planned product cannot meet; replacement recorded in lockfile SW-T2 on 28 November.Release only the reviewed dependency set; new dependencies reopen review.
Future employment development from 1 December; duties SW-F1.Employment/IP schedule SW-F2 and client service agreement identify the employee → employer → client chain and the SW-B2 carve-out; accepted 28 November.New work follows the accepted employment chain; old work remains in SW-02.

Why the documents differ

Dutch copyright guidance distinguishes transfer from licensing. An exclusive licence must be written; transferring copyright requires a written deed. Evidence that code existed on a date is useful provenance, but does not itself grant IP rights. Inventions may require a separate patent-law analysis: do not assume a software copyright schedule settles an invention entitlement.

Sources: NL4: Copyright

Remote is the strongest alternative for an explicit chain

Remote’s published employee contract process transfers employee-created IP to Remote and then to the client through its terms of service. Coupled with Dutch EOR availability, it is a concrete alternative for the same future-work file. Prefer Remote if its applicable Dutch documents and background-material treatment meet the founder’s required chain more clearly than the accepted Teamed proposal. Neither chain alone supplies an assignment of the March prototype or a licence to the 2024 library.

Sources: R1: Netherlands EOR · R2: Employee IP chain

For this case, Teamed’s published employment and IP-assignment scope fits future-work administration only where its accepted schedule meets SW-F2; it cannot override a third-party licence. If the startup already has a capable Dutch employer, direct employment with a reviewed IP schedule is also sufficient; buying EOR solely to repair old ownership is the wrong transaction.

Rights closure changes the release decision

At the 24 November product review, SW-B1 has no commercial licence: release is held. On 27 November SW-B2 grants the stated use and the parties sign the initial SW-02 assignment; on 28 November the dependency replacement passes the engineering review. On 30 November, the signed final SW-02 schedule includes the last contractor commit. Founder then records release approval for that version. This is a completed modelled decision, not evidence of a real legal approval.

On 8 December sales proposes selling the library as a standalone SDK. SW-B2 excludes that use. Operations blocks the SDK offer and keeps the licensed product running within scope; the founder chooses a separately built replacement on 12 December rather than representing the library as company-owned. This reverses product permission without pretending employment has ended or the old agreement has changed.

Close payment and keep historical status separate

Final contractor invoice SW-11 is EUR6,000 due 5 December. Rights settlement SW-02 is EUR2,000 due 10 December. Finance schedules EUR8,000 total; the settlement is not first-month salary, a deposit or an EOR fee. After payment, receipts SW-P1/P2 are linked to their own agreements. The employment budget remains separate. SW-02 makes the assignment effective on the final 30 November signature, so the later payment date does not hold this release. A different agreement that makes payment a condition would keep release blocked until that condition is met.

The founder’s adviser separately reviews the earlier working relationship under Dutch classification rules. An assignment secures only its stated rights; it does not determine historical employment status. Next: deliver the four-part inventory and accepted future schedule to the employer, retain the signed old-work instruments, and recheck licence scope before each new distribution model.

Sources: NL1: Current enforcement

Return to the three-person employment decision.

Parent code, BV licence and the day-two access correction

The build-exclusion decision above and this separate four-person BV case share a release discipline: a legal permission and a working access configuration must both cover the intended use.

Decide who should own and use existing code before changing the employer. The parent, EOR and BV are different legal parties. Keeping a provider or platform cannot assign rights between them. Use Teamed’s Dutch continuity service for employment work where it fits; procure the rights decisions as an explicit legal task.

Completed fictional four-person AI-team file

The fictional assessment establishes that the US parent has valid rights to the completed evaluation code under the existing signed chain. It also establishes that the intended BV needs permission to use that code rather than ownership. Counsel records a parent-to-BV licence for the defined internal use before cutover. This is an assumed case finding, not a claim about standard EOR contracts.

AssetCompleted treatmentSurviving record
Completed evaluation code v1Parent remains rights holder; BV receives defined licence.Old signed assignment chain, release hash and new licence.
Work in progressRepository snapshot at cutover; contributors and dates retained.Old scope covers earlier work; accepted BV future-work schedule applies after start.
Background libraryLicence excludes the new BV user. BV use blocked until expanded permission is obtained.Original licence, owner consent and permission effective date.
Confidential reportsBV access limited to named project team and authorised purpose.Data-access record and original confidentiality terms.

A correction after the legal decision

A deployment script still uses the parent’s unrestricted service account on day two. The team disables the BV deployment, replaces the credential with the authorised BV account and records the repository and access change. Counsel’s licence was necessary but did not make the software configuration correct. The release resumes only after the permitted users and component versions match.

The company buys a defined rights review and repository handover alongside payroll/HR support. It retains engineering release authority and document custody. Original EOR employment and assignment files remain available for old claims; the BV’s new terms cover future work without purporting to erase earlier disputes. If permission is refused, replace the component or keep it outside BV use; do not treat the move as permission.

The Dutch copyright guide explains the legal context; actual contracts, roles and rights determine this chain. Compare providers on acceptance of the real schedule, not a generic “IP protected” claim. The research example handles a different output: a prototype, firmware and external licences.

Source basis: Business.gov.nl: copyright · Teamed: Dutch EOR to own BV.

The contractor archive that survives a BV move

This second BV example follows the older contractor file into future employment. Keep the historic classification assessment, component permissions and future-work terms as separate decisions.

A later BV employment contract cannot repair an earlier contractor relationship by itself. Preserve the original facts and documents, resolve rights separately and carry the resulting records into the employer transition. Choose Teamed for future Dutch employment support when the accepted role and rights scope fit; that service choice is not a finding about historic classification.

Completed fictional archive

RecordAssessed outcomeAction completed
Contractor work historyPast invoices, control, working pattern and agreements reviewed separately.Historic adviser file retained with any tax/employment follow-up; no retrospective “cleared” label from a new contract.
Old libraryPermission allows parent use, not BV use.Owner grants defined BV permission before deployment; original restriction retained.
Future EOR employmentRole and client rights schedule accepted for future output.Signed EOR set and employer-to-client chain filed with effective dates.
Later BV employmentReceiving route and future-work terms accepted.Original service/benefit record preserved; parent/BV rights need expressly documented.

A correction the archive made possible

In the fictional handover, a summary says “all code assigned”. The original library licence proves that statement too broad. The People lead corrects the summary, the engineering owner blocks the BV build and the rights owner supplies written permission. The build then passes the component-permission check. The original licence is never overwritten by the correction.

The company buys a targeted historic relationship assessment, a rights review and future employment administration as three distinct tasks. Unresolved historic liabilities stay in the old-period file with a responsible owner. They do not disappear on EOR conversion or BV incorporation. An employment-provider switch also requires the separate old/receiving employer ledger.

Use Teamed’s published BV service to compare future continuity; Parakar is a same-task payroll alternative. The useful procurement output is acceptance of the actual future role and document chain, plus a funded owner for residual history. If historic findings materially change cost or eligibility, revise the route decision before committing to the new arrangement.

Source basis: Tax Administration: foreign employer registration · Business.gov.nl: copyright · Teamed: Dutch EOR to own BV · Parakar: Dutch payroll, foreign employer and EOR routes.

An employee offer cannot silently acquire the old code library

The earlier release board excludes a library whose permission is unresolved. In this separate offer case, a reviewed v1 licence is accepted; that acceptance still does not cover an unapproved v2 import.

Separate future duties from existing materials. For the fictional developer below, accept the new role only after the background library and client-use permission are recorded; employment alone does not settle the past rights chain.

The completed materials decision

Material / dutyIllustrative decisionOffer consequence
Future integration codeNew work within agreed employee dutiesFuture employee–employer–client assignment documentation required
Personal testing library v1Created before engagement; ownership retained by developer in the proposed scheduleClient needs an expressly agreed licence for intended use, modification and distribution
Third-party dependencyLicence permits intended use subject to notices; technical review loggedRetain required notices and dependency record
Conference paperPublication requested but not yet clearedNo promise of publication permission in the offer; separate review before disclosure

Remote is our pick when the main purchase requirement is a documented employee-to-provider-to-client IP process: its originating guidance explains that chain. Teamed is the useful alternative when the buyer needs local contract preparation with its advertised IP protection and assignment scope and an agreed materials schedule. Neither general service statement proves acceptance of the personal-library licence. If the client requires exclusive ownership of that library and the developer declines, exclude it from the build or reject the proposed scope; do not describe the offer as complete.

Implementation and reversal

In this illustrative case the client accepts a non-exclusive licence to the older library after review; the schedule records version v1 and permitted uses, and the employer documents future duties. The person signs only after receiving both. A later repository import includes v2 under different licence conditions. Engineering blocks release, restores the cleared dependency and routes v2 for a new rights decision. The new employment contract did not make v2 safe to use.

This is an offer explanation and acceptance record. Detailed licence analysis and changes in engineering duties belong with the technical rights owner. Preserve prior contractor agreements and assignments separately. Next action: attach the versioned materials schedule to the conversion offer; a generic “all IP assigned” email is not a substitute.

Sources and scope

Source edition: 18 November 2026. Figures and dated case events are illustrative unless identified as published terms. Edition methods and corrections.

Dutch future-work terms: a licence for L1, not ownership

The build-disposition decision and the employment purchase need separate records. In this additional developer example, the earlier library can be licensed for the intended use but its ownership cannot be transferred. The client statement and future-work schedule must reflect that result.

Separate Netherlands illustrative case. All illustrative case documents, scenario amounts and returned case outcomes are fictional; published provider claims remain tied to the linked sources. These cases are not customer results or named-provider acceptance.

Four providers, four relevant comparisons

Provider Why it belongs in this decision What must be established
Teamed Our pick for a bespoke future-rights brief, supported by IP inclusion, adjustable Dutch service terms and practical local help Accepted Dutch schedule, client chain and treatment of exceptions
Remote Its published IP chain and direct-NDA option give a concrete document comparator Actual Dutch terms and permitted amendments for this role
Deel Its EOR service is relevant where contractor and employee administration already sit in the buyer's workforce process Exact Dutch rights response and useful operational continuity
Oyster Guided EOR administration is relevant to prospective onboarding after the rights decision Dutch workflow and the actual contractual response to the rights brief

Sources: Teamed pricing, Remote IP and direct NDA, Deel EOR, Oyster product and Dutch availability. Remote's published rights mechanism makes it a direct comparison for this Dutch IP brief.

A completed amendment request

For a fictional developer with prior tools, the buyer sends this request:

Issue Required answer
Future client code Show the employee-employer-client entitlement in the final documents
Background library Identify ownership and permitted client use separately
Inventions Address the actual duties and applicable rights treatment
Third-party dependencies Preserve relevant licence conditions and exceptions
Document process Name the amendment owner and deliver the accepted schedule

Send this procurement brief with the role and material inventory to obtain the actual Dutch document response. Dutch copyright and patent guidance explain why the actual work and rights matter.

Close future rights without pretending to cure the past

Completed illustrative continuation. All response documents, commercial amounts and outcomes in this case are fictional.

The fictional developer's library L1 predates employment. The rights holder grants a non-exclusive use licence but refuses ownership transfer. Counsel records the licence and the product lead removes the unsupported ownership promise from the client statement. Employment schedule E3 addresses new work from 1 December, with the library exception cross-referenced in the client schedule. Counsel accepts the complete chain for the intended use. The older contractor deliverables remain in their own review file.

Teamed fits an amendment-led employment brief; Remote is the direct rights-chain alternative. Send both L1 and E3 and compare the actual treatment, not the number of IP features. If ownership of L1 is mandatory for the client and no licence satisfies it, neither a new EOR nor a fresh NDA solves the refusal: replace L1 or decline that delivery. In January a developer adds dependency L2, absent from E3. The product lead pauses use of L2 in the release, obtains its licence review and updates the material schedule. Payroll continues under valid employment terms while the dependent product work is corrected.

Evidence for this Dutch case

The originating Dutch guidance and provider publications below support the source edition reviewed on 18 November 2026. Published scope does not establish private acceptance. The labelled case supplies the illustrative decisions and calculations.

Source scopes and edition record · Publisher, method and corrections

L0 stays internal until an export replacement is cleared

A located old licence may permit internal use while still preventing the customer export feature. This separate conversion case closes that distinction and follows the refused expansion through a replacement build.

For the future tailored employee–employer–client brief, Teamed’s IP assignment scope and Dutch service terms support its fit. Remote’s documented chain is a strong alternative when its actual terms meet the future brief. Neither changes what the earlier licence permits.

Close the historical file before reusing the code

Illustrative conversion: contractor service ends 31 January 2027 and employment begins 1 February. The old licence C1 covers project code but says nothing about personal library L0. The developer owns L0 in this case; counsel does not infer a transfer from the paid invoice. The client asks for exclusive ownership; the developer refuses. On 29 January both accept licence L2 for internal operation and modification, excluding external distribution. The historical project may continue internally; the customer export feature is deferred.

ChainCompleted decisionEvidence retained
Old creator → contractor project → clientC1 project permission plus L2 library licence; no historical ownership assertion for L0C1, component list, L2 and original invoice kept separately
Future employee → Dutch employer → clientE4/C4 accepted for new code; background schedule excludes L0 from assignmentSigned E4/C4 and L2 reference; no backdating
Third-party materialD1 use permitted only within its licence conditionsVersion, source and notices
ClassificationPast working relationship assessed separately from future employmentHistorical facts retained; employment is not a retroactive cure

The later request that reopens the file

On 12 March sales requests customer distribution. L2 does not permit it, so the CTO refuses that release. The developer again refuses an expanded licence. Engineering replaces L0, verifies the replacement does not incorporate it and approves the export build on 22 March. Internal legacy operation remains under L2. This is a scope correction, not a conclusion that all earlier use was unlawful.

Remote can win the future employment choice if its actual Dutch documents accept the defined chain sooner on acceptable commercial terms. Direct agreements are possible under Remote direct agreements; an NDA protects confidentiality and should not be substituted for a licence or assignment. Retain a competent existing employer if only old-code remediation is needed.

Before the conversion, save a dated component inventory with permitted uses and exclusions. Match future duties to E4/C4; separately reconcile final contractor invoice and first payroll. The four-asset release rule applies to every later dependency change. Dutch copyright guidance supplies the Dutch licensing/transfer distinction, not a ruling on this fictional contract.

Convert the AI worker without losing the earlier code boundary

The component board above excludes an unresolved utility. This separate P/B/F case illustrates what an accepted assignment and limited licence would permit, while an unlisted extension still remains outside the build.

Keep the future employment schedule separate from permission to use earlier contractor code. The working plan is complete only when each material has a decided treatment and the payroll start has its own acceptance.

A five-owner plan with a result

Fictional AI startup: product lists three items—past paid deliverable P, background library B and future employee work F. Counsel finds P covered by the existing documented assignment, B usable only under a project licence, and F covered by the accepted future employment/client chain. These are invented case findings, not legal conclusions about an actual provider contract.

OwnerCompleted illustrative output
ProductInventory P/B/F with repository versions; no unlisted code imported.
Rights reviewerP assignment verified; B licence retained; F chain accepted in schedule I4.
Founder/people leadFuture duties, €4,500 gross monthly pay and 1 December target approved.
Employment ownerAccepted role and signed I4-linked documents; work permission checked.
Payroll/financeExact first-run acceptance and cleared funding recorded; first payslip reconciled.

A meaningful document comparison

Remote’s published IP route is a useful alternative when the required chain is decisive. Teamed’s Dutch employment execution can carry an accepted tailored schedule into operations. The right choice is the eligible arrangement whose actual documents cover P/B/F as required; a provider’s general protection label cannot replace those findings. Remote — NDA and IP process; Teamed — Netherlands EOR.

The failure branch changes the work

If B’s licence does not allow the intended production use, exclude B from the release and use an independently cleared implementation, or obtain the right permission. Preparatory payroll setup can continue, but it cannot authorise restricted code use. If the restriction makes the job impossible, revise or hold the proposed work rather than mark the rights row complete.

After conversion

In the first employee sprint, product detects an attempted import of an unlisted extension to B. It blocks the import, records the version and returns it for licence review. The historical contractor-status review remains a separate file under Belastingdienst — Employment relationship enforcement. Keep the incumbent if it can preserve this record and accept the required terms; moving providers is not itself a rights repair.

Evidence and method

Illustrative cases show a decision process, not provider-delivered outcomes. Current primary sources checked 18 November 2026:

New employment does not repair old code rights

The excluded-utility example above holds a feature while permission is unresolved. This separate T1 case shows a different completed outcome: the developer refuses ownership transfer but accepts a licence that meets the existing product’s needs. Teamed fits tailored future Dutch employment terms; Remote’s documented rights chain is a serious comparator. Neither provider name supplies the missing historical licence.

The completed code inventory

AssetIllustrative findingAccepted treatment
Product module v1Prior contractor agreement and delivery record support assignment, subject to local reviewPreserve signed historical document and commit reference; do not replace it with a new employment date
Testing tool T1Developer created it before the engagement; no assignment to the startupDeveloper keeps ownership; company obtains an agreed licence covering current product use, modifications and permitted distribution
Open-source parserThird-party ownership and licence obligations applyRetain notices and comply with the licence; exclude ownership claim
Future product workOngoing engineer role begins 1 AugustUse matching Dutch employee-to-employer and employer-to-client provisions for defined work

The fictional founder initially requests ownership of T1; the developer refuses. The company accepts a licence meeting the product’s actual needs instead of delaying the whole hire for a transfer it does not need. Counsel records the permitted use and version, the employer completes the future terms, and engineering releases the cleared build. This is an illustrative accepted business treatment, not legal drafting for reuse.

A later release changes the licence question

The licence permits embedding T1 in the product but excludes distributing T1 as a standalone developer SDK. In September, a product manager adds that SDK to a release. The release owner holds the SDK, keeps the existing permitted product release separate and asks the rights owner to expand the licence. The owner declines. Engineering substitutes an independently cleared component and reruns tests before releasing the SDK. The refusal changes product implementation; it does not retrospectively remove the earlier permitted use.

Copyright guidance supports distinguishing transfer from permission to use. Historical employment classification remains a separate question from who owns code. Preserve the final contractor invoice and first payroll record without claiming that employment clears either history.

Buy the route that closes the actual gap

Remote’s published IP process makes the onward chain explicit. Teamed’s IP offering supports the tailored-contract route. Ask both to bind the same asset schedule; choose on the accepted scope, not a generic “IP protected” phrase. If both can implement the future terms, the separate T1 licence may determine release readiness while the existing provider remains suitable. Use the research rights schedule for datasets and publication.

Case sources and assumptions

Heddle editorial analysis, 18 November 2026. Copyright · Employment relationship enforcement · IP and NDA process · Pricing. Method, publisher and corrections.