If you read Tuesday's piece on the season's harvest, you already have the inner foundation. You understand the difference between decision-making and true harvest, and you've likely already run parts of your own quarter through the Harvest Inventory's four questions. This post is the structural companion to that one, the implementation architecture that works best once the inner foundation is already in place.

Understanding the difference between what to carry and what to release is necessary, but it isn't sufficient on its own. Insight without a process tends to evaporate the moment your inbox fills back up. What you need next is a system, something concrete enough to run this week, specific enough to actually finish and simple enough that you'll return to it every quarter instead of only when a season ends dramatically enough to force the question.

This post delivers that system in full: the Complete, Carry, Release method, the exact AI-assisted workflow for running it on your real Q3 project list, and a step-by-step protocol you can complete in a single sitting.

Why Season Close Comes Before Q4 Planning

Most planning frameworks assume you're starting from a clean slate. List your goals, map your quarter and build your calendar. What almost none of them account for is the fact that you're rarely starting clean. You're starting on top of a quarter that just happened, full of projects at various stages of completion, commitments made under different circumstances and mental residue from decisions you haven't fully processed yet.

Planning on top of that residue doesn't fail dramatically. It fails quietly. The new quarter's goals compete with old quarter's unfinished business for the same limited attention, and because the old business is invisible on any planning document, you experience the cost as vague overwhelm rather than a clear, nameable problem. Three weeks into a new quarter, momentum has mysteriously stalled, and most CEOs blame the new plan rather than the old mess it was built on top of.

This is why end of quarter business planning that skips straight to goal-setting so often underperforms its own ambition. The plan itself might be excellent. But a plan is only as clean as the ground it's built on, and an unclosed quarter is not clean ground, no matter how good the intentions behind the new goals are.

Season close exists to remove this hidden cost before it accumulates. It isn't a nice-to-have ritual for CEOs with extra time. It's the load-bearing step that determines whether everything built afterward has clear ground to stand on. Skip it, and you're not saving time. You're borrowing it from a future week that will have to deal with the same unfinished business anyway, usually at a less convenient moment.

Think of it the way a contractor thinks about a foundation. Nobody sees the foundation once the building goes up, and nobody budgets extra time for it happily. But every structural problem that shows up later traces back to something that wasn't properly settled before the framing started. A quarter is the same. The parts of it that go unclosed don't disappear once Q4 begins. They become the cracks that show up in month two, usually blamed on the new plan rather than the old ground it was poured onto.

The Complete, Carry, Release System

Here is the full method, named so you can return to it every quarter without reinventing the process each time.

Complete identifies which open loops from the closing quarter genuinely need finishing before you move forward and closes them deliberately rather than letting them drag into the next season by default.

Carry names, specifically and in writing, what this quarter actually built that has ongoing value: the capacities you developed, the systems now in place, the relationships strengthened, the assets created. This is not a highlights reel. It's an honest inventory of what compounds.

Release identifies what does not come forward: the strategies that ran their course, the commitments made for reasons that no longer apply, the ways of working that belonged to a version of the business that has already evolved past them.

Run in that order, this system takes an unfinished, sprawling quarter and turns it into a clean, three-part inheritance for the next one: a short list of things actually finished, a short list of things worth building on, and a short list of things you've consciously set down. Everything else, by definition, either falls into one of these categories or wasn't significant enough to need sorting in the first place.

Notice what this system deliberately does not ask you to do. It doesn't ask you to evaluate whether the quarter was good or bad, successful or disappointing. That kind of judgment tends to short-circuit honest sorting, because a quarter you've labeled disappointing gets everything in it dismissed, including the genuine capacities it built, and a quarter you've labeled a win gets everything carried forward uncritically, including strategies that only worked because of circumstances that won't repeat. Complete, Carry, Release sidesteps the verdict entirely and goes straight to the more useful question: regardless of how this quarter felt, what specifically is worth doing something about now.

Phase One: Complete

Start here because unfinished work is the loudest source of mental noise, and closing even a few genuine loops creates immediate, felt relief.

Begin by listing every project, deliverable and commitment from this quarter that isn't fully closed. Resist the urge to filter as you list. Write down everything, including the small things you've been quietly ignoring.

