Look Back Before You Put a Time on a Job

Build a record that uses past job times to estimate recurring work.

Introduction

30 Second Summary

Recurring work can feel familiar enough to estimate from memory. The surprise comes when the same jobs keep finishing later than the time you planned around.

In this project, you will build a single Notion page that uses completed jobs to guide the time you put on the next recurring job. Google Calendar protects three later checkpoints without producing an early result.

What You'll Build

You open one page to see where each estimate came from, record what the job actually took, and decide whether looking backward has earned a permanent place in your planning.

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

A remembered baseline showing eight recurring kinds of work beside the time each one usually takes.
A weekly recording practice that preserves first-thought order, reveals the basis for odd-job estimates, and records actual times as jobs finish.
A prewritten decision rule supported by reminders for day 7, day 28, and day 66.
A Secret Mission: Use Gemini Apps or Claude on day 66 to rebuild the remembered table from recorded actuals, then check every middle value yourself.

Are there any prerequisites?

A Notion account and a Google Account support the primary path. Paper plus an existing reminder tool preserve the same practice if either account is unavailable.

Before We Start

This step locks in the recurring work you want to estimate from past actuals. Your reason keeps the focus on finding a time you can plan around.

Set Up Your Practice Page

Your practice needs one durable home for the remembered table, weekly jobs, and later reading. A Notion page holds that content while Google Calendar protects the dated checks.

In this step, you will create a blank practice page. You will also confirm that Gmail and Google Calendar open under the same Google Account.

In this step, get ready to:

Create a blank practice page on Notion's Free plan.
Confirm access to Gmail under your chosen Google Account.
Confirm access to Google Calendar under your chosen Google Account.

Create your persistent practice page

Your Notion page is the durable record for this practice. The Free plan keeps this page setup at no cost.

Search for Notion in your browser.
Open the official Notion result.

You should now be on Notion's official website with access to its account flow.

Complete Notion's sign-in flow with your existing account.
Select Free if Notion asks you to choose a plan.

You'll see your Notion workspace after the account flow finishes.

Click New page in the sidebar.

You'll see an empty page where the practice can take shape.

Enter Look Back Before You Put a Time on a Job as the page title.
Leave the page body empty.

That first piece is ready. Your titled page now gives the practice a stable home.

Keep the titled page open in its browser tab.

A paper sheet or another persistent page tool preserves the same practice when Notion is unavailable.

Label your paper sheet or replacement page with the tool's name if Notion is unavailable.
Leave everything below the replacement label blank.

You should see the replacement tool's name at the top with a clear space underneath it.

Confirm Gmail and Google Calendar access

One Google Account keeps your series inbox connected to your reminder calendar. Both tools are available at no charge with that account.

Search for Gmail in your browser.
Open the official Gmail result.

You'll see Google's account flow or your existing Gmail inbox.

Create a Google Account through the on-screen account flow if you do not have one.
Complete the sign-in flow with the Google Account you will use for this practice.

You'll see the Gmail inbox for your chosen Google Account.

Search for Google Calendar in a new browser tab.
Open the official Google Calendar result.

You'll see Google Calendar open under a signed-in account.

Check the Google Account shown in Gmail's top-right account area.
Check the Google Account shown in Google Calendar's top-right account area.

Both tools should show the same Google Account. This confirms that the inbox and calendar belong to the same setup.

Leave Gmail unchanged without creating a project message or label.
Leave Google Calendar unchanged without creating project reminder events.

You have the access piece sorted. Both Google tools are ready under one account.

Can't open both Google tools?

Check the account shown in the top-right account area of each tool.
Complete the on-screen sign-in flow again if one tool shows a different account.

Help me get Gmail and Google Calendar open under the same Google Account.

A replacement mail tool plus a replacement calendar tool preserves the same boundary when a Google Account is unavailable.

Write the name of your mail replacement at the top of your practice page if a Google Account remains unavailable.
Write the name of your calendar replacement at the top of your practice page.

You should see both replacement names recorded above the blank practice area.

Open your named mail replacement once.
Open your named calendar replacement once.

You'll know both replacement tools are accessible before the recording practice begins.

Check each tool's role

A final layout check confirms that each tool has one job. This boundary prevents the reminders from becoming a second copy of the practice.

Where does everything live?

