Three Times, Not In Between

Set a three-times-a-day Gmail routine with safety rules and a preset verdict.

Introduction

30 Second Summary

Email can turn every new arrival into a reason to look, even when the message can wait. By the end of a day, those quick glances can feel impossible to count.

In this project, you will compare a normal week of Gmail checking with a week built around three fixed looking times. You will use Notion to hold the evidence while Google Calendar holds three dated events.

What You'll Build

On Day 66, you will open one page that shows when you looked, what the practice cost, and which prewritten KEEP or DROP verdict applies.

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

  • A single evidence page where you can see which alerts stay protected and which Gmail surfaces can wait.
  • A visible two-week pattern built from one at-the-time mark per check, ending in one measured DROP.
  • Three dated reminders that return you to the practice on Day 8, Day 14, and Day 66 without creating daily prompts.
  • Secret Mission: On Day 66, read the original two-part rule to write KEEP or DROP without adding a new number or feeling score.

Are there any prerequisites?

You need a Notion account plus a Google Account. The same steps also work with paper, a phone reminder, or another mail service.

Before We Start

This checkpoint confirms access to your personal Notion, Google Calendar, and Gmail accounts or the paper and phone-reminder replacements before any hands-on work begins. Its safety boundary keeps ward alarms, on-call phones, lone-worker alerts, school calls, care alerts, security alerts, and any other urgent channel unchanged, with Gmail excluded whenever its alerts cannot be separated.

Make the Page and Fix the Rules

Your break predictions and verdict branches need to exist before results can influence them. Writing them later would let the answer shape the test.

You use a single Notion page to keep the safety list, rules, marks, costs, and verdict together. Google Calendar stores only three dated transitions.

Your Gmail settings remain unchanged while Week 1 begins.

In this step, get ready to:
  • Build one page containing the safety boundary, alert paths, definitions, and tally areas.
  • Prewrite the three times, break tests, and verdict branches.
  • Prepare the dated transitions before beginning the unchanged Week 1 tally.
Create the page and map safe alert paths

A safety boundary separates urgent channels from the Gmail surface that can wait. The page keeps that boundary visible before any alerts change.

  • Switch back to Notion in your browser.
  • Select 📝 at the top of the left sidebar.
  • Enter Three Times, Not In Between as the page title.

You should see the new page title at the top of the page.

  • Build the first page sections by copying this structure:
PAGE EXAMPLE

STAYS ON
ward alarm
on-call phone
school calls

CAN WAIT
Gmail on laptop

ALERT PATH
Settings > See all settings
Desktop notifications
Mail notifications off
Save Changes

CHECK TIMES
9:00 am
1:00 pm
5:00 pm

How does this page shape help?

  • The STAYS ON section protects channels that must continue to reach you promptly.
  • The CAN WAIT section names the Gmail surface eligible for this practice.
  • The ALERT PATH section records the route you may use on Day 8.
  • The CHECK TIMES section keeps the future schedule outside Google Calendar.
  • Replace the examples under STAYS ON with the urgent channels you identified earlier.
  • Replace the example under CAN WAIT with the exact Gmail surface eligible for the practice.

Your page now separates protected channels from the mail surface that can wait.

  • Keep the copied computer alert path under ALERT PATH when it applies to your Gmail surface.
  • Trace the current notification path on any other eligible Gmail surface.
  • Add each traced path under ALERT PATH.
  • Leave every alert setting in its current state.

Keep Safety Notes Private

Use short functional descriptions for protected channels. Personal names or confidential details are unnecessary.

Shared definitions keep every mark focused on the same behavior. They also protect DROP from turning into several competing results.

  • Add the project definitions below the page structure by copying this block:
A check means opening Gmail to see what is there. Opening it only to send a message already planned does not count. If I also look at new mail, it counts.

A cue means the thing that prompts me to look. An alert can be a cue. A written time can also be a cue.

A tally means one plain mark made at the time of a check.

A break list means the things I think may go wrong. Each line can later be marked yes or no.

The DROP is the only measured number. It means Week 1 checks minus Week 2 checks.

A cutoff means the line the result must cross. Here the cutoff asks whether Week 2 is under half of Week 1. I read that answer as yes or no. I do not record it as another result.

