T55 Steering committee decision memo
Steering committee decision memo
What the Northstar steering committee needs to decide this cycle, the evidence behind each recommendation and what happens if a decision slips. Prepared by Kettering Transformation for Northstar's steering committee. Covers decision items due between Sep 24 and Oct 2, 2026.
Three decisions requested from this committee
This cycle asks the committee to decide on the sales team structure, integration alerting and the month-end close calendar. Each decision below has a single recommended option, evidence from the engagement and a named client decision owner. We need a decision or a deferral by the meeting date below for each item, or it carries into the next reporting cycle.
Sample template: the firm, people, clients and figures are fictional, and the embedded view holds synthetic sample records.
Live example from the Dashboards app, shown with Redwood Mobility's demo data.
How an item moves through this log
stateDiagram-v2
[*] --> Captured
Captured --> Analyzing
Analyzing --> RecommendationReady: enough evidence
RecommendationReady --> ClientDecision: sent to committee
ClientDecision --> Actioned: approved
ClientDecision --> Deferred: postponed
Actioned --> Closed
Deferred --> Closed: revisited
Closed --> [*]
The Decision board below shows only items in Recommendation ready or Client decision, the two stages where the committee has something to act on.
Before you share this page with a client
The decision board in this template holds decision items from several client engagements. Before sending the memo to a steering committee, switch the embed to a saved view filtered to that client's engagement, or share a copy of the page that uses the filtered view. A committee must never see another client's decisions.
1. Regional sales team merge
| Option | Description | Evidence | Recommendation |
|---|---|---|---|
| A: Merge now | Combine both regional teams under one territory map from November | Overlapping territories caused 14 disputed accounts this year | |
| B: Status quo | Keep two teams and resolve disputes case by case | Dispute rate has been rising each quarter | |
| C: Merge in Q1 2027 | Delay the merge until the new fiscal year | Avoids mid-quarter disruption, but disputes continue three more months |
Decision due: Oct 1, 2026. Client decision owner: Ruth Okafor.
2. Integration monitoring gap
| Option | Description | Evidence | Recommendation |
|---|---|---|---|
| A: Add failure alerts | Route failed sync alerts to the operations channel within 5 minutes | Two silent sync failures found last quarter, both caught by chance | |
| B: Status quo | Continue relying on manual daily checks | No added cost, but failures can run undetected for days |
Decision due: Oct 2, 2026. Client decision owner: Ruth Okafor.
3. Fixed close calendar
| Option | Description | Evidence | Recommendation |
|---|---|---|---|
| A: Publish a fixed calendar | Name an owner for each close day, publish dates for the quarter | Month-end close finished between day 6 and day 11 over the last six months | |
| B: Status quo | Let each team set its own close pace | Simple, but the finance team cannot plan around a moving date |
Decision due: Oct 2, 2026. Client decision owner: Ruth Okafor.
Two findings are not ready for this committee
Data quality threshold and lost account reason taxonomy are still in analysis and are not on this agenda. The reason taxonomy review missed its Sep 18 checkpoint because the client's closed lost export arrived without the loss reason field; Owen Brooks has asked Northstar's CRM administrator to resend it before analysis can resume.
Attendees
Decision log for this meeting
A decision counts as recorded only once it is written in the item's Decision field on the board and the card moves out of Client decision. A verbal steer in the meeting is not sufficient on its own.
How this memo is produced
- Decisions and recommendations are pulled from the engagement decision log, filtered to Northstar items in Recommendation ready or Client decision.
- Options tables are drafted by the consultant owner named on each item and reviewed by the engagement lead before the memo is sent.
- All names, figures and dates in this template are synthetic sample data.
How to use this template
Duplicate this page once per steering committee cycle. Replace these values; if a required value is missing, show Needs review instead of guessing.
| Variable | Meaning | Required |
|---|---|---|
{{client.name}} | Client whose steering committee the memo serves | Required |
{{meeting.date}} | Date and time of the steering committee meeting | Required |
{{decision.item_name}} | Name of each decision item pulled onto this agenda | Required |
{{decision.recommended_option}} | The consultant's recommended option for each decision | Required |
{{decision.owner}} | Named client decision owner for each item | Required |
{{decision.due_date}} | Date the decision is needed by | Optional |
Never present a verbal steer from the meeting as a recorded decision; update the source decision log first, then this memo.