A structured meeting format for reviewing plan alignment across levels — surfacing bottom-up signals, reconciling with top-down targets, and making modification decisions in real time.
The Gap Between Check-Ins and QBRs
In a continuous planning model, check-ins happen weekly and the QBR happens quarterly. That’s 13 micro-assessments and one macro-assessment. What’s missing is the meso-level: a structured moment, mid-quarter, where the entire hierarchy pauses to assess plan health across all levels simultaneously.
Check-ins are granular: one KR, one person, one data point. They’re excellent for detecting signals at the individual level. But they don’t show the cross-level picture — whether the modifications that teams have made over the past six weeks have kept the hierarchy aligned, or whether gradual drift has accumulated into a systemic gap.
QBRs are comprehensive but retrospective. By week 13, the quarter is over. Any misalignment discovered at the QBR is information that would have been actionable at week 6 but is now merely instructive.
The mid-quarter recalibration meeting fills this gap. It’s a structured, 45-minute session held at week 6 or 7 of the quarter. Its purpose is not to review results (that’s the QBR) or to report status (that’s the check-in). Its purpose is to assess the health of the planning system itself: are plans at every level still aligned with reality and with each other?
The mid-quarter recalibration is not a progress review. It’s a plan health check. The question isn’t “are we on track?” It’s “are our plans still valid?” These are different questions with different answers and different actions.
When to Hold It
The recalibration meeting should be held at the midpoint of the quarter, when enough execution data exists to assess plan validity but enough time remains to act on findings.
| Quarter Length | Recommended Timing | Rationale |
|---|---|---|
| 13 weeks (standard) | Week 6 or 7 | Six weeks of check-in data provides 40–50% of the quarter’s execution signal. Seven weeks remaining is enough to absorb significant plan modifications. |
| 12 weeks (fiscal quarter) | Week 6 | Slightly tighter. Week 6 gives exactly 50/50 split between assessment data and remaining execution time. |
| Monthly OKR cycle | Day 14–16 of the month | For organizations running monthly OKR cycles, the mid-cycle check happens at the two-week mark. |
Schedule the meeting at the beginning of the quarter so it’s in everyone’s calendar before the quarter starts. Don’t schedule it reactively when problems emerge — the point is to catch problems that haven’t emerged yet.
Some organizations hold two recalibration meetings: one at week 4–5 (early signal check) and one at week 8–9 (course correction before the final push). This is appropriate for high-volatility environments or quarters with significant uncertainty. For most organizations, one meeting at week 6–7 is sufficient.
Who Should Attend
The recalibration meeting is a leadership meeting, not an all-hands. The attendees should be the people who own plans at the parent level and have visibility into the aggregated view. Typically:
| Hierarchy Depth | Attendees | Duration |
|---|---|---|
| 2 levels (VP + Teams) | VP and all team leads (5–8 people) | 30 minutes |
| 3 levels (VP + Directors + Teams) | VP and directors (4–6 people). Team leads are on-call but not in the room. | 45 minutes |
| 4+ levels (CEO + VPs + Directors + Teams) | CEO and VPs (5–7 people). Directors contribute pre-read data but attend only if their area is flagged. | 45–60 minutes |
The meeting should be small enough for a real conversation (under 8 people) and senior enough to make modification decisions on the spot. If a VP decides to reduce a target during the meeting, they should have the authority to do so without scheduling a follow-up.
The Pre-Read: Data That Should Be Prepared
The recalibration meeting should be data-driven, not discussion-driven. The facilitator (typically the CEO, VP of Operations, or Chief of Staff) prepares a pre-read that attendees review before the meeting. This pre-read contains five data sets, all pulled directly from Profit.co:
1. The Aggregation Health Dashboard.
For each parent-level KR, show three numbers: the operating plan target, the current aggregated bottom-up total (reflecting any modifications teams have made), and the gap. Color-code: green for gaps under 5%, yellow for 5–10%, red for over 10%.
This dashboard immediately surfaces which parent KRs have healthy alignment and which have drifted. The meeting focuses on the yellows and reds.
2. The Modification Activity Summary.
For each parent KR, show how many child plan modifications have been made since the quarter started, the average time-to-modify (from signal to modification), and whether the modifications were proactive (signal-driven) or reactive (triggered by a QBR or escalation). This data comes from the audit trail.
A parent KR with zero modifications in six weeks is either perfectly calibrated (rare) or suffering from cascade drift (common). A parent KR with 15 modifications may be in a volatile environment or may have had a poorly calibrated initial plan.
3. The Trajectory Comparison.
For each parent KR, plot two lines: the operating plan’s expected trajectory and the actual check-in trajectory. If the actual line is diverging from the plan line, the plan needs modification. If they’re converging (actual is catching up to plan), the plan may be correctly calibrated despite early deviations.
4. The Assumption Validity Check.
At the start of the quarter, each parent KR’s plan was built on assumptions: a product launch date, a hiring timeline, a pipeline conversion rate. List the top three assumptions for each parent KR and mark each as: holding (assumption remains valid), at risk (showing signs of stress but not yet broken), or broken (assumption has been invalidated by events).
Broken assumptions that haven’t triggered a plan modification are the highest-priority agenda items for the meeting. They represent known misalignment that hasn’t been addressed.
5. The Cross-Functional Alignment View.
For shared KRs with cross-functional contributors, show whether each department’s contributing plan is on track and whether the contributions still sum correctly. Flag any cross-functional KR where one department’s modification has created a downstream misalignment that hasn’t been resolved.
The pre-read takes approximately 30 minutes to prepare using Profit.co’s dashboard and audit trail exports. It should be distributed to attendees 24 hours before the meeting. Attendees who arrive without reviewing the pre-read slow the meeting down; make pre-read review a condition of attendance.
The 45-Minute Agenda
The recalibration meeting follows a structured agenda designed to maximize decision-making per minute:
Minutes 1–5: Health Dashboard Review
The facilitator projects the aggregation health dashboard. No commentary yet — just the data. Attendees scan for green, yellow, and red KRs. The facilitator asks: “Any surprises? Anything on this dashboard you didn’t expect?” Surprises indicate information gaps that the notification system may have missed.
Minutes 5–10: Assumption Validity Scan
Walk through the assumption validity check for each parent KR. Focus on broken assumptions first. For each broken assumption, ask: has the plan been modified to reflect this? If yes, confirm the modification was appropriate. If no, flag it as a priority for the decision segment.
At-risk assumptions get a quick assessment: what would tip this from “at risk” to “broken”? Is there a specific date or data point that would confirm the break? This creates a watch list for the next six weeks.
Minutes 10–30: Decision Segment (Yellow and Red KRs)
This is the core of the meeting. For each yellow or red KR, the owner presents a 2-minute summary:
What’s the gap? (One number: the deviation between plan and aggregate.)
What’s the root cause? (Capacity, risk, stale assumption, cross-functional misalignment.)
What’s the proposed action? (Modify the plan, invest to close the gap, redistribute, or adjust the target.)
The group discusses and decides. Decisions should be made in the meeting, not deferred. The facilitator tracks each decision and assigns a 48-hour deadline for execution. Typical decisions:
| Decision Type | Example | Execution Timeline |
|---|---|---|
| Modify a parent plan | “Reduce the Q3 pipeline target from $5M to $4.5M based on the channel algorithm change.” | Modify in Profit.co within 24 hours. Cascade to children per propagation rules. |
| Invest to close a gap | “Approve a $30K contractor budget for Team B to recover their capacity shortfall.” | Budget approval within 48 hours. Team B revises plan once contractor starts. |
| Redistribute across children | “Shift $200K of Sales allocation from EMEA to APAC, which has pipeline headroom.” | Both directors modify their plans within 48 hours. |
| Accept the gap | “The 7% gap on the NPS KR is structural. We accept 41 as the realistic target instead of 45.” | Parent owner modifies target inline within 24 hours. |
| Watch for one more check-in | “Team C’s deviation is new this week. Wait for the next check-in before deciding.” | No action. Revisit at the next check-in. Facilitator adds to their watch list. |
Minutes 30–40: Cross-Functional Check
Review the cross-functional alignment view. For shared KRs, confirm that contributing departments’ plans still fit together. If a modification in one department has created a downstream misalignment, the two department leads resolve it in the meeting or commit to a 24-hour follow-up.
This segment is often the fastest because cross-functional KRs have their own notification systems. If the notifications are working, the alignment is already maintained. The recalibration meeting confirms this rather than discovering it.
Minutes 40–45: Action Summary and Close
The facilitator reads back each decision made during the meeting: which KRs are being modified, who is responsible, and the deadline. Each owner confirms. The facilitator sends a written summary within 2 hours of the meeting — not as meeting minutes, but as an action tracker.
The 45-minute budget is strict. If the meeting runs long, it’s because the pre-read wasn’t reviewed or because the facilitator allowed discussion to drift into status reporting. The recalibration meeting is a decision forum, not a discussion forum. Diagnosis happens in the pre-read. Decisions happen in the meeting. Execution happens after.
After the Meeting: The 48-Hour Execution Window
The recalibration meeting is only as valuable as the follow-through. Every decision made in the meeting must be executed within 48 hours. Here’s the post-meeting workflow:
Facilitator sends the action summary within 2 hours. Each action item has an owner, a specific action (modify plan, redistribute, invest, adjust target), and a 48-hour deadline.
KR owners execute modifications in Profit.co. Each modification follows the standard workflow: open Modify Plan, use AI to adjust, document the rationale referencing the recalibration meeting.
Propagation rules handle the cascade. If a parent plan is modified, child owners receive notifications per the configured rules. The 48-hour review window for review-required cascades starts from the parent’s modification, not from the meeting.
Facilitator verifies completion at the 48-hour mark. A quick scan of the audit trail confirms that all decisions have been executed. Any unexecuted actions are escalated directly.
The next weekly check-in reflects the new plans. Teams check in against the recalibrated plans, and the first post-recalibration data point provides immediate signal on whether the modifications were well-calibrated.
The 48-hour execution window is the discipline that makes the recalibration meeting worth 45 minutes of leadership time. Without it, decisions made in the meeting become “intentions” that drift into the next quarter’s QBR. With it, the entire hierarchy is recalibrated within two days of the meeting.
What the Meeting Is Not
The recalibration meeting is a specific ritual with a specific purpose. To keep it effective, protect it from scope creep:
| The Recalibration Meeting Is… | The Recalibration Meeting Is Not… |
|---|---|
| A plan health check: are our plans still valid? | A progress review: how are we tracking against targets? |
| A decision forum: we decide to modify, invest, or accept. | A discussion forum: we explore options and defer decisions. |
| Data-driven: pre-read provides the facts. | Narrative-driven: each department tells their story. |
| 45 minutes, strict agenda. | Open-ended, expands to fill available time. |
| Focused on yellows and reds. | A review of every KR in the hierarchy. |
| A mid-quarter ritual held on a fixed schedule. | A reactive meeting called when something goes wrong. |
The most common failure mode is allowing the meeting to become a status review. When someone starts reporting their numbers (“we’re at 42% against a plan of 48%”), the facilitator redirects: “That’s the check-in data. The question for this meeting is: should the plan change?” Status belongs in check-ins. Plan decisions belong here.
Measuring the Meeting’s Effectiveness
After two or three quarters of running the recalibration meeting, assess its impact with these four metrics:
| Metric | What to Measure | Healthy Outcome |
|---|---|---|
| Decisions per meeting | Number of explicit plan modification decisions made during the meeting. | 3–7 decisions per meeting. Fewer than 3 suggests the plans are well-calibrated (good) or the meeting isn’t surfacing real issues (bad). More than 7 suggests the quarter’s initial plans were poorly set. |
| 48-hour execution rate | Percentage of meeting decisions executed within the 48-hour window. | Over 90%. If decisions aren’t being executed, the meeting is generating intentions, not actions. |
| QBR surprise reduction | The number of KR results at the QBR that were “surprises” (i.e., not anticipated by the mid-quarter recalibration). | Decreasing quarter over quarter. The recalibration should catch most issues by week 7, leaving few surprises at week 13. |
| Cascading modification speed | Time from recalibration meeting decision to full hierarchy alignment. | Under 72 hours for all modifications decided in the meeting. The 48-hour execution window plus propagation cascade should close the loop within 3 days. |
Adapting the Format for Different Org Sizes
The 45-minute format described above is optimized for organizations with 3–4 hierarchy levels and 8–15 parent-level KRs. Here’s how to adapt it for other contexts:
Small Organizations (2 levels, 5–10 parent KRs)
Reduce to 30 minutes. The health dashboard and decision segment can be combined since there are fewer KRs to review. The pre-read may be a simple email rather than a formal document. The cross-functional check may not be needed if most KRs are single-department.
Large Organizations (4+ levels, 15+ parent KRs)
Expand to 60 minutes, but maintain the same structure. Add a “triage” step at the beginning: the facilitator identifies the 5–7 KRs that need discussion and skips the rest. Without triage, a meeting with 20 parent KRs becomes a marathon of two-minute summaries that produces exhaustion instead of decisions.
Alternatively, large organizations can run departmental recalibration meetings (30 minutes each, department-level KRs) followed by a company-level recalibration meeting (45 minutes, company-level KRs informed by the departmental meetings). This staged approach prevents the company-level meeting from getting bogged down in departmental details.
Remote and Distributed Teams
The recalibration meeting works well remotely if two conditions are met: the pre-read is distributed and reviewed before the meeting (even more important remotely, because screen-sharing a large dashboard for the first time in a video call wastes precious minutes), and the Profit.co dashboard is screen-shared throughout (everyone should see the same data at the same time). Decisions are captured in a shared document that’s visible to all attendees during the meeting.
The Recalibration Cadence in Context
The mid-quarter recalibration meeting fits into a broader planning cadence that includes three distinct rituals:
| Ritual | Frequency | Purpose | Duration |
|---|---|---|---|
| Check-in | Weekly | Individual KR health: is my plan still valid? Check-Decide-Act. | 3–5 min per KR |
| Recalibration meeting | Mid-quarter (week 6–7) | Hierarchical plan health: are plans aligned across all levels? Decisions made. | 45 min |
| Quarterly business review | End of quarter | Comprehensive assessment: what did we achieve, how did we adapt, what do we carry forward? | 2–4 hours |
Each ritual serves a different time horizon and a different level of analysis. The check-in is the atomic unit: one person, one KR, one decision point. The recalibration meeting is the mid-level integration: one leadership team, all parent KRs, one synchronized health check. The QBR is the macro-level learning: the full organization, the full quarter, the full narrative.
The recalibration meeting is the newest and most underutilized of the three. Most organizations already have check-ins and QBRs. Adding the mid-quarter recalibration is the intervention that connects them — turning weekly signals into quarterly outcomes without waiting for the QBR to discover what went wrong.
The Ritual That Saves the Quarter
Most quarters are saved or lost in weeks 5 through 8. It’s the period when early-quarter assumptions have been tested by real data, when dependencies have either delivered or slipped, and when the gap between plan and reality is wide enough to see but narrow enough to close. After week 8, the remaining time is often too short for meaningful course corrections.
The mid-quarter recalibration meeting is deliberately placed in this window. It creates a structured moment where leadership looks at the hierarchy’s plan health, makes decisions about which plans to modify, and executes those modifications within 48 hours. The meeting itself is 45 minutes. The impact — six weeks of better-aligned execution — is immeasurable.
You can’t control whether your plans need modification. You can control whether you discover the need at week 7 or week 13. The recalibration meeting ensures it’s week 7 — every quarter, on schedule, with data, with decisions, and with follow-through.
One meeting. 45 minutes. The entire hierarchy recalibrated.
Profit.co’s aggregated dashboards, audit trail exports, and inline plan modification make the recalibration meeting data-driven and decision-ready. Start your free trial.