Conflict Resolution Checklist

Capture date, time, store number, shift, associates involved, and any customer or witness names. Use the store closing log format so the incident ties back to the same Z-report and shift the conflict occurred on.

Associate-vs-associate (scheduling, sweethearting accusation, shift coverage) and associate-vs-customer (refund dispute, age-restricted sale, accessibility complaint) follow different escalation paths. Harassment, discrimination, threats, or theft accusations route to HR/LP immediately and bypass peer mediation.

Harassment, discrimination, or threats trigger the HR hotline same-day. Do not attempt to mediate between the parties yourself — that can compromise the investigation and create personal liability. Preserve any CCTV from the incident before the retention window rolls.

Sweethearting accusations, refund-fraud disputes, or shrink-related conflicts route to the LP officer or district LP manager. Pull the relevant POS exception report (post-voids, manual refunds, no-sales by cashier) before the conversation.

Meet in the back office, not on the sales floor. Ask open-ended questions: what happened, who was present, what they want as an outcome. Take dated notes in the manager's day-book — these become the record if the conflict later goes to HR or unemployment review.

For refund or transaction disputes, run the cashier's transaction log and any exception report covering the shift. For incidents on the floor, request CCTV review from LP before the standard 30/60/90-day retention window expires.

Block the meeting for a low-traffic window so the floor stays covered — typically mid-morning weekday or right after open. Predictive-scheduling jurisdictions require advance notice for adding hours, so post the meeting time inside the standing schedule.

Each party states their version uninterrupted, then summarizes the other's account back. This active-listening step catches the misunderstandings that drive most floor conflicts (who was on register vs. floor, who owned the planogram reset, who took the refund call).

Capture candidate fixes: revised refund-approval threshold at the POS, clearer drawer-assignment SOP, planogram reset paired with a stock associate, shift-swap rule requiring 24-hour notice. Write them on the whiteboard so the discussion is about systems, not blame.

If the resolution changes refund authority, drawer floats, planogram cadence, or shift-swap rules, edit the SOP and post it in the back office. Email the change to the team and ask each associate to acknowledge in writing on the next shift huddle.

If the joint session ended at "No" or "Partial," the district manager owns next steps — formal write-up, transfer to a sister store, performance improvement plan, or termination per the employee handbook. Forward the day-book notes and evidence file.

One week after the resolution, meet briefly with each party on shift to confirm the behavior change is sticking and the SOP update is being followed. Most relapses show up in week one — drawer-count variances, missed refund approvals, or a re-flare in the same scheduling dispute.

Save the summary to the associate's personnel file and the store-ops shared drive. Note the conflict type, resolution, and SOP change so the next store manager has the context if a similar incident recurs.

If the underlying issue likely affects other stores (POS refund threshold too low, planogram reset under-staffed, shift-swap policy unclear), submit it as a district-level change request. Patterns across stores are how SOPs get rewritten.