# Steering Pack

The monthly executive steering pack covering progress, metrics, autonomy, risks and the decisions leadership needs to make, on one page per topic.

## What this is for

The steering committee is where the transformation gets decided: which departments go next, which risks are accepted, which promotions are approved and where help is needed. A good pack lets executives spend the meeting on decisions instead of status. It shows progress against the plan, results against baseline, autonomy by department, and the few items that need a decision today. Month 1's pack is the first; the same format runs every month to Month 12.

## When to use it

Monthly. The pack goes out two business days before the meeting so members arrive having read it. The Month 1 version doubles as the Month-1 Steering Report deliverable. In quarter-end months, the pack feeds the quarterly business review.

## Who's involved

- **Solutions Partner** owns the pack and runs the meeting.
- **Executive sponsor** chairs and signs off decisions.
- **Steering members** (department heads, InfoSec lead, IT lead, CoE lead once formed) read and decide.
- **Business owners** and **Champions** supply department updates.

## How to fill it in

1. The Project Clone drafts every section from the portal: milestones, deliverables, dashboard metrics, risk register and decision log.
2. The Solutions Partner reviews the draft, writes the executive summary in their own words and sharpens the decisions.
3. Business owners confirm their department line (two minutes each).
4. The InfoSec lead confirms the security and governance section.
5. Send two business days ahead. Keep the main pack to the sections below; details go in the appendix.
6. After the meeting, record decisions and actions in section 8 and in the portal decision log within one business day.

## The template

### Cover

| Field | Entry |
|---|---|
| Organization | _Northgate Supply (fictional)_ |
| Steering meeting | _Month 3, Day 88_ |
| Engagement day / stage | _Day 88 of 365 · First results_ |
| Prepared by | Solutions Partner, with the Project Clone |
| Decisions requested today | _3_ |

### 1. Executive summary (5 lines maximum)

- **Overall status:** On track / At risk / Off track
- **Biggest win this month:**
- **Biggest risk this month:**
- **What we need from you today:**
- **Next month's focus:**

> _Example: On track. Support Triage Clone gave back 46 agent hours a week against baseline. Risk: ERP write access for Finance is 2 weeks late. We need a decision on Department 3 and approval to promote AP intake to Execute with approval. Next month: Finance launch, Champions cohort 2._

### 2. Plan progress

| Stage / milestone | Planned date | Status | Forecast | Note |
|---|---|---|---|---|
| _InfoSec Clones live_ | _Day 28_ | _Done_ | | |
| _Department 1 (Support) live_ | _Day 55_ | _Done_ | | |
| _Department 2 (Finance) live_ | _Day 95_ | _At risk_ | _Day 105_ | _ERP connection approval pending_ |
| _90-Day Results Report_ | _Day 90_ | _On track_ | | |

Deliverables this month:

| Deliverable | Status | Link | Sign-off |
|---|---|---|---|
| | Draft / In review / Signed | | |

### 3. Results against baseline

| Department | Metric | Baseline | This month | Target | Trend |
|---|---|---|---|---|---|
| _Support_ | _Median first-response time_ | _9.5 hrs_ | _2.1 hrs_ | _3 hrs_ | _Improving_ |
| _Support_ | _Agent hours on triage per week_ | _58_ | _12_ | _20_ | _Improving_ |
| | | | | | |

### 4. Adoption

| Department | Users in scope | Weekly active | % | Avg Power Rating | Tasks completed | Hours given back | Champion |
|---|---|---|---|---|---|---|---|
| _Support_ | _66_ | _57_ | _86%_ | | _4,210_ | _46/wk_ | _Yes_ |
| | | | | | | | |

### 5. Autonomy by department

| Department | Clone / workflow | Level | Since | Next level proposed | Evidence pack |
|---|---|---|---|---|---|
| _Support_ | _Ticket routing_ | _3 Execute with approval_ | _Day 70_ | _Day 126_ | _Not yet_ |
| _Finance_ | _AP invoice coding_ | _2 Recommend_ | _Day 82_ | _Requested today_ | _Link_ |

Level counts: Assist __ · Recommend __ · Execute with approval __ · Execute within limits __ · Orchestrate __

### 6. Security and governance

| Item | This month | Status |
|---|---|---|
| New connections approved / pending | _4 / 1_ | |
| Governance incidents above agreed severity | _0_ | |
| Overrides reviewed by InfoSec | _Yes, Day 84_ | |
| Risk register changes | _2 added, 1 closed_ | |
| Skill version changes through change control | _3_ | |
| Access review completed | | |

### 7. Top risks and issues

| # | Risk / issue | Impact | Likelihood | Owner | Mitigation | Needs steering? |
|---|---|---|---|---|---|---|
| 1 | _ERP write access approval delayed_ | _Finance launch slips 2 weeks_ | _High_ | _IT lead_ | _Launch read-only; review write scope Day 100_ | _Yes, accept the slip_ |
| | | | | | | |

### 8. Decisions

| # | Decision requested | Options | Recommendation | Decision | Owner |
|---|---|---|---|---|---|
| 1 | _Department 3 selection_ | _HR onboarding vs. Procurement intake_ | _HR (score 4.2 vs. 3.6)_ | | |
| 2 | _Promote AP coding to Execute with approval_ | _Approve / defer_ | _Approve; evidence pack attached_ | | |
| 3 | | | | | |

### 9. Actions from last steering

| Action | Owner | Due | Status |
|---|---|---|---|
| | | | Done / Open / Overdue |

### 10. Next 30 days

- Departments launching or in pilot:
- Promotions to be reviewed:
- Training and comms:
- What we need from steering members:

### Appendix (optional)

Department detail, full risk register extract, Adoption Dashboard export, Champion council notes.

## Good looks like

- The executive summary fits on a phone screen and states the ask plainly.
- Decisions are framed with options and a recommendation, not "for discussion".
- Results show baseline, actual and target side by side. No metric without a baseline.
- Bad news is early and specific, with a mitigation and an owner.
- Autonomy is shown per workflow, so leaders see exactly what runs with and without a person in the loop.
- Common mistake: a 40-slide status deck. If it is not a decision, a risk or a result, it belongs in the appendix.

## How Clone helps

The **Project Clone** builds the draft overnight from the portal: milestones, deliverable status, Adoption Dashboard metrics, autonomy history, the risk register and open actions. The **GRC Clone** supplies the security and governance section. After the meeting, the Project Clone logs decisions and actions in the portal and chases owners before the next pack.

## Sign-off

| Role | Name | Date | Decision |
|---|---|---|---|
| Executive sponsor | | | Pack accepted; decisions recorded |
| Solutions Partner | | | Pack issued |

## Related

- [Success Metrics Baseline](/playbook/templates/success-metrics-baseline)
- [Autonomy Promotion Evidence Pack](/playbook/templates/autonomy-promotion-evidence-pack)
- [AI Risk Register](/playbook/templates/ai-risk-register)
- [90-Day Results Report](/playbook/templates/ninety-day-results-report)
- [The Clone Solutions Method](https://clone.org/solutions/method)

---
From the Clone Solutions Playbook: https://solutions.clone.org/playbook/templates/steering-pack
