The Weekly Operator Review Playbook

You have monitoring data coming in. Prices change, products launch, stores go down and come back up. The question is not whether you have enough data. The question is whether you are turning that data into decisions.

This playbook covers how to run a weekly competitive review that takes 30 minutes or less and produces clear, actionable takeaways. It is designed for operators who already have monitoring in place and want a structured process for making sense of what the data tells them.

Why Weekly, Not Daily

Daily reviews are reactive. You see a price drop, you react. You see a new product, you scramble. Daily cadence creates urgency where none exists and makes every change feel like it requires immediate action.

Weekly reviews are strategic. You see patterns instead of individual data points. You can assess whether a competitor's price change is a trend or a blip. You can batch your responses and make decisions with more context.

If something truly urgent happens, your alerts will tell you in real time. The weekly review is for everything else.

The 30-Minute Review Framework

Block 1: KPIs and Trends (5 minutes)

Start with the high-level numbers from your weekly report. (For a detailed breakdown of what each section means, see the weekly report reading guide.)

• Total changes across your competitive set. Is this week busier or quieter than usual?
• Price changes. How many products saw price movements? Net direction (more drops or more increases)?
• Catalog changes. How many new products appeared? How many were removed?
• Issues. Any stores down or showing monitoring problems?

You are looking for anomalies, not reviewing every data point. If total changes are within your normal range, move on. If they are unusually high or low, note it for investigation.

Block 2: Top Price Movers (10 minutes)

Review the biggest price drops and increases across your competitive set:

• Drops that affect your products. Is a competitor cutting prices on products you also sell? If so, by how much, and is it likely to persist?
• Increases that create opportunities. A competitor raising prices may create an opening for you to capture price-sensitive customers.
• Patterns across multiple products. Multiple products changing by the same percentage at the same retailer suggests a pricing policy change, not individual product decisions.

For each significant mover, decide: respond now, watch for another week, or ignore.

Block 3: New Products and Launches (10 minutes)

Review new products detected across your competitive set:

• Direct competitive threats. New products that overlap with your catalog. Note the price positioning and features.
• Category expansion signals. Competitors entering new categories may be testing or strategically expanding.
• Launch frequency trends. Is a competitor launching more or fewer products than usual?

The competitor launch tracking guide covers how to categorize and respond to different types of launches.

Block 4: Decisions and Actions (5 minutes)

End each review with concrete next steps. For each observation that matters:

• What did you see? One sentence describing the observation.
• What does it mean? Your interpretation of why this matters.
• What will you do? Specific action, or a decision to continue watching.

Write these down. A review without recorded decisions is wasted time.

Customizing Your Review

What to Include

The four blocks above cover the essentials. Depending on your business, you may also want to review:

• MAP compliance. If you track minimum advertised prices, include a MAP review block. The MAP and pricing policy guide covers this in detail.
• Anomaly alerts. Unusual patterns like sudden catalog drops or repeated site issues.
• Your own performance. Compare your pricing and catalog changes against the competitive landscape.

What to Exclude

Keep the weekly review focused. Push these to less frequent reviews:

• Store-by-store deep dives. Do these quarterly, not weekly.
• Historical trend analysis. Do this monthly using your accumulated weekly notes.
• Strategic planning. The weekly review feeds into strategy but is not the place to make major strategic decisions.

Making It Stick

Schedule It

Block 30 minutes on the same day each week. Most operators find Monday or Tuesday mornings effective because it sets context for the week ahead. Do not make it optional.

Use Your Weekly Report

Your monitoring tool's weekly report should be the primary input for your review. Configure the report to show the data you need in the order you review it. If your report does not surface the right information, adjust the settings. Configuring your report sections and thresholds ensures the report matches your review process.

Keep Notes

Maintain a simple log of your weekly review takeaways. Over time, this log becomes a valuable record of competitive moves and your responses. It also helps you identify whether your monitoring is capturing the right signals.

Iterate

Your first few weekly reviews will take longer than 30 minutes. That is fine. As you develop pattern recognition and refine your monitoring settings, the process gets faster. Revisit your alert thresholds and report configuration every few weeks to optimize signal-to-noise ratio.

Operator Checklist

• [ ] Block 30 minutes weekly on a consistent day (Monday or Tuesday recommended)
• [ ] Configure your weekly report to match the review framework order
• [ ] Set mover thresholds to surface meaningful price changes, not noise
• [ ] Review KPIs first, then movers, then launches, then decide
• [ ] Record at least 3 takeaways per review session
• [ ] Review your monitoring settings quarterly for signal-to-noise optimization
• [ ] Share relevant takeaways with your team within 24 hours of each review

Frequently Asked Questions

What if nothing significant happened this week? That is a valid takeaway. Note it and move on. Consistent quiet weeks may mean your competitive landscape is stable, or your thresholds need tightening to surface more subtle changes. For guidance on building weekly, monthly, and quarterly review cadences as a team, see the competitor reporting rhythm guide.

How many competitors should I track in my weekly review? Focus on 5 to 15 competitors. More than that dilutes attention. You can track more stores for alerting purposes, but your weekly review should focus on the stores that matter most.

What if I find something that needs immediate action during the review? Handle it or delegate it, but do not let it derail the rest of the review. Finish the review first, then address the urgent item. Incomplete reviews create blind spots.

Should I share the weekly review with my team? Yes, share the takeaways (not the raw data). A summary email with 3 to 5 bullet points keeps your team informed without requiring them to run their own reviews.

How does this relate to daily alert monitoring? Daily alerts handle urgent, time-sensitive events (site down, extreme price drops). The weekly review handles strategic patterns and decisions. They complement each other. Do not try to replace one with the other.

---

Bonesaw is a product of MoonsLink. Monitoring capabilities described in this guide reflect publicly accessible product data collected through standard web protocols. Bonesaw does not access private or authenticated data. All data collection respects robots.txt directives and site access policies.