---
name: scorecard
description: Analyse your weekly EOS scorecard — calculate variances, identify trends, and generate commentary for each metric.
---

# /scorecard

Analyse the weekly scorecard, calculate variances against targets, identify trends, and generate objective commentary ready for your leadership meeting or investor update.

## When to Run

- Before or after the weekly L10 meeting
- When preparing investor updates
- When you need a quick health check on the business

## What It Does

1. Reads your scorecard data (CSV, Notion export, or structured text)
2. Calculates variance (actual vs target) for each metric
3. Assigns status: on track, at risk, or off track
4. Identifies multi-week trends if historical data is available
5. Generates one-line commentary for each metric
6. Flags metrics that need attention with placeholders for human context

## Input

Provide your scorecard data in any of these formats:

### Option A: Structured table

```
| Metric               | Actual | Target |
|----------------------|--------|--------|
| Weekly Gross Revenue | $480k  | $400k  |
| New Leads (Qualified)| 38     | 50     |
| Median Response Time | 45s    | 60s    |
| Gross Margin %       | 16.2%  | 15.0%  |
| Runway (months)      | 14     | 12     |
```

### Option B: Raw text

```
This week: Revenue $480k (target $400k), 38 qualified leads (target 50),
response time 45s (target 60s), margin 16.2% (target 15%), runway 14 months.
```

### Option C: File path

Point to a CSV or Notion export file.

## Output Format

For each metric:

```
[Metric]: [Actual] ([Target] target) [+/-Variance%] [Status]
Commentary: [Objective observation]. [Trend if available]. [Placeholder for context if needed].
```

### Status Rules

- **On track**: actual meets or exceeds target
- **At risk**: within 10% of target
- **Off track**: more than 10% below target
- For "lower is better" metrics (response time, rework %): invert the logic
- For ratios/percentages: use absolute difference, not percentage of percentage

### Commentary Rules

**Always include:**
- The objective observation (what happened)
- Whether this is highest/lowest if historical data available

**Only include if you have data:**
- Multi-week trends ("3rd consecutive week of decline")
- Comparison to prior period

**Leave as placeholder if uncertain:**
- Why the metric moved
- What to do about it
- Whether it's seasonal

```
[PLACEHOLDER: Reason for variance — check with [likely owner]]
```

## Example Output

```
Weekly Gross Revenue: $480k ($400k target) +20% ✅ On track
Commentary: Above target by 20%. Highest weekly revenue in Q1.

New Leads (Qualified): 38 (50 target) -24% ❌ Off track
Commentary: Below target by 24%, 2nd consecutive week of decline.
[PLACEHOLDER: Reason for lead volume drop — check with Growth team]

Median Response Time: 45s (60s target) +25% ✅ On track
Commentary: Well within SLA at 45s. Improved from 52s last week.

Gross Margin: 16.2% (15.0% target) +1.2pp ✅ On track
Commentary: Above target by 1.2 percentage points.

Runway: 14 months (12 target) ✅ On track
Commentary: Healthy at 14 months, reflecting current burn rate.
```

## Summary Block

After individual metrics, provide:

```
SCORECARD SUMMARY
─────────────────
Total metrics: X
On track: X | At risk: X | Off track: X

Key focus areas:
- [Metric 1]: [One-line action needed]
- [Metric 2]: [One-line action needed]

Placeholders to fill: X
```

## Adapting This Command

Replace the example metrics with your own scorecard metrics. Common EOS scorecard metrics include:

- Revenue (gross, net)
- Lead volume and conversion rates
- Customer satisfaction / NPS
- Operational SLAs (response time, completion rate)
- Sprint / delivery metrics
- Runway and burn rate
- Employee engagement (eNPS)