PARA Method Explained: Organize Notes in 4 Folders

PARA uses four folders for notes, files, and references. This guide adds four practical tools most summaries skip. The Move Rule decides when a note should move, stay, or get linked. The Fit Score shows whether the problem is folders, names, search, or source review. The AI Review Rule treats bucket suggestions as drafts for your weekly review. The PARA Playbook turns cleanup into a 15-minute review instead of a rebuild.

The part most PARA summaries miss is the move rule. I tested this rule during a weekly review of 47 saved notes in my own workspace. I do not start cleanup by making more folders. I start with the repeat-search problem. If I search for the same note twice in one week while working on the same output, that note either belongs in a current project, needs a clearer name, or should become part of an area I maintain.

Use the PARA Fit Score in this guide as the practical test. If the score is below 5, fix bucket names and project outcomes first. If it is 8 or higher, PARA is probably fine. The next issue is search, links, or source review.

The PARA Move Rule

Most PARA guides explain the four buckets. The harder choice is knowing when to move an item. Use this rule:

Move a note when its job changes. Link it when two jobs need it. Leave it alone when search can find it.

Forte's official PARA guide makes the same action-first point:

Tiago Forte, founder of Forte Labs: "the ultimate system for organizing your life is one that is actionable."

That keeps PARA just-in-time. You avoid a long filing project before the note matters. You also avoid a junk drawer where every saved link becomes a "resource."

Just-in-time organization means you file at the moment of use. Do not build empty folders for a future self you cannot predict. Wait until a note has a job, then move it to the smallest place that makes the next use obvious.

Table 1: PARA Move Rule for deciding whether to move, link, or leave an item.

Where PARA Fits in a Second Brain

Building a Second Brain is the larger method. PARA is the filing layer inside it. CODE explains the work loop. Capture saves raw material. Organize gives it a home. Distill makes the best parts easier to reuse. Express turns notes into an output.

That means PARA should not do every job. It should answer one question: where should this item live right now?

Table 2: Role-specific PARA use cases and the layer each reader may add next.

For AI tools, PARA is a guardrail. Let AI suggest a bucket, rename a vague file, or find a source across Resources. Do not let it move items without a weekly review. The useful check is whether the note has a current job, an ongoing role, or future value.

What Is the PARA Method?

The PARA method is an organization system created by Tiago Forte. It uses four buckets: Projects, Areas, Resources, and Archives. These buckets cover active work, ongoing roles, useful notes, and old material.

PARA is an acronym for the four buckets:

1. Projects: Short-term efforts with a clear goal and deadline
2. Areas: Ongoing responsibilities you maintain over time
3. Resources: Topics of interest you may reference in the future
4. Archives: Old items from the other three buckets

That's the entire system. No sub-categories to agonize over. No tagging taxonomies to design. Four buckets map to how you use information, with no color-coding schemes to maintain.

The important shift is activity. A project sits close to current work. An area stays open because it needs upkeep. A resource waits until it becomes useful. An archive keeps old material out of the way without deleting it.

Why Four Categories?

Tiago Forte designed PARA around one idea. Information is useful when it supports action. The four buckets reflect four action levels:

• Projects are the most actionable. You're working on them right now
• Areas require ongoing attention but aren't time-bound
• Resources might be useful someday
• Archives are done but worth keeping

This path from active to old tells you where to look. Working on something now? Check Projects. Need a note for an ongoing role? Check Areas. Exploring a topic? Check Resources. Looking for old work? Check Archives.

Breaking Down Each Category

Projects

A project has two defining characteristics: a clear goal and a deadline. If it doesn't have both, it's not a project.

Examples:

• Write research paper on climate policy (due March 15)
• Redesign portfolio website (launch by end of month)
• Plan spring break trip (depart April 5)
• Complete biology lab report (due Friday)

Not projects:

