Investigate a reported pay discrepancy with a clear fact trail
Gather timesheet and assignment facts before responding to a pay concern.
When a worker reports pay below an expected amount, a client success manager should begin with a clear fact trail. A fast response based on one account risks confusion for the worker, payroll team, site supervisor, and client contact. The first conversation has a narrower purpose. Learn which pay period and shift prompted concern, explain what review will happen, and name a time for an update. Respectful listening matters, yet reassurance without records does not resolve a discrepancy.
Open a case note during or soon after the conversation. Record the worker’s name or case identifier according to local practice, contact date and time, pay period, shift date, reported difference, assignment location, and documents already provided. Quote key words when practical. “Friday hours look short” differs from “My rate looks different.” Do not convert either statement into a finding. A case note should show what the worker reported, which records need review, who owns each check, and when a status update is due.
Ask focused questions so the worker need not repeat a long story. “Which Friday shift are you referring to?” “What hours do you expect?” “Did you submit a correction through your supervisor?” “Have you received a response from anyone else?” These questions establish a starting point. Avoid personal details unrelated to time, rate, assignment, or approval records. A worker deserves an explanation of next steps instead of a request to solve an internal record problem without help.
The assignment record often supplies one part of the picture. Confirm assignment start date, stated rate, expected schedule, site or department, and any recorded change request. Then compare those details with the relevant time entry. Look for date, clock in time, clock out time, break entry when present, approval status, and later edits. A difference between an assignment record and a time entry does not prove an error. Each source answers a different question. One describes agreed assignment terms. The other describes submitted work time.
Payroll records add a separate source. Review the pay period attached to the concern, pay date, hours or units recorded, rate used, and adjustment notes. If a source contains unclear shorthand, do not guess. Ask payroll for a plain explanation suited to a worker update. Client success managers coordinate facts and communication. Payroll staff own payroll review. Site supervisors own confirmation of local time records. A CSM should name those owners rather than speaking beyond available records.
A fictional example shows a clean first response. Andre calls CSM Keiko and says, “My Friday hours look short.” Keiko replies, “I will review the Friday time entry and assignment record. Which Friday do you mean, and did you submit a correction to your supervisor?” Andre says this marks his first report. Keiko continues, “I will ask payroll to review the record and ask your site supervisor to confirm clock out time. I will send an update by 3 p.m. tomorrow, even if review is still underway.” Andre knows which records Keiko will check and when contact will resume.
Keiko writes a short case note. “Worker reports short Friday hours for August 14. Worker states no correction submitted. Assignment record and time entry await review. Payroll owner: Ren. Supervisor confirmation owner: Lila. Worker update due August 18 at 3 p.m.” The note separates a report from evidence. Suppose the time entry shows eight hours, while supervisor approval shows seven and a half. Keiko does not tell Andre which number will control. She asks Lila whether a time correction exists and asks Ren whether payroll received a revised record before processing.
Timing deserves its own review. A worker who hears nothing after a promised update has a new service problem even when payroll review needs more time. Set a realistic update time based on record access and owner availability. If one fact remains unavailable, send a status note at the agreed time. State which documents received review, what remains open, who has the next action, and when another update will arrive. Do not describe an adjustment as complete until the responsible team confirms completion. Precision supports trust more reliably than a hopeful estimate.
Communication with a client contact needs a narrow scope. A site supervisor often needs shift date, submitted hours, approval record, and location. Such a person does not need unrelated pay history or broad personal details. Ask a direct operational question: “Please confirm whether your record shows an August 14 clock out at 4:30 p.m. and whether any correction was submitted.” This request gives the supervisor a defined task. Keep payroll amounts and worker discussion within the internal review path unless an authorized owner asks for more detail.
Conflicting records need an organized response. In a fictional practice situation, an assignment confirmation lists an hourly rate, a timesheet lists one number of hours, supervisor approval lists another, and payroll notes an adjustment request with no completion date. First, label every record by source and date. Next, identify which source needs clarification. Then ask one owner a question tied to one record. “Ren, does the adjustment note show a processed change or a pending request?” “Lila, which submitted time record supports your approval?” One question at a time reduces crossed messages and undocumented assumptions.
Some cases reveal a missing document. Say a supervisor approval record has not reached the case file. Tell the worker which information still needs review and who received a request. Avoid claiming a payment error or blaming a supervisor. A useful update sounds like this: “We reviewed your assignment and submitted time entry. We await supervisor confirmation for the August 14 shift. Lila received a request. I will contact you by 10 a.m. Tuesday with an update.” The worker receives a clear time and named owner without false certainty.
Close a case after the designated owner confirms the outcome and the worker receives an explanation suited to available facts. The final case note should include reviewed sources, decision owner, completed action or remaining route, worker contact date, and any promised next contact. Do not add judgments about motive or fault. A concise record supports later review if similar reports appear. Repeated reports from one site or shift deserve separate analysis, yet each worker report still needs its own evidence trail.
For a fictional desk exercise, arrange an assignment confirmation, a timesheet, a supervisor approval, and a payroll note. Remove one document before beginning. Ask a teammate to play the worker and report a short Friday shift. Start a case note with period, shift date, reported concern, assigned owners, and update time. After your teammate identifies a missing record, say which owner will receive a request and state an exact update time. At 2 p.m., send the worker a message using only facts present in the exercise, then place the requested record beside the case note.
Practice these next
Respond to a reported site concern with immediate factual escalation and respectful communication.
A client success manager gathers job related feedback, protects privacy, and creates a fair response path after an assignment concern.
A client success manager investigates missed starts with grouped facts, clear owners, and respectful candidate privacy.
Address a supervisor concern with job related and respectful worker feedback.
Client success managers turn uncertain volume forecasts into shared operating reviews with assumptions and owners.
Transfer account knowledge through an agreed service map and limited access to private details.