Route It While It Is Open

Build a running log to route incoming work and test a deferral limit.

Introduction

30 Second Summary

A message can stay undecided long after you close it. Soon, your inbox contains items you have read but still have not routed anywhere.

In this project, you will create one permanent decision page for routing each newly read item while it is still open. You will test a prewritten deferral limit using one count from your running log.

What You'll Build

You will watch one permanent page guide each open item into a complete route before a prewritten rule turns your latest log sample into a clear outcome.

By the end of this project, you'll have:

  • A permanent routing page that helps you choose what happens to each item while it is still open.
  • A running log where every deferred item includes a specific action day or next-decision day.
  • A prewritten review rule that tests your chosen deferral limit using the most recent twenty entries. A word-only cost note records how the habit felt.
  • Secret Mission: Compare assistant route suggestions with your own choices by writing disagreement reasons without calculating an agreement score.

Are there any prerequisites?

You need twenty waiting items that still need a decision. You can use Notion with Gmail plus Google Calendar, or take the accountless path with paper plus a phone reminder.

Before We Start

A clear commitment makes this habit specific before any hands-on work begins. You’ll define the arriving work you want to route while it is open and why choosing its route before putting it down matters to you.

Create the Permanent Page

Your routing commitment captures the intention. Every later check must be answerable from the page itself.

A permanent page keeps the tool facts visible. It also makes the scope and limits available without relying on memory.

In this step, you'll create that continuing home.

You'll also prepare the source of waiting items. Your reminder tool will be available for the later review date.

In this step, get ready to:
  • Choose a permanent home for the running log.
  • Prepare a source of waiting items plus one reminder tool.
  • Add the three exact page blocks.
Choose one continuing page

The habit needs one place that continues across days. Choose the path that fits the tools you already use.

Notion path

This path uses Notion as the permanent home. A Notion account is required.

  • Open Notion in your browser.
  • Sign in to your Notion account.
  • Follow the on-screen account setup if you choose to create an account.
  • Use the page creation control in the sidebar to create a page under Private.
  • Enter ROUTE IT WHILE IT IS OPEN as the page title.
  • Keep this page open.

Paper path

This path keeps the same protocol without requiring an account. One continuing sheet or notebook page becomes the permanent home.

  • Choose one continuing sheet or notebook page.
  • Write ROUTE IT WHILE IT IS OPEN as the title.
  • Keep this page available for every later entry.

That gives the habit a stable home. Each day continues on this same page.

Prepare the waiting items and reminder tool

Gmail supplies waiting messages for the later batch. Google Calendar stays available for one review reminder.

Google tools

  • Open Gmail in a browser.
  • Sign in to your Google Account if prompted.
  • Follow the account setup flow if you choose to create a Google Account.
  • Confirm that you can see waiting messages.
  • Open Google Calendar in another browser tab.
  • Sign in to the same Google Account if prompted.
  • Confirm that the calendar is available for one later reminder.

Paper and phone

  • Gather your already-waiting paper items.
  • Keep those items beside your continuing page.
  • Open the existing reminder tool on your phone.
  • Confirm that it can save a future reminder.

Your source for the later batch is ready. Your reminder tool is available for the review date.

Having trouble getting access?

  • Finish any Google Account sign-in screen before returning to Gmail.
  • Use the same Google Account in Google Calendar.
  • Follow the paper path if you prefer to continue without an account.
  • Still stuck? Help me prepare Gmail and Google Calendar for this routing project.
Add the exact page blocks

The page must explain the habit without relying on lesson memory. Exact wording also keeps every later check tied to the same protocol.

  • Place these two blocks directly below the page title by copying the text exactly:
THIS PAGE

This is one running log.
Every time I read something new, I choose its route while it is still open.
I do not start a new log each day.
The first count is background only.
It does not decide whether I keep or drop the habit.

WHAT THIS CAN AND CANNOT SAY

Research cannot decide whether this habit fits my work.
This project does not reduce how much arrives.
Defer means choosing not to act on an item now and writing the day when I will act or decide again.
The count measures how often I defer.
It does not measure whether my priorities improved.

Why these two blocks matter

  • The THIS PAGE block establishes one running log. It keeps the first count from becoming a decision.
  • The WHAT THIS CAN AND CANNOT SAY block defines defer. It limits what the measurement can claim.
  • Compare every line with the reference above.
  • Correct any wording differences.

