Notion Goal Tracker Template: Quarterly OKRs and Check-ins
Running a Quarterly OKR Cycle Inside the Notable Dashboard
Objectives and Key Results (OKRs) are simple in theory and messy in practice. You name an ambitious objective, attach two or three measurable key results, and check in often enough that the numbers stay honest. The mess comes from tooling: a spreadsheet nobody opens, or a habit tracker with no memory of the bigger goal. The free Notable Dashboard closes that gap because its Goals & Habits component and its Tasks & Projects database live in the same workspace, so an objective and the work feeding it never drift apart.
This walkthrough sticks to the fields the template ships with — the Goals Tracker, the Tasks database, and the Quick Stats row at the top of the dashboard.
Framing an Objective as a Goal With Measurable Key Results
An objective is the qualitative destination; the key results are the quantitative proof you arrived. The Goals Tracker treats each entry as a single goal record, so the cleanest mapping makes the objective the goal itself and expresses its key results through the fields on that record.
Get the Free Notion Dashboard
Tasks, goals, habits, budget and calendar. 100% free.
Grab the Free Template →Write the objective as the goal Name — something directional like “Launch the redesigned onboarding flow” rather than a vague “Improve onboarding.” Then lean on the fields that make it measurable:
- Progress (%) becomes your headline key-result number. With one dominant metric, drive Progress directly from it; with several, set Progress to the average completion so a single glance tells you whether the quarter is on track.
- Due Date anchors the objective to the quarter — the last working day of Q1, Q2, Q3, or Q4, so the goal has a hard horizon rather than an open-ended “someday.”
- Status keeps the lifecycle visible as the goal moves from planned to active to closed.
When an objective genuinely needs multiple distinct key results, give each one its own goal record sharing the same quarterly Due Date, grouped under a shared tag. That keeps every key result independently measurable through its own Progress field instead of hiding three metrics behind one bar.
Writing Key Results That the Fields Can Actually Track
A key result only works if it maps to a number the template can hold. “Grow trial signups from 400 to 1,000” translates to a Progress value you update weekly; “Make onboarding feel better” does not. Before committing an objective, check that every key result reduces to a percentage, a count, or a clear done/not-done state that Progress and Status can represent.
Setting the Quarter-Long Due Date and Cadence
The Due Date field does more than mark a deadline; it defines the window your check-ins work within. A calendar quarter gives you roughly thirteen weeks — long enough to move a real metric, short enough that drift shows up fast. Set it the moment you create the goal, before you touch any tasks, so the ambition is bounded from day one. With the horizon fixed, the cadence is a rhythm you run on top: a light weekly touch and a heavier monthly review.
The Weekly and Monthly Check-in Ritual
The check-in is where OKRs earn their keep. The point is not to celebrate activity but to update Progress with the current truth and decide what to do about the gap.
The Weekly Touch
Once a week, open the Goals Tracker and do three things per active goal: update Progress (%) to the latest real number, glance at the Due Date to gauge the runway left, and confirm the Status still matches reality. Five minutes is enough. The discipline is refusing to inflate Progress to feel productive; a stalled number is a signal, not a failure.
The Monthly Review
Once a month, go deeper. Ask whether each key result is pacing toward its target given the time gone, whether any objective should be re-scoped, and whether the tasks feeding it are the right ones. This is also when to retire goals whose Due Date has passed and move their Status to done, keeping the tracker a picture of the live quarter rather than a graveyard.
How the “Active Goals” Quick Stat Rolls Up
The Quick Stats row at the top of the dashboard is not typed in by hand — each stat is a filtered or rolled-up view of a linked database. The Active Goals stat counts goal records currently in flight, so it moves on its own as you update Status during check-ins. Close a completed objective and the number ticks down without anyone editing the dashboard. That live count is a quiet accountability check: if Active Goals reads eleven halfway through the quarter, you are over-committed, and the stat is telling you to cut before the numbers do.
Linking Key-Result Tasks to a Parent Goal
An objective stays honest only when the work beneath it is visible. The Tasks & Projects database carries Name, Status, Due Date, Priority, Progress (%), Project, Tags, and Assigned To — enough to tie execution back to the goal it serves. Tag the tasks that move a given key result, and set their Due Dates inside the quarter so they ladder up to the goal’s deadline.
Now the two databases reinforce each other. When a goal’s Progress looks stuck during a weekly touch, drop into Tasks & Projects, filter to that objective’s tag, and see whether the supporting work is blocked, unassigned, or not started. Because everything is one database surfaced through multiple views, that connection costs no extra setup. To try the structure first, you can duplicate the free Notable Dashboard and map your current quarter into the Goals Tracker in a single sitting.
Run this loop for a quarter and OKRs stop being a document you revisit twice and become a living instrument: objectives bounded by Due Dates, key results carried in Progress, execution linked through Tasks, and a Quick Stat that never lets you pretend you are less committed than you are.
