The managed close playbook. Every Sunday night, in eight minutes.

Playbook · Chapter overview · v2.2 (Jul 23, 2026)

01Text primitives.

Sunday at 8 p.m., the operator who closes the week cleanly does the same three things every time: reads runway from a written artifact, updates the artifact, and closes the book. Nothing about the number changes on Monday morning; the reading of it does.

The managed close is not a longer weekly review. It is a shorter one, done in the same order every week, so the ritual is invisible and the derivative work is the point. What follows is that ritual, rendered as a component library so you can see what the reader page can hold before you download the PDF.

The lede is a lighter serif-adjacent body class used at the top of chapters and inside part breaks to slow the eye down between dense sections.

02Quotes.

Two treatments live in the reader. The default cmp-quote is a soft-plum blockquote for pulled sentences. The attributed variant carries a source line for external voices.

The managed close is not a longer weekly review. It is a shorter one, done in the same order, so the ritual is invisible and the derivative work is the point.

Every operator who eventually broke their cash panic did the same swap: they stopped opening the bank app and started deriving runway once a week.

— Maya Williams, Co-Founder & CEO, Cohesion Insight

03Images.

The reader page supports three figure treatments. Standard 16:9, dark tile, and before/after two-column. All three render inside a card with a caption strip beneath.

04Lists, checklists, steps.

Three list treatments. Plain unordered lists for reading, checklists for do-this-Sunday work, and numbered steps for procedural sequences.

Plain reading list

• The bank balance is a lookup, not a decision.
• Runway is derived. It is an artifact, not a stat.
• Rituals survive because they are short, not because they are important.

Checklist

• Screenshot the bank balance into your ops doc.
• Divide the last 90 days of expenses by three.
• Write balance ÷ monthly burn = runway in months.
• Close the browser tabs. The artifact is the point.

Numbered steps

05Stats, callouts, asides.

Three inline emphasis blocks. A pull-stat card foregrounds a number with a citation. Callouts flag a tip, a warning, a note, or a key insight. Asides sidebar a related idea without breaking the reading line.

06Data, code, tables.

Three technical blocks. A code snippet with an optional caption for the reader's own spreadsheet formula. A data table for weekly comparisons. And a part-break to end the chapter cleanly.

=ROUND(B2 / (SUMIFS(expenses[amount], expenses[date], ">="&TODAY()-90) / 3), 1)

Runway in months, computed in the ops doc. B2 = current balance. Denominator is trailing 90 divided by 3, so a slow month does not skew the derivative.

07Listicle rows.

Numbered listicle rows are the reader's long-form list treatment. Each row carries a meta strip, a bolded claim, and a body paragraph. Use them for signals, symptoms, and heuristics — anything you want the reader to scan first and read second.

1. 01
   Signal · Cash · High impact

   You checked the derived number and it disagreed with your gut.

   Almost always means one big AR line skewed the trailing 90. Look for a single invoice larger than 2× the median, recompute without it, and see if the runway shifts. If yes, you do not have a runway problem, you have a concentration problem.

2. 02
   Signal · Burn · Medium impact

   Two months in a row, monthly burn jumped 15%+ vs. the trailing average.

   Not a fire, but a smoke alarm. Something got hired, subscribed, or renewed. Track down which line moved and decide if it is structural or seasonal. Runway is only as good as the burn number underneath it.

3. 03
   Signal · Process · Low impact

   You skipped the derivation two weeks in a row.

   Not because the number is bad, because the ritual is soft. The moment the derivation feels optional, the balance-check reflex comes back. Re-anchor the ritual to a calendar event you cannot skip.

08Author, CTA, footnotes.

Three closers. An author byline inside the body for a guest voice or a co-author. A mid-body CTA card for a low-friction next step. And a footnote block for citations, keyed to superscripts¹ in body text.

The Monday version of this playbook, delivered against your own numbers, is what Cohesion Insight ships. But the ritual works without us. Steal it — the artifact is the point¹.