Goal Plan
Success Definition
Projects / Milestones
| Milestone | Due date | Next action | Status |
|---|---|---|---|
Daily Actions
| Task | When | Linked milestone | Status |
|---|---|---|---|
Supporting Habits
| Habit | Frequency | Why it supports the goal |
|---|---|---|
Use this goal planning template to define what done looks like, break the goal into milestones and daily actions, choose the habits that support it, and set a review cadence. The daily action table is the part that decides whether the goal moves.
Blank What you copy
| Milestone | Due date | Next action | Status |
|---|---|---|---|
| Task | When | Linked milestone | Status |
|---|---|---|---|
| Habit | Frequency | Why it supports the goal |
|---|---|---|
Filled in An example goal
| Milestone | Due date | Next action | Status |
|---|---|---|---|
| Proposal agreed with Maria | 30 October | Call on Tuesday | In progress |
| Venue booked | 6 November | Pay Sam the deposit | Waiting |
| Booking page live | 20 November | Write the page copy | Not started |
| Task | When | Linked milestone | Status |
|---|---|---|---|
| Three questions for Maria | Monday, 9:00 | Proposal agreed | Done |
| Pay the venue deposit | Wednesday | Venue booked | Scheduled |
| Draft the booking page | Thursday, 9:00 | Booking page live | Scheduled |
| Habit | Frequency | Why it supports the goal |
|---|---|---|
| 9:00 focus block | Weekdays | The launch work happens before the inbox opens |
| Friday weekly review | Weekly | Keeps the milestones honest |
Paste it into Notion Obsidian Bear iA Writer Logseq Craft or any app that reads Markdown. The # marks turn back into headings and the | marks into tables.
Writing in Apple Notes, Google Docs or Word? instead, and it pastes with the headings and tables already in place.
# Goal Plan Goal: Horizon: Why it matters: ## Success Definition - What does done look like? - How will I know progress is real? ## Projects / Milestones | Milestone | Due date | Next action | Status | |---|---|---|---| | | | | | ## Daily Actions | Task | When | Linked milestone | Status | |---|---|---|---| | | | | | ## Supporting Habits | Habit | Frequency | Why it supports the goal | |---|---|---| | | | | ## Risks - What could derail this? - What would make me revisit the goal? ## Review - Review cadence: - Next review date: - Latest note:
Goal:
Horizon:
Why it matters:
What does done look like?
How will I know progress is real?
| Milestone | Due date | Next action | Status |
|---|---|---|---|
| Task | When | Linked milestone | Status |
|---|---|---|---|
| Habit | Frequency | Why it supports the goal |
|---|---|---|
What could derail this?
What would make me revisit the goal?
Review cadence:
Next review date:
Latest note:
Start by defining what done means. A vague goal produces vague action. A useful goal has a success definition you could show someone else, a next milestone, and a next action small enough to start this week.
Then connect the goal to the day. The most important part of this template is not the goal statement at the top. It is the daily action table. If a goal never changes what is on today's list, it stays an intention.
Fill in the risks section honestly. Some goals should change when the context changes, and naming those conditions in advance makes the later review far more useful than a yes or no on progress.
The path from a goal to a finished thing is short when you write it out:
One goal with a next action beats five goals with none.
A good goal plan explains why the goal matters, defines what success looks like, names the next milestone, and points at a specific action that belongs on a task list or calendar.
Start with the next visible milestone rather than the finished outcome, then write the smallest action that moves it forward. Repeat after each milestone instead of planning the whole path up front.
Sometimes. If a repeated behavior is what actually produces the outcome, track it as a habit. If a step happens once, keep it as a task and do not turn it into a streak.
Fewer than feels comfortable. Most people can hold one or two active goals alongside ordinary life, and a plan that fills a whole page is usually several goals wearing one name.
Set the cadence when you write the plan, and match it to the goal's horizon. A quarter-long goal usually wants a weekly check-in and a monthly look at whether the goal still fits.
HourLife is built around connecting the bigger picture to the day: goal, project, task, focus session, review. Goals can carry projects and tasks, tasks can appear in Today, and focus sessions attach real effort rather than intention.
That makes progress something you can read back. Daily review, highlights, and journal records accumulate into a history, so a goal check-in draws on evidence instead of a percentage bar.