Systems & tools

The notice loop: a week that learns

An open six-step method for running your life on a weekly rhythm: capture, notice, shape, review, learn, repeat. It works on paper, in a notes app, or in a planner. This page teaches the whole thing.

Aleem O'BalogunBy Aleem O'Balogun|Updated |13 min read

The short answer

The notice loop is a six-step method for running your life on a weekly rhythm: capture, notice, shape, review, learn, repeat. Unlike systems that only remember, the loop closes: what your system noticed shapes the week, and what the week taught feeds the next one. It runs in any tool, from paper to a planner app.

Steps

  1. 1

    Capture

    Get every commitment, idea, worry and date out of your head and into one place you trust, the moment it appears. No sorting in the moment; sorting is a different job on a different day.

  2. 2

    Notice

    At a standing time each week, your system shows you what it knows: what is coming with lead time, what is building up quietly, which note you captured three weeks ago now matters. You do not go looking; the system speaks first.

  3. 3

    Shape

    Turn what was noticed into a drafted week: a handful of priorities placed against your real commitments and your real capacity, across the whole of life rather than just work.

  4. 4

    Review

    Look at the draft and decide: keep, change, or drop each piece. Nothing is real until you have said yes to it. This is also where the week that just ended gets its honest reading.

  5. 5

    Learn

    Record what the week taught in a form the next pass will actually use: what slipped and why, what was oversized, what mattered more than planned. One honest line beats a page of reflection.

  6. 6

    Repeat

    Run it again next week, starting from what this week learned rather than from a blank page. The loop compounds; a single pass is just a plan.

Why systems that remember don't change your week

Most personal systems are built to remember. You capture notes, organise them into folders or links, and retrieve them when you think to search. Every part of that is useful, and none of it changes what happens on Thursday. The archive grows; the week stays exactly as reactive as it was. If you have ever kept a beautiful second brain while your actual weeks ran on adrenaline and a calendar full of other people's meetings, you have felt the gap this method exists to close.

The gap is not a missing app. It is a missing shape. Capture, organise, retrieve is a line: it starts at an idea and stops at a search box. A line can hold everything you have ever known and still never put one of those things into your week, because no step in it ever decides anything. The fix is to bend the line into a loop, and to add the two verbs that remembering systems do not have.

The notice loop, named

The notice loop is six verbs run on a weekly rhythm: capture, notice, shape, review, learn, repeat. The six steps above are the whole method; there is no hidden layer. What makes it a loop rather than a routine is the last verb but one: what this week taught is recorded in a form the next pass uses, so every week starts from evidence instead of from optimism.

The loop is deliberately tool-agnostic. It has been run on paper for centuries in pieces; parts of it are the best ideas of the best-known systems, credited below. asambl named it and built a planner around it, but you do not need asambl to run it, and this page teaches it as if you never will.

The line and the loop

A second brain remembers. A planner comes back around.

The same raw material, run two ways. A second brain captures, organises and retrieves, then stops. asambl runs a loop that closes, so each week starts from what the last one learned.

A second brain

a line that ends

  1. Capture

    Clip it, jot it, save it

  2. Organise

    Folders, tags, backlinks

  3. Retrieve

    Search, when you remember to

  4. Then it waits. The library grows; the week does not.

asambl

a loop that closes

  1. Capture

    Straight into your inbox, from any device

  2. Notice

    A weekly digest surfaces what matters and recalls the note that fits

  3. Shape

    asambl drafts the week around it, across your life areas

  4. Review

    You accept, change or decline each block

  5. Learn

    Your corrections feed the next week's brief

  6. Repeat

    Next week starts where this one left off

Notice and Shape are asambl's own words for the two steps a second brain has no name for.

The step other tools skip: Learn

When you rate how a week actually went and note what missed, or leave items unfinished, asambl keeps that as a correction and threads it into the next week's brief. A plan that misfired once is less likely to repeat. It is the weekly-review habit, carried from one week to the next for you, rather than a note you file and forget.

See a week built from the one before

Notice and shape: the two verbs remembering systems lack

Motion schedules. Notion stores. Obsidian remembers. Each is genuinely good at its verb, and none of them has the two in the middle of this loop.

To notice is to have your system speak first. A remembering system answers when asked, which means everything depends on you thinking to ask, on the right day, about the right thing. A noticing system has a standing appointment: once a week it surfaces what is coming with lead time, what has quietly built up, and which of your own captured notes now matters. The passport that expires in eight weeks, the friend's birthday in three, the recipe you saved that fits Thursday. Noticing is what turns an archive into an early-warning system, and it is the reason the loop is named after it: seen early, almost everything in a life is calm; seen late, the same things are emergencies.

To shape is to turn what was noticed into a week you could actually live: priorities placed against fixed commitments, sized to the capacity you really have, across the whole of life rather than just the job. Shaping is where most systems quietly hand the work back to you. The notice loop makes it an explicit step with an explicit output: a drafted week, on one page, that the next verb gets to judge.

Running the loop on paper

The fastest way to believe the loop is to run one pass of it with no software at all.

