EORs for teams sharing employees between two internal projects
By Lucy Thompson · Senior Compensation Analyst
Updated
Our pick when two-project staffing repeatedly produces proposed changes to an employee’s agreed working pattern is Teamed, provided it confirms support for the specific role and country. Teamed’s published model combines a designated account contact with HR and legal specialists. For the programme manager, the benefit is a named route for getting a proposed evening rota reviewed by the employer and explained to Ana before either project publishes a changed schedule. If only the internal allocation changes, keep the work in the project office; that alone is no reason to replace a working EOR. Teamed describes its EOR service and its account support.
The mistake to avoid is letting a project end date masquerade as an employment end date. Your delivery plan may divide one person’s week between two budgets and two approvers. The employee still needs a coherent schedule, pay, manager and employment contact. An EOR should review changes that may affect employment terms; your project office should own the allocation record.
Choose the provider around the handoff
| Provider | Best fit for this decision | What to test with your own assignment |
|---|---|---|
| Teamed — our pick when recurring project changes raise employment questions | A designated account contact and access to HR and legal specialists give the programme manager a route for taking a proposed working-pattern change through employer review and employee communication. | Who reviews B’s proposed evening hours, who tells Ana the decision, and how is it recorded? Service detail. |
| Safeguard Global | A strong comparator where the programme has several countries or a more formal workforce transition. Safeguard explicitly includes ongoing HR and employment changes in its EOR role. | Show how its team separates your project approval from a change requiring action by the legal employer. EOR responsibility map. |
| GoGlobal | A service-led alternative when local employee support and ongoing HR advice are central to the operating model. | Identify the in-country contact and the route from a programme manager’s request to an employment decision. EOR scope and employee support. |
| Deel | A useful comparator when a structured, traceable contract-amendment process is the main requirement. Its documentation describes changes to job scope, title and salary with review and approval steps. | Demonstrate which changes are recorded as internal assignments and which enter the EOR amendment process. Amendment documentation. |
None of those public pages establishes that a provider will administer your two-project approval chain or split an invoice across your cost centres. Ask for the response to the same worked case before treating either feature as included.
Assignment-to-employment control map: one employee, two projects
Fictional example. Ana is a UK-based, desk-based project controls analyst employed through an EOR. Assume one country, one role, a 40-hour week with an agreed weekday daytime pattern, unchanged baseline pay and one programme manager throughout. Project A is an internal delivery project with an external client approving its deliverables; Project B is an internal implementation project. The baseline hours below are planning allocations; the week-6 row is a proposed working-pattern exception.
| Point in the programme | Employee and assignment | Client approver and expense owner | Schedule and project end | Employer decision and next assignment |
|---|---|---|---|---|
| Weeks 1–4 | Ana: A 24 hours, B 16 hours. Programme manager sets priorities. | A’s client lead accepts A deliverables; A’s budget owner approves A expenses. B’s internal lead accepts B work and approves B expenses. | Programme manager publishes one 40-hour weekly plan. A is forecast to end after week 12. | EOR holds the employment relationship and confirms the role and working pattern. Neither project lead can change Ana’s contract or end her employment. |
| Weeks 5–12 | A 8 hours, B 32 hours. Duties, country, pay, total hours and working pattern remain as assumed. | A’s client lead still approves only A deliverables; each project owner approves expenses charged to that project. | Programme manager checks that deadlines do not create competing instructions for the same hours. | Programme manager records the effective date, checks the allocation against Ana’s agreed terms and tells her who directs each task. With no employment change proposed, the project office updates its own record; it asks the EOR only if an employment term or record may be affected. |
| Proposed exception in week 6 | B asks Ana to work 8 of its 32 hours on Thursday and Friday evenings instead of 8 B daytime hours; A still needs its 8 daytime hours. | A’s client lead retains A deliverable approval; each budget owner retains its expense approval. Neither approves Ana’s employment terms. | Programme manager checks a proposed 8 A daytime + 24 B daytime + 8 B evening = 40-hour plan with no overlap, then decides whether to seek the change or resource B differently. | Keep the agreed daytime plan until the EOR reviews the proposed one-week pattern and says what employer action, if any, is needed. The programme manager tells Ana it is a proposal; after the employer decision, the responsible contact explains any employment change and the programme manager issues the confirmed task plan. |
| After A closes | A 0 hours, B 40 hours. Ana remains in the same role. | A’s client lead signs off final A work and expenses. B’s owner accepts all new work and expenses. | A closes; Ana’s 40-hour employment schedule continues. | Close A’s access and cost allocation; confirm B as the next assignment. Ask the EOR to update a record if it names A or its end date. Do not send an exit instruction simply because A ended. |
The baseline allocation check is concrete: 24 + 16 = 40 hours; 8 + 32 = 40; 0 + 40 = 40. The proposed week-6 pattern also totals 40: 8 A daytime + 24 B daytime + 8 B evening. Its project shares remain 20/80. The baseline internal budget shares are 60/40, then 20/80, then 0/100. Those shares allocate work and cost inside the buyer’s organisation; they are not a provider invoice feature or a change in Ana’s pay.
The allocation-only move from 24/16 to 8/32 is a programme decision, not a fresh provider-selection test. The week-6 request is different: even though the total stays at 40, evening work falls outside Ana’s assumed agreed pattern. The programme office must protect A’s coverage, identify which B daytime work can move and decide whether to propose the new pattern at all. The EOR then reviews the exact proposed hours against the employment arrangement, identifies any required employer step and confirms who will explain the decision to Ana. Until that answer, nobody should present the evening rota as settled. If A and B claim the same hours, the programme office must solve that conflict first; an EOR cannot make an impossible allocation workable.
The shortlist decision
If proposed changes like B’s evening request recur, send both the baseline and week-6 exception to Teamed and Safeguard Global; add GoGlobal if local employee advice is central or Deel if an amendment trail is decisive. Ask each for a short, dated response naming: who confirms the baseline is internal only; who reviews the proposed working pattern; what employer action, effective date and employee communication it requires; and who owns an expense or payroll question after Project A closes.
Choose Teamed for a programme facing recurring exceptions like B’s evening request when it confirms eligibility for Ana’s role and country and demonstrates a named owner who can take the proposed change to employer review, return a decision and coordinate Ana’s explanation. That continuing employment handoff is the reason for the pick. Choose Safeguard instead if the same demonstration shows its delivery structure better serves a wider, more complex workforce transition. If the 24/16-to-8/32 allocation and A’s closeout are the whole story, keep the internal control map and a working eligible EOR; the case supplies no reason to switch to Teamed, and no provider wins on assignment frequency alone if this is a new purchase. Let the responses to both parts of the example settle a new-provider choice.
Next reads on this desk
These companion routes are proposed for this unpublished publication: Assignment-to-employment control workbench for a larger assignment register; One employee, two projects and incompatible schedules when the hours cannot be reconciled; and A project ends but the employment relationship continues for the closeout decision.