You'll see both block headings beneath the page title. Each sentence appears on its own line.

Text not matching?

  • Undo any formatting change that altered the wording.
  • Check a paper copy one line at a time.
  • Still stuck? Help me compare these two page blocks with the required wording.

The final block records which tools support the protocol. It also keeps the running log separate from the later reminder.

  • Place this tool block directly below the first two blocks by copying the text exactly:
TOOLS

Page: Notion Free.
Mail: Gmail.
Reminder: Google Calendar.
Notion needs a Notion account.
Gmail and Google Calendar use one Google Account.
I may swap any named tool for an equivalent.
Without these accounts, I may use paper and my phone's existing reminder.
The log stays on the page.
Only the reminder goes in the calendar.

What the tool block protects

The block makes every named tool replaceable. It also states where the log belongs.

Only the later reminder belongs in the calendar. The running log remains on the permanent page.

  • Compare every line with the tool block above.
  • Correct any wording differences.

You'll see the TOOLS heading below the first two blocks. Its final line keeps the calendar limited to the reminder.

Tool block incomplete?

  • Check that every tool line appears once.
  • Check that the paper fallback remains in the block.
  • Still stuck? Help me compare my TOOLS block with the required wording.

The complete page state for this step is available below for comparison.

✔️ Awesome, I've got everything!

Your page now includes its title plus all three required blocks. It is ready for the final check.

ⓧ I'd like to double check the full code

  • Compare your permanent page with this complete reference:
THIS PAGE

This is one running log.
Every time I read something new, I choose its route while it is still open.
I do not start a new log each day.
The first count is background only.
It does not decide whether I keep or drop the habit.

WHAT THIS CAN AND CANNOT SAY

Research cannot decide whether this habit fits my work.
This project does not reduce how much arrives.
Defer means choosing not to act on an item now and writing the day when I will act or decide again.
The count measures how often I defer.
It does not measure whether my priorities improved.

TOOLS

Page: Notion Free.
Mail: Gmail.
Reminder: Google Calendar.
Notion needs a Notion account.
Gmail and Google Calendar use one Google Account.
I may swap any named tool for an equivalent.
Without these accounts, I may use paper and my phone's existing reminder.
The log stays on the page.
Only the reminder goes in the calendar.

What should match?

This is the complete page text for this step. Every line should appear once on your permanent page.

Before you check, which of the first two blocks do you expect to contain the word Research?

  • Return to the top of your permanent page.
  • Read the first two blocks.

You'll find the word Research only in the second block. It appears in exactly one sentence.

That's the foundation locked in. Your page can now explain its scope without relying on memory.

Your permanent page is ready. Next, you'll add the ordered plan plus the four route rules that govern every log entry.

Add the Plan and Route Rules

Your permanent page already states what the habit can measure. The next decisions still need boundaries that cannot shift with the first batch.

This step defines the plan's unusual terms. It also defines all four routes.

The cutoff goes on the page before any item is routed. The review rule also goes on the page before the first result exists.

In this step, get ready to:
  • Add the ordered setup plan with an output for every time row.
  • Define all four routes with your numeric do-it-now limit.
  • Prewrite the measurement section with its cutoff, outcomes, review date space, and cost space.
Build the setup budget

The plan is a budget for the setup session. Its output column makes each row testable without claiming that routing takes a fixed amount of time.

  • Return to the permanent page from earlier.
  • Place the insertion point below the existing TOOLS block.
  • Add the following block exactly as written:
SETUP PLAN

WHEN  | WHAT THIS ROW PRODUCES
0-5   | Page blocks; four route rules; DEFER definition; DO IT NOW limit; cutoff value; review date space; keep/drop rule; cost space
5-10  | Twenty items already waiting
10-28 | Twenty routed log lines
28-32 | First deferral count marked BACKGROUND ONLY
32-35 | Review date written on the page; one reminder saved

This plan is a budget.
It does not claim how long routing takes.
Account sign-in and page creation happen before minute 0.
Finishing DO IT NOW items happens after the routing pass.
That work sits outside these rows.
Fill MINS after an item is finished.

