Close your week: the Friday shutdown

A system without a weekly close slowly fills back up, so the Friday shutdown is what keeps your head empty for good

You are at the Close step of the Empty-Head Loop, the move that makes everything before it sustainable. A weekly review for freelancers is not bureaucracy, it is the maintenance pass that keeps the inbox trustworthy, the calendar honest and the head empty. The shift here is that a review agent drafts the recap and surfaces the open loops, so the close takes thirty minutes rather than the two hours that made you skip it.

By the close you will have a repeatable Friday shutdown checklist that empties the inbox, plans the next week, and ends with a genuine boundary so the weekend is yours.

The weekly close is maintenance, and a system without maintenance fails

Every step in this loop degrades over a week. The inbox fills, the calendar drifts from reality, completed projects linger, new commitments arrive uncaptured. The Friday shutdown is the scheduled maintenance that resets all of it, and it is the single habit that separates a system that lasts from a productivity binge that collapses in a fortnight.

It does a second job that matters as much: it creates an ending. A one-person firm has no closing bell, so the work bleeds into the evening and the weekend because nothing ever declares it done. The shutdown is that declaration. You review, you plan, you close the laptop, and the week is genuinely over.

The Friday shutdown checklist

Run this every Friday, same time, blocked on your calendar as an anchor:

1. Empty the inbox to zero. Process every captured item from the week through the Clarify routine. The inbox starts the new week empty.
2. Review the action and project lists. Mark what is done, update what moved, kill what died. Every open project should have a clear next action.
3. Review open loops and someday. Scan the someday list for anything now ready to activate, and the calendar for slipped blocks to reschedule.
4. Plan next week. Rough-block the coming week to 60% capacity from the updated list, so Monday starts with a plan rather than a scramble.
5. Write the recap and close. Note what got done, what slipped and why, and one thing to change. Then shut the laptop and stop.

Let the review agent draft the recap

The mechanical parts of the close, gathering what happened and surfacing what is open, are work an agent does in seconds. The review agent reads your completed and slipped tasks for the week, your calendar, and your project list, and drafts the recap and the open-loops summary for you to react to.

A worked prompt:

You are my review agent. From this week's completed tasks, slipped tasks and calendar, draft a recap with: tasks completed, tasks slipped and their stated reasons, projects that advanced, projects that stalled, open loops still unresolved, and three suggested priorities for next week. Flag any project with no next action. Keep it to one screen. Do not invent outcomes I did not record.

You read its draft, correct the few things it misjudged, and use its suggested priorities as the starting point for next week's plan. The close becomes a thirty-minute review of a draft rather than a two-hour build from a blank page, which is precisely why it stops getting skipped.

A solo operator's Friday shutdown: a worked example

Take a freelance developer running a one-person consultancy, the sort whose weeks blurred together with no clear end, so Saturday mornings were spent half-working and quietly resentful. The challenge was that the developer had tried weekly reviews twice and abandoned both, because a manual review took close to two hours and always lost to Friday-evening fatigue.

The approach was the checklist above with the review agent doing the gathering. The agent drafted the recap and open-loops list each Friday; the developer reviewed it, planned the next week to 60%, and closed.

The measurable result over two months: the shutdown settled at about thirty-five minutes and, because it now fit, ran every single week without a miss, where two prior attempts had collapsed inside a fortnight. The developer reported reclaiming Saturday mornings entirely, because the week now had a clean ending instead of a frayed one.

INTERVIEW EWOUD: What does your own Friday shutdown look like, and what was the moment you realised closing the week properly was what finally gave you the weekend back?

Pitfalls at the close stage

Skipping it when busy. The busy weeks are exactly the weeks the system most needs resetting. Protect the shutdown block hardest when the week was hardest.

Letting it sprawl. A two-hour review will not survive. Use the agent to keep it near thirty minutes, or it gets dropped.

Reviewing without planning. A review that does not produce next week's rough plan leaves Monday a scramble. Always end on the plan.

Not actually stopping. The point of the close is the boundary. If you review and then keep working, you have skipped the most valuable step.

With the week closed cleanly and the next one already roughed out, the loop is complete and repeats. The final chapter pulls the whole Empty-Head Loop together, points you to the agents that run it, and gives you the single action to start today.