Clone Solutions
Template

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

FieldEntry
OrganizationNorthgate Supply (fictional)
Steering meetingMonth 3, Day 88
Engagement day / stageDay 88 of 365 · First results
Prepared bySolutions Partner, with the Project Clone
Decisions requested today3

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 / milestonePlanned dateStatusForecastNote
InfoSec Clones liveDay 28Done
Department 1 (Support) liveDay 55Done
Department 2 (Finance) liveDay 95At riskDay 105ERP connection approval pending
90-Day Results ReportDay 90On track

Deliverables this month:

DeliverableStatusLinkSign-off
Draft / In review / Signed

3. Results against baseline

DepartmentMetricBaselineThis monthTargetTrend
SupportMedian first-response time9.5 hrs2.1 hrs3 hrsImproving
SupportAgent hours on triage per week581220Improving

4. Adoption

DepartmentUsers in scopeWeekly active%Avg Power RatingTasks completedHours given backChampion
Support665786%4,21046/wkYes

5. Autonomy by department

DepartmentClone / workflowLevelSinceNext level proposedEvidence pack
SupportTicket routing3 Execute with approvalDay 70Day 126Not yet
FinanceAP invoice coding2 RecommendDay 82Requested todayLink

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

6. Security and governance

ItemThis monthStatus
New connections approved / pending4 / 1
Governance incidents above agreed severity0
Overrides reviewed by InfoSecYes, Day 84
Risk register changes2 added, 1 closed
Skill version changes through change control3
Access review completed

7. Top risks and issues

#Risk / issueImpactLikelihoodOwnerMitigationNeeds steering?
1ERP write access approval delayedFinance launch slips 2 weeksHighIT leadLaunch read-only; review write scope Day 100Yes, accept the slip

8. Decisions

#Decision requestedOptionsRecommendationDecisionOwner
1Department 3 selectionHR onboarding vs. Procurement intakeHR (score 4.2 vs. 3.6)
2Promote AP coding to Execute with approvalApprove / deferApprove; evidence pack attached
3

9. Actions from last steering

ActionOwnerDueStatus
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

RoleNameDateDecision
Executive sponsorPack accepted; decisions recorded
Solutions PartnerPack issued