What does this plan establish?

  • The WHEN column keeps the rows in order from 0-5 through 32-35.
  • The WHAT THIS ROW PRODUCES column names a visible output for every row.
  • The lines below the rows separate the setup budget from later do-now completion.
  • The final line defines when MINS is filled.
  • Keep both sides of every plan row visible.
  • Check that the final row starts with 32-35.
  • Confirm that the final output names the review date.
  • Confirm that the final output names one reminder.

You should see five ordered rows. Each row should have a named output in the right column.

Is the output column hard to read?

  • Widen the page view if the right column wraps too tightly.
  • Turn the paper sideways if you are using the accountless path.
  • Keep every word unchanged while adjusting the layout.
  • Still stuck? Help me format the setup plan without changing its wording.
Define the four routes

Each route needs a boundary that you can apply while an item is open. The do-it-now boundary uses a number you choose before routing begins.

  • Place the insertion point below the completed SETUP PLAN block.
  • Add the following block exactly as written:
THE FOUR ROUTES

DO IT NOW
Use this when I can finish the item within my written limit.
MY DO-IT-NOW LIMIT: ____ minutes.
During the setup session, I route every item before finishing any DO IT NOW work.
I finish those items after the routing pass, even when they fit my limit.

GIVE IT A DAY
Use this when I choose to defer.
I write a specific day in DAY.
I do not write "later" or "soon".
If the real action day is unknowable, I write the next day when I will decide again.
A GIVE IT A DAY entry without a written day is not complete.

HAND IT ON
Use this when another person can take the next action and I can send it to them.
If I have nobody to hand the item to, I do not use this route.

THROW IT AWAY
Use this when I choose no further action and need no record beyond this log line.

What do the route boundaries mean?

  • DO IT NOW applies only when the item fits your written time limit.
  • GIVE IT A DAY requires a specific action day or next-decision day.
  • HAND IT ON applies only when another person can accept the next action.
  • THROW IT AWAY closes an item that needs no further action.
  • Record your chosen whole-number time limit here: your chosen number.
  • Replace only the four underscores in MY DO-IT-NOW LIMIT: ____ minutes. with your chosen number.
  • Leave every other route line unchanged.
  • Read all four route rules before moving on.

The page now gives each route a boundary. Every deferred item requires a written day.

Is a route rule incomplete?

  • Enter the same whole number you recorded if the limit line is still blank.
  • Restore any missing sentence by comparing your page with the block above.
  • Keep later plus soon inside the rule that rejects vague deferrals.
  • Still stuck? Help me check the four route rules for missing boundaries.
Prewrite the measurement rule

The measurement counts only one route. Writing its boundary first prevents the first result from changing the rule.

  • Place the insertion point directly below THE FOUR ROUTES block.
  • Add the following block exactly as written:
THE MEASUREMENT AND RULE

Cutoff means the boundary I choose before I count.
MY CUTOFF: fewer than 10 deferred items out of the most recent 20.
THE MEASUREMENT: GIVE IT A DAY entries among 20 log entries.
The other three routes remain visible in the log.
I do not total them.

REVIEW DATE: ____________________

KEEP: The review measurement is fewer than 10.
DROP: The review measurement is 10 or more.

The cutoff tests whether my work fits the deferral limit I chose.
A legitimately deferral-heavy period can produce DROP even when I followed every route rule.
DROP is not a verdict on how well I routed.
It means this work did not fit my chosen limit during this run.
I may change the cutoff only before a new run.

COST AFTER THE FIRST WEEK

Write this once, in words.
Write what the habit felt like.
Write any irritation.
Write what I stopped doing to make room.
Write when I would rather have skimmed.
Do not turn this note into a number.

What does this rule protect?

  • GIVE IT A DAY is the only route counted.
  • The other routes stay visible without totals.
  • KEEP covers counts below 10.
  • DROP covers counts of 10 or more.
  • The first-week cost note stays qualitative.
  • Leave REVIEW DATE: ____________________ blank for now.
  • Keep the cutoff line unchanged.
  • Keep both outcome lines unchanged.
  • Keep the cost prompts below the review rule.

You should see one blank for the future review date. The measurement boundary plus both outcomes should already be visible.