The practice page holds the remembered table, weekly jobs, estimates, actuals, rules, cost note, and later reading.

Google Calendar will hold only the dated checks. It stays unchanged during this step.

Gmail remains the series inbox. This project creates no email task, message, or label.

Before you compare the tools, which place do you expect to contain the working notes?

Arrange your titled practice page beside Google Calendar or your named calendar replacement.
Switch to Gmail or your named mail replacement.
Compare the Google Account shown in Gmail with the account shown in Google Calendar.
Confirm that each named replacement opens if you used swap-in tools.
Return to the side-by-side page and calendar view.

You should see the titled blank practice page beside the open calendar. On the primary path, Gmail and Google Calendar show the same Google Account.

Google Calendar contains no project reminders yet. Gmail contains no project message or label.

With replacements, each named tool should open from the label at the top of your practice page.

Good work. Your practice now has a durable home without producing an early result.

Your workspace is ready. Next, you'll give the blank page its remembered table and first-thought weekly list.

Build the Remembered Table

Your Notion page or paper replacement gives this practice a durable home. The page still needs a structure for the work you will record.

A remembered table gives you a starting baseline. A first-thought list fixes this week's job order before later treatment can influence it.

A list by itself cannot show whether a time comes from past work or padding. This step preserves that gap so you can see exactly what the next stage needs to solve.

Google Calendar stays unchanged during this step. All new material belongs on the project page.

In this step, get ready to:

Copy the five-window plan without changing any MAKES: line.
Create a remembered table with eight recurring work kinds.
Write ten expected jobs in their original first-thought order.

Map the page into five windows

The ordered plan gives every part of the practice a fixed place. Its MAKES: lines identify the concrete result of each window.

Return to the project page from earlier.
Add the ordered plan by copying this text exactly:

0 to 8
Write eight recurring kinds and one usual time each.
Mark the table as remembered.
MAKES: the table.

8 to 13
Write this week's jobs in first-thought order.
Number them 1 to 10. Do not reorder them.
MAKES: ten numbered jobs.

13 to 25
Odd jobs get three lines. Even jobs get one.
MAKES: ten estimates.

25 to 30
Write the gap, cutoff, and decision rules.
Set reminders for day 7, day 28, and day 66.
MAKES: the rules and three reminders.

30 to 35
Write where each actual goes.
Leave a space for the first-month cost note.
MAKES: the rule for actuals and the cost space.

How Does the Plan Work?

The five windows divide the page-building work into small sections.
Each MAKES: line names the result produced during that window.
The plan leaves its total unstated so the five original windows remain unchanged.

Read the five windows from top to bottom.
Confirm that every window keeps its MAKES: line.
Confirm that you did not add a sentence stating a total inside the plan.

You have locked in a roadmap that gives every later addition a named place.

Does the Plan Look Different?

Compare each line with the reference block if a time window or MAKES: line is missing.
Remove any extra sentence that states a total inside the plan.

Help me fix my ordered plan.

Build your remembered baseline

A remembered baseline captures the time you usually associate with each recurring kind of work. These times come from memory.

The worked layout below shows the shape of an eight-row table. Your table uses your own recurring work kinds and remembered times.

MY TABLE (remembered, not recorded).

Monthly report          2h 30
Supplier call           15 min
Stock count             45 min
Fixing a shift clash    20 min
Writing up a visit      30 min
Chasing an invoice      10 min
Weekly order            40 min
Tidying the back room   1h

What Does This Layout Show?

The heading labels the source of the times before any recorded actuals exist. Each row pairs one repeatable kind of work with one usual time.

The example uses plain characters such as 2h 30 and 15 min. This keeps the table readable on a page or on paper.

Type MY TABLE (remembered, not recorded). below the ordered plan.
Write eight kinds of work that you perform repeatedly beneath the heading.

You should now see eight work kinds beneath the remembered heading.

Add one usual time beside each work kind.
Use plain characters for every table entry.

You should see eight rows with one remembered time on every row.

You have captured the baseline with a label that keeps memory separate from later evidence.

Struggling to Choose Eight Kinds?

Choose work that produces a recognisable result more than once.
Use the time you usually say when someone asks how long that kind of work takes.
Keep each row broad enough to recur during future weeks.

Help me identify recurring work kinds.

Freeze the weekly list order