• "Get healthier" (no deadline, no clear endpoint)
• "Learn Spanish" (ongoing, no clear completion)
• "Stay on top of email" (that's an Area)

Most people have 10-15 active projects at any time. If you have more than 20, some of them aren't projects. They're aspirations. Move them to Resources or archive them.

Areas

Areas are ongoing roles with a standard to maintain but no finish date. They represent commitments in your life.

Examples:

• Health and fitness
• Finances
• Academic coursework
• Professional development
• Apartment / living space
• Relationships

Areas don't end. You don't "finish" your health. You maintain it. That changes where notes go. Project notes move to Archives when the project ends. Area notes build over time.

Resources

Resources are topics you might use later. They are not tied to a current role. They hold ideas, links, and notes for future work.

Examples:

• Machine learning techniques
• Travel destinations
• Cooking recipes
• Design inspiration
• Productivity methods (yes, including PARA itself)

Resources are the most flexible bucket. A note about salary talks goes here if you are only learning. If you start a job search, move that note into the project.

Archives

Archives hold old items from the other three buckets. Put finished projects, dropped roles, and stale resources here.

Examples:

• Completed course materials from last semester
• Old client projects
• A hobby you've paused
• Tax documents from previous years

The archive isn't a graveyard. It's cold storage. You can pull things out when they become relevant again. The point is keeping your active workspace clean.

How to Implement PARA

Step 1: Start Where You Are

Don't reorganize everything at once. That's a trap. Instead, apply PARA to new information going forward. Old files can stay where they are until you naturally need them.

Step 2: Create Four Folders

In your primary tool. Whether that's your file system, Notion, Atlas second brain workspace, or anything else. Create four folders:

/Projects
/Areas
/Resources
/Archives

Step 3: Apply the Two-Question Test

When you save something new, ask two questions:

1. Is this related to a current project? If yes, it goes in that project folder.
2. Is this related to an ongoing area of responsibility? If yes, it goes in that area.

If neither, it goes in Resources. If it's old or inactive, Archives.

Step 4: Do a Weekly Review

Spend 15 minutes each week reviewing your PARA structure:

• Have any projects been completed? Move them to Archives.
• Have any resources become relevant to a current project? Move them.
• Are any "projects" areas in disguise? Recategorize them.

The weekly review keeps PARA from becoming another abandoned system.

PARA Goals and Commitments

PARA works best when each active folder points at a real commitment. A vague folder name creates clutter because it does not say what you owe, when it matters, or who needs the result.

Identifying Commitments

Start with the promises you have already made. A class assignment, client deliverable, job search, product launch, or trip plan belongs in Projects when it has an outcome and a date. A role such as health, finances, teaching, or team management belongs in Areas because it needs steady upkeep.

Connecting Efforts to Long-Term Goals

PARA is not a goal-setting system, but it should reflect your goals. If a folder does not support a current commitment, an ongoing role, or future work you still care about, it probably belongs in Archives.

Goal Setting Inside PARA

Use goals to name projects, not to create more buckets. Improve writing is too vague for Projects. Draft literature review by July 12 is clear enough to act on, review, and archive later.

PARA vs Other Systems

Different systems solve different problems. Here is how PARA compares with other approaches. For a deeper look, see our comparison of note-taking systems.

Table 3: PARA compared with Zettelkasten, folders, and tags.

PARA vs Zettelkasten

The Zettelkasten method and PARA solve different problems. PARA organizes information for action. Zettelkasten connects ideas for thinking.

Use PARA when you need to manage projects, roles, and practical notes. It helps you find things fast and keep your workspace clean.

Use Zettelkasten when you are building long-term knowledge. It fits researchers, writers, and students who need ideas to connect over time.

Use both when PARA handles the top level. Let Zettelkasten handle idea work inside Resources.

PARA vs Traditional Folders

Deep folder trees seem logical but break down quickly. Where do you put a proposal that involves two clients? What about a personal project that uses work skills?

PARA avoids this by sorting around action. The same file might move from Resources to Projects to Archives. It should live where it helps most right now.

The CODE Framework and PARA

Capturing Information

PARA is the storage layer inside Tiago Forte's broader CODE workflow: capture, organize, distill, express. PARA handles the organize step. It tells you where a note should live after capture.

Table 4: PARA's role inside the CODE workflow.

Distilling to Essentials

PARA does not decide which sentence matters most. That is distillation work. Keep highlights, quotes, and key claims with the source until a project needs them.

Expressing Your Knowledge

Expression is the output step. A paper, memo, lesson plan, or launch brief should pull from Projects first. Resources feed the work only after the project has a real deliverable.

The PARA Playbook: Friction Tests and Team Rules

I use a simple PARA friction test when a folder starts to feel messy:

Table 5: PARA friction test for weekly review.

AI search does not replace PARA. It reduces the penalty when a useful note sits in the wrong bucket. It can suggest where a source belongs. The weekly review still decides whether the note supports a project, an area, or future work. If Resources contains papers or source notes, read the smart notes app guide after setup.

PARA and AI Integration

AI can help sort after PARA gives you the rule. Let it propose a bucket, rename vague files, or find old sources. Review the move yourself before changing the folder.

Team Collaboration with PARA

For teams, PARA needs naming rules before it needs more folders. Use one shared rule per bucket:

"Only when a project or area becomes collaborative... should it be moved to shared Projects or Areas folders."

Tiago Forte makes that point in his team PARA guide. Shared PARA should start small. Move work into the team system only after another person needs the folder.

Table 6: Team PARA naming rules that keep shared folders readable.

Using Labels and Links in PARA

Use links and labels only when they solve a real lookup problem:

Table 7: Labels and links to use with PARA when one item belongs in more than one place.

When Not to Move a Note Yet

PARA gets worse when every useful item moves too early. Before moving a note, check the job it is doing today.

Table 8: PARA checks for deciding when a note should stay where it is.

Using PARA with Atlas

PARA gives you structure. A research tool can help when one folder turns into a source library. That is the part a folder system handles poorly.

Here's how they work together:

Projects: Keep project sources together. If the project depends on papers or reports, use cited search to check claims.

Areas: Build small reference bases around ongoing roles. A health area might hold lab notes, doctor questions, and insurance files. A teaching area might hold rubrics, syllabi, and student feedback.

Resources: Keep useful notes here until they support active work. Search can help. The weekly review still decides when a resource should move.

Archives: Keep old notes out of view. Make sure they stay searchable. An old source can become useful again.

The split is simple. PARA decides where the note lives. Search decides how fast you can retrieve it. If Resources is mostly papers, reports, or source notes, add better search before you add more folders.

Best Software Tools for PARA

Use file folders or Drive for shared documents, Notion for project databases, Obsidian for linked notes, OneNote or Evernote for capture, and Atlas-style cited search when Resources becomes a source library.

The 15-Minute PARA Review Scorecard

PARA only works if old choices get corrected. Use this quick review once a week:

Table 9: Weekly PARA review checklist for keeping folders clean.

PARA Fit Score

Use this quick score before you rebuild a messy notes app. Give each row 0, 1, or 2 points.

Table 10: PARA Fit Score rubric for deciding whether to fix names, move notes, or rebuild folders.

Scores below 5 usually mean the problem is not the app. The buckets are unclear. Scores from 5 to 7 usually need a review pass. Scores from 8 to 10 mean PARA is working, and the next problem is probably search, links, or source review.

Here is the score in use:

Table 11: Worked PARA Fit Score examples showing the manual move that improves each setup.

Common PARA Mistakes

Mistake 1: Too Many Projects

If you have 25 "projects," most are not real projects because real projects need active attention. Most people can handle 5-10 at a time, so move the rest to Areas, Resources, or Archives.

Mistake 2: Confusing Areas and Projects

"Get healthy" is an area, while "Run a 5K by June" is a project. Projects end, and areas keep going. Treating an area as a project creates a task that never closes.

Mistake 3: Over-Organizing Resources

Your Resources folder does not need 50 subfolders, so keep it simple. If search keeps failing, improve names before you add more folders.

Mistake 4: Never Archiving

If you have not touched a project in three months, it is not active, so archive it. You can always bring it back.

Mistake 5: Applying PARA Everywhere at Once

Do not reorganize email, files, notes, and bookmarks at the same time. Pick one tool, get PARA working there, and expand later.

Who Should Use PARA?

PARA works best for people who:

• Manage several projects at once
• Need a low-upkeep system
• Want to find notes quickly without complex setup
• Feel overwhelmed by their current digital mess
• Have tried and abandoned more complex systems

PARA may not be enough if you:

• Need deep idea links. Add Zettelkasten for this.
• Work mainly with research and academic writing.
• Need cited search across many source notes.

For most people, PARA is a strong starting point. Add other systems only when a real problem appears.

PARA Starter Templates and FAQs

Use these starter folders before you design anything custom:

/Projects/Project name - outcome
/Areas/Role or standard to maintain
/Resources/Topic or source library
/Archives/Old project name - archived

This template is enough for most first setups. Add subfolders only after a folder becomes hard to scan.

Table 12: PARA setup FAQ for common implementation hurdles.

Getting Started

You can start PARA in five minutes:

1. Create four folders in your primary tool
2. Move your current active projects into the Projects folder
3. Sort new notes with the two-question test
4. Schedule a 15-minute weekly review

For more on building a second brain, start with the tool guide.

Compare personal knowledge management and the Zettelkasten method when PARA feels too light.