Client problems

What to do when a client wants a different person on the project: 32 ways to manage the request

When a client asks for a different person on the project, find out what needs to improve, assess whether a change is practical, and confirm who can authorize it. Address any immediate service problem while the request is reviewed. If a handover is agreed, name the new responsibilities, transfer the relevant project information, and explain the next checkpoint.

A change request can reflect a skills gap, communication mismatch, availability problem, loss of confidence, or a misunderstanding about roles. Replacing someone without understanding the issue may leave the same problem in place. Handle the conversation privately and fairly, without promising an immediate personnel change or sharing confidential staff information.

The messages below are illustrative project communication. They do not determine employment decisions or legal rights. Requests involving discrimination, harassment, safety, or other serious concerns need the appropriate organizational process and qualified advice where required.

What to do first when a client requests another team member

1. Ask for the specific issue, desired improvement, and any immediate project risk.
2. Check the agreed roles, service commitments, and approval authority for a staffing change.
3. Separate a fixable workflow problem from a capability, conduct, or availability concern.
4. Assess a suitable response: clarify roles, add support, change the contact, or arrange an appropriate handover.
5. Confirm the decision, responsibilities, communication route, and next review point without disclosing private personnel details.

What to do when a client first asks for another person

Listen for the specific project need before committing to a change. A calm, private conversation can reveal whether the client wants a new contact, a different skill, or a response to a particular service failure.

1. What to do when a client asks for a replacement without giving a reason

Ask what is not working and what improvement they want. Keep the question neutral, without demanding that the client defend the request or inviting personal criticism. Explain that understanding the issue helps identify a useful response.

Do not promise a replacement before checking authority and availability. Summarize the concern and give a realistic next step for review. If the client does not want to discuss details with the current contact, offer the appropriate escalation route rather than forcing that conversation.

• “What would need to improve for the project to work better?”
• “Is the concern about communication, expertise, availability, or a specific incident?”
• “I will review the request before confirming any change.”
• “If preferred, the concern can be raised through the appropriate project lead.”

2. What to do when a client says the working relationship does not click

Ask for practical examples of the mismatch, such as response style, meeting structure, or how feedback is handled. A vague interpersonal concern may still point to an addressable workflow issue. Avoid pressuring the client to make personal judgments about the team member.

Explain the options that can be assessed, including a different communication process or contact person. Do not assume that everyone must have the same style to work effectively. The goal is a functioning project relationship with clear expectations, not agreement about personalities.

• “Which parts of the working process feel difficult?”
• “Would a different review format or contact arrangement help?”
• “We can assess the practical options without making personal judgments.”
• “Let us define the improvement needed before choosing the response.”

3. What to do when a client asks for the person they worked with before

Check what the client valued about the earlier arrangement and whether that person is actually available for the current scope. Do not imply that a previous engagement guarantees access to the same individual indefinitely.

If the requested person is unavailable, explain the available alternative and how continuity can be supported. Avoid disclosing private reasons for absence. A clear brief and handover may preserve the useful parts of the earlier experience even when the team differs.

• “What worked particularly well in the previous arrangement?”
• “I need to check availability for this project’s scope and timing.”
• “If that person is unavailable, we can explain the suitable alternative.”
• “The project history can support continuity without restarting the briefing process.”

4. What to do when a client asks to remove someone immediately

Clarify whether there is an immediate conduct, safety, access, or service concern requiring the appropriate escalation. Take specific serious concerns seriously without assuming all allegations are established facts. Do not promise a personnel outcome before the authorized process has assessed it.

For ordinary project dissatisfaction, explain how the request will be reviewed and what work can continue safely and appropriately. Keep the discussion private and factual. If temporary contact arrangements are needed, confirm them through the responsible lead rather than improvising a permanent change.

• “Is there an immediate concern that needs escalation before work continues?”
• “Please describe the specific issue through the appropriate private channel.”
• “The responsible lead will assess the request and any interim arrangement.”
• “I cannot confirm a permanent change before that review.”

What to do when communication is the reason for the change request

Identify the expectation that was missed. Different response habits, unclear instructions, and fragmented channels can damage confidence even when the technical work is sound. A new person may help, but the process also needs attention.

5. What to do when a client says the team member does not reply

Review the actual communication record and agreed response expectations. Ask which unanswered decision or request is blocking progress. Avoid defending the team member automatically or accepting a broad claim without checking the relevant facts.