First-thought order preserves the sequence that comes to mind before alternating treatment affects odd and even positions. Sorting by size or urgency would change which jobs land in those positions.

Place your cursor below the remembered table.
Write the first job you expect this week as item 1.

The first item fixes the starting point of your original order.

Continue the same first-thought process until your list reaches item 10.
Keep every job in its original position.

You should now see ten expected jobs numbered 1 through 10.

Leave every job without an estimate.

How Future Lists Stay Consistent

Each later week uses another first-thought list numbered 1 through 10. The odd and even treatment begins only after that order is fixed.

Before you check, ask yourself whether this week's jobs can have defensible estimates yet.

Read the project page from top to bottom.
Check that the ordered plan contains all five windows.
Check that every MAKES: line remains in place.
Count the rows in the remembered table.
Count the jobs in the weekly list.
Compare the weekly list with your original first-thought order.
Confirm that no estimate appears beside a weekly job.

You will see five ordered windows with every MAKES: line preserved. The remembered table contains eight recurring work kinds with one usual time each.

The weekly list runs from 1 through 10 in its original order. It has no sorting or estimates.

The missing estimates are the intended shortfall. The page cannot yet show the past-work source behind a time.

Your starting record is now locked in. Next, you will make the source behind each estimate visible.

Estimate Jobs from Past Work

Your remembered table now sits above ten jobs in their original first-thought order on your Notion page. That preserved order makes the alternating treatment visible across the week.

However, the ten jobs still have no defensible estimates. This step exposes whether each time comes from past work or unsupported padding before you write it.

In this step, get ready to:

Give every odd-numbered job a three-line past-work trail.
Give every even-numbered job one estimate line.
Keep the completed example on the page as a reference.

Give odd jobs a visible past-work trail

A remembered baseline gives each job a starting time. The backward-looking sentence shows why you kept or changed that time.

Before you inspect the list, do you think another person could trace any job's estimate back to completed work?

Switch back to the Notion page from earlier.
Read job 3 from its number to the empty space below it.

You can see the job, but there is no time or source to defend. That shortfall is intentional.

Odd jobs solve this by showing the remembered time first. They connect the new estimate to evidence from completed work.

Match jobs 1, 3, 5, 7, and 9 with the closest kinds in your remembered table.
Choose each estimate from past work while keeping the remembered time when no past job supports a change.
Write exactly three lines beneath each odd-numbered job using this order: Table says: with the old remembered time, one sentence naming a past job or shared past-job pattern, and ESTIMATE: with the chosen time.
Read job 3 from top to bottom to check the three-line order.

You should see the old table time first. The next line should point backward to completed work.

The third line should contain the estimate. Jobs 1, 5, 7, and 9 should follow the same structure.

Does the second line point backward?

Replace a sentence that only describes the current job with the name of a completed job.
Use a shared pattern from several past jobs when one named job does not fit.
Keep the remembered time when you cannot support a different estimate from past work.

Ask for help checking whether your sentence points backward: Does my odd-job sentence refer to completed past work clearly enough?

Keep even jobs to one estimate line

Even-numbered jobs create the comparison pattern. Each one records an estimate without showing the three-line reasoning trail.

An added margin would hide whether the estimate came from past work or extra padding. The remembered table time stays in place when completed jobs support no different value.

Locate jobs 2, 4, 6, 8, and 10 in the original weekly list.
Choose each estimate from past work while keeping the remembered time when no past job supports a change.
Write one line beneath each even-numbered job in the format ESTIMATE: 10 min. using the chosen time.
Check each even-numbered job for extra reasoning or margin lines.
Read job 4 from top to bottom to check its one-line structure.

You should see one ESTIMATE: line beneath job 4. Jobs 2, 6, 8, and 10 should match that structure.

Does an even job have extra lines?

Remove any table-time line beneath the even-numbered job.
Remove any past-work sentence beneath the even-numbered job.
Return to the remembered table when an unsupported margin has changed the estimate.

Ask for help checking the odd and even pattern: Help me identify which lines to remove from my even-numbered jobs.

Add the completed worked example and verify

A completed reference shows how estimates later sit beside actual times. Its displayed actuals are examples of later entries.

Your own jobs only receive estimates today. The example stays on the page for future comparison.

Add the first five worked entries beneath your own weekly list by copying this block:

