Module 3: Weekly Counts, Coaching, Client-Book Review

Why This Module Matters

Daily routines keep a store safe and functioning; weekly routines are where a store leader actually steers it. A week is long enough to see real patterns in sales, inventory, and client relationships that a single day can’t reveal, and short enough that problems get caught while they’re still small. This module covers the three weekly disciplines that matter most: a fixed-slot business review, a real cycle-count rhythm, and active oversight of how the team is actually building client relationships — not just logging contact information.

The Weekly Business Review: Same Slot, Same Five Reports, Every Time

A specific, published weekly-review model calls for a fixed time slot — the same day and time every week, ideally Monday morning — running through five specific reports in the same sequence each time, completed in under fifteen minutes when nothing unusual surfaces: weekly turnover split between product sales and gift-card redemptions, compared against the same week last year and the previous four weeks; net profit margin for that same period; repairs completed, open-within-deadline, and overdue; customer purchases and old-gold acquisitions, specifically to identify which customers are worth a proactive follow-up; and top sellers and slow movers, by product, category, seller, and date range. The value of this specific structure — same slot, same five reports, same order — isn’t the individual numbers themselves; it’s that a fixed review habit surfaces a real problem within a week of it starting, rather than a month or a quarter later when it’s harder to reverse.

Weekly Cycle Counts: The Alternative to the Annual Big-Bang Count

Trade guidance is direct that annual-only inventory counting is inadequate for a category with this much value concentrated in a small physical footprint — the recommended alternative is regular, weekly-to-monthly inventory control instead. A specific, published cycle-count model: count one category each week, so the entire store gets counted by year-end, and any errors get caught as they happen rather than surfacing all at once during one stressful annual count. This weekly cadence should be supplemented, not replaced, by frequent case counts and truly random, unscheduled spot-checks of specific SKUs in back stock — the specific reasoning being that an employee who knows exactly when a scheduled count will happen has time to prepare for it, which defeats part of the count’s actual purpose. When a discrepancy does turn up, the correct sequence is: recount first, check whether the piece is actually in a repair box or out on approval with a client, check recent sales around that item number for a possible scan error, and only as a genuine last resort write it off as a loss. The broader cultural point matters as much as the mechanical steps: don’t automatically assume every disappearance was a simple miscount, and investigate clusters of discrepancies quickly and thoroughly rather than writing them off individually.

The Weekly Team Meeting: Accountability, Not Just Announcements

A weekly team meeting serves a distinct purpose from the daily huddle — it’s where a store leader checks clienteling accountability (are associates actually honoring each client’s recorded contact preference, and are thank-you notes genuinely going out daily, not just when convenient), reviews repair take-ins and which jobs are due the next day, and runs a scheduled training topic as part of a broader weekly training calendar. This is also the natural moment to enforce the specific gratitude process this course’s broader clienteling research establishes: a dedicated store process for sending thank-you notes, with a real sending deadline and genuine accountability for whether it actually happened — not an assumption that it did.

Client-Book Review: Checking the Cadence, Not Just the Count

A widely used jewelry-specific clienteling cadence — often marketed as “2-2-2” — calls for a personal thank-you within 2 days of a purchase, a value-add check-in at 2 weeks (how the client is enjoying the piece, plus an invitation to a cleaning appointment, trunk show, or relevant event), and a next-purchase prompt at 2 months (new arrivals tailored to the client’s style, with specific pieces set aside for them). A weekly client-book review is where a store leader actually verifies this cadence is happening — not by asking “did everyone follow up this week” and accepting a yes, but by spot-checking specific client records against the cadence and following up directly with anyone who’s fallen behind. This same review is where a leader should be identifying which customers, based on that week’s purchase and old-gold-acquisition data, are actually worth a proactive contact this week, rather than leaving outreach entirely to individual associate initiative.

A Worked Scenario: The Discrepancy That Wasn’t Theft

During a scheduled weekly count of the diamond stud category, one pair doesn’t match the system record. Before writing anything off, the store leader runs the correct sequence: a recount confirms the discrepancy is real, a check of the repair log finds nothing, but a check of recent sales around that item number reveals a scanning error from three days earlier — the pair was sold correctly, but scanned under an adjacent item’s code. The system gets corrected, no loss actually occurred, and no associate gets wrongly suspected of anything. Skipping straight to “we’re missing a pair of diamond studs” and treating it as a security incident would have created exactly the kind of unnecessary anxiety and mistrust this careful, sequential discrepancy protocol is specifically designed to prevent.

Practice Exercise

Using your store’s actual client records, spot-check five recent purchases against the 2-2-2 cadence (or your store’s equivalent): were the 2-day thank-you, 2-week check-in, and 2-month next-purchase prompt actually sent, on time, for each one? For any gap you find, draft the specific outreach that should go out now to close it, and discuss with your team what changed in the process to prevent the same gap next time.

Key Takeaways

• A fixed-slot weekly business review — same day, same time, same five reports in the same order — surfaces real problems within a week of them starting, rather than a month or a quarter later when they’re harder to reverse.
• Weekly cycle counts (one category per week, supplemented by unscheduled spot-checks) catch inventory errors as they happen, which is specifically why annual-only counting is considered inadequate for this category.
• The correct sequence before declaring an inventory loss is recount, check repair/approval status, check recent sales for a scan error, and only then write it off — treating every disappearance as potential theft skips real, common, non-criminal explanations.
• The weekly team meeting checks clienteling accountability (are contact preferences actually being honored, are thank-you notes actually going out) and reviews the repair pipeline, distinct from the daily huddle’s day-to-day focus.
• A weekly client-book review means actively spot-checking the store’s clienteling cadence (like 2-2-2) against real client records, not simply assuming the team is following it because no one has reported otherwise.