Capture all week into one pocket note or one inbox page: every stray commitment, idea and date, one line each. On Sunday, sit down for half an hour. First, notice: read the inbox, scan the next four weeks of your calendar, and ask what is coming that needs lead time, what has been building up, and which captured line now matters. Circle at most five things. Second, shape: on one page, write the week's fixed commitments, then place three to five priorities from the circled list into the real gaps, sized honestly. Third, review: read the draft once and strike anything you do not believe. What survives is the plan. At the end of the week, learn: one line at the bottom of the page about what slipped and why. Next Sunday, read that line before you do anything else. That is the whole method.

The template below is that page, ready to copy or print. It is free and it stays free; the loop is an open method, and the point of this guide is that you can run it forever with a pen.

The notice loop, on one pagenotice-loop.md · free to copy, yours to keep
# The notice loop: week of ____________

## Captured this week (one line each, no sorting)
-
-
-

## Notice (Sunday, 10 minutes)
Read the inbox above, scan the next 4 weeks of the calendar, then answer:
- Coming up that needs lead time:
- Quietly building up:
- A captured line that now matters:

## Shape (10 minutes)
Fixed commitments this week:
-
Three to five priorities, placed in the real gaps, sized honestly:
1.
2.
3.

## Review (5 minutes)
Read the draft once. Strike anything you do not believe. What survives is the plan.

## Learn (end of the week, one honest line)
What slipped, what was oversized, what mattered more than planned:
-

Next week: read the Learn line first, then start again.

The one-page runner: paste it into any notes app or print it. One page per week; the Learn line at the bottom is what the next week reads first.

Where the loop sits in the canon

The loop stands on well-known shoulders, and naming them matters more than pretending novelty.

From Getting Things Done it takes its respect for capture and for a standing weekly review; David Allen proved forty years ago that a mind is for having ideas, not holding them. GTD closes its loop tightly for tasks and projects; the notice loop widens the frame to a whole life and moves the initiative to the system, which speaks before you ask. From Building a Second Brain and Tiago Forte's PARA it takes the insistence that notes should be organised for action, then adds the scheduled pull that storage systems leave to chance. The Zettelkasten tradition solves a different problem beautifully, thinking and writing, and is a fine companion to the loop rather than a competitor. Ryder Carroll's bullet journal deserves particular credit: its monthly migration is the closest ancestor of the notice verb, run by hand with a pen, and anyone who has felt migration work knows why noticing earns its place in the loop's name.

At the far end sits Daniel Miessler's TELOS, an open framework for writing down your problems, missions, goals and metrics, now the context layer of his open-source LifeOS project. TELOS answers a question the loop deliberately does not: what is all this in service of? The two compose naturally. A purpose stack like TELOS is the layer above; the notice loop is the weekly engine underneath that turns whatever you are aiming at into what actually happens between Monday and Sunday.

Where the loop breaks, and the honest fixes

Every failed system fails at a joint. The loop has five, and knowing them is most of the maintenance.

  • Capture without a pull
    • the inbox grows and nothing reads it
    • the fix is the standing notice appointment, not more capturing
  • Notice without lead time
    • you scan only the coming week, so everything arrives urgent anyway
    • scan four weeks, not one
  • Shape without honesty
    • the draft assumes a heroic week
    • size to the capacity you actually had last week, not the one you wish for
  • Review as rubber stamp
    • you accept the whole draft unread
    • strike one thing every week on principle until reading it becomes real
  • Learn skipped
    • the week ends and nothing is written
    • one line is enough, and next week reading that line comes before everything

How asambl runs the loop

asambl is this loop built as a planner, and this section is the only one where the product appears. Capture lands in one inbox from desktop or phone. Notice is a deterministic weekly digest: dates with lead time, quiet build-ups, and the captured note that fits the coming week, surfaced without being asked. Shape is a drafted week across your life areas, sized to your declared capacity, with a Plan A, B and C for the weeks that will not go to plan. Review is the gate everything passes: you keep, change or drop each block, and nothing reaches your calendar until you say yes. Learn is your corrections and your week rating, threaded into the next draft's brief, so a plan that misfired once is less likely to repeat. Repeat is a Sunday.

asambl helps you notice what matters before it becomes urgent. That sentence is the whole product; the loop is why it is possible. And the honest bridge, stated plainly: you can run the notice loop forever without asambl, on the template above. asambl exists because the middle verbs, noticing and shaping, are the ones that cost the most willpower every single week, and they are the ones software can carry without taking the decisions away from you.

Seen early, almost everything in a life is calm. Seen late, the same things are emergencies.

Sources

The canon this method stands on, credited and linked. The notice loop itself is open: use it in any tool, teach it, adapt it; attribution with a link is appreciated.

  • David Allen, Getting Things Done (gettingthingsdone.com): capture discipline and the weekly review.
  • Tiago Forte, Building a Second Brain and PARA (buildingasecondbrain.com): organising notes for action.
  • The Zettelkasten tradition (zettelkasten.de): the thinking-and-writing companion, a different job done well.
  • Ryder Carroll, the Bullet Journal method (bulletjournal.com): migration, the hand-run ancestor of the notice verb.
  • Daniel Miessler, TELOS (danielmiessler.com/telos) and LifeOS (github.com/danielmiessler/LifeOS): the open purpose stack that composes with the loop from the layer above.
← All guides