Address the pending project issue and explain the next response point. If coverage is inadequate, assess a backup or different contact. For wider silence problems, see what to do when a client stops replying, while keeping responsibility for the provider’s own communication separate.

• “Which request is still awaiting a response?”
• “We will check it against the communication arrangement for this project.”
• “The immediate next step is resolving the outstanding decision.”
• “If coverage needs to change, the project lead will confirm the appropriate contact.”

6. What to do when a client finds the communication too technical

Ask which explanations were hard to use and what level of detail would help. A technically accurate answer can still fail if it does not support the client’s decision. Avoid suggesting that the client is at fault for not understanding specialist language.

Try a clearer summary or a different meeting format before assuming a personnel change is necessary. If a separate client-facing contact is available and useful, assess that arrangement. The technical role and communication role can differ, but responsibilities must remain clear.

• “Which part of the explanation did not make the next decision clear?”
• “We can provide a plain-language summary with the key trade-off.”
• “A different review format may help the conversation.”
• “If a separate contact is appropriate, we will confirm that role explicitly.”

7. What to do when a client feels their feedback is ignored

Compare the submitted feedback with the implemented version and response notes. Determine whether comments were missed, misunderstood, or intentionally not applied for a stated reason. Do not treat every unimplemented preference as either an error or an unreasonable demand.

Explain the status of each relevant point and correct genuine omissions. If the problem is a fragmented review process, consolidate the instructions. The guide on contradictory client feedback helps when several instructions conflict. Assess the staffing request alongside the actual workflow issue.

• “Let us compare the submitted comments with the latest version.”
• “These points were implemented; these need clarification or correction.”
• “Any decision not to apply a comment should have a clear explanation.”
• “We will assess the contact arrangement after identifying the underlying issue.”

8. What to do when a client dislikes the meeting style

Ask what would make meetings more useful: a written agenda, shorter discussion, advance materials, or a decision summary. A mismatch in meeting style may be resolved without changing the person responsible for the work.

Offer a practical adjustment and a checkpoint to assess whether it helps. Do not make the client repeat an ineffective format indefinitely while the concern is dismissed. If a different facilitator is available, explain that role without obscuring who remains responsible for delivery.

• “Would an agenda and advance questions make the review more useful?”
• “We can keep the meeting focused on the decisions needed.”
• “A written summary will record the agreed next steps.”
• “If a different facilitator is appropriate, we will clarify that arrangement.”

What to do when the client questions skills or delivery quality

Assess the specific work and requirement. A concern about capability should be examined through the project evidence, not dismissed as personal criticism or accepted solely because the client prefers a different name on the team.

9. What to do when a client says the assigned person lacks experience

Ask which project requirement is not being met and review the relevant work. The client may have identified a genuine gap or may be reacting to limited information about the person’s role. Avoid disclosing private employment history or making unsupported claims about competence.

Explain the capability available to the project and assess whether additional review or specialist support is needed. A staffing decision should address the actual requirement. Do not promise a more senior title as a substitute for clarifying the work and responsibility.

• “Which requirement is not being met by the current arrangement?”
• “We will review the relevant deliverable and support available.”
• “Additional specialist review may be appropriate if a gap is confirmed.”
• “The response should address the project need rather than a title alone.”

10. What to do when a client requests a specialist for one part of the project

Define the task needing specialist capability and assess whether it can be supported without replacing the whole team. A focused review or separate workstream may solve the problem more effectively than a complete handover.

Confirm availability and responsibilities before promising the specialist’s involvement. Explain what the existing team member will continue to handle and who approves the specialist output. For capabilities not currently offered, use the guide to an unsupported service request.

• “Which part of the project requires the additional specialist capability?”
• “We can assess a focused role rather than assume a complete replacement.”
• “Availability and responsibilities need confirmation first.”
• “The updated plan will identify who delivers and approves each part.”

11. What to do when a client loses confidence after an error

Acknowledge the specific error and explain how it is being corrected. A personnel change does not by itself repair the deliverable or prevent the same process failure. Identify the relevant checking or communication improvement as well.

Ask what reassurance the client needs for the next stage. Additional review or a different contact may be useful, but assess those options rather than promising a change immediately. Avoid exposing internal disciplinary discussions. The client needs an accurate recovery plan and accountable delivery.