What do these definitions protect?

  • A check counts whenever you look at new mail.
  • A tally records that check at the time it happens.
  • A break list gives each concern a yes-or-no test.
  • The cutoff produces a temporary yes-or-no reading.
  • The DROP remains the only measured number saved on the page.
  • Check that the page title appears as Three Times, Not In Between.
  • Confirm that every protected channel appears under STAYS ON.
  • Confirm that each eligible Gmail alert path appears under ALERT PATH.
  • Confirm that all six definitions appear on the page.

Good progress. Your page now protects urgent channels while defining exactly what the practice measures.

Fix the times, break list, and verdict rules

A prewritten decision rule commits you to both possible outcomes before Week 1 supplies any evidence. The break list does the same job for your concerns.

  • Replace the sample entries under CHECK TIMES with three exact times using am or pm.
  • Add the between-times rule plus the break-list example by copying this block:
Gmail stays closed between my three times.

BREAK LIST EXAMPLE
late client reply | no
manager asks why | yes
SERIOUS: missed safety message | no

Why write the break list now?

Each line predicts something that may go wrong. Writing the list now keeps later knowledge from rewriting your original concerns.

The SERIOUS line defines the event that stops the practice regardless of the final number.

  • Replace the example break items with concerns from your own situation.
  • Rewrite each concern until it can be answered with yes or no.

The yes-or-no values beside the items are your predictions. Day 14 is when you mark what actually happened.

  • Prefix your stop-condition item with SERIOUS.
  • Keep the written check times inactive until Day 8.

The outcome areas need to exist before the first tally mark. Blank areas prevent the result or verdict from appearing early.

  • Add the fixed branches plus the empty tally areas by copying this block:
KEEP if the cutoff reads YES and SERIOUS reads NO.
DROP if the cutoff reads NO or SERIOUS reads YES.
SERIOUS wins whatever the DROP.

WEEK 1
Mon
Tue
Wed
Thu
Fri
Sat
Sun

WEEK 2
Mon
Tue
Wed
Thu
Fri
Sat
Sun

DROP
COST
DAY 66 VERDICT

How will this rule work?

  • The KEEP branch requires the cutoff to read yes.
  • The same branch requires the serious item to read no.
  • The DROP branch applies when either requirement fails.
  • The serious item always overrides the numeric drop in checks.
  • The blank areas reserve one place for the measured result, one place for costs, and one place for the Day 66 verdict.
  • Confirm that both verdict branches match the copied wording exactly.
  • Confirm that the serious override appears below the branches.
  • Leave WEEK 2 empty.
  • Leave DROP empty.
  • Leave COST empty.
  • Leave DAY 66 VERDICT empty.

That is the commitment locked in. Both verdicts now exist before the answer does.

Schedule the transitions and start Week 1

Google Calendar holds the three dates when the practice changes or gets read. The three daily check times stay on the Notion page.

The day you create the page is Day 1. Day 8 is seven calendar days later.

Day 14 is thirteen calendar days later. Day 66 is sixty-five calendar days later.

  • Switch back to Google Calendar in your browser.
  • Select Create.
  • Enter Day 8: Switch as the event title.
  • Set the event date to Day 8 of your run.

The event editor should now show the Day 8 title on the date when all three changes begin.

  • Select Add notification if the event has no notification.
  • Select Save.

You should see Day 8: Switch saved on the selected date.

  • Select Create.
  • Enter Day 14: Read as the event title.
  • Set the event date to Day 14 of your run.

The second editor should now show the Day 14 title on the date when you read the two weeks.

  • Select Add notification if the event has no notification.
  • Select Save.

You should see Day 14: Read saved on its selected date.

  • Select Create.
  • Enter Day 66: Verdict as the event title.
  • Set the event date to Day 66 of your run.

The third editor should now show the Day 66 title on the date when you apply the original rule.

  • Select Add notification if the event has no notification.
  • Select Save.

You should see Day 66: Verdict saved on its selected date.

Where can notifications arrive?

Google Calendar event notifications can arrive on a phone, in a web browser, or by email. Choose a delivery surface that you already check reliably.

Browser delivery needs permission for Google Calendar. The Calendar page must remain open in the browser for that delivery method.

  • Keep the three daily check times on the Notion page only.
  • Confirm that you created no daily Calendar event for those times.

