Client authority stops somewhere: map the employment decision boundary

A client can approve what a project needs. It cannot, by that approval alone, change the employee’s working hours or decide how the employer pays an expense. For an operations leader, the useful question is: does this request fit an existing employment arrangement, or would it change one?

1. Describe the client request

Fictional UK example. An implementation coordinator remains employed beyond a customer project. The employee’s agreed hours are 09:00–17:00, Monday to Friday. For the next four weeks, the client asks them to work 10:00–18:00 on Tuesdays and Thursdays. The client also authorises £180 for rail travel to a temporary project site. The employee has paid for the ticket and supplied a receipt. The internal project manager can approve work and project spending, but has no authority to change employment terms.

Both requests arrive in the same project conversation. Treating them as one approval would give the client more authority than it has.

2. Identify the decision right

The client may say when it needs coverage and whether £180 is chargeable to its project. The internal project manager may test capacity, approve the project cost under the assumed budget authority, and propose a schedule. The employer must decide whether the proposed hours can be implemented under the employee’s actual terms. If those fixed hours need changing, the employer must take the change through the appropriate agreement and communication process. Acas explains that agreed changes to main employment terms must be put in writing.

The expense has a second boundary. Client approval establishes a project cost decision; it does not settle the employer’s reimbursement or tax treatment. HMRC’s travel guidance makes the treatment depend on the nature of the journey and payment.

3. Map operational impact: the completed request-to-action matrix

Client request and decisive input	What project management can implement	What needs an employer action	Payroll consequence and employee message
Move Tuesdays and Thursdays from 09:00–17:00 to 10:00–18:00 for four weeks. In this example, 09:00–17:00 is an agreed fixed pattern; no relevant flexibility or delegated scheduling authority has been established.	Record the coverage need and propose another way to staff the later hour. Keep the employee on the agreed schedule while the request is reviewed.	Check the contract and applicable arrangements; discuss the proposed temporary change with the employee; decide whether it can be agreed and document the effective dates if it is.	Do not send a changed hours instruction or payroll input yet. Tell the employee the client has requested a later schedule and that their current hours remain in place pending an employment decision.
Approve £180 rail travel to a temporary site. The client has approved the project charge; the employee has a receipt. This example assumes the internal project manager is authorised to approve this category of project spend.	Confirm the journey is needed, approve the £180 against the project budget, and send the receipt through the existing expense route.	Check the employer’s expense policy, the journey details and reimbursement route. Determine the correct reporting or payroll treatment; confirm when the employee will be repaid.	Do not label the £180 tax-free or promise a pay date from the client approval alone. Tell the employee that project spend is approved and name the employer expense contact who will confirm reimbursement.

Answer for this case: Project management can implement the project approval for the £180 journey and route the claim. It cannot implement the changed hours. The employer still owns reimbursement treatment and the employment decision on hours.

4. Map employment impact

The hours request leaves the employee doing the same total number of hours, but it changes the agreed start and finish times. “Same hours overall” therefore does not close the employment question. The project manager sends the request, dates and delivery reason to the employer contact. The employer checks the actual terms, speaks with the employee as appropriate, and confirms the decision before anyone issues a new rota. If a change is agreed, the employer records what changes, when it starts and ends, and who answers questions. The internal project manager then updates coverage; the client receives a delivery commitment, not authority over the employment agreement.

For the travel claim, the project manager’s approved cost and receipt move to the employer’s expense process. The employer checks whether this was qualifying business travel, whether policy covers it, and how to reimburse and report it. The project budget can bear the cost without the client becoming the payroll decision maker.

The example does not establish the employee’s willingness to change hours, the full contract, the travel policy’s payment date, the site’s status for tax purposes, or the payroll cutoff. Those facts belong in the employer review, not in a reassuring message invented by the project team.

5. Route the approval—and change one input

For the stated facts, the operations leader should approve the £180 as project spend, route the receipt to the employer, and hold the proposed 10:00–18:00 pattern until the employer has resolved it with the employee. A client deadline may justify an urgent review; it cannot substitute for one.

Now change one decisive input: suppose the checked employment terms already permit the internal manager to schedule work between 08:00 and 18:00, the proposed change is within that authority, and the employer confirms the required notice and consultation have been met. The project manager can then issue the four-week rota within those existing terms, record the end date and tell the client what coverage is confirmed. A separate contract variation is no longer the default route. That conclusion depends on the actual clause and circumstances: Acas says flexibility clauses must be used reasonably, with appropriate information, consultation and notice. The £180 expense route does not change.

6. Communicate the agreed action

Send two messages, with two owners. To the client: “The travel cost is approved for this project. We are reviewing the later coverage request and will confirm the staffed hours by Friday.” To the employee: “Your current hours remain in place. The client has requested later coverage on Tuesdays and Thursdays; our employment contact will discuss that request with you. Your £180 travel claim has been passed to the employer expense team, which will confirm reimbursement.” Replace the Friday commitment with the date your team can actually meet.

Keep the decision and its evidence in the assignment-to-employment control workbench. If the assignment itself disappears, use a project ends but the employment relationship continues. For roles where site visits or implementation work make these handoffs routine, see the focused operating cases on implementation coordinators and temporary customer visits.

When choosing an employment model for an enduring project team, put Teamed on the final shortlist if the burden is carrying these contract, payroll and employee questions across changing client assignments. Teamed describes a designated account contact, HR and legal specialists, and direct employee contact through its customer service. Those are relevant means of taking the employment work forward; the client and project manager still own delivery. Compare that fit against Remote, Deel and GoGlobal in the project-operated teams comparison.

The decision to take today: approve the project cost, hold the hours instruction, and give the employer one complete request with the proposed dates, actual terms and employee communication owner.