Steering decision log

Steering meeting of Sep 24, 2026 State on Sep 28 Three shift template actions not started Client-visible

What the steering group decided on Thursday, September 24, 2026, and where each of the four decisions stands on Monday, September 28: the actions it became, who owns them and when they are due. Kept by Emeka Achebe, PMO analyst at Ferncastle Operations Group, and reviewed by Philippa Sinclair, program director, for Gareth Pryce, chief operating officer at Fairhaven Home Stores, and the workstream leads. The rule of the log is simple: every decision turns into owned workstream actions within two days, and a decision still waiting for an owner is shown as such, not hidden.

Sample template: the firm, people, clients and figures are fictional, and the embedded view holds synthetic sample records.

The four decisions of September 24

Each decision shows its owner, the Fairhaven owner and the actions it became. Owned means a named person has accepted it. The two day mark for each decision was Sep 26.

Decisions and their actions

The table lists each steering decision with the actions linked to it. Record type tells a decision from an action, and Linked decision ties each action back to its decision. Read the Status column for actions that are Owned but not started, and the Due column for those due before the Oct 8 steering meeting. Fairhaven has 18 rows here: the four decisions and their 14 actions. The view also holds 3 rows for Prescott Medical Supply and 3 for Halvard Brewing Company, 24 in all.

Did every decision get an owner in two days?

The squares below show the state two days after the meeting: three decisions had owned actions within two days, and one was still waiting for an owner, which was named later. The one waiting was the shift template pilot. Gareth Pryce then named the regional operations manager as its owner on Sep 26, so the table above, which is the state on Sep 28, shows all four as Owned.

Live example from the Dashboards app, shown with Fairhaven Home Stores' demo data. Block dates move forward each week, so they can differ from the sample dates on this page.

I had not named a store operations owner in the room. Seeing the decision sit there with no one against it is what made me name one the same week.

Where the 14 actions stand

All 14 actions from the four decisions are counted by workstream and status. Five are done, five are in progress and four are not started. Store labor scheduling carries three of the four that have not started.

Live example from the Dashboards app, shown with Fairhaven Home Stores' demo data.

From decision to action

How each decision of Sep 24 reached its actions, and where one of them waited:

flowchart LR
    M["Steering meeting, Sep 24: 4 decisions"] --> D1["Reset the replenishment pilot date to Oct 16"]
    M --> D2["Pilot the new shift template in eight stores"]
    M --> D3["Hold two stores out of the labor totals"]
    M --> D4["Plan wave 2 and the shrink baseline for November"]
    D1 --> A1["4 actions: 2 closed, 2 in progress"]
    D2 --> G{"Store operations owner named?"}
    G -->|"Not at the meeting"| W["3 actions unassigned"]
    W -->|"Sep 26: regional operations manager named"| A2["3 actions owned, not started"]
    D3 --> A3["2 actions: 1 closed, 1 in progress"]
    D4 --> A4["5 actions: 2 closed, 2 in progress, 1 not started"]

Check before the next steering meeting

Before Thursday, October 8

Check the three shift template actions are underway. Owner: Emeka Achebe, before Oct 8

Reconcile the two store labor trackers with both store managers. Owner: Hamish Aldous, Oct 7

Check the four replenishment actions at the steering meeting. Owner: Philippa Sinclair, Oct 8

Review the five wave 2 and shrink baseline actions at the steering meeting. Owner: Hamish Aldous, Oct 8

Send the loss prevention access request once a Fairhaven owner is named. Owner: Philippa Sinclair, Oct 9

✓Exclude the two stores from the pack totals. Owner: Emeka Achebe, done

✓Name an owner for the shift template decision. Owner: Gareth Pryce, done Sep 26

How to use this template

Record every steering decision on the day of the meeting, then link each decision to its actions, owners and due dates within two days. Show any decision still waiting for an owner.

Variable	Meaning	Required
{{steering.meeting_date}}	Date of the steering meeting the decisions came from	Required
{{decision.title}}	The decision as the sponsor stated it	Required
{{decision.owner}}	Person who owns carrying the decision into action	Required
{{decision.client_owner}}	Client person named as owner of the decision	Required
{{action.linked_rows}}	Actions linked to the decision with owner, due date and status	Required
{{decision.state}}	Whether the decision is Owned or Waiting for owner	Required
{{action.next_check}}	Date the actions are checked, normally the next steering meeting	Optional

If a required value is missing, show Needs review in its place and hold the entry; never fill an owner with a guess. If the register cannot be read, show Unavailable instead of the counts.

The live Dashboards blocks on this page show the Fairhaven Home Stores demo profile. Point each block at your own client's profile, or remove it, before you share the page. Filter the embedded view to the same client as well.