• “The error needs correction regardless of the staffing decision.”
• “We will explain the check being added to the next delivery.”
• “What would help restore confidence in the remaining work?”
• “The project lead will assess any change to the contact or review arrangement.”

12. What to do when a client rejects the work and asks for another creator

Compare the delivered work with the brief and identify the mismatch. The concern may be a missed requirement, an unclear direction, or a subjective preference. Do not replace the creator before understanding what the next person would need to do differently.

Explain the correction or revised direction and assess whether a different assignment is appropriate. Use what to do when a client dislikes the first draft for the detailed feedback process. A new person should receive a clearer target, not the same unresolved brief.

• “Let us identify what the current work is missing against the brief.”
• “The next version needs a clear direction regardless of who produces it.”
• “We will assess whether a different assignment would address that need.”
• “The revised brief should be confirmed before another full draft begins.”

What to do when availability or workload drives the request

Check the actual coverage needed and available capacity. Do not promise an immediate replacement before confirming that the proposed arrangement can support the project. A handover also takes time and needs planning.

13. What to do when a client needs coverage while the assigned person is away

Explain the confirmed coverage arrangement and the tasks that remain active. Keep personal reasons for absence private. Ask which decisions or deliverables require attention during the period so support can be matched to the actual need.

If no full replacement is available, state what can be covered and discuss the remaining schedule. Do not imply that a backup contact has the same role or authority unless confirmed. The client should know who handles messages, who can make decisions, and what work can proceed.

• “This is the confirmed project contact during the absence.”
• “Which decisions need attention before the usual contact returns?”
• “The backup role covers these tasks and approvals.”
• “Any uncovered work needs a separate timing discussion.”

14. What to do when a client wants someone available in a different time zone

Ask whether the need is for live meetings, faster responses, or continuous support. A time-zone difference may be managed through a clear asynchronous process, but some projects need genuine overlapping availability.

Assess the available team arrangement without promising constant access. Explain whether a different contact, scheduled overlap, or another service model is feasible. For communication expectations, see handling client contact outside business hours. A staffing change should support a defined coverage need.

• “Which tasks require live overlap rather than written updates?”
• “We will assess the available coverage for those periods.”
• “A different contact may help, but continuous support is a separate requirement.”
• “The agreed availability will be stated with the relevant time zone.”

15. What to do when a client believes the team member is overloaded

Ask which project effects the client has noticed, such as missed updates or delayed deliverables. Review those facts without discussing private workload details from other clients. The concern is whether this project is receiving the agreed service.

Explain the recovery or coverage plan where a gap is confirmed. Additional support may be appropriate, but do not promise a replacement solely to avoid discussing a schedule problem. Keep the next checkpoint realistic and make responsibility clear.

• “Which missed update or deliverable is causing concern?”
• “We will review this project’s commitments and coverage.”
• “If additional support is needed, the lead will confirm the arrangement.”
• “The next update will state the responsible contact and realistic delivery point.”

16. What to do when a replacement would delay delivery

Explain the handover steps and the effect on remaining work. A new person may need to review decisions, files, and unresolved issues before producing reliable output. Do not describe that preparation as unnecessary delay or hide it to make the change sound easy.

Offer the feasible options, such as temporary support, a staged handover, or a revised date. Let the client understand the trade-off between continuity and the requested change. For broader timing pressure, use the guide to an earlier delivery request.

• “A replacement needs time to review the current project and decisions.”
• “That preparation affects the remaining delivery plan.”
• “We can assess temporary support or a staged handover.”
• “Please consider the timing trade-off before the arrangement is finalized.”

What to do when the request involves sensitive or inappropriate reasons

Keep the conversation private, factual, and focused on legitimate service needs. Serious conduct concerns and discriminatory requests require the appropriate organizational process. Do not improvise personnel decisions or disclose private information to satisfy a client.

17. What to do when a client gives a personal reason unrelated to the work

Ask whether there is a specific service issue that needs attention. A personal preference does not automatically justify replacing a team member. Avoid inviting unnecessary private information or making assumptions about either person’s motives.

Use the organization’s appropriate process to assess the request fairly. Explain the available project response without disclosing internal personnel discussions. If the issue can be addressed through communication or role clarity, consider that route before treating a personal mismatch as a delivery failure.

• “Is there a specific service issue affecting the project?”
• “We need to assess the request through the appropriate process.”
• “The response will focus on the work and legitimate project requirements.”
• “Private personnel matters will not be discussed in the client conversation.”