Now apply one filter to the full list: is this worth completing or is it worth abandoning? Not everything unfinished deserves to be finished. Some open loops were never that important in the first place and completing them now would cost more attention than simply closing the loop by deciding, consciously, not to finish it. Both completion and deliberate abandonment count as closure. What doesn't count is leaving something in limbo, neither finished nor released, quietly draining attention indefinitely.

For the items worth finishing, be specific about what "finished" actually means. Vague completion criteria are how projects linger for months. "Finish the client project" is not a completion criterion. "Send the final deliverable and the closing email" is. Write the specific, concrete action that would let you cross each item off permanently, then schedule those actions before doing anything else on this list.

For the items worth abandoning, close them with the same intention you'd give a completed project. Send the email that says this isn't moving forward. Archive the half-built system. Cancel the subscription for the tool you stopped using. An abandoned loop that's been formally closed stops costing you attention. An abandoned loop that's just been ignored keeps costing you attention indefinitely, which defeats the entire purpose.

One more distinction worth naming here: completing and perfecting are not the same task, and confusing them is how a twenty-minute closing action turns into a three-week delay. If the client deliverable is genuinely done but you're tempted to polish it further before sending, that's perfectionism borrowing the language of completion. Send what's actually finished. Save the polishing instinct for work that's still meant to grow.

Phase Two: Carry

This phase is where most quarterly reviews stop short, because naming what actually compounds requires more precision than simply listing what happened.

Go through the quarter category by category: capacities, systems, relationships, assets. For capacities, name specifically what you can now do that you couldn't reliably do three months ago. For systems, name what processes or structures now exist that didn't before and confirm they're actually documented somewhere rather than living only in your head. For relationships, name which connections strengthened this quarter in ways that will matter going forward. For assets, name the concrete things created that have ongoing value: content, tools, templates, positioning language.

The discipline here is specificity. "I got better at boundaries" is not carry-worthy until you can name the actual mechanism: "I now have a script I use for declining scope creep requests and I've used it successfully four times." The specific version is what actually transfers into the next quarter. The vague version evaporates the moment you stop thinking about it directly.

Write this list down somewhere you'll actually see it again, not buried in a journal you'll never reopen. This becomes your starting resource inventory for Q4: not a list of goals, but a list of what you already have to build with, which changes the entire posture of the planning that follows.

This inventory also does quiet work on your own self-perception that a highlight reel never manages. A highlight reel tells you what happened. A specific carry-forward list tells you who you've become, in language concrete enough to actually believe. That's a different kind of evidence than a win, and it tends to hold up far better under pressure because it isn't dependent on external validation to feel true.

Phase Three: Release

Release is the phase most CEOs skip, not because it's difficult intellectually but because it requires actively choosing to stop something and stopping feels riskier than continuing by default.

Look specifically for three categories: strategies that produced results only because of circumstances that no longer apply, commitments made for reasons that have since resolved or changed, and ways of working that were sustainable for a season but would create real cost if continued indefinitely. None of these need to have failed to qualify for release. Something can have worked beautifully and still belong to a season that's over.

For each item you identify, write one sentence naming what it gave you and one sentence naming why it's being released now. This isn't sentimental, it's precise. The first sentence protects the value of what happened. The second sentence gives you permission to stop without the decision feeling arbitrary or wasteful.

Then take one concrete action for each release: an email, an archived file, a canceled subscription, a direct conversation. A release that only happens in your head tends to quietly resume the moment pressure returns. A release that's been enacted in the world stays released.

If you find yourself unable to take the concrete action, even after writing both sentences, that resistance is worth sitting with rather than pushing past. Sometimes it signals the release is premature and the thing still has real work left to do. More often, it signals an identity attachment rather than a genuine strategic reason to continue, and naming that difference honestly is itself part of the release.

It's worth saying plainly that release is not the same as failure and treating it that way is what makes so many CEOs hold onto strategies well past their useful life. A marketing approach that generated real revenue for two quarters and then stopped scaling didn't fail. It did its job and its job is now finished. Naming it that way, out loud or in writing, changes the entire emotional weight of setting it down.

The AI Tools Section

Running the full Complete, Carry, Release system by hand across an entire quarter's worth of projects can feel like its own project. This is exactly the kind of dense, structural work that AI handles well, freeing your actual attention for the judgment calls only you can make. The tools do the sorting and organizing. You make every real decision.

