# Your Operating Playbook

Put the judgment of your experienced operators to work across the business

An experienced operator sees a result and knows what to ask next. Is the change unusual for this location? Is it concentrated in a category? Does the same pattern appear nearby? What would they inspect before deciding on an action?

Your operating playbook captures that judgment. It guides how Scoop reads the data, investigates a finding, and recommends a response. This is the business knowledge behind **Domain Intelligence**.

## What goes into the playbook

We build the playbook with your operators and the people who know your data. It covers the decisions they make during a performance review.

| Part of the playbook | What we establish with your team |
|---|---|
| Meaning of the measures | What each measure counts, how it is calculated, and which period it covers |
| Useful comparisons | The targets, historical periods, and peer locations that make a comparison meaningful |
| Reasons to investigate | Which changes, combinations of results, or developing trends deserve attention |
| Diagnostic questions | What to examine next, and which evidence would support or weaken an explanation |
| Operating exceptions | Circumstances that change how a result should be interpreted |
| Practical responses | Your standard actions, who can carry them out, and when escalation is appropriate |

This knowledge often exists across operating manuals, management reports, and people's experience. We bring it together through structured conversations and review it against actual briefings during the pilot.

## Definitions change the conclusion

A sales count could mean transactions, items, or customers. Those are different measures. A decline in transactions doesn't, by itself, tell you whether fewer people visited or fewer visits resulted in a purchase.

Dates matter too. Sales accumulated during a month and inventory held on a particular date describe different things. Comparing either with an unsuitable prior period can make normal performance look like a problem.

We establish these distinctions with your team so the investigation starts from the business meaning of the figures. The briefing's labels and comparisons help the reader interpret them.

## The playbook guides the next question

Consider an illustrative retail example. Total sales are steady, but one category is weakening. Your operators may want to examine transaction volume, average sale value, inventory availability, and margin before deciding what to do.

If transactions have fallen while average sale value holds up, the next question concerns volume. If sales are holding up while margin falls, the investigation needs to examine the mix and margin pattern. Those situations lead to different checks with the team.

Scoop applies this diagnostic approach to each location. The same operating standards produce findings specific to the evidence. [Inside a Scoop Investigation](https://docs.scoopanalytics.com/docs/inside-an-investigation) follows this example through to a management response.

## See the playbook at work

The [illustrative briefing](https://docs.scoopanalytics.com/docs/sample-performance-briefing) makes these distinctions concrete. The table shows business knowledge that would guide this simplified retail example; it is not a customer's private rulebook.

| Playbook element | Example | Effect on the investigation |
|---|---|---|
| Definition | Average sale is sales divided by transactions; a transaction is not a store visit | A transaction decline cannot by itself establish lower traffic |
| Comparison | Compare August 1–15 with the same days last year | A short current period is not compared with a full prior month |
| Diagnostic question | Is the decline coming from transaction count, average value, or category mix? | A1 leads to a volume check; A2 leads to a mix check |
| Exception | Overall margin can change when category mix changes, even at unchanged category margins | Do not conclude that pricing deteriorated from the store margin alone |
| Action and authority | A store manager can inspect availability; shared operating decisions may require a district manager | The proposed work fits the reader's responsibility |

The numbers show what changed. The playbook helps determine what that means for the next management decision.

## Actions stay within the manager's responsibilities

The playbook also captures how your business responds. A location manager might inspect the affected category and review its recent transactions. A district manager might compare execution across locations or bring a shared issue to a regional leader.

These distinctions make the recommendation usable. The manager needs to understand where to start, what to check, and which decision belongs to someone else. Your existing policies and management judgment still govern the action.

## Keep the playbook current

During the pilot, your operators review whether the questions and recommendations fit the business. After rollout, managers can flag missing context, incorrect interpretations, or actions that don't fit local conditions.

Our team reviews that feedback with you. When a definition, threshold, exception, or standard action needs to change, we agree the change and when it will apply. You describe the business requirement in plain English; we maintain the playbook.

Your organization's operating knowledge is used only for your implementation and is never shared with other clients.

---

**Related:** [How Scoop Works](https://docs.scoopanalytics.com/docs/how-scoop-works) · [Getting Started with Scoop](https://docs.scoopanalytics.com/docs/onboarding) · [Working with Action Plans](https://docs.scoopanalytics.com/docs/working-with-action-plans)