Are the outcome lines missing?

  • Restore the KEEP line if counts below the boundary have no outcome.
  • Restore the DROP line if counts at the boundary have no outcome.
  • Remove any totals added for the other three routes.
  • Still stuck? Help me verify that the cutoff and outcomes cover every possible count.
  • Use the reference tab to compare the complete permanent page with your version.

✔️ Awesome, I've got everything!

Great. Your permanent page now holds every boundary needed before routing starts.

ⓧ I'd like to double check the full code

The limit line below uses the number you recorded above. Every other line should match your page character for character.

THIS PAGE

This is one running log.
Every time I read something new, I choose its route while it is still open.
I do not start a new log each day.
The first count is background only.
It does not decide whether I keep or drop the habit.

WHAT THIS CAN AND CANNOT SAY

Research cannot decide whether this habit fits my work.
This project does not reduce how much arrives.
Defer means choosing not to act on an item now and writing the day when I will act or decide again.
The count measures how often I defer.
It does not measure whether my priorities improved.

TOOLS

Page: Notion Free.
Mail: Gmail.
Reminder: Google Calendar.
Notion needs a Notion account.
Gmail and Google Calendar use one Google Account.
I may swap any named tool for an equivalent.
Without these accounts, I may use paper and my phone's existing reminder.
The log stays on the page.
Only the reminder goes in the calendar.

SETUP PLAN

WHEN  | WHAT THIS ROW PRODUCES
0-5   | Page blocks; four route rules; DEFER definition; DO IT NOW limit; cutoff value; review date space; keep/drop rule; cost space
5-10  | Twenty items already waiting
10-28 | Twenty routed log lines
28-32 | First deferral count marked BACKGROUND ONLY
32-35 | Review date written on the page; one reminder saved

This plan is a budget.
It does not claim how long routing takes.
Account sign-in and page creation happen before minute 0.
Finishing DO IT NOW items happens after the routing pass.
That work sits outside these rows.
Fill MINS after an item is finished.

THE FOUR ROUTES

DO IT NOW
Use this when I can finish the item within my written limit.
MY DO-IT-NOW LIMIT: [[DO_IT_NOW_LIMIT="your chosen number"]] minutes.
During the setup session, I route every item before finishing any DO IT NOW work.
I finish those items after the routing pass, even when they fit my limit.

GIVE IT A DAY
Use this when I choose to defer.
I write a specific day in DAY.
I do not write "later" or "soon".
If the real action day is unknowable, I write the next day when I will decide again.
A GIVE IT A DAY entry without a written day is not complete.

HAND IT ON
Use this when another person can take the next action and I can send it to them.
If I have nobody to hand the item to, I do not use this route.

THROW IT AWAY
Use this when I choose no further action and need no record beyond this log line.

THE MEASUREMENT AND RULE

Cutoff means the boundary I choose before I count.
MY CUTOFF: fewer than 10 deferred items out of the most recent 20.
THE MEASUREMENT: GIVE IT A DAY entries among 20 log entries.
The other three routes remain visible in the log.
I do not total them.

REVIEW DATE: ____________________

KEEP: The review measurement is fewer than 10.
DROP: The review measurement is 10 or more.

The cutoff tests whether my work fits the deferral limit I chose.
A legitimately deferral-heavy period can produce DROP even when I followed every route rule.
DROP is not a verdict on how well I routed.
It means this work did not fit my chosen limit during this run.
I may change the cutoff only before a new run.

COST AFTER THE FIRST WEEK

Write this once, in words.
Write what the habit felt like.
Write any irritation.
Write what I stopped doing to make room.
Write when I would rather have skimmed.
Do not turn this note into a number.

Before you check the completed page, do you expect every boundary to be visible without relying on memory?

  • Read the permanent page from SETUP PLAN through COST AFTER THE FIRST WEEK.
  • Confirm that every plan row has an output.
  • Confirm that every route says when to use it.
  • Confirm that the do-it-now limit contains a number.
  • Confirm that the cutoff says fewer than 10 deferred items out of the most recent 20.
  • Confirm that no prose sentence states a summed time.
  • Confirm that the cost space asks for words instead of a number.

You should find a visible output for every plan row. Each route should say when it applies.

Your do-it-now limit should show a number. The cutoff should show fewer than 10 deferred items out of the most recent 20.

Both outcomes should already exist. No prose sentence should state a summed time.

