Muse for Weekly Review: The Friday Shutdown, What Shipped, and Next Week's Top Three
A weekly review setup for Muse: a Friday shutdown that clears every inbox, checks what actually shipped against the calendar, and leaves next week with three named priorities.

Friday afternoon is where the week either closes or carries over. If you leave with loose threads still in your head, you rehearse them all weekend and start Monday by rebuilding the list you meant to write on Friday. A weekly review fixes that in one sitting. You clear what piled up, you check what actually happened, and you decide what next week is for before anyone else fills it.
Muse does the assembling work in that sitting. It processes the inboxes you paste in, compares the calendar and the task list against what shipped, checks the waiting-for list, and drafts next week’s top three from the evidence you give it. You make the calls on what to drop, what to chase, and what matters most. Muse never marks work done that the record does not show as done, and it never invents a priority you did not choose.
The structure comes from David Allen’s Getting Things Done. Allen calls the weekly review the critical success factor for keeping the system trustworthy, and his official checklist runs in three phases: Get Clear, Get Current, and Get Creative. Cal Newport adds the closing move from Deep Work, a shutdown ritual that ends with the phrase “shutdown complete” once every incomplete task has a trusted plan or a place where it will be revisited. This lesson combines the two: Allen’s review for the content, Newport’s shutdown for the ending.
The short version
- Run the review in one Friday sitting, in order: Get Clear, Get Current, then choose next week’s top three. Do not plan next week before the inboxes are empty.
- Get Clear means every inbox reaches zero for the review: email, task inbox, notes, and the items still only in your head. Each item becomes a next action, a waiting-for entry, a reference note, or a deletion.
- Get Current means the lists match reality: mark what shipped, review last week’s calendar for follow-ups, review next week’s calendar for prep, check waiting-for items, and give every active project one current next action.
- End with three outcomes for next week, not a long task list, and a shutdown note that records what is parked and where. If a top three item has no time on next week’s calendar, it is a wish, not a plan.
- The failure mode to watch for is a review that copies last week’s plan forward without checking it against the calendar. The fix is a rule that Muse works only from the calendar and lists you paste in that sitting.
The Setup: The Friday Shutdown
Call the whole arrangement the Friday Shutdown. The example I run it against is a project lead at a 14-person services firm who runs client delivery and internal ops. She blocks Friday 3:30 to 4:15 p.m., closes the door, and works from four inputs she pastes into Muse in order: her email inbox export for the week, her task list with statuses, her calendar for last week and next week, and a waiting-for list with a name and a date for each item. Her outputs are fixed every week: a cleared-inbox log, a shipped-versus-planned note, a waiting-for chase list, and a one-page plan for next week with three outcomes at the top.
The setup holds together on a few standing pieces. A standing instruction from our memory guide holds the durable parts: the Friday slot, the four inputs in order, the rule that nothing is marked done without evidence in the pasted material, and the names of the projects that are paused on purpose so they are not flagged as stalled. Each week’s inputs follow the same discipline as a task brief written for an agent: what the week was supposed to deliver, what the sources are, and what done looks like for the review itself. The reminder and the first inbox sweep run as a scheduled routine, so the sitting starts with the material gathered rather than with 10 minutes of hunting for it. The daily version of the same habit is the nightly audit, a short evening pass that keeps the Friday job from becoming a week’s worth of sorting in one go.
The review borrows its record discipline from the meetings lesson, where an action item counts only when it has an owner, a date, and a stated outcome, and its numbers discipline from the spreadsheets lesson, where a total in the summary must match the rows underneath it. A shipped list in the weekly review follows the same rule. If the calendar shows a launch meeting on Tuesday and the task list still shows the launch as in progress, the review surfaces that gap instead of smoothing it over.
| Phase | What you check | What leaves the phase |
|---|---|---|
| Get Clear | Email inbox, task inbox, notes, head | Every item sorted to next action, waiting-for, reference, or delete |
| Get Current | Action lists, last week’s calendar, next week’s calendar, waiting-for, projects | Shipped list that matches the record, chase list, one next action per project |
| Choose and close | Someday list, next week’s fixed commitments | Three outcomes for next week, parked items named, shutdown note written |
Prompt 1: Get Clear and Empty Every Inbox
Run this first, before you look at next week. Allen’s Get Clear phase has three steps: collect loose papers and materials, get “IN” to zero, and empty your head. “IN” here is every place work lands during the week, not just email. Process each item completely in the sitting. An item you leave as “still in the inbox, will deal with it Monday” is an item your head keeps carrying.
Process the inboxes below for my weekly review. Return: (1) Sorted list, grouped as Next actions, Waiting for, Reference, and Delete. For each next action, write it as one physical next step with an owner as named below and a date if the material below gives one. For each waiting-for item, write who I am waiting on, what I am waiting for, and the date I recorded it. (2) Needs a decision: any item where the material below does not say what should happen next, listed separately with the exact wording from below. (3) Mind sweep prompts: based only on the projects and names below, list questions that would surface anything I have not captured, for example a project with no item in any inbox. Rules: use only the material below. Do not invent an owner, a date, or a next step. Do not mark anything done. If an item is unclear, put it under Needs a decision instead of guessing.
Email inbox for the week: [paste it]. Task inbox and notes: [paste them]. Loose items still in my head, as I dictate them: [write them]. Active projects and owners: [paste them].
Read the Needs a decision list yourself and decide each item in the sitting. That list is the review working as intended. It shows you exactly where the system was vague, and clearing it on Friday is cheaper than rediscovering the same ambiguity on Tuesday.
Prompt 2: Get Current and Check What Actually Shipped
Run this second, with last week’s plan beside the record of the week. Allen’s Get Current phase reviews action lists, previous calendar data, the upcoming calendar, the waiting-for list, project lists, and any relevant checklists, and it requires at least one current action item on each project. Compare what you said would ship with what the calendar and the task list show as shipped, and flag what slipped without anyone deciding to slip it.
This is also where the waiting-for check belongs. Record a follow-up action for anything overdue, and check off anything that arrived. A waiting-for item with no follow-up date gets forgotten.
Compare last week’s plan with the record below and return my Get Current review. Return: (1) Shipped: items the record below shows as completed, each with the evidence from below, for example a completed status or a calendar event that happened. (2) Slipped: items on last week’s plan with no completion evidence below, each with its last recorded status exactly as written below. (3) Calendar follow-ups: action items triggered by last week’s calendar events, and prep actions triggered by next week’s calendar events, each with a date from the calendar below. (4) Waiting-for check: every waiting-for item, marked as arrived, still waiting within its date, or overdue with a draft follow-up line I can send. (5) Project check: every active project from the list below, with its one current next action, or flagged as no next action recorded. Rules: use only the material below. Do not mark an item shipped unless the evidence below says it shipped. Write not recorded where the material does not say. Do not invent a metric, a date, or a reason for a slip.
Last week’s plan and top three: [paste them]. Task list with current statuses: [paste it]. Last week’s calendar and next week’s calendar: [paste them]. Waiting-for list with names and dates: [paste it]. Active project list: [paste it].
Read the Slipped list without rewriting it. Some slips are fine, because the week changed and the work mattered less than what replaced it. Close those in Prompt 3. The slips that matter are the ones nobody chose, where a project had no next action or a waiting-for item sat past its date. Fix the system cause in the review, a missing next action or a missing follow-up date, rather than promising to try harder next week. That project-by-project check is the same habit the ops manager pattern applies across a set of routines, one place that verifies the other lists are still current.
Prompt 3: Choose Next Week’s Top Three and Shut Down
Run this last, and keep it short. Allen’s Get Creative phase reviews the someday/maybe list, promotes anything that has become active, deletes what no longer interests you, and leaves room for a new idea. Then you choose. Three outcomes for next week is the working limit in this setup. An outcome is a result, for example “client report sent,” not an activity, for example “work on report.” Place each outcome against next week’s calendar from Prompt 2. If there is no open block large enough for the work, name what moves or what drops before you close the review.
Newport’s shutdown is the final minute. Every incomplete task now has either a plan you trust or a place where it will be revisited, which for this setup is the parked list in the shutdown note. Write the note, read it once, and end the week.
Draft next week’s plan and my shutdown note from the review below. Return: (1) Top three outcomes for next week, chosen only from the candidates I write below, each written as a result, with the calendar block from next week’s calendar below where the main work will happen, or flagged as no block available. (2) Parked on purpose: items from the slipped list below that I mark as parked, each with where it is recorded and the date it will be revisited, using only the dates below. (3) Someday check: items from the someday list below that the review shows are now active, and items to delete, listed separately for me to confirm. (4) Shutdown note, five lines maximum: what shipped this week in one line, the top three for next week, anything overdue that has a follow-up date, what is parked and when it returns, and one line naming the first task for Monday morning. Rules: use only the material below and the candidates I write. Do not add a fourth outcome. Do not invent a calendar block, a date, or a result. If a top three outcome has no block available, keep it in the list and flag it, do not quietly drop it.
Candidates for next week’s top three, in my order: [write up to five]. Slipped list and shipped list from this review: [paste them]. Next week’s calendar: [paste it]. Someday list: [paste it]. Items I am parking, with revisit dates: [write them]. First task for Monday: [write it].
Send any follow-up drafts from Prompt 2 before you write the shutdown note, or schedule them with a date in the note itself. A shutdown note that says a chase is handled when the draft is still sitting unsent is the one crack that lets the weekend rehearsal back in.
What Can Go Wrong
The common failure is a review that trusts the plan instead of the record. You paste last week’s top three, Muse carries them forward in polished language, and the shipped list reads well while saying nothing true, because no calendar or task status was ever checked against it. It happens when the inputs are thin (a plan with no statuses, a calendar with no outcomes), and it gets worse over weeks because each review inherits the last review’s wording.
The fix is an evidence rule you keep in the standing instruction: Muse may write shipped only when the pasted record shows a completed status or a held event, it writes not recorded everywhere else, and you read the Slipped list first at the next review. If Muse flags a project as no next action recorded three Fridays in a row, the project is not stalled by accident. Decide in the sitting whether to give it a next action, park it with a revisit date, or close it, and record that decision in the shutdown note so the fourth Friday does not ask the same question.