Claude (claude.ai) does the heavy lifting on the initial audit. Export or list every project, commitment and deliverable from this quarter, then give Claude a simple prompt: "Here is my full list of Q3 projects and commitments. Sort each one into Complete, Carry, or Release, and give a one-sentence reason for each suggestion." Review every suggestion rather than accepting it wholesale. Claude is excellent at surfacing patterns you might miss across a long list, but the final call on what's genuinely worth carrying forward is yours alone. Use a second prompt for phase two specifically: "From this list of what I'm carrying forward, help me draft a one-page Q4 starting point document that names my available capacities, systems, relationships and assets in specific, concrete language." This becomes the actual resource document you build your Q4 plan on top of.

Notion (notion.so) is where the sorted lists live once Claude has helped you organize them. Create three simple database views: Complete, Carry, and Release. As you close loops in phase one, move them into a Complete archive rather than deleting them, so there's a record of what actually got finished this quarter. The Carry view becomes your living Q4 starting point document, the one you'll actually open when planning begins.

Claude, used a third time, helps with a task most CEOs never think to run: identifying which content assets from the quarter have compounding value worth investing in further. Give Claude a list of what you created this quarter: blog posts, offers, frameworks, lead magnets, social content. Ask: "Which of these show signs of compounding value, meaning ongoing engagement, repeat requests or organic sharing, and which were one-time efforts that don't need further investment?" This turns a vague sense of "that did well" into a specific list of what's actually worth building on in Q4, rather than starting every new content push from scratch.

Throughout all of this, the tools organize and surface patterns. They do not decide what matters to you. A capacity that mattered enormously to your own growth this quarter might look unremarkable in a sorted list, and only you know that it belongs in the Carry column regardless of what the pattern-matching suggests. Keep that judgment firmly in your hands throughout.

The One-Sitting Season Close

Here is the complete protocol, structured to be run in a single sixty-to-ninety minute sitting rather than spread out indefinitely, because a season close that drags on for weeks tends to never actually finish.

Minutes 0 to 20, Complete. List every open loop. Filter into finish or abandon. Schedule the specific finishing actions. Send any closure emails for abandoned items immediately, while you have the momentum.

Minutes 20 to 45, Carry. Work through capacities, systems, relationships and assets category by category. Write the specific version of each, not the vague one. Save this as your Q4 starting point document.

Minutes 45 to 60, Release. Identify what belongs to the closing season. Write the one sentence of what it gave you and the one sentence of why it's being released. Take one concrete action per item before the sitting ends.

Minutes 60 to 90, optional but recommended. Run the Claude audit on your full project list to catch anything the manual pass missed, and build your one-page Q4 resource document from what you carried forward.

Block this on your calendar as a single, protected appointment with yourself, the same way you'd protect a client meeting. A season close that gets squeezed into the margins of a busy day rarely gets finished properly and an unfinished season close defeats its entire purpose.

A few practical notes on running this well. Do it somewhere you won't be interrupted, phone genuinely out of reach rather than face down beside you. Have your full project and task list pulled up before you start the clock, so the sitting is spent sorting and deciding rather than hunting for what needs sorting. And resist the urge to do this across several short sessions spread over a week. The value of the compressed sitting is momentum: each phase builds on the clarity of the one before it and that clarity tends to dissipate if too much time passes between phases.

If ninety minutes feels like more than you can protect right now, run a shortened twenty-minute version instead of skipping the practice entirely: five minutes each on Complete and Release, ten minutes on Carry, since Carry is the phase most likely to be skipped under time pressure and the one that gives Q4 its actual starting resources. A shortened season close still beats no season close by a wide margin.

Tuesday's piece gave you the philosophical case for why harvest matters more than decision-making at the close of a season. This post gives you the actual mechanism for doing it: a named system, an AI-assisted workflow and a protocol you can run this week. Held together, they mean Q4 doesn't start as a fresh burst of energy layered on top of an unfinished Q3. It starts on ground you've actually cleared, carrying only what's genuinely yours to build with.

If you want the deeper version of this work, including the full journaling letter and the exact prompt sequence for running your own audit end to end, this week's Plus edition walks through it in full.

Related Reading

● The Season's Harvest: How to Carry the Right Things Into What Comes Next
● The Honest Inventory: How to See What Your Business Has Already Become
● The Worth Audit: How to Find Where Your Business Is Underselling Before the Client Even Arrives
● Discernment Over Decision: How Deep Self-Knowledge Changes Your Relationship With Opportunity