Your rules now exist before the first result. Next, you'll assemble and route the first twenty items.

Route the First Twenty Items

Your permanent page now holds the fixed route rules plus the cutoff chosen before any results exist. Your next goal is to turn those rules into twenty real routing decisions.

Your existing Gmail inbox or paper stack supplies the batch. The plain-character examples expose incomplete deferrals before you record real work.

In this step, get ready to:
  • Add the running log key with five examples to the permanent page.
  • Assemble twenty waiting items by starting with unread messages.
  • Route all twenty items before completing any DO IT NOW work.
Build the running log key

The examples establish what a complete line looks like before your own items enter the page. Their plain characters make missing days easy to spot.

  • Return to the permanent page from earlier.
  • Add the running log key below the cost space by copying this block exactly:
MY RUNNING LOG

MINS means minutes spent finishing an item chosen as DO IT NOW.
A dot means the field does not apply or is not available yet.
For DO IT NOW, I replace the MINS dot after I finish the item.

ROUTE | WHAT IT NEEDS | DAY | MINS
DO IT NOW | Reply with available times | . | 2
GIVE IT A DAY | Check figures after the report arrives | Friday | .
HAND IT ON | Send the facilities question to the building contact | . | .
THROW IT AWAY | Delete the expired offer | . | .
GIVE IT A DAY | Choose the next step after the supplier replies | Tuesday | .

How the Log Stays Readable

  • The ROUTE field records one decision from the four rules.
  • The WHAT IT NEEDS field records the next action in plain words.
  • The DAY field makes every deferral specific.
  • The MINS field records completion time only for finished DO IT NOW items.
  • Read the explanation from MINS through the five examples.
  • Confirm that the MINS definition appears before the ROUTE | WHAT IT NEEDS | DAY | MINS header.
  • Confirm that the block contains exactly five example lines.

Does the Log Block Look Different?

  • Check that every vertical bar from the copied block remains in place.
  • Keep each example unchanged so the specific days remain visible.
  • If a line wraps on screen, widen the page view without changing its text.
  • Still stuck? Help me compare my running log block with the required text.
Assemble twenty waiting items

This batch comes from work that is already waiting. Starting with unread items keeps the launch focused on material you have not processed yet.

Gmail messages

  • Return to Gmail from earlier.
  • Identify unread messages first.
  • Count each identified message toward your batch.
  • If your count is below twenty, identify the most recent read messages that still need a decision.
  • Stop when your batch reaches exactly twenty messages.

Paper items

  • Return to the waiting paper items from earlier.
  • Identify items that still need a decision.
  • Count each identified item toward your batch.
  • Stop when your batch reaches exactly twenty items.

The source batch is ready. You now have exactly twenty waiting items available for one uninterrupted routing pass.

Route before doing

This pass records decisions before execution begins. A complete deferral always carries a specific action day or next-decision day.

  • Return to the first item in your assembled batch.
  • Choose one route for that item from DO IT NOW, GIVE IT A DAY, HAND IT ON, or THROW IT AWAY.
  • Add one real line below the five examples.
  • Write what the item needs in plain words under WHAT IT NEEDS.
  • For a GIVE IT A DAY item, write a specific action day or next-decision day under DAY.
  • Enter a dot in every field that does not apply or is not available yet.
  • Repeat this routing loop for the remaining nineteen items.

Before you count the lines, predict whether every deferred item names a real day.

  • Count the real lines beneath the examples.
  • Scan every GIVE IT A DAY line for a specific day.

You'll see twenty real lines beneath the five examples. Every GIVE IT A DAY line names a specific day instead of later or soon.

That is the routing pass complete: all twenty items now have a route before any DO IT NOW work begins.

Why Separate Routing From Finishing?

The setup plan budgets the routing pass separately from completion work. Finishing a quick item during the pass would mix execution time into the routing rows.

Your written limit still decides which items qualify for DO IT NOW. Completion begins only after every item has a route.

  • Finish each item routed to DO IT NOW after the routing pass.
  • Track the minutes spent finishing each applicable item.
  • Replace that item's MINS dot with its actual completion minutes.
  • Leave MINS as a dot for every other route.