Week 1 records your normal behavior. Your written times remain inactive while Gmail stays open or closed exactly as usual.

  • Switch back to Gmail in your browser.
  • Check your inbox as you normally would.
  • Return to the Notion page.
  • Add one plain mark to today under WEEK 1 immediately after the check.

You have your first real baseline mark. Week 1 is now recording your existing Gmail routine without changing it.

Before the final review, do you expect to find any changed Gmail setting or daily Calendar event?

  • Count the project events saved in Google Calendar.
  • Select one project event.

You should see exactly three project events. The selected event should list at least one notification.

  • Return to the Notion page.
  • Confirm that today has one at-the-time mark under WEEK 1.
  • Confirm that DROP remains blank.
  • Confirm that your Gmail alerts still match their normal settings.

You should see the complete page plus the first Week 1 mark. No Gmail setting or daily check-time event should have changed.

✔️ Awesome, I've got everything!

Your page contains the fixed plan. Your three dated events are ready while Gmail remains unchanged.

ⓧ I'd like to double check the final state

  • Confirm that the Notion page is named Three Times, Not In Between.
  • Confirm that STAYS ON contains every protected urgent channel.
  • Confirm that CAN WAIT names the eligible Gmail surface.
  • Confirm that ALERT PATH contains each eligible Gmail alert path.
  • Confirm that the page defines check, cue, tally, break list, DROP, and cutoff.
  • Confirm that three exact check times include am or pm.
  • Confirm that the page includes Gmail stays closed between my three times..

The remaining checks cover the prewritten decision plus the unchanged Week 1 start.

  • Confirm that every break-list line can be answered with yes or no.
  • Confirm that one learner-defined line begins with SERIOUS.
  • Confirm that both verdict branches plus the serious override match the original wording.
  • Confirm that WEEK 1 contains the first at-the-time mark.
  • Confirm that WEEK 2, DROP, COST, and DAY 66 VERDICT remain blank.
  • Confirm that Google Calendar contains the three project events with notifications.
  • Confirm that no daily event exists for the three check times.
  • Confirm that Gmail alerts plus normal checking habits remain unchanged.

Your safety boundary plus your decision rules are fixed before the results exist. Next, you will build the full Week 1 baseline one check at a time.

Tally Your Unchanged Week

Your safety boundary is fixed before any result exists. Your decision rules are fixed too.

Now you need a Week 1 record of your normal Gmail checking. This record becomes the starting point for the later comparison.

An at-the-time tally in Notion captures each check while it happens. Rebuilding marks from memory would weaken that record.

In this step, get ready to:
  • Record every Gmail check at the time it happens from Day 1 through Day 7.
  • Preserve your normal Gmail routine throughout Week 1.
  • Keep every result area blank until the Day 14 reading.
Mark every Gmail check as it happens

The saved check definition decides when a mark belongs in WEEK 1. Each qualifying look gets one plain mark on the current day's row.

  • Return to the Three Times, Not In Between page in Notion.
  • Read the saved check definition before recording your next mark.
  • Place the text cursor at the end of the current day's row under WEEK 1.
  • Type | once immediately after every new Gmail check.
  • Repeat this at the time of each check through Day 7.

Your current day's row gains one new | after the next qualifying look. You've captured that check while it was still fresh.

Keep Week 1 unchanged

Week 1 is the unchanged comparison. Its value comes from preserving your normal routine.

  • Keep every protected channel listed under STAYS ON unchanged.
  • Leave eligible Gmail alert settings in their normal state.
  • Leave Gmail open or closed according to your normal habit.
  • Look at Gmail whenever you normally look.
  • Keep the three written check times inactive.
  • Leave every response in BREAK LIST blank.

Why Keep This Week Normal?

Week 1 shows how often you check under your existing routine. It gives Week 2 a starting pattern for comparison.

Changing your routine during Week 1 would mix the two phases. The unchanged week protects the meaning of every later mark.

Confirm Week 1 is complete

Your raw marks are the complete Week 1 record. Results stay blank until the later reading.

Before you review the page, pause to predict which sections will still be blank.

  • Return to the Three Times, Not In Between page after Day 7 ends.
  • Confirm every Gmail check from Days 1 through 7 has one mark made at the time.
  • Confirm WEEK 2 remains empty.
  • Confirm BREAK LIST remains unmarked.
  • Confirm DROP remains blank.
  • Confirm COST remains blank.
  • Confirm DAY 66 VERDICT remains blank.
  • Confirm no daily totals have been added.

