Review Template: Close a 13-Week Cycle with Evidence

Start with the result, not the story

A cycle review can easily become a memory contest. People recall the frantic final week, the meeting that went sideways, or the one milestone that felt like a breakthrough, while quieter evidence gets lost. A small amount of structure keeps the review grounded: write down the target, record what actually happened, cite the source, calculate the variance, and choose what happens next.

“Publish six of eight planned reports” is more useful than “mostly complete.” The first statement identifies a count, makes the shortfall visible, and gives the next cycle something to examine. The second is a mood disguised as a status update. Neither result is automatically good or bad; the point is to make the result specific enough to learn from.

Use the template below as a working record, not a verdict on the people who did the work. A review should help a person or team make the next cycle more deliberate. It should not reward polished explanations over honest data.

The 30-minute review, at a glance

Bring the original 90-day plan, the milestone tracker, and the simplest reliable evidence for each target. A calendar, project board, learning log, or published deliverable may be enough. Do not spend the session rebuilding data that should have been captured during the cycle; mark that gap, agree on a source for next time, and keep moving.

For a team review, appoint one person to capture decisions and another to locate evidence. For a solo review, use the same sequence and set a timer. The time limit is not there to rush important issues; it helps prevent a review from turning into a sprawling retelling of the whole quarter.

Copy-ready outcome review template

Make one row for every committed outcome. Keep the original target intact, even if priorities changed halfway through. If scope was formally revised, record both the original target and the dated change so the result remains interpretable.

Use the same unit in the target and actual columns whenever possible. If the target was “eight reports,” the actual should be a report count—not “good progress.” If the target was a capability, pair it with an observable test, such as passing a defined assessment or delivering a task without assistance. For a qualitative outcome, state the agreed acceptance criteria and identify who confirmed them.

Evidence does not need to be elaborate. A link to a shipped feature, a dated customer email, a completed checklist, or a calendar record can be enough. Label the source so another person can find it. If no trustworthy evidence exists, write “not captured” rather than filling the gap with confidence or guesswork.

Calculate variance without hiding the context

For count-based goals, subtract the actual from the target to show the gap. If a target was 8 deliverables and the actual was 6, the gap is 2. For a simple completion rate, divide actual by target: 6 ÷ 8 = 0.75, or 75%. These calculations describe the result; they do not explain it or tell you whether the target was sensible.

For goals where a higher number is not necessarily better—such as defects, response time, or unresolved tickets—agree on the direction of success before interpreting the gap. A cycle might target fewer than 10 open defects; an actual result of 12 is two above the ceiling, not 120% success. Write the measure’s direction beside the target if there is any chance of confusion.

Do not compare unlike measures as if they were interchangeable. “Six reports published” and “75% of interviews completed” can sit in one review, but they do not combine into a meaningful average without a deliberate scoring model. A clean row-by-row comparison usually reveals more than a single blended score.

Three prompts that turn results into decisions

Once the table is filled, pause before proposing fixes. Ask these three questions and answer each with a concise, specific statement.

1. What most affected the result? Identify the strongest influence you can support with evidence. For example: “Two subject-matter reviewers were unavailable during weeks 6 and 7, so four reports waited for approval.” Avoid using broad labels such as “communication” or “motivation” without describing what happened.
2. Which action should be repeated or dropped? Name a behavior, routine, or commitment—not a personality trait. “Keep the Tuesday 20-minute draft review; it cleared comments before the final week” is actionable. So is “stop scheduling interviews before consent materials are approved.”
3. What is the single adjustment to carry into the next cycle? Choose one change that can be observed in the calendar, plan, or workflow. “Reserve one reviewer for two hours each Thursday” is testable. “Be more organized” is not.

Teams may have several important lessons, but the last prompt deliberately asks for one adjustment. Treat it as the primary experiment, not a ban on other improvements. A long list of changes can be difficult to implement and impossible to evaluate. If multiple changes are essential, separate them into explicit owners and checkpoints rather than hiding them in a general intention.

Worked example: reports that stopped at six

Imagine a project team planned to publish eight customer research reports in 13 weeks. At the review, it verifies six published reports in the shared folder, each with a date and an approved summary. The remaining two are drafts awaiting review. The result is not eight, and it is not “nearly done”: it is six published reports against a target of eight, with two drafts in a different state.

The team checks its weekly notes and finds that interviews were completed close to schedule, but review requests stacked up during weeks 6–8. The main influence was not a shortage of interviews; it was limited reviewer availability. The team decides to keep the interview cadence, change the approval arrangement, and stop treating a submitted draft as a published report.

Its next-cycle adjustment becomes: “Name a backup reviewer before the first interview and reserve a Thursday review block each week.” That decision has a visible owner and a calendar location. At the next checkpoint, the team can see whether review time was reserved and whether drafts moved through approval. The review has produced a practical experiment instead of a vague promise to work harder.

A week-by-week closeout sequence

Week 13 is the formal close, but the review works better when evidence is already easy to find. Use this sequence to avoid turning the last 30 minutes into an emergency data hunt.

This sequence is not a replacement for a milestone tracker or risk log. It is the closeout layer that uses those records. A milestone can show when a deliverable was due; the review explains whether the planned outcome was achieved and what should change as a result.

Separate a missed target from a failed cycle

A 90-day cycle may produce a valuable result even when a target is missed. A team could discover that a planned feature is unsafe to release, that a course requires more practice than expected, or that a proposed process cannot meet a required standard. Record the result honestly, then distinguish between the outcome and the quality of the decision-making that produced it.

Consider four different cases: the target was met with the planned approach; the target was missed because a known risk occurred; the target became irrelevant after a documented scope change; or the target was poorly defined and could not be measured reliably. These call for different next steps. Repeating the same plan makes sense in one case; revising the risk response, resetting scope, or improving the measure may be better in the others.

Keep scope changes visible. If a stakeholder removed two deliverables in week 7, record the date, decision, and revised expectation. Do not quietly replace the original target in the final review; that erases useful information about planning and decision-making. A fair account can show both what was originally promised and what was formally changed.

Make the handoff specific

The last minutes of a review should produce a handoff, not just a set of observations. Fill in this compact block before closing the document:

For example: “Reserve Thursday review time; owner: project lead; first action: book the recurring block by Monday of week 1; checkpoint: end of week 3; evidence: calendar bookings and median review turnaround.” This is concrete enough to revisit. “Improve review speed” is not.

If no new cycle is planned, the handoff still matters. Name the final owner of unfinished work, the next decision-maker, and any date by which a follow-up is required. A project that ends without an owner for its open items can leave useful work in limbo.

Common review traps—and how to avoid them

• Changing the target after seeing the result. Keep the original commitment visible. Record approved changes separately with dates and reasons.
• Confusing activity with outcome. “Held 12 meetings” is an activity count; it does not prove that a decision was made or a deliverable was completed.
• Using evidence that cannot be checked. “Everyone agreed it went well” may be a useful observation, but it is not a substitute for the agreed measure or a traceable source.
• Turning variance into blame. Ask which conditions, choices, and dependencies shaped the result. The purpose is to improve the next operating plan, not to assign a character flaw.
• Adding every lesson to the next plan. Prioritize the most important adjustment and give it an owner and checkpoint. Keep secondary ideas in a backlog.
• Ending without a decision. “Discuss next cycle” is not a handoff. State what will be kept, changed, or stopped, and who will act.

A reusable closeout worksheet

Copy this section for each 90-day project, learning sprint, or personal initiative. Keep the review date and evidence links with the completed worksheet so the next cycle can refer to the record rather than relying on recollection.