1  July report                     ODD
   Table says: 2h 30.
   Past July reports had the same three sections.
   ESTIMATE: 2h 30. ACTUAL: 2h 40. OVER.

2  Call the supplier               EVEN
   ESTIMATE: 10 min. ACTUAL: 25 min. OVER.

3  Stock count after big delivery  ODD
   Table says: 45 min.
   Past big-delivery counts took 1h.
   ESTIMATE: 1h. ACTUAL: 50 min. INSIDE.

4  Fix the shift clash             EVEN
   ESTIMATE: 10 min. ACTUAL: 20 min. OVER.

5  Write up warehouse visit        ODD
   Table says: 30 min.
   Past warehouse visit notes took 35 min.
   ESTIMATE: 35 min. ACTUAL: 30 min. INSIDE.

What does this example show?

Jobs 1, 3, and 5 show the remembered time before the backward-looking sentence.
Jobs 2 and 4 keep the estimate structure to one line.
The ACTUAL, INSIDE, and OVER entries model information written later.
These filled results are examples. They do not count as today's results.

Confirm worked jobs 1 through 5 appear beneath your own list.

You should see three odd examples with backward-looking sentences. You should also see two even examples with one estimate line each.

Did the first example lose its spacing?

Undo the paste when the worked jobs merge into your own numbered list.
Paste the block beneath job 10 so the example remains separate.
Check that each odd worked entry keeps its three indented detail lines.

Ask for help restoring the first half of the example: Help me separate this worked example from my own weekly list.

Complete the worked example by copying its final five entries below the first half:

6  Chase the invoice               EVEN
   ESTIMATE: 10 min. ACTUAL: 5 min. INSIDE.

7  Weekly order before holiday     ODD
   Table says: 40 min.
   Past holiday-week orders took 55 min.
   ESTIMATE: 55 min. ACTUAL: 1h. OVER.

8  Send the weekly rota            EVEN
   ESTIMATE: 20 min. ACTUAL: 15 min. INSIDE.

9  Tidy after a large delivery     ODD
   Table says: 1h.
   Past after-delivery tidy-ups took 1h 15.
   ESTIMATE: 1h 15. ACTUAL: 1h. INSIDE.

10 Book the machine repair         EVEN
   ESTIMATE: 30 min. ACTUAL: 30 min. INSIDE.

How does the example finish?

Jobs 7 and 9 complete the set of five odd worked entries.
Jobs 6, 8, and 10 complete the set of five even worked entries.
Job 10 shows that finishing exactly at the estimate counts as INSIDE.
The whole example now provides a reference for writing actuals after future jobs finish.

Confirm the worked example contains jobs 1 through 10 in numerical order.

You should see five worked odd entries with three detail lines. You should also see five worked even entries with one detail line.

Is the worked example incomplete?

Check for missing job numbers between 1 and 10.
Restore any missing ACTUAL or INSIDE or OVER text from the copied blocks.
Keep the worked example separate from your own estimates.

Ask for help comparing the copied text: Help me find what is missing from my ten-job worked example.

Before the final check, which entry should reveal a past-work trail at a glance?

Read your odd job 3 from top to bottom.
Read your even job 4 from top to bottom.
Scan jobs 1 through 10 to confirm their original order remains unchanged.

Your odd job 3 should start with Table says: and its old time. The next line should name a past job or shared past-job pattern.

The third line should begin with ESTIMATE:. Your even job 4 should contain one ESTIMATE: line only.

The same pattern should repeat across all ten jobs without changing their order. You now have ten estimates whose structure reveals how past work informed them.

That is the key shift completed. Your weekly list now carries a visible basis for every odd estimate and a consistent comparison line for every even estimate.

Your estimates are ready. Next, you will fix the counting rules and decision rule before any results exist.

Set Rules and Reminders

Your weekly list now has ten estimates with a visible source for every odd-numbered job. The next job is to protect how those entries become one later reading.

Rules written after the week could invite later exclusions. An early count could create a result before both groups are ready.

An on-the-day judgment could also move the cutoff. This step fixes each decision before work begins.

In this step, get ready to:

Prewrite the actual-writing and counting rules.
Add the delayed reading, research passage, limitations, and first-month cost space.
Create the day 7, day 28, and day 66 reminder events.

