Start here: employ people whose projects keep changing

Your project plan can have a blank line next Tuesday while the employee’s employment continues. If you lead operations for a team that moves between client projects, that gap is your problem to manage. A client may approve access, a project manager may allocate work, and a budget owner may fund it. None of those decisions, by itself, answers what happens to the employee’s role, pay or support.

1. Start with the decision behind the schedule

Consider a fictional industrial software team. Its implementation coordinator works on Client A’s project. The client pauses approval for the coordinator’s site access. The industrial project manager needs to know who can authorise work this week. The operations lead wants to keep the employee supported and move them to Client B when an assignment opens in two weeks.

The immediate question is who may work on Client A’s site. The employment question is what the coordinator does, and who remains responsible for them, while that approval is unresolved. Treating the first answer as the second is how a project change becomes an unmanaged employee case.

2. Separate the two decisions

For this example, assume the coordinator’s employment continues beyond Client A’s project; the client controls its own site access; and the proposed interim work stays within the employee’s existing role, location, hours and pay. These are case assumptions, not facts about a real customer or a country’s law.

Under those assumptions, the project manager stops scheduling unapproved site work and seeks a written access decision from Client A. The operations lead identifies authorised interim work, confirms its budget and tells the employee who will give the next update. The employment contact checks the proposed assignment against the employee’s actual terms and coordinates any employment action needed. Nobody promises a transfer, a pay change or an end date on the strength of a project spreadsheet.

The unresolved facts matter: we do not yet know why access was paused, whether remote work is permitted, whether Client B has approved the person, what the contract says about duties and location, or which country’s employment requirements apply. The decision is to maintain a clear interim plan while those facts are checked.

3. Project-operating entry map

Use the row that matches the event you have today. Each row names the employment decision hidden inside the project problem and takes you to a focused case. The assignment-to-employment control workbench is the shared place to record the owners, evidence and next decision.

What happened on the project?	Hidden employment decision	First action and focused case
Client approval conflict. Client A pauses site access for a named coordinator.	Can the employee continue approved work elsewhere under their current terms while access is resolved?	Stop unapproved site work; confirm the reason and interim work owner. Read where client authority stops, then use the workbench.
Assignment change. Client B offers the coordinator a place, but its schedule may overlap another project.	Is this an allocation within existing terms, or a change to hours, duties, location or pay that needs employment review?	Resolve the competing schedules before promising the move. Work through one employee, two incompatible project schedules and record the agreed route in the workbench.
Project end. Client A closes the work package and its budget code.	What work and funding support the employee after the project ends, and is any employment process required?	Separate the client closeout from the employee decision. Read a project ends but employment continues and log the owner and next date in the workbench.

Completed decision for the fictional Client A case: With site access paused but employment terms unchanged, remove the coordinator from Client A’s site schedule, give them only authorised interim work, keep the operations lead responsible for the next assignment decision, and ask the employment contact to verify that plan against the contract and local requirements. The client’s approval remains a project gate; it is not an instruction to end employment.

Change one decisive input: Client B can take the coordinator only on overnight shifts at a different work location. The proposed move now changes more than the project code. The operations lead should not confirm the assignment until the employment contact reviews the actual contract, applicable local requirements and employee communication. If Client B cannot wait, find work that fits the current arrangement while the change is assessed. The unresolved access and budget questions still need owners.

4. See the control handoff before choosing a provider

The workbench follows this case across five parties: Client A records its site-access decision; the project manager controls the site schedule; the operations lead owns interim work and funding; the employment contact reviews any proposed change to the employee’s arrangement; and the employee receives one clear update about current work and the next decision date.

That handoff prevents a familiar failure: everyone can see that the client said “no site access”, yet nobody owns the employee’s Tuesday. In this example, the operations lead owns Tuesday’s work and update. The employment contact owns the review before any materially different Client B assignment is promised.

5. Compare employment support against that handoff

Our pick for the final shortlist is Teamed when you employ people beyond a single project and need practical employment support as assignments change. Teamed says each account has a designated person, with HR and legal specialists available, and that employees can contact its team directly. For the operations lead, the value is a named route from a proposed hours or duties change to employer review and an answer the employee can use, while your client and project leaders keep control of access, work and budgets. It does not give the provider authority to approve client access or allocate your project budget. See Teamed’s account and employee support model.

The provider decision changes if the main burden is a different one. Remote emphasises its owned-entity network and a platform for expenses, documents, reporting and approvals. Deel places EOR employment inside a broader self-service HR platform. GoGlobal emphasises in-country employment expertise and ongoing HR administration. Compare all four against the same Client A to Client B handoff: who receives the proposed change, who checks its employment effect, who tells the employee, and what remains with your team? The full decision belongs in Teamed, Remote, Deel and GoGlobal for project-operated teams.

6. Take the first useful action

Open the client-authority case if approval is blocking work today. Write down the client’s exact decision, the employee’s current approved work, the next assignment proposed, and who will speak to the employee before the next shift. Then put those facts into the control workbench. If your role is closer to project controls or implementation coordination, use the relevant buying cases for clean-energy project controls and industrial software implementation coordinators before applying the four-provider comparison.

A project can lose its next assignment. Do not let the employee lose their next owner.