18. What to do when a client requests a change on discriminatory grounds

Do not automatically grant the request or repeat the client’s discriminatory rationale as an accepted project requirement. Record the relevant concern through the appropriate private process and involve the responsible lead. Keep the immediate interaction professional and avoid escalating abusive language.

Assess any legitimate service need separately, such as a required language capability or accessibility arrangement. Do not use that assessment to disguise an inappropriate request. Applicable obligations and personnel decisions may require qualified advice; the client conversation should not invent a legal conclusion.

• “We can discuss specific service and communication requirements.”
• “We cannot treat that personal characteristic as an accepted project-selection criterion.”
• “The request needs review through the appropriate organizational process.”
• “Any legitimate capability need will be assessed separately.”

19. What to do when a client reports harassment or serious misconduct

Provide an appropriate private reporting route and take the concern seriously. Ask for the information needed by the responsible process without conducting an improvised public investigation. Do not promise confidentiality beyond what can actually be provided or guarantee a particular outcome.

Follow the organization’s process for any immediate protective or contact arrangement. Keep the client informed about the next procedural step where appropriate, while preserving privacy and fairness. A general project guide cannot determine whether an allegation is established or what personnel action should follow.

• “This concern should be raised through the designated private reporting route.”
• “The responsible team will explain the information needed and next steps.”
• “Any immediate contact arrangement will be assessed through that process.”
• “I cannot promise a particular outcome before the concern is reviewed.”

20. What to do when a client asks for private details about the team member

Explain that private personnel information is not part of the project update. Provide the service information the client needs, such as current responsibilities, coverage, and the next contact. Do not disclose health, employment, disciplinary, or other personal details to justify a change.

If the client has a legitimate question about qualifications relevant to the service, route it through the appropriate public or authorized information. Keep that distinct from private records. The practical outcome is confidence about project delivery without unnecessary disclosure.

• “I can explain the project coverage and responsibilities.”
• “Private personnel details are not part of the client update.”
• “Relevant service qualifications can be addressed through the appropriate information.”
• “The next delivery contact and checkpoint will be confirmed clearly.”

What to do when a staffing change needs approval or negotiation

Clarify what the client can request and who makes the assignment decision. Do not confuse a request for a different contact with authority to direct internal employment matters. Keep the commercial project arrangement separate from private personnel processes.

21. What to do when the client asks for a specific senior person

Ask what capability or responsibility the client expects that person to provide. The request may be for reassurance, a decision-maker, or specialist review rather than daily involvement. Assess the appropriate role before promising access.

Check availability and the actual service arrangement. If the named person cannot take the role, explain a suitable alternative where one exists. Avoid implying that a senior title guarantees a better result. The proposed arrangement should address the identified project need.

• “What role would you want that person to play in the project?”
• “A focused review may address the concern without changing daily delivery.”
• “Availability and scope need confirmation before any commitment.”
• “We will explain the appropriate alternative if that assignment is unavailable.”

22. What to do when the requested replacement is not available

State the availability limit and describe the options that can genuinely be assessed. Do not promise to find someone immediately or name an unconfirmed replacement. Explain whether the existing arrangement can be supported while a decision is made.

Ask which priority matters most: a particular capability, continuity, timing, or a different contact style. That can guide the next option. If no suitable arrangement exists, discuss the project status openly through the actual agreement rather than leaving the client waiting indefinitely.

• “The requested person is not available for this assignment.”
• “We can assess these confirmed support or handover options.”
• “Which requirement should guide the alternative?”
• “If none fits, we need to discuss the project’s next state clearly.”

23. What to do when a client expects a staffing change at no additional cost

Review the actual service commitment and reason for the change. A provider’s need to correct inadequate coverage differs from a client-requested expansion of the role. Do not assume that every change is chargeable or that every requested arrangement is included.

Explain any proposed scope or timing effect before seeking approval. Keep private employment costs out of the discussion unless genuinely relevant and appropriate. If the arrangement changes the service, document it clearly rather than surprising the client after the handover.

• “We need to assess the change against the service already agreed.”
• “Correcting a coverage gap is different from adding a broader role.”
• “Any proposed change to the scope or terms will be explained first.”
• “No additional arrangement should be assumed before it is confirmed.”

24. What to do when a client threatens to leave unless the person is replaced