Before your final check, predict which fields should contain numbers.

  • Return to the permanent page from earlier.
  • Read the five example lines without changing them.
  • Count the twenty real lines below the examples.
  • Check that no deferred day says later or soon.
  • Check that only completed DO IT NOW items have numbers under MINS.

You'll see five unchanged example lines above twenty real lines. Every real GIVE IT A DAY line names a specific day.

Each completed DO IT NOW line shows actual minutes in MINS. Every non-applicable field remains a dot.

Does a Real Log Line Look Incomplete?

  • If the page has fewer or more than twenty real lines, correct the batch before continuing.
  • If a deferred line says later or soon, replace it with a specific action day or next-decision day.
  • If a deferred item has a number under MINS, restore the dot.
  • Still stuck? Help me check my twenty real routing lines.

Your first twenty items now form a complete routing sample. Next, you'll record its deferral count without letting that first result decide the habit.

Record the Background Count and Review Date

Your first 20 real log lines now show how the four routes behave with waiting work. The next job is to preserve that snapshot without letting it overrule your prewritten cutoff.

The first deferral count can look like a verdict. You will label it as background before saving one learner-specific review date in Google Calendar or your existing phone reminder.

In this step, get ready to:
  • Count only GIVE IT A DAY entries among the first 20 real lines.
  • Write the date that falls 66 days after your project start date.
  • Save one reminder on the same date without changing the cutoff or outcomes.
Count the first deferred entries

The only calculated value in this step is the number of GIVE IT A DAY entries among your first 20 real lines. The other routes stay visible without totals.

  • Return to the permanent page from earlier.
  • Locate the first 20 real lines below the five example lines.
  • Count each real line whose route is GIVE IT A DAY.
  • Record the result here: your first deferred count.

Good progress. You now have the only number this background block needs.

  • Add the background block below the twentieth real line by copying this exact text:
FIRST COUNT: BACKGROUND ONLY

THE MEASUREMENT: GIVE IT A DAY entries among the first 20 = ____
This is background only.
It does not decide KEEP or DROP.
I do not compare it with the review measurement to decide.

What Does This Block Protect?

The BACKGROUND ONLY label keeps this first result separate from the later review. The prewritten rule stays reserved for the most recent 20 entries on the review date.

The measurement records how often you deferred in this first batch. It makes no claim about routing quality or priority quality.

  • Replace the blank after the equals sign with your first deferred count.
  • Leave DO IT NOW, HAND IT ON, and THROW IT AWAY untotaled.
  • Read the completed block to confirm that it says BACKGROUND ONLY.

You should see one filled measurement in the new block. The block should state that this result does not decide KEEP or DROP.

Still Unsure Which Lines to Count?

  • Count only the 20 real lines you added for waiting items.
  • Exclude the five example lines above your real entries.
  • Need another pair of eyes? Help me check which running-log entries belong in my background count.
Calculate your review date

The review date depends on the day you started this project. A fixed example date would disconnect the reminder from your own run.

  • Use your project start date to calculate the calendar date 66 days later.
  • Record the result here: your review date.

Your recorded value should be one calendar date based on your own start date.

  • Return to your permanent page.
  • Find the line that begins REVIEW DATE: ____________________.
  • Replace the blank with your review date.
  • Keep the existing cutoff unchanged.
  • Keep both prewritten outcomes unchanged.

The REVIEW DATE space should now show your learner-specific calendar date. The original KEEP and DROP rules should still sit above it.

Unsure About the 66-Day Date?

  • Use the day you began the project as your start date.
  • Add 66 calendar days to that start date.
  • Need help checking the calculation? Help me verify a date that is 66 days after my project start date.
Save one review reminder

Only the reminder belongs in your calendar. The permanent page remains the source for the cutoff and prewritten outcomes.

  • Choose the reminder path that matches your setup.

Google Calendar

  • Switch back to Google Calendar from earlier.
  • Click Create in the top-left corner.
  • Enter Review Route It While It Is Open as the event title.

The event title field should now show Review Route It While It Is Open.

  • Set the event date to your review date.
  • Use Notifications to keep exactly one event notification.

The event details should show your selected date. They should show one event notification.

  • Click Save.

You should see the event saved on your calendar under the review date.

Phone Reminder

  • Return to the existing reminder app on your phone.
  • Create one new reminder.
  • Enter Review Route It While It Is Open as the reminder title.