You should see raw Week 1 rows containing only the marks you made at the time. The other measurement areas remain untouched.

  • Confirm no feeling score has been added.
  • Return to Google Calendar from earlier.
  • Confirm Day 8: Switch remains saved with a notification.
  • Confirm Day 14: Read remains saved with a notification.
  • Confirm Day 66: Verdict remains saved with a notification.
  • Confirm no daily events exist for the three check times.

You've secured a trustworthy Week 1 record by marking each check while it happened.

✔️ My Week 1 is complete

Your Week 1 record now contains one at-the-time mark for every Gmail check from Days 1 through 7. Your normal Gmail routine remained unchanged.

ⓧ I want to double check

The original page foundations should still match the rules you fixed before Week 1.

  • Confirm your original safety lists remain unchanged.
  • Confirm your eligible Gmail alert paths remain documented.
  • Confirm every original definition remains on the page.
  • Confirm the three exact check times still include am or pm.
  • Confirm Gmail stays closed between my three times. remains written on the page.
  • Confirm BREAK LIST still contains one learner-defined SERIOUS item.
  • Confirm every BREAK LIST response remains blank.
  • Confirm the prewritten KEEP and DROP rules remain unchanged.

The measurement areas should show only the Week 1 marks earned in this step.

  • Confirm WEEK 1 has one at-the-time mark for every Gmail check from Days 1 through 7.
  • Confirm WEEK 2 remains empty.
  • Confirm DROP remains blank.
  • Confirm COST remains blank.
  • Confirm DAY 66 VERDICT remains blank.
  • Confirm no daily totals exist.
  • Confirm no feeling score exists.

Your connected tools should also match their state from the beginning of Week 1.

  • Confirm Day 8: Switch remains saved with a notification.
  • Confirm Day 14: Read remains saved with a notification.
  • Confirm Day 66: Verdict remains saved with a notification.
  • Confirm no daily check-time events exist.
  • Confirm Gmail alert settings remained unchanged throughout Week 1.
  • Confirm Gmail stayed open or closed according to your normal habit.
  • Confirm the three written check times remained inactive.

Your unchanged week is now recorded without extra results. On Day 8 the three coordinated changes begin together.

Switch to Three Fixed Times

Your at-the-time Week 1 marks in Notion now capture seven days of normal Gmail checking. That unchanged week gives the next phase a fair starting point.

Today's two-minute switch activates one bundled routine. Eligible alerts turn off.

Gmail closes between your three fixed times. Your later DROP describes the bundle without identifying which part mattered.

In this step, get ready to:
  • Protect urgent channels before making the switch.
  • Turn off only eligible Gmail alerts.
  • Activate the bundled Day 8 routine.
Review the safety boundary

A safety boundary keeps urgent paths outside this practice. Any Gmail surface that cannot separate waiting mail from protected alerts stays on.

  • Switch back to your Three Times, Not In Between page in Notion.
  • Read every entry under STAYS ON.
  • Compare each saved alert path with your protected channels.
  • Leave the setting on for any path that still carries a protected alert.
  • Remove that Gmail surface from the practice if its controls stay linked.
  • Confirm that every remaining alert path belongs to mail under CAN WAIT.

Why Review STAYS ON First?

The switch applies only to alerts that can wait. Protected channels keep working exactly as they did during Week 1.

A protected path takes priority over the practice. This keeps urgent messages outside the experiment.

Switch all three parts together

Your saved paths show where each eligible alert is controlled. Following those paths keeps the switch limited to the surfaces you assessed earlier.

  • Read the first eligible Gmail alert path saved on your Notion page.
  • Return to the Gmail alert surface from earlier.
  • Follow the saved path to its alert control.
  • Turn off the eligible alert.
  • Repeat the saved path for every remaining eligible Gmail alert.
  • Revisit each saved eligible path to confirm its alert setting is off.

You should see every eligible alert in its off state. Protected alert controls remain unchanged.

Cannot Separate an Alert?

Leave that alert on. Remove its Gmail surface from the practice so the protected channel stays available.

Check that you followed the path saved on your Notion page. A different device can have its own notification control.

Help me check whether a Gmail alert can be safely included in this practice.

  • Switch back to the three written check times on your Notion page.
  • Read each time with its written am or pm label.
  • Close the Gmail browser tab.
  • Begin using the three written times on Day 8.
  • Keep Gmail closed between those times.