Clarify the unresolved issue and the decision the client needs. Take the commercial concern seriously without promising an inappropriate personnel outcome under pressure. Explain the review process and the available project options.

If the request cannot be met, state that clearly and discuss the engagement’s next steps under the actual agreement. Avoid threats, invented penalties, or a public argument about the team member. The goal is an informed project decision, even if the relationship cannot continue in its current form.

• “I understand that this issue affects the decision to continue.”
• “We still need to assess the request through the appropriate process.”
• “These are the project arrangements that can be offered.”
• “If none is suitable, we should discuss the next steps under the existing agreement.”

What to do when a handover is agreed

Make the transition concrete. The new person needs the current brief, decisions, files, unresolved issues, and a clear role. A handover should reduce the client’s coordination burden rather than make them rebuild the project history.

25. What to do when the client wants the handover immediately

Explain the minimum preparation needed for a reliable transition. Identify urgent tasks separately from the full transfer. A new contact can sometimes be introduced quickly while detailed production handover continues, but that arrangement needs clear limits.

Do not promise instant continuity if the replacement has not reviewed the work. State who handles each task during the transition and when the new arrangement becomes effective. The client should not receive conflicting instructions from two people both appearing to lead the project.

• “We can separate the immediate contact change from the full production handover.”
• “The new lead needs to review the current decisions and files.”
• “During the transition, these tasks remain with the existing contact.”
• “The effective handover point will be confirmed explicitly.”

26. What to do when the new person needs the project history

Prepare a concise record of the approved brief, latest version, key decisions, and outstanding questions. Link to the relevant authorized files rather than forwarding every message indiscriminately. Keep private personnel discussions out of the project handover.

Ask the incoming person to identify any gaps before the first client review. The client may need to confirm a decision, but should not have to repeat information already recorded. Use the guide to incomplete materials when essential source files are missing.

• “The handover includes the current brief, version, and decision record.”
• “Only relevant authorized project information will be transferred.”
• “The incoming lead will identify any remaining gaps before the review.”
• “The client will only be asked to clarify genuinely unresolved points.”

27. What to do when responsibilities overlap during the transition

Name the owner of each active task and the person authorized to confirm changes. A temporary overlap can support continuity, but unclear ownership creates duplicate work and inconsistent messages. Do not rely on the client to resolve internal responsibility questions.

Use one agreed route for consolidated updates. Explain which person is the main contact and when that changes. Keep the arrangement simple enough to follow, especially if only a small part of the project is transferring. Review the overlap once the handover is complete.

• “These tasks remain with the current team member until the stated checkpoint.”
• “The incoming lead owns the next review and subsequent delivery.”
• “Client updates will come through one confirmed contact.”
• “The temporary overlap will end once the handover is complete.”

28. What to do when the new person disagrees with earlier project decisions

Ask the incoming person to identify whether the concern is a factual error, a missed requirement, or a preference for a different approach. A handover is not automatic permission to restart approved work. Evaluate the concern against the current brief.

If a change is necessary, explain it to the client with its impact before implementation. If it is merely a different preference, preserve the agreed direction unless an appropriate revision is approved. Avoid undermining the previous team member through unnecessary criticism.

• “Is the concern a requirement issue or a different preferred approach?”
• “The approved direction remains the reference for the handover.”
• “Any necessary change will be explained with its scope and timing effect.”
• “We will not restart agreed work solely because the project has a new lead.”

What to do after the staffing decision

Check whether the original service concern has actually improved. A change of person is a means to a working project arrangement, not proof that every issue is resolved. Keep the next review focused on observable delivery and communication.

29. What to do when the client is happy with the replacement

Confirm the new contact and responsibilities, then return the project to its normal workflow. Avoid repeatedly discussing the previous team member or asking the client to justify the preference. The useful evidence is whether communication and delivery now meet the agreed expectations.

Keep the handover record and any unresolved work visible. A positive first interaction does not automatically approve pending deliverables. Ask for the next project decision in the usual process and close the transition when the necessary tasks are complete.

• “The new contact and responsibilities are now confirmed.”
• “The remaining project decisions are listed in the current review summary.”
• “We will use the normal approval process from this point.”
• “The transition can close once the outstanding handover items are complete.”

30. What to do when the same problem continues with the replacement

Revisit the underlying requirement and process. Repeated dissatisfaction may reflect an unclear brief, conflicting reviewers, unrealistic coverage expectations, or a service gap that a personnel change did not address. Do not assume the client is simply impossible to satisfy.

