TemplateSteering 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
- The Project Clone drafts every section from the portal: milestones, deliverables, dashboard metrics, risk register and decision log.
- The Solutions Partner reviews the draft, writes the executive summary in their own words and sharpens the decisions.
- Business owners confirm their department line (two minutes each).
- The InfoSec lead confirms the security and governance section.
- Send two business days ahead. Keep the main pack to the sections below; details go in the appendix.
- 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 |