Why Start Everything Together?

Eligible alert silence starts with mailbox closure. The three fixed times begin at that same point.

Your comparison therefore measures the bundled routine. It cannot show whether one part caused the eventual DROP.

Start Week 2 and verify the switch

The WEEK 2 area records checks from the routine's first active day. At-the-time marks keep later memory from changing the count.

  • Return to Gmail at your first written check time.
  • Check your mail using the definition already saved on your Notion page.
  • Close Gmail after the check.
  • Immediately add one plain mark under WEEK 2 in Notion.
  • Add one mark for any extra check between the written times.
  • Leave the BREAK LIST unmarked.
  • Leave DROP blank.

Before the final check, do you expect any part of the page outside Week 2 marking to have changed?

  • Switch back to your Notion page.
  • Confirm that STAYS ON remains unchanged.
  • Confirm that WEEK 2 contains the mark from your first Day 8 check.
  • Confirm that the BREAK LIST remains unmarked.
  • Confirm that DROP remains blank.
  • Check your browser tab bar to confirm that Gmail is closed.
  • Switch back to Google Calendar from earlier.
  • Confirm that only the three saved dated events remain.

Your protected STAYS ON channels remain unchanged. Eligible Gmail alerts show as off.

Gmail is closed between your three written times. WEEK 2 shows the mark from your first Day 8 check.

The BREAK LIST remains unmarked. DROP remains blank.

Google Calendar still contains Day 8: Switch, Day 14: Read, and Day 66: Verdict. You should see no daily events for the three check times.

You've completed the coordinated switch. Your Week 2 evidence now starts from one clear Day 8 boundary.

✔️ The Day 8 switch is active

All three parts started together. Protected channels remain unchanged while Week 2 marking is underway.

ⓧ I'd like to double check the final state

  • Confirm that protected STAYS ON channels remain unchanged.
  • Confirm that only eligible Gmail alerts are off.
  • Confirm that Gmail stays closed between looks.
  • Confirm that the three written times became active together on Day 8.
  • Confirm that WEEK 2 marking started on Day 8.

These checks confirm the Day 8 change itself. The remaining checks protect the original plan.

  • Confirm that the original rules remain unchanged.
  • Confirm that the BREAK LIST remains unmarked.
  • Confirm that DROP, COST, and DAY 66 VERDICT remain blank.
  • Confirm that the three dated Calendar events remain saved.
  • Confirm that no daily Calendar events exist for the three check times.

Your bundled routine is active. Next, you'll keep it steady through Week 2 with one at-the-time mark for every look.

Tally Your Three-Time Week

The Day 8 switch activated your complete routine for Gmail. Eligible alerts are now off.

This week tests whether the combined routine changes how often you look. The at-the-time tally protects the comparison from memory gaps.

In this step, get ready to:
  • Make one at-the-time mark for every Gmail check during Days 8 through 14.
  • Keep the three-part routine active throughout Week 2.
  • Protect the safety boundary if your serious item occurs.
Mark every check when it happens

Each mark records one real look at the moment it happens. This keeps forgotten checks from disappearing from your Week 2 evidence.

What counts as a check?

Use the definition already saved on your page. Opening Gmail to see what is there counts as one check.

Sending a planned message without looking at new mail adds no mark. Looking at new mail during that visit adds one mark.

  • Switch back to your Three Times, Not In Between page in Notion at each Gmail check.
  • Add one plain mark under the current day in WEEK 2.
  • Add the mark at the time of the check.
  • Mark every between-time check in the same daily row.
  • Leave DROP blank.
  • Leave daily totals off the page.
  • Leave feeling scores off the page.
  • Leave DAY 66 VERDICT blank.

Your Week 2 row grows whenever you look. More than three marks on a day remain valid evidence.

Three Is the Target

Three checks each day is the target for the routine. Every extra check still belongs in the tally.

The comparison depends on an honest record of your actual behavior. A hidden check would weaken that record.

Keep the three changes together

The routine depends on alerts staying off during the practice. It also depends on Gmail staying closed between your written times.

Why Keep the Parts Together?

The tally measures the three changes as one routine. It cannot identify which part caused a difference.

