Weekly close
A weekly close is the recurring leadership ritual where every KPI owner reports actuals, the team reviews variance, and any breaking commitment gets a named action and a name.
A **weekly close** is the recurring point in a leadership week — typically a single hour on a fixed weekday — when every owner submits the actual value of the KPI they own, the leadership team reviews variance against plan, and any commitment that is breaking gets a named action attached to a named human. Everything before the close is collection. Everything after is execution.
Why it matters
Without a fixed close, KPI reporting becomes a function of who pushes hardest. The founder asks the head of sales for the pipeline number on Wednesday because the board call is on Thursday. The head of sales asks an SDR for the underlying activity numbers Wednesday afternoon. The numbers get assembled retroactively, often partially, often by the wrong person, and almost always after the moment when an action could have changed the result. The week is over before the leadership team sees it.
The close inverts the flow. The deadline exists before the question. Owners submit to a known schedule, not in response to a request, and the consolidated signal lands on the leadership team's desk on the same day every week regardless of whether the founder is in the building.
Anatomy of a real close
- A fixed weekday and time, picked once and not moved. Predictability is the entire mechanism.
- A named owner per KPI — one human accountable for one number, not a team or a department.
- A submission deadline that precedes the review by a small, fixed window (typically 60–90 minutes), so the consolidated picture is ready before the leadership team meets.
- A consolidated signal — one document, one screen — published immediately after the review, not assembled later in the week.
- A consequence for missed submissions that is visible to the team without the founder having to chase it. The signal carries the gap.
What it is not
- Not a meeting. A meeting is the optional second step. The close is the submission, the consolidation, and the signal — most of which happen without anyone being in a room.
- Not a dashboard refresh. A dashboard is a reading surface. The close is the act of producing the reading and deciding what to do about it.
- Not a status update from the founder. The point of the close is to remove the founder as the consolidator. If the founder is still the one assembling the picture on Friday afternoon, the close has not been installed.
Common failure modes
The most common failure is a close with no consequence for missed submissions — owners learn within three weeks that the deadline is rhetorical, and the cadence collapses back into chase. The second most common is a close that runs but produces no consolidated artifact, so the leadership team reviews their KPIs in isolation and never gets a single picture of the week. The third is a close scheduled too late in the week, which leaves no operating room to act on what it surfaces before the next cycle begins.
All three failures share one root cause: the close was treated as a meeting on a calendar rather than as a system with inputs, outputs, and a published signal. A meeting that no one prepares for is a status update. A close is a closing of the books on the operating week.