Prewrite the actual and counting rules

A finished job becomes useful when you record its actual time immediately. A countable job also needs a rule that handles equality, exclusions, and unfinished work consistently.

Which rules stay fixed?

Write the actual beside a job as soon as it finishes.
Inside includes equal to the estimate.
Leave out a job that never started.
Count an unfinished started job as over only when time already spent is longer than its estimate. Otherwise leave it out.
Count once, when each group has its first 20 countable jobs.
Once one group reaches 20, ignore its later extras while the other group catches up.
Use one subtraction only: odd inside count minus even inside count equals the gap.
Keep doing the three odd-job lines if the gap is 4 or more. Stop if it is under 4.
Day 7 is an actual-writing check. It is not a count.
Day 28 is the first time to look for enough jobs. If either group is short, do not calculate. Move the same check forward one week until both groups are ready.
Day 66 is the verdict date. Read the prewritten sentence against the one gap. If the equal-group rule is still unmet, the number still does not exist.

Switch back to your project page in Notion from earlier.
Add a blank ACTUAL: space beside the estimate for each of your ten jobs.
Copy every rule from the callout above into the page exactly as written.
Read job 1 from its first line through its blank ACTUAL: space.

You should still see exactly three lines for job 1. Its third line now has a place for the actual time when the job finishes.

Add the delayed reading and its limits

The delayed reading keeps today's setup separate from the later result. The research explains why day 66 is deliberately late without promising when this practice becomes automatic.

Why is day 66 deliberately late?

Research on repeated health behaviours found a middle time near two months for automaticity to approach a plateau, with wide variation. That finding describes many people and different behaviours, not this reader.

It does not say when this recording habit is installed. Day 66 is a deliberately late verdict date, not a promise.

Add the four-sentence research passage above to your project page exactly as written.
Read the final sentence of the new passage.

It should end by defining day 66 as a deliberately late verdict date. That wording keeps the research separate from a personal promise.

What belongs in the cost note?

At the end of the first month, fill the cost line once in words.
Name what you stopped doing to make room.
Name what it felt like to write an actual much larger than the estimate above it.
Do not record how long the practice took.

Add the first-month cost rule above to your page.
Leave a blank space directly beneath the rule for the future note.

Your page now reserves one written reflection for the end of the first month. It does not turn the practice itself into another timed job.

What can the later gap show?

Twenty against twenty is small. The cutoff is a rule written first, not proof.
The page cannot show that the extra lines caused the gap.
The even jobs are not a clean comparison because the remembered table cannot be unseen. The direction of that influence is unknown.
The work does not become faster. The prize is a time that can be planned around.
The aim is not to finish under every estimate. The hoped-for pattern replaces steady running-over with smaller misses in both directions.
Finishing early can feel worse because time was already given up.

Add every limitation and prize statement above beneath the research passage.

How does the one subtraction work?

EXAMPLE COUNT, NOT YOUR RESULT.

Odd inside: 13 of 20.
Even inside: 9 of 20.
GAP: 13 - 9 = 4.
Cutoff written first: 4.
Rule result: KEEP.

Add the example count above beneath the limitation statements.

The only filled count on your page is now clearly marked as an example. Your own gap remains absent today.

Create the three reminder events

The three dates protect different moments in the practice. Google Calendar holds those dates while your project page holds every rule and job.

Day 7 protects the recording habit. It checks whether actuals are being written without producing a count.

Switch back to Google Calendar from earlier.
Click Create.
Enter Day 7 actual-writing check in the event title field.
Select the date that falls seven days after today.
Use Add notification under Notifications to add one reminder.
Click Save.

You should see the day 7 event saved on its selected date.

What happens on day 7?

Day 7 checks whether you are writing each actual when its job finishes. No inside count or gap belongs on this date.

Day 28 checks whether both groups are eligible for the one subtraction. A short group moves the same check forward by one week.

Click Create.
Enter Day 28 enough-jobs check in the event title field.
Select the date that falls 28 days after today.
Use Add notification under Notifications to add one reminder.
Click Save.

You should see the day 28 event saved on its selected date.

What makes day 28 ready?

Both odd and even groups need 20 countable jobs before you calculate. If either group is short, the gap still does not exist.

Day 66 is the late verdict date. It reads the one eligible gap against the keep-or-drop sentence already on your page.