The routine changes when you look. It does not reduce incoming mail or improve replies by itself.

  • Keep eligible Gmail alerts off.
  • Look at Gmail at each of your three written times.
  • Close Gmail after each look.
  • Keep every STAYS ON channel unchanged.
  • Leave every BREAK LIST line blank while no serious event occurs.

Your Serious Line Is the Stop Rule

Stopping early can feel like losing the week. The serious rule protects urgent communication before it protects the comparison.

  • Mark the SERIOUS line yes if that event occurs.
  • Restore the affected setting.
  • Stop the run.

A serious stop ends the three-part practice. Your protected channels remain available throughout the week.

Verify the complete Week 2 record

Completeness matters more than reaching exactly three checks each day. The finished page preserves what happened without turning Week 2 into a result.

Before the final check, do you expect your WEEK 2 area to show every look or only the three planned looks?

  • Return to your Notion page from earlier on Day 14.
  • Inspect WEEK 2 for every at-the-time mark through Day 14.
  • Confirm every between-time check has its own mark.
  • Confirm DROP remains blank.
  • Confirm no daily total appears.
  • Confirm no feeling score appears.
  • Confirm no verdict appears.

Check the Routine Boundary

The page shows the tally evidence. Your final routine check confirms the conditions that produced those marks.

  • Confirm the BREAK LIST remains blank if no serious event occurred.
  • Confirm the SERIOUS line reads yes if the serious event stopped the run.
  • Confirm eligible Gmail alerts remained off unless the serious stop required restoration.
  • Confirm Gmail remained closed between looks unless the serious stop ended the run.
  • Confirm the three written times remained active unless the serious stop ended the run.
  • Confirm every STAYS ON channel remained unchanged.

With no serious stop, you should see at-the-time marks for every check across Days 8 through 14. Every between-time check also has its own mark.

If the serious item stopped the run, its line reads yes. The affected setting is restored.

In both paths, DROP stays blank. You should see no daily total, feeling score, or verdict.

  • Crop your evidence to show the WEEK 2 tally area with the blank DROP area.

You have captured a complete Week 2 record from checks made in the moment. Next, you will mark the break list before counting either week.

Read the Day 14 Results

Your Week 2 tally in Notion now captures every Gmail check from the three-part routine. Today you turn those old marks into one Day 14 reading.

A number can change how you remember what went wrong. You will complete the break list before you count so your earlier predictions stay independent of the result.

In this step, get ready to:
  • Complete every BREAK LIST line before counting.
  • Produce the single DROP result.
  • Finish the word-only COST record.
Complete the break list before counting

Your BREAK LIST preserves what you thought might happen before the routine began. Completing it first keeps the later number from reshaping those observations.

  • Switch back to the Three Times, Not In Between page from earlier in Notion.
  • Find the BREAK LIST section.
  • Mark every unfinished line yes or no based on what happened.
  • Complete the SERIOUS line before counting either week.
  • Check that no BREAK LIST line remains blank.

That is the memory-sensitive part done. Your predictions are now fixed before the number can influence them.

Calculate the single DROP number

The two weekly counts are temporary working values for one subtraction. Only the resulting DROP stays on the page as a measured number.

  • Count the marks in WEEK 1 as a temporary working value.
  • Count the marks in WEEK 2 as a temporary working value.
  • Subtract the Week 2 working value from the Week 1 working value.
  • Write DROP = Week 1 - Week 2 in the blank DROP area.
  • Complete that line with a final equals sign followed by your subtraction result.
  • Read your prewritten cutoff as yes or no by checking whether Week 2 is under half of Week 1.
  • Leave the cutoff answer off the page.
  • Leave the DAY 66 VERDICT area blank.

The weekly counts have now served as working parts of the subtraction. The page keeps only the final DROP number.

Write the costs and close the tally

The COST section records consequences in words without creating another measured outcome. It also names any effect from slower replies.

  • Write that tallying ends today under COST.
  • Write who noticed slower replies.
  • Write whether any BREAK LIST item caused a real cost.
  • Leave any duration out of the page.
  • Leave any time-saved measure out of the page.
  • Leave any feeling score out of the page.
  • Finish the Day 14 block by adding these exact lines:
The count tells me whether I checked less.
It does not tell me whether it helped.
It cannot tell me which of the three parts mattered.

