Guide · 7 min read

    Strategy Review: Agenda, Cadence, and Management Reporting

    A strategy review is only worth holding if it leads to decisions. Here you get a concrete agenda for the quarterly review, the cadence for the four meeting types, and a model for management reporting without double work.

    Published · Updated · 7 min read

    In short

    • The review should be about deviations and decisions — not about reviewing everything.
    • Status is updated by the owners before the meeting, and materials are read in advance.
    • Separate weekly operational meeting, monthly follow-up, quarterly review, and annual seminar.
    • Decision log with owner and deadline is the first item on the next review.

    What is a strategy review?

    A strategy review is the meeting where management reviews the status of strategic goals, KPIs, projects, and risks — and makes decisions based on it. It is not an operational meeting and not a presentation round. The value lies in addressing deviations while there is still time to act.

    The difference between a good and a useless review is rarely the meeting leader. It lies in the preparation: is the status updated by the owners before the meeting, and is the agenda based on what is red or delayed — or do you go through everything from start to finish?

    Management reporting goes hand in hand with the review. When the board and management see the same figures and the same status logic, the double work of creating a separate report for each forum disappears.

    Agenda for a quarterly strategy review (120 min)

      1. Decisions from last review               10 min
         — have they been implemented? If not: why?
      2. Status of strategic goals                 20 min
         — only goals with yellow/red status
      3. KPI deviations                            25 min
         — figures outside target level + missing data
      4. Projects and milestones                   25 min
         — delays, resources, dependencies
      5. Risks above tolerance threshold           15 min
      6. Prioritization and decisions              20 min
         — what do we stop, what do we accelerate?
      7. Summary: owner, action, deadline           5 min

    Green goals and KPIs are not reviewed. They are in the material and should be read before the meeting — meeting time is spent on what requires a decision.

    The four meetings in a well-functioning cadence

    Separate the purposes so that the strategic meeting is not consumed by operations.

    Weekly operational meeting

    15-30 min

    Only this week's tasks and obstacles. No strategy points.

    Monthly follow-up

    45-60 min

    KPI status and project progress. Deviations are assigned an owner and deadline.

    Quarterly strategy review

    2-3 hours

    Prioritization, risks, and decisions on goals, resources, and ambition level.

    Annual strategy seminar

    1-2 days

    Analyses are revisited, and goals for the next period are formulated.

    How to conduct a review that leads to decisions

    1. 1. Close status one week before

      Owners update KPIs, projects, and risks by a fixed deadline. If status is not updated, the item is not ready for the meeting.

    2. 2. Build the agenda on deviations

      Goals and KPIs in yellow and red, delayed milestones, and risks above the threshold set the agenda — not the order in a spreadsheet.

    3. 3. Send out materials in advance

      Participants read the status before the meeting. The meeting begins with questions and choices, not with a review.

    4. 4. Demand an explanation per deviation

      The owner answers three things: why does the figure deviate, what are we doing, and when will we see the effect?

    5. 5. Make at least one real prioritization

      What do we stop or postpone to accelerate something else? Reviews without prioritization repeat themselves.

    6. 6. Log decisions with owner and deadline

      The decision log is the first item on the next review. This is the single action that has the greatest impact on progress.

    Management reporting: manual report vs. continuous status

    AreaManual reportContinuous status in Plandura
    PreparationDays of collection and formatting before each meeting.Owners update continuously; material is always current.
    FiguresCopied in, often in multiple versions.One source for goals, KPIs, projects, and risks.
    StatusAssessed by the person writing the report.Calculated based on target level and latest measurement.
    DecisionsRecorded in minutes that are not re-read.Logged with owner and deadline and opens the next review.
    Board of DirectorsReceives its own document.Sees the same picture as management.

    Five signs of a review that isn't working

    • The meeting is spent reviewing everything, even what is green.
    • Status is updated the same morning by one person for everyone else.
    • No decisions are made — only agreements to follow up later.
    • Last meeting without a decision log, so the same discussion is repeated.
    • Operational matters take over the agenda because they are more urgent.

    Frequently asked questions

    What is a strategy review?

    +

    A strategy review is a regular meeting where management reviews the status of strategic goals, KPIs, projects, and risks, and makes decisions about prioritization and resources. The purpose is to correct the course in time, not to report results retrospectively.

    How often should one hold a strategy review?

    +

    Quarterly for the actual strategy review, combined with monthly follow-up on KPIs and projects. Annually, a longer seminar is held where analyses and goals for the next period are updated.

    What should the agenda include?

    +

    Decisions from the last meeting, status of goals with yellow or red status, KPI deviations, delayed projects and milestones, risks above the tolerance threshold, and a prioritization round that concludes with decisions including owner and deadline.

    Who should participate?

    +

    The management team and the owners of the goals, KPIs, and projects on the agenda. If an owner is not present, the item cannot be decided, and the meeting ends up postponing the decision.

    How to prevent operations from taking over the meeting?

    +

    Keep operational meetings separate from the strategy review, allocate time for each item, and only review what deviates. Operational matters that arise during the meeting are forwarded to the weekly operational meeting with an owner.

    How does Plandura support strategy reviews?

    +

    Plandura sets up reviews according to your chosen cadence, builds the agenda based on the actual status of goals, KPIs, projects, and risks, and logs decisions with owner and deadline. The next review opens with the decisions made last time.

    These guides are closely connected to strategy review and are natural next steps in your strategy work.

    Conduct reviews based on actual status

    Create a free account and get reviews with automatic agenda, decision log, and status on goals, KPIs, and projects.