PRODUCTIVITYDays to result

The PARA Organization Method

Organize your digital life into four categories based on actionability not topic

Problem it solves

low productivity

Best for

Knowledge workers overwhelmed by digital files and notes, anyone whose documents are organized by topic but never used, professionals managing multiple projects simultaneously, people who want a universal system across all their apps

Not ideal for

People working on a single long-term project with no variety, environments with rigid pre-existing organizational structures, situations where a simple folder hierarchy is genuinely sufficient

Overview

Why this framework exists

PARA is Tiago Forte's universal organizational system that replaces traditional topic-based filing with actionability-based filing. PARA stands for Projects (active endeavors with deadlines and defined outcomes), Areas (ongoing responsibilities you manage continuously), Resources (topics of ongoing interest for reference), and Archive (inactive items from the other three categories). The revolutionary insight is that most organizational systems fail because they are built around subjects (marketing, finance, personal, work) rather than around how actionable the information is. Topic-based systems create comprehensive reference libraries that feel organized but are rarely used. PARA ensures that the most actionable information — your current projects — is always front and center, while less actionable information recedes into Areas, Resources, and Archive. The system applies universally across note-taking apps, file systems, email, and task managers.

Core principles

5 total
  1. Organize by actionability not by topic — projects first, then areas, then resources
  2. Every note file and document should live in one of exactly four categories
  3. The system should be universal across all apps and platforms
  4. Projects have deadlines and defined outcomes — everything else is an area, resource, or archived
  5. Regular maintenance moves items between categories as actionability changes

Steps

4 steps
  1. Define Your Current Projects
    List every active project you are working on — each must have a defined outcome and a deadline. Projects are the most actionable category and should contain the notes, files, and resources directly needed for current work. Examples: launch new product, write quarterly report, plan team offsite. If it does not have a deadline and outcome, it is an Area, not a Project.
  2. Identify Your Areas of Responsibility
    List the ongoing areas of your life that require continuous management but do not have deadlines or defined endpoints. Examples: health, finances, team management, professional development, home maintenance. These are responsibilities you maintain indefinitely, containing reference material and ongoing notes.
  3. Catalog Your Resources
    Collect topics of ongoing interest that are not tied to current projects or responsibilities. Examples: marketing techniques, book notes, design inspiration, industry trends. Resources are reference material you want to access when relevant projects arise in the future.
  4. Archive Everything Else
    Move completed projects, inactive areas, and outdated resources to the Archive. The Archive is not deleted — it is accessible but out of the way. This keeps your active workspace clean and focused on what matters now. Regular archiving prevents the system from becoming cluttered and overwhelming.

Checklist

Saved in your browser

Examples

2 cases
PARA Applied Across Multiple Apps

Forte demonstrates using the same PARA structure across a note-taking app, file system, email, and task manager. Each app has the same four top-level categories. A project folder in the file system mirrors a project tag in the note app, which corresponds to a project list in the task manager. This universality means you always know where to find things regardless of which app you are in.

OutcomeThe universal structure eliminated the common problem of information fragmentation across apps. Instead of wondering whether a document was in Google Drive, Evernote, or email, the PARA structure ensured consistent findability across all platforms.
Tiago Forte
The Deadline Test for Projects vs Areas

A common confusion is whether something is a Project or an Area. Forte uses the deadline test: writing a book is a Project (deadline, defined outcome). Becoming a better writer is an Area (ongoing, no endpoint). Running a marketing campaign is a Project. Managing the marketing function is an Area. The distinction seems simple but transforms how people organize their work.

OutcomePeople who applied the deadline test reported immediately decluttering their task lists and note systems by 30-50%, as they recognized that many items they treated as active projects were actually ongoing areas requiring different management approaches.
Tiago Forte

Common mistakes

3 traps
Creating Too Many Categories
The entire point of PARA is having exactly four categories. Adding subcategories, tags, or additional levels reintroduces the complexity the system is designed to eliminate. If you cannot decide between Project and Area, use the deadline test: does it have a defined outcome and deadline? If yes, Project. If no, Area.
Never Archiving
Without regular archiving, the Projects and Areas folders become cluttered with inactive items, destroying the actionability gradient that makes PARA work. When a project completes, archive it immediately. When an area becomes irrelevant, archive it. The Archive exists specifically so you can remove without deleting.
Organizing Resources by Topic Hierarchy
Resources should be a flat list of topics, not a nested hierarchy. Creating sub-folders within Resources reintroduces the topic-based complexity PARA replaces. If a Resource folder has sub-folders, it has probably become too broad — split it into multiple flat Resources or consider whether it should be an Area.

Origin story

How this framework came to be

Forte created PARA after years of experimenting with organizational systems that all eventually collapsed under their own weight. Topic-based systems grew endlessly — every new interest created a new folder, and no amount of subfolder nesting resolved the ambiguity of where things should go. He realized the solution was to organize not by what information is about but by how actionable it is. Projects change frequently, Areas change slowly, Resources change rarely, and the Archive captures everything else. This actionability gradient solved the organizational problem universally.

Source

Traced to primary
Source · ESSAY
Building a Second Brain: An Overview
Tiago Forte · 2019
Open source →

Related frameworks

Browse all Productivity →