The reminder title should now show Review Route It While It Is Open.

  • Set the reminder date to your review date.
  • Set exactly one alert for that date.

The reminder details should show your selected date. They should show one alert.

  • Save the reminder.

You should see the reminder saved in your phone's reminder list.

Before you check, do you expect the reminder date to match the date written on your permanent page?

  • Open your saved event or reminder.
  • Compare its date with the date in the REVIEW DATE space.
  • Confirm that the event or reminder has exactly one notification.
  • Return to your permanent page.
  • Read the FIRST COUNT: BACKGROUND ONLY block.
  • Confirm that the original cutoff remains unchanged.

The reminder date should match the learner-specific date in REVIEW DATE.

The first-count block should say BACKGROUND ONLY. Your page should show no totals for DO IT NOW, HAND IT ON, or THROW IT AWAY.

Your cutoff should still show its original boundary. Both prewritten outcomes should remain unchanged.

Can't Match the Reminder Date?

  • Check that the reminder uses your review date.
  • Keep one event notification if the reminder currently shows extras.
  • Still stuck? Help me verify my review date setup.

You have protected the later decision from an early snapshot. Next, you'll route new work while it is still open.

Run the Habit and Apply the Rule

Your first twenty lines proved that the permanent page can hold a real routing pass. Now routing while an item is open becomes the everyday habit that keeps your running log connected to ordinary reading.

The later sample tests your chosen deferral limit against entries created during ordinary reading. It measures whether this run fits your cutoff without judging your priorities or routing quality.

In this step, get ready to:
  • Route every newly read item in the continuing log while the item is still open.
  • Write one word-only cost note at the end of the first week.
  • Apply the prewritten rule to the most recent twenty entries on the review date.
Route each new item while it is open

The same running log continues across days. To defer an item, you choose not to act now and write the day when you will act or decide again.

  • Return to the incoming-item source you set up earlier.
  • Keep each newly read item open while you choose its route.
  • Choose one of the four existing routes by using the rules on your permanent page.
  • Add the item to the same running log before putting it down.
  • Write a specific action day for every GIVE IT A DAY entry.
  • Write a specific next-decision day when the action day is unknowable.
  • Inspect the newest log line after routing your first newly read item.

You should see one new line in the same running log. If its route is GIVE IT A DAY, the DAY field should contain a specific day.

That first continuing entry is the key shift. Your routing habit now runs during ordinary reading.

Is a deferred entry incomplete?

  • Replace later or soon with a specific action day or next-decision day.
  • Move entries from any second log into the permanent page.
  • Continue adding new entries to the same running log.
  • Still stuck? Help me repair my continuing log without adding route totals.
Write the first-week cost note

The cost note captures the experienced cost of the habit in words. It stays separate from your single deferral measurement.

  • Switch back to the permanent page at the end of the first week.
  • Find the existing COST AFTER THE FIRST WEEK section.
  • Describe what the habit felt like.
  • Write down any irritation you experienced.
  • Name what you stopped doing to make room.
  • Record when you would rather have skimmed.
  • Keep the note free of counts, rates, scores, minutes, or any other numerical outcome.
  • Read the finished note from start to finish.

You should see one qualitative note written in words. You should see no calculated outcome in this section.

You have now recorded the habit's experienced cost without creating another result.

Apply the review rule

The review uses the most recent twenty entries already in the running log. This sample tests the fixed deferral boundary you chose before any review result existed.

  • Switch back to the permanent page on your saved review date.
  • Identify the most recent twenty existing entries in the same running log.
  • Add the review block below your completed cost note by copying this text exactly:
REVIEW MEASUREMENT

THE MEASUREMENT: GIVE IT A DAY entries among the most recent 20 = ____
Read the KEEP or DROP rule written before this result existed.
Do not change the cutoff after seeing this result.
A different cutoff belongs to a new run.

What does this block preserve?

  • The most recent 20 keeps the review tied to your continuing log.
  • The KEEP and DROP outcomes use the boundary written before the result existed.
  • The final line reserves any changed cutoff for a new run.

