A Simple Actions and Task Management System In Notion

TL;DR

Create new actions from the Actions database home view, including priority, status (e.g., “not started”), and a target date.

Briefing Cornell Notes

Briefing

A pre-built Notion “Actions” database for freelancers and solo businesses turns day-to-day task management into a structured workflow: create an action, connect it to objectives and projects, track it through filtered views, and then archive it automatically once finished. The system’s core value is that it keeps tasks tied to business goals—like monthly traffic targets—while also supporting practical execution details such as deadlines, dependencies, and quick navigation links.

Setup starts from a home dashboard. If projects and objectives are “stacked,” that dashboard becomes the home view; otherwise, the Actions database appears as a single-page view with key fields. From there, a new action can be added directly from a priority column. The example walks through creating a high-priority SEO task for an existing project (“seo foundations project”), with the action name set to something like “write our first keyword article.” The action is then assigned an area (e.g., “contents”), linked to relevant objectives (such as “2500 monthly website visitors” or an “article per week” goal), and given a status of “not started.” A target date is set to keep the work time-bound, and a pre-built task template can be inserted to standardize the action page.

Two additional fields add operational depth. The “go link” field is designed for faster navigation—useful when the work happens outside Notion. For instance, a link can point directly to a Webflow CMS page so the writer can jump from the task board into the content system. The “blocked by” field supports task dependencies. By selecting tasks from within the same Actions database, a user can mark what must be completed first. If a task is blocked, a dedicated “blocked tasks” view can list the blocked task, the specific blocking task, and the project it belongs to—making bottlenecks visible without manual searching.

The database includes multiple built-in views to manage workload at different time horizons. “Live actions” show anything not yet completed or archived. Separate views list tasks due today, due within the next seven days, and due within the next 30 days. There are also views for archived and completed tasks, plus status-based filtering and the blocked-tasks view. Completion drives the workflow: once an action is marked complete, it disappears from “live actions” and appears under “archived and completed tasks,” keeping the board clean and ensuring the system reflects current priorities.

Overall, the system functions as a goal-linked task engine: it connects execution to objectives, supports deadlines and dependencies, and uses views to surface what matters now—while automatically moving finished work into an archive for later reference.

Cornell Notes

The Notion Actions system provides a goal-linked task workflow for freelancers and solo businesses. Users create actions with priority, status, target dates, and an optional template, then connect each action to existing projects and objectives (e.g., monthly website visitor targets). Two fields enable practical execution: “go link” for quick jumps to external tools like a CMS, and “blocked by” for dependencies between tasks stored in the same database. Built-in views (live, due today, next 7/30 days, archived/completed, status filters, and blocked tasks) help users focus on what’s actionable. Marking an action complete automatically removes it from live views and moves it into archived/completed.

How does the system ensure tasks stay connected to business goals rather than living as isolated to-dos?

Each action can be linked to objectives and projects already stored in Notion. In the example, the action “write our first keyword article” is tied to an objective such as “2500 monthly website visitors” (and/or an “article per week” objective). That linkage means the task board reflects goal progress, not just personal productivity.

What’s the difference between “go link” and “blocked by,” and when would each be used?

“Go link” is for navigation—typically pointing to where the work happens outside Notion (e.g., a Webflow CMS page). “Blocked by” creates dependencies inside the Actions database: if a task can’t start until another task is finished (like keyword research before writing a keyword article), the blocking task is selected in “blocked by.”

How do the pre-built database views help someone triage work day-to-day?

The system includes multiple views that slice the same Actions database by time and state. “Live actions” show tasks not completed/archived, while “due today,” “next seven days,” and “next 30 days” surface near-term priorities. There are also views for archived/completed tasks, status filtering, and a dedicated “blocked tasks” view that lists what’s waiting on what.

What happens to an action after it’s marked complete?

Completion triggers an automatic move in the workflow. The example notes that once a task is marked complete (e.g., after finishing keyword research), it immediately disappears from “live actions” and appears under “archived and completed tasks,” keeping the active board focused on unfinished work.

Why does the system support adding tasks directly from a priority column?

Adding from the priority column streamlines intake and ensures new work enters the workflow with an assigned priority. In the example, a new action is created as “high priority” directly from the list/column, and the priority is already preset to highest priority because it was added from that column.

Review Questions

When creating a new action, which fields are used to set priority, status, and timing, and how are actions linked to objectives?
How would you model a dependency where keyword research must be finished before writing a keyword article using “blocked by” and the blocked-tasks view?
What view(s) would you check to find tasks due today versus tasks that have already been completed and archived?

Key Points

1
Create new actions from the Actions database home view, including priority, status (e.g., “not started”), and a target date.
2
Link each action to the relevant project and objective so execution maps to business goals like monthly traffic targets.
3
Use “go link” to jump quickly to external systems (such as a Webflow CMS page) where the work is performed.
4
Use “blocked by” to define task dependencies by selecting other tasks within the same Actions database.
5
Rely on built-in views—live, due today, next 7/30 days, archived/completed, status filters, and blocked tasks—to manage workload.
6
Marking an action complete automatically removes it from live views and moves it into archived/completed tasks to keep the board current.

Highlights

“Blocked by” turns dependencies into a first-class feature by linking tasks inside the same Actions database and surfacing bottlenecks in a dedicated blocked-tasks view.

“Go link” supports faster execution by letting users click out from an action board directly into an external CMS or tool.

Completion isn’t just a checkbox: finished actions disappear from “live actions” and land in “archived and completed tasks” automatically. 

Topics

Notion Actions Database
Task Dependencies
Objective Linking
Filtered Views
Archiving Workflow