Click Create.
Enter Day 66 verdict in the event title field.
Select the date that falls 66 days after today.
Use Add notification under Notifications to add one reminder.
Click Save.

You should see the day 66 event saved on its selected date. All three reminders are now in place.

Before you check, do you expect to find any learner result or gap on your page today?

Search your Notion page for day 7.
Search your Notion page for day 28.
Search your Notion page for day 66.

You should find one fixed rule for each date. You should not find a calculated learner gap.

Return to Google Calendar from earlier.
Open the Day 7 actual-writing check event.
Confirm that the day 7 event has one notification.
Open the Day 28 enough-jobs check event.
Confirm that the day 28 event has one notification.
Open the Day 66 verdict event.
Confirm that the day 66 event has one notification.

You should see three saved events on three different dates. Each event should have a notification.

Missing an event or notification?

Reopen the event that is missing its notification.
Select Add notification beside Notifications.
Click Save.

Use this if a date, title, or notification still looks wrong: Help me check my three Google Calendar reminder events without creating an early result.

You did the careful part before the numbers could influence you. Your rules and reminders now protect one delayed reading without creating a result today.

Secret mission

Rebuild the Table on Day 66

On day 66, turn your recorded actuals into a checked replacement for the remembered table. You will use Gemini Apps or Claude to find each middle time. You will verify every value yourself before changing the page.

Clean Up Your Resources

The practice stays on the named no-cost plans. Keeping the resources creates no ongoing project charge.

Choose whether to keep the practice active, pause its notifications, or delete its project resources.

Stay on the No-Cost Plans

Keep using the no-cost plans named in this project. The project does not require Notion AI, a Google AI plan, or Claude Pro.

Resources you used:

The Notion page titled Look Back Before You Put a Time on a Job containing your complete recording practice.
The Google Calendar event for the day 7 actual-writing check.
The Google Calendar event for the day 28 enough-jobs check.
The Google Calendar event for the day 66 verdict.

Keep everything running

No action is needed. Choose this option if you want the page to keep supporting your recurring work.

Leave the Look Back Before You Put a Time on a Job page in place.
Keep notifications active on the day 7, day 28, and day 66 events.
Continue writing each actual beside its job as soon as the job finishes.

Your table stays available for future estimates. The reminders continue protecting the recording habit.

Pause - I'll come back to this later

Remove only the event notifications to pause the practice. The Notion page stays intact.

Return to Google Calendar from earlier.
Select the event for day 7.
Open the event's editing controls.
Choose Remove beside Notifications.
Click Save.
Repeat the notification removal for the day 28 event.
Repeat the notification removal for the day 66 event.
Confirm all three events remain saved without notifications.

All three dates remain on the calendar without prompts. This interrupts the recording habit until you restore the notifications.

Return to each saved event when you are ready to resume.
Choose Add notification beside Notifications.
Click Save after editing each event.

Each event keeps its original date. Its notification prompts you again.

Delete - I don't want to use this again

Deleting the practice can feel drastic. Your Google Account stays intact.

Only the Notion page and the three project events are removed.

Return to the Look Back Before You Put a Time on a Job page from earlier.
Open the page menu for Look Back Before You Put a Time on a Job.
Use the menu's deletion option.
Complete any confirmation shown by Notion.
Confirm the page is removed from your Notion workspace.

Return to Google Calendar from earlier.
Select the event for day 7.
Use the event's deletion control.
Select the event for day 28.
Use the event's deletion control.
Select the event for day 66.
Use the event's deletion control.
Confirm none of the three dates shows a project reminder.

That completes the cleanup. The page and all three reminder events are gone.

Nice Work!

You did it! You built a recording practice that uses completed jobs to put a more defensible time on the next recurring job.

You've learned how to:

Build a remembered baseline for recurring work. You can now replace eligible rows with times supported by recorded actuals.
Apply an alternating treatment without changing the first-thought order. Odd jobs show their past-work basis while even jobs keep one estimate line.
Use prewritten decision rules to protect one delayed reading. Your day 7, day 28, and day 66 reminders keep early results from creeping into the practice.
Secret Mission: Rebuild eligible table rows with a checked middle value from the latest three actuals. You verified each typical yourself before reading the existing gap against the keep-or-drop sentence.

Ready to quiz yourself?