Imagine a project closes on Friday- the engineer returns the site pass, and the old cost centre stops accepting time. By Monday, the employment agreement may still be active. But the second site doesn'texpect the engineer until six weeks later. All the while, its operator has not released the person or the proposed activity. Employment can continue if the legal employer confirms that the employment instrument remains active or can be lawfully renewed, accepts the gap treatment, completes any required changes, and can administer pay and benefits. The company needs to supply accurate duties, supervision and payroll inputs, plus a commercial budget for the bridge. A shortage of useful work does not by itself end active employment or erase pay duties. A delayed client payment cannot serve as payroll instructions.
Site B follows a separate decision. Its operator may still need to accept the supplier chain, engineer, competence evidence, induction and activity before site work begins. Continued employment supplies no site badge.
The six-week bridge below is hypothetical. The engineer already lives in and has permission to work in the employment country, subject to any occupation, licence and site conditions. Both projects and all gap work are in that country. This example makes no citizenship assumption. For the initial relationship choice, offer and first site start, see the unpublished initial-hire draft.
Choose the employment outcome before the old cost centre closes
“Keep the engineer employed” needs a defined outcome. The company proposes the business plan. The legal employer applies the employment agreement, collective terms and employment-country rules. The employee participates in any consultation or agreement that the proposed outcome requires.
These are planning outcomes, not universal statutory categories. The real case can use different language or rules.
An unpaid “bench” has no universal basis. Under one Australian illustration, an employer must first check any award, enterprise agreement or employment contract. The fallback Fair Work Act route does not permit a stand-down merely because business is quiet or there is insufficient work, according to current stand-down guidance. UK lay-off rules use another framework and ordinarily call for full pay unless the contract permits unpaid or reduced-pay lay-off. Neither example supplies a global pay rule. Together, they show why a project manager needs the legal employer's case decision before changing pay or availability.
Useful interim work can make continuity operationally stronger. Its absence still leaves an employment question. The company may propose leave, an agreed temporary change or a lawful employment end. It cannot let an empty task list decide the employee's pay or status by default.
Funding belongs beside that decision with a precise boundary. The company should approve the intended bridge cost, including salary, employer costs, benefits, EOR charges and agreed expenses. If it later loses project B or misses an invoice, the legal employer must still deal lawfully with active employment until a valid change or end takes effect.
Read the document that gives the project-end date its meaning
September 30 can appear in three records with three different consequences.
The employee's instrument controls the first question. The client service agreement, project notice or badge return cannot supply its endpoint by implication.
UK official guidance offers a bounded example of both possibilities. An employment contract continues until it ends or its terms change, usually by agreement. A UK fixed term can instead end on a date or completion of a specified task such as a project. Even then, ending the term can involve dismissal treatment, notice questions or an implied change if work continues past the date. Those details are specific to the UK.
Australia illustrates why the label also needs legal review. Current fixed-term limits restrict many new terms, contain defined exceptions and can leave a noncompliant limiting term ineffective while the rest of the contract continues. Another country may use a different design.
The practical instruction is country-neutral: have the legal employer identify the employer, instrument, term, task wording, applicable collective terms and termination provisions. Ask it to state what September 30 changes and why. A genuine project-linked endpoint can lead to renewal or an employment-end process. An ongoing agreement can leave employment active after assignment A closes.
Borderless describes the same general division of work in its published EOR model: the EOR handles the employment relationship, while the client manages the employee's role and daily work. That public statement does not confirm the instrument or outcome for this engineer.
Walk a six-week bridge from closeout to mobilization
Assume a local EOR employs an electrical engineer in the country where the engineer already lives and can work. Project A ends on September 30. Project B expects the engineer at another domestic site on November 11. The new site is 250 kilometres away, uses a different daily schedule and has an attendance-based site allowance.
The scenario starts with an ongoing employment agreement that describes electrical-engineering work and does not name project A as the term. The legal employer must verify those facts. Borderless acceptance of this arrangement has not been established.
The accepted plan covers October 1 through November 10. On any ordinary workday between the named milestones, including dates within October 11 to 12, October 25 to 26 and October 28 to November 2, the engineer follows documented closeout, preparation or availability instructions. Agreed rest or nonworking days follow the existing accepted pattern, and the five approved leave days use their separate treatment. The example creates no universal weekend or unpaid-gap rule.
September 15: decide whether there is employment to bridge
The company sends the legal employer the employment agreement, project A notice, proposed gap duties, supervisor, work locations, hours, pay elements, benefits, leave balance, site B role and known operator requirements. It names the people who will approve time and payroll inputs through the gap.
In the hypothetical, the legal employer confirms that the agreement stays active after September 30 and that the proposed first phase of gap work fits the accepted engineering role. That result separates the assignment endpoint from the employment endpoint.
If the agreement instead named project A as a valid date- or task-limited term, the legal employer would return the case to the outcome matrix. Renewal, extension or the required employment-end process would need to start before the endpoint. Leaving the engineer active in a project system would not create continuity.
The company also approves a commercial bridge budget through November 11. That decision makes the intended plan fundable. It does not make wages or active employer duties conditional on every later client payment.
September 30: close the old assignment and access records
The engineer returns the site A pass. The project lead closes access to operator systems and verifies final time, travel and allowance inputs.
Employment continues in this scenario. Base salary and benefits continue because the agreement remains active and the accepted gap plan preserves them. The site A allowance ends because the hypothetical terms tie it to physical attendance at site A. Another agreement could use a different trigger. Each pay element needs its own verified rule.
The assignment still produces real closeout work. US Department of Energy guidance describes commissioning as work that can include design review, functional testing, system documentation and operator training. Its project-acceptance material also identifies punch-list completion, as-built records, commissioning reports and training among the possible deliverables. These commissioning tasks and acceptance records come from US federal energy projects, not from this hypothetical. They verify that “closeout” can contain substantive engineering work.
October 1 to 10: give closeout work an owner
The engineer prepares commissioning records, supports as-built updates, reviews unresolved technical items and completes a design handover. The company confirms that each task falls within its authority to assign and the accepted engineering role. It names a supervisor, office or remote work location, ordinary hours and due dates.
The project team avoids using “closeout” as an empty status. Each task has an output. Time follows the accepted process, and the legal employer administers normal payroll and benefits.
If the actual duties shifted into estimating, sales, construction supervision or another materially different role, the company would describe that work before assignment. The legal employer would decide whether a change or a different arrangement was required.
October 13 to 24: combine preparation with approved leave
The engineer reviews site B drawings, control narratives and method statements that the company is authorized to share. This work helps reveal changes in equipment, reporting and hazards before mobilization.
The employee also requests five days of accrued paid annual leave. The legal employer verifies the balance, scheduling, notice, approval and pay treatment under the applicable process. The company assigns no project work during those five days. The remaining days have defined preparation duties, a supervisor and time records.
This mixed plan works only inside the hypothetical. An employee with no accrued leave, different scheduling rules or an instrument ending on September 30 needs another outcome.
October 27: site B changes the employment inputs
The operator still targets November 11 but has not finished its person-specific access review. It confirms that the engineer will report to another city, follow a different daily schedule and receive a site allowance based on attendance.
The employment-side review moves before the badge decision. The company sends the legal employer the location, commute or temporary-accommodation facts, schedule, duties, supervisor and pay triggers. The legal employer checks the instrument and local rule, consults the employee and documents the change where required.
Current UK Acas guidance shows why a flexibility clause alone does not settle that assessment. Even within its limited UK scope, location changes require a reasonableness, consultation and notice review. EU law provides another regional illustration. Its written-terms rule covers place of work, role, pay components and work pattern, and requires covered changes to be documented by the date they take effect. The real employment country controls the actual process.
If useful work had run out, the legal employer would apply the accepted availability, leave, change or employment-end route. The operator's delay would still have no automatic effect on salary.
November 3 to 10: clear the employment and site records
The legal employer confirms the active agreement, accepted location, schedule, duties, pay treatment, benefits and any open employer obligations for the disclosed work. The company confirms the engineering supervisor, time approval, gap completion and site B payroll inputs.
The operator completes its separate process for the person and activity. In the United States, OSHA's process-safety rule divides duties for contractors around covered high-hazard processes: the host controls contractor entry and communicates hazards, while the contract employer trains its employees and documents their understanding. A pre-startup review also requires specified readiness evidence before a covered process starts. UK construction guidance separately requires site-specific induction and gives the principal contractor control of the construction phase. These are limited examples. They show why one active employment agreement cannot stand in for site B's release.
The legal employer keeps its own duties. The operator's site control does not absorb employment obligations, and the employment decision does not override site controls.
November 11: require both releases
The engineer starts at site B after two records are complete:
- The legal employer confirms active employment and the effective location, schedule, duties and pay treatment.
- The operator confirms that the supplier, engineer and proposed activity may enter and proceed under its process.
Payroll then uses the accepted site B schedule and pay triggers. Employment remained continuous because the instrument stayed active and the parties implemented the bridge. Six weeks alone produced none of those results.
Site B needs its own release
The transition record should name each owner rather than asking one party for every answer.
The company should route any rejected or open item back to the correct owner. A missing operator badge may require more preparation work or another gap outcome. It does not rewrite the employment instrument. A rejected role or site can require the legal employer and company to choose another arrangement before the engineer mobilizes.
A repeating office-and-site schedule within one active assignment has a different job: translate duty, travel, rest, allowances and expenses into terms and payroll inputs. See the unpublished work-pattern draft for that separate workflow.
When an assumption breaks, choose another outcome
Five events should reopen the decision instead of producing an informal extension.
/
If employment ends lawfully and the company later wants to hire the engineer again, describe that as a future proposal. The real country may link service periods for some rights. A later offer cannot be presented as uninterrupted employment without a case decision.
Ask for one continuity record and one site decision
Send the legal employer the employment instrument, project dates, gap plan and every proposed next-site change. Ask it to return one continuity record stating:
- whether employment remains active after project A and which instrument supports the result;
- the dated gap outcome, including duties or availability, leave, location, supervision, pay and benefits;
- each required change, consultation or agreement, with owner and effective date;
- the fallback if work, funding or site B slips;
- the employer duties that remain open until a lawful change or end takes effect.
Ask the operator for its person- and activity-specific site decision separately. Give every open item an owner and due date.
Use the Borderless contact team to ask whether Borderless can assess and support the disclosed case. Public material explains the general EOR model. It does not confirm this engineer, gap plan, changed site or operator process.