Why these statements matter

  • The first statement limits the count to the question it can answer.
  • The second statement keeps the benefit question separate from checking frequency.
  • The third statement reflects that alerts, mailbox closure, and written times changed together.
  • Confirm that all three statements appear beneath your Day 14 reading.
  • Confirm that COST contains no duration, time-saved figure, or feeling score.
  • Stop adding tally marks after Day 14.
  • Keep eligible Gmail alerts off until Day 66 unless the SERIOUS item required restoration.
  • Keep Gmail closed between your three written times until Day 66 unless the SERIOUS item stopped the run.
  • Keep the three written times active until Day 66 unless the SERIOUS item stopped the run.
  • Leave every protected STAYS ON channel unchanged.

Your Day 14 tally is now closed. The three-part routine continues until Day 66 unless the serious condition stopped the run.

Protected urgent channels remain unchanged.

  • Predict whether the finished page should contain one measured number or several.
  • Confirm that every BREAK LIST line has a yes or no mark.
  • Confirm that the original WEEK 1 and WEEK 2 tally marks remain unchanged.
  • Confirm that DROP is the page's only measured number.
  • Confirm that the cutoff answer is absent from the page.
  • Confirm that COST is written only in words.
  • Confirm that all three count statements appear on the page.
  • Confirm that DAY 66 VERDICT remains blank.

You will see a complete Day 14 reading that keeps DROP as its only measured number. The final verdict remains blank for the later rule reading.

That completes the Day 14 reading. Your later verdict now has a clean record based on the rule you wrote before the answer existed.

Secret mission

Make the Day 66 Verdict

On Day 66, read the old evidence through the rule you wrote before the result existed. Record one KEEP or DROP verdict without adding a new measure or judging how the day feels.

Clean Up Your Resources

Clean Up Your Resources

Choose whether to continue the routine, pause it, or remove its records. This project has no paid resource or ongoing cost.

Resources you used:

  • One Notion page named Three Times, Not In Between.
  • Three dated Google Calendar events named Day 8: Switch, Day 14: Read, and Day 66: Verdict.
  • Your eligible Gmail alert configuration, with protected channels unchanged.

Keep everything running

Everything can stay as it is if your prewritten verdict supports continuing the routine.

  • Retain the Three Times, Not In Between page as your complete record.
  • Retain the three dated events as historical markers.
  • Keep eligible Gmail alerts off through the saved paths.
  • Keep Gmail closed between the three written times.
  • Continue looking at Gmail at the three written times.
  • Keep every protected urgent channel unchanged.

Pause - I'll come back to this later

This option stops the active routine while preserving the page and dated events for later reference.

  • Review the saved eligible Gmail alert paths on the Three Times, Not In Between page.
  • Restore every eligible Gmail alert that remains off through its saved path.
  • Leave any alert already restored after a SERIOUS event turned on.
  • Keep every protected urgent channel unchanged.
  • Return Gmail to your usual open-or-closed pattern.
  • Return to your usual checking schedule.
  • Retain the Notion page and three Google Calendar events.

Delete - I don't want to use this again

Choose a clean removal if you no longer need the routine or its records.

  • Review the saved eligible Gmail alert paths on the Three Times, Not In Between page before removing it.
  • Restore every eligible Gmail alert that remains off through its saved path.
  • Keep every protected urgent channel unchanged.
  • Return Gmail to your usual open-or-closed pattern.
  • Return to your usual checking schedule.
  • Delete the three dated events from their event details in Google Calendar: Day 8: Switch, Day 14: Read, and Day 66: Verdict.
  • Delete the Three Times, Not In Between page from its page menu in Notion.

Nice Work!

Nice Work!

You did it! Your Notion page now records the full path from the safety check to a prewritten Day 66 verdict for Gmail.

What you learned:

  • Defined a safety boundary before changing any eligible alert. Wrote the break list and both verdict branches before the outcome existed.
  • Kept an unchanged Week 1 baseline with one at-the-time mark for every check. Started all three parts of the Day 8 switch together. Continued marking every Week 2 check, including looks between the written times.
  • Marked every break-list line before counting. Kept DROP as the only measured number. Described COST in words. Used Google Calendar for the three dated checkpoints without adding daily events.
  • Secret Mission: Applied the prewritten KEEP or DROP rule on Day 66. Reached the verdict without adding a new calculation, feeling score, or judgment of the day.

Ready to quiz yourself?