Compare the observed issue with the agreed improvement and identify the next corrective action. Another replacement should not be the automatic response. If the project goal or scope needs resetting, use what to do when a client changes the brief.

• “The same concern appears to remain after the handover.”
• “Let us compare it with the improvement we agreed to achieve.”
• “The process or scope may need adjustment beyond changing the contact.”
• “We should identify that cause before considering another replacement.”

31. What to do when the request is declined

Explain the project decision and available alternatives without revealing private personnel details. State what will be done to address any legitimate service issue. A declined staffing request should not mean the underlying concern is ignored.

Ask whether the offered arrangement meets the client’s needs and discuss next steps under the actual agreement if it does not. Keep the tone respectful and avoid presenting the decision as a personal victory for the team member. The client needs an accurate route forward.

• “The requested staffing change is not being offered.”
• “The service concern will be addressed through the support arrangement described here.”
• “Private personnel matters are not part of the project explanation.”
• “If this arrangement does not meet the need, we should discuss the appropriate next step.”

32. What to do when the client keeps requesting new people without a clear reason

Ask for a specific project requirement and review the pattern through the responsible lead. Repeated changes can disrupt continuity, but that does not remove the need to assess each substantive concern fairly. Do not label the client difficult as a substitute for understanding the issue.

Define the service and decision process that can be offered. If no workable arrangement can be agreed, discuss the engagement’s future under the actual terms. Avoid endless handovers without a clear improvement target or unauthorized promises about personnel assignments.

• “We need a specific service requirement to assess the next change request.”
• “Repeated handovers are affecting continuity and need a clearer purpose.”
• “The project lead will review the available arrangement.”
• “If no suitable process can be agreed, we should discuss the engagement’s next stage.”

What to avoid when a client requests another team member

Do not promise a replacement before checking the reason, authority, and availability. Do not disclose private staff information, assume allegations are proven, or grant an inappropriate request without the relevant review. Keep immediate service corrections separate from personnel decisions.

Avoid making the client repeat the whole project during a handover. Do not let a new lead silently overturn approved work or treat a staffing change as proof that the original problem has disappeared. Confirm responsibilities and assess whether the agreed improvement is actually happening.

Frequently asked questions about changing the person on a client project

What to do when a client asks for a different contact but the same production team?

Clarify the communication role and assess whether that arrangement is available. A different contact can help coordination without changing who creates the work. Confirm who consolidates feedback, who makes delivery decisions, and how messages reach the production team. Avoid adding a relay that creates more delay or ambiguity.

What to do when a client asks whether a replacement will be more senior?

Explain the capability and responsibility required for the project. A title alone does not establish fit. Assess the available role and any specialist review needed, then describe that arrangement accurately. Do not promise a senior person’s involvement before availability and scope are confirmed.

What to do when a client asks why the previous person left the project?

Provide the project information needed for continuity, such as the new contact and handover status. Do not disclose private employment, health, or disciplinary details. If the client raised a service concern, explain the appropriate project response without presenting confidential internal discussions as part of the update.

What to do when a client asks to interview several possible replacements?

Assess whether that selection process fits the service and is available. Clarify the legitimate capability criteria and the role being discussed. Do not promise access to staff or private information without the appropriate authorization. A focused introduction or capability summary may be more suitable than an open-ended selection process.

What to do when a client asks for a replacement after the work is almost complete?

Identify the unresolved issue and assess whether a focused review or contact change would address it. Explain the impact of a full handover on checking and delivery. Do not force a complete restart or dismiss the concern solely because the project is near completion. Confirm the smallest appropriate response that meets the actual need.

Sources for sensitive staffing and complaint issues

The U.S. EEOC explains that covered employment decisions must not be based on discriminatory grounds; its national-origin guidance specifically addresses discriminatory customer preferences. These are U.S. sources, not universal rules for every jurisdiction. See EEOC prohibited employment practices and EEOC national-origin guidance.

Acas guidance for Great Britain advises taking bullying or discrimination complaints seriously and using an appropriate process. Its formal-complaint guidance discusses a neutral investigator. These references support escalating serious concerns rather than improvising a staffing outcome: Acas handling complaints and Acas formal complaints. Checked September 15, 2026. Apply the relevant local rules and qualified advice to an actual personnel matter.