Respond when a client asks staffing to solve attrition

When an operations leader asks a staffing partner to solve attrition, start with a shared review of the early work experience. Recruiting influences who enters an assignment. Attrition also reflects schedules, supervisor contact, training space, transportation, job expectations, and changes after acceptance. A quick promise to supply more applicants risks repeating the same departure pattern with a larger group.

The first goal is not a diagnosis from one call. The goal is a clear question. Ask where departures cluster, when people leave, and what changed around those points. An executive who says, "We are losing people," might mean open shifts, missed production, training disruption, or frustrated supervisors. Each concern calls for different evidence. A useful conversation makes those differences visible before anyone selects a response.

Use the client leader's own timing words. If she says employees leave during their first ninety days, ask whether exits rise after orientation, after a schedule change, or after a supervisor handoff. Ask whether one location or one shift sees more exits than others. Narrow questions give people a place to look. Broad questions often produce long stories with no shared next action.

Consider this fictional practice situation. Nia leads operations for a billing group facing a busy period. She tells Owen, her staffing account executive, "New hires keep leaving before ninety days. We need better retention before the next billing cycle." Owen replies, "I want to understand where the early experience changes. What do grouped exit themes, attendance records, and training dates show?" Nia says schedule changes appear more often than pay in supervisor notes. Her team runs one class each month, and supervisors sometimes move people before training ends.

Owen does not answer with a sourcing promise. He says, "A short review with training and operations would help separate schedule pressure from intake expectations. Please bring class dates, planned schedules, and interview messages." Nia agrees. Owen asks each attendee for fifteen minutes of preparation and schedules a meeting after she identifies record owners. He has given urgency a place to go without claiming a cause.

Preparation matters because attrition talk often becomes a search for one person to blame. Request grouped information rather than personal stories. Ask for departure timing by class or location, recurring exit themes, training dates, expected start dates, attendance patterns, and first month schedule changes. Ask how recruiters describe hours, location, supervisor contact, training attendance, and schedule flexibility. Names and private details add little when the question concerns a pattern.

Explain how missing records will be handled. Owen might say, "Where records are incomplete, we will mark an open question instead of filling gaps with a guess." Such language reduces pressure to produce a polished answer. People then have permission to distinguish observed facts from assumptions. A meeting built from one memorable story often ends with a weak plan because no one checks whether the story represents the wider group.

In the fictional example, Nia's group identifies twelve departures from a class of forty. Eight happened after an evening assignment moved to a weekend rotation. Those numbers deserve attention, yet they do not establish a reason for every exit. The group needs to ask whether every affected worker received a change, whether interviews mentioned weekend work, and whether supervisors explained the revision before day one. One manager might report an urgent coverage need. The training lead might report unused seats after start dates shifted. Both details shape a response.

Keep observations separate from explanations. Owen says, "We know eight departures followed a rotation change. We do not know whether notice, travel time, supervisor contact, or another factor drove each decision." Then he asks who owns each missing record and when a grouped view will be ready. This approach avoids a premature finding and prevents recruiting from inheriting an issue outside its control.

Ask the group to leave with decisions rather than a complaint inventory. Interview language is one decision area. If recruiters describe schedules as stable while operations expects frequent rotations, both teams need accurate wording for future conversations. Training intake is another area. A monthly class might create a queue, leaving leaders to decide whether start dates, class size, or manager coverage need attention. Record every decision owner, source material, and follow up date while everyone is present.

Staffing support still has a practical role after the review. Recruiters might ask candidates about availability against known shift windows. They might explain rotation expectations before acceptance. An account executive might coordinate start dates with confirmed class capacity. Present each adjustment as a response to shared evidence, not as an assurance about attrition. When schedule details remain unsettled, candid language helps candidates assess an assignment with fewer surprises.

Do not let a request for more people hide a capacity problem. More applicants do not resolve a full classroom, a missing trainer, or a supervisor with no time for first day questions. Raise those conditions plainly. Ask the client leader whether each condition belongs in the near term plan, then note who will decide. Staffing teams do useful work when they surface delivery constraints early rather than treating every empty shift as a recruiting gap.

The meeting also benefits from a time boundary. Reserve thirty minutes. Spend the first ten on patterns and dates, the next ten on open questions, and the final ten on decisions. A participant who raises a separate concern should receive a note in the record, along with an owner for later review. This keeps a schedule question from consuming time needed for training evidence or vice versa.

If the group reaches conflicting accounts, do not force agreement in the room. A supervisor might say weekend assignments were announced during interviews. A recruiter might say approved interview language described weekday availability. Record both statements with sources. Ask for the relevant script and schedule record. A later answer grounded in records serves everyone better than a quick compromise built from uncertain memory.

Follow up in plain language. Owen's fictional note might say, "Nia will share grouped departure timing and class dates by Tuesday. The training lead will confirm class capacity by Wednesday. Operations will provide the rotation change dates. We will meet Thursday at 2 p.m. to decide which interview and start date changes belong in the next class." Each sentence names an action, an owner, or a date. None implies a retention outcome.

Use this fictional rehearsal before a client review. A warehouse leader reports eighteen departures across six weeks and requests fifty new workers. During a first call, you learn all eighteen started in two classes, one trainer left during the second class, and several assignments changed after orientation. Say, "Before we discuss volume, I would like a thirty minute review of class coverage, assignment changes, and interview messages. Who should join from training and operations?" Then draft a Thursday 2 p.m. invitation naming those records. Send your draft to the meeting owner for confirmation of attendance and source availability.