Before you count, picture which prewritten outcome you expect to apply.

  • Count only the GIVE IT A DAY entries among the selected twenty lines.
  • Replace the blank in the review block with that count.
  • Read the existing KEEP rule.
  • Read the existing DROP rule.
  • Choose KEEP when the result is fewer than 10.
  • Choose DROP when the result is 10 or more.
  • Copy the matching prewritten outcome line beneath the completed block.
  • Leave the fixed cutoff unchanged.

If your count is fewer than 10, the applied outcome is KEEP. If your count is 10 or more, the applied outcome is DROP.

The result reports whether this run fit your chosen deferral limit. It does not grade your priorities or routing quality.

  • Check every new GIVE IT A DAY line for a specific action day or next-decision day.
  • Confirm that the cost section contains one word-only note.
  • Confirm that the review block contains the deferral count from the most recent twenty entries.
  • Confirm that the matching prewritten outcome follows the completed review block.
  • Confirm that no totals appear for the other three routes.
  • Confirm that the fixed cutoff remains unchanged.

You should see one continuing log with complete days on every deferred entry. You should also see one word-only cost note.

The review block should contain your single deferral count. The matching prewritten outcome should appear beneath it.

Your fixed cutoff should remain unchanged. No totals should appear for the other routes.

Does the review result look wrong?

  • Mark the newest existing log entry as one edge of your sample.
  • Count backward until the sample contains twenty entries.
  • Recount only the entries labeled GIVE IT A DAY.
  • Restore the prewritten boundary if the cutoff changed during the review.
  • Still stuck? Help me check my review sample without changing the cutoff.

You have now run the habit during ordinary reading and tested it against the rule written before the result existed. Your page preserves the cost, boundary, and outcome without turning the review into a quality score.

Secret mission

Compare Routes Without Creating Another Outcome

Compare a redacted batch with suggestions from an assistant you already use. Record each disagreement in words. Keep every calculated comparison outcome off the page.

Clean Up Your Resources

Clean Up Your Resources

This project created no paid resources, so the named setup has no ongoing project cost. Choose whether to keep the page and reminder, pause the habit, or remove both.

Resources you used:

  • One permanent page stored in Notion or on a continuing paper equivalent.
  • One review reminder stored in Google Calendar or an existing phone reminder app.

Your existing Gmail account or equivalent incoming-item source remains unchanged. No assistant account needs cleanup because this project did not create one.

Keep everything running

No action is needed. Choose this if you want to continue using the routing habit with the page and review reminder intact.

  • Continue routing newly read items into the same running log.
  • Retain the saved review reminder.
  • Keep using the existing page instead of starting a new log each day.

Pause - I'll come back to this later

Pause the habit without erasing your page. An interrupted run does not produce a review outcome.

  • Write the pause date in words on the permanent page.
  • Stop adding newly read items to the continuing log.
  • Leave the prewritten keep-or-drop rule unapplied for the interrupted run.

Delete - I don't want to use this again

Deleting these artifacts removes your project record and review reminder. Actions already taken on routed items remain in effect.

  • In Notion's sidebar, use the page menu beside ROUTE IT WHILE IT IS OPEN to move the page to Trash.
  • Confirm that the page no longer appears among your active pages.
  • If you used paper, discard the continuing sheet or notebook page.
  • In Google Calendar, select the event titled Review Route It While It Is Open on your learner-specific review date.
  • Use the delete control in the event details to remove the event.
  • Confirm that the learner-specific date no longer shows the review event.
  • If you used a phone reminder, delete the saved review reminder from your reminder app.

That clears the only project artifacts you created. Your incoming-item source remains available for normal use.

Nice Work!

Nice Work!

Great work! Your permanent page now supports a routing habit that runs while each item is still open.

You've learned how to:

  • Create a permanent decision page containing the ordered plan plus all four route rules. Use the same page across days.
  • Maintain one continuing log that captures every route while the item is still open. Give each GIVE IT A DAY entry a specific day. Record the experienced cost once in words.
  • Test the fixed cutoff using only the GIVE IT A DAY count from the most recent twenty entries. Keep the first count as background. Apply the prewritten KEEP or DROP outcome without turning it into a judgment of routing quality.
  • Complete the optional Secret Mission by comparing an assistant's suggestions with your own routes. Share only redacted item descriptions. Record disagreements in words without creating a second calculated outcome.

Ready to quiz yourself?