The PARA Method: A Complete Guide

PARA is a system for organising digital information, created by productivity educator Tiago Forte. He first published the framework in a 2017 blog post and later expanded it into a dedicated book, The PARA Method (2023), building on ideas from his earlier Building a Second Brain (2022).

The acronym stands for the system's four categories:

Projects: short-term efforts with a clear goal and deadline.

Areas: ongoing responsibilities with no end date.

Resources: topics of interest for future reference.

Archives: inactive items from the other three categories.

That's all there is to it. Every piece of digital information in your life, every document, note, file, bookmark, and half-formed idea, belongs in one of these four buckets. The organising principle isn't topic or subject matter but actionability. Projects are the most actionable (you're working on them right now), Archives are the least (you're done with them), and Areas and Resources sit somewhere in between.

Most people organise information by what it's about. Marketing stuff goes in the marketing folder. Finance stuff goes in the finance folder. Forte's argument is that this is the wrong axis entirely. A PDF about marketing strategy could be a project deliverable, an area reference, a general resource, or an archived artifact. Where it belongs depends on its role in your life right now, not its subject matter.

It's a subtle shift but it changes how you relate to your files. Instead of asking "what is this about?" you ask "what am I doing with this?" One question leads to taxonomies, the other leads to action.

The four categories

Projects

A project is a series of tasks linked to a goal, with a deadline. That last part matters, because a project has a finish line. You will, at some point, be done with it.

Examples: launch the new website, write the quarterly report, plan the holiday, move flats, hire a new designer, complete the online course.

Each project should be specific enough that you can picture what "done" looks like. "Improve my health" is not a project. It's an area (we'll get to those). "Run a 5k in under 30 minutes by September" is a project. The verb, the specificity, and the deadline are what make it one.

Forte recommends keeping your active project list between 10 and 15. More than that and you're probably confusing projects with areas, listing tasks as projects, or carrying zombie projects that should have been archived weeks ago.

Areas of responsibility

An area is an ongoing part of your life that requires continuous attention but has no endpoint. Areas don't get completed, they get maintained, which is what makes them fundamentally different from projects.

Examples: health, finances, career development, parenting, home maintenance, direct reports, professional development.

The project/area distinction is the single most important thing to get right in PARA, and it's the thing people most frequently get wrong. A project lives inside an area. "Finances" is the area. "Sort out the ISA before the April deadline" is a project within it. Treat an area as a project and you'll feel like you never finish anything. Treat a project as an area and you'll never feel the urgency to actually complete it.

A useful test: if it has a verb ("launch," "complete," "write"), it's probably a project. If it's a noun representing a domain of your life ("health," "finances," "marketing"), it's probably an area.

Resources

Resources are topics you're interested in or find useful but that aren't tied to a current responsibility or active project. Reference material for potential future use.

Examples: notes on a programming language you're learning for fun, bookmarks about interior design, articles on management theory, a collection of typefaces you like, recipes you want to try someday.

The line between resources and areas comes down to responsibility. Areas are things you're responsible for. Resources are things you're interested in. Your job's marketing strategy is an area. Marketing as a general topic of interest is a resource.

Resources are also the natural home for the output of your reading and research. Articles you've clipped, books you've annotated, papers you've saved, talks you've bookmarked. Material that might feed into future projects but doesn't have a specific job right now.

Archives

Archives are inactive items from any of the other three categories. Completed projects, areas you're no longer responsible for, resources you've lost interest in.

Examples: a completed website launch (formerly a project), a previous job role (formerly an area), a collection of notes on a hobby you've moved on from (formerly a resource).

The archive is not a bin. You're not throwing things away, you're putting them to sleep. Archived material can be reactivated at any time. A completed project might contain templates, research, or lessons learned that become useful months or years later. That area you archived when you left your last job might become relevant if you move back into a similar role.

Forte's rule: never delete, always archive. Storage is cheap and you really cannot predict what will turn out to be useful.

How information flows

One thing worth understanding is that PARA isn't a static filing cabinet. Information moves between categories as your life and work change.

A resource (an interest in machine learning) generates a project (complete an ML course by June). The project finishes and moves to the archive, but the notes and materials stay in resources because the interest continues. An area (career development) spawns multiple projects over time: update CV, attend conference, get certified. Each one finishes and archives. When an area is no longer your responsibility, the whole thing moves to the archive.

This flow is one of PARA's genuine strengths. It acknowledges that information doesn't have a fixed home. The same document might start in a project, move to resources when the project completes, and end up archived years later. The system accommodates this naturally rather than forcing you to make a permanent decision on day one.

Setting it up

Start with what's active

Forte specifically advises against spending a weekend reorganising your entire digital life into PARA, and he's right. Start with what's active right now.

List your current projects. Be specific: "Launch redesigned website by March 15" not "work on website." If you have more than 15, you probably need to archive some or demote them to someday-maybe items in Resources.

List your areas of responsibility, both professional and personal. The domains you maintain: health, finances, a specific work function, a relationship, a side business.

Create folders or sections for these in whatever tool you use, whether that's a notes app, a file system, or a workspace. Add a Resources section and an Archives section, and you're up and running.

Don't pre-create empty folders. Forte tells a story about an engineering firm where employees wasted significant time navigating elaborate pre-built folder structures that were mostly empty. Only create a folder when you have something to put in it.

Organise as you go

Forte calls this "just-in-time organisation." You don't schedule time to tidy your system. You organise each item as you encounter it, as a natural part of working.

When something new arrives, whether it's an email, a document, a note, or a bookmark, you ask one question: what is this most relevant to right now? Active project? Goes there. Ongoing area? Goes there. Interesting but not currently actionable? Resources. Can't think of any use for it? Skip it entirely.

This keeps the system lightweight and prevents the buildup of an unfiled backlog. And because you're making the filing decision in the moment, when you have the most context about what the item means and why you saved it, you're more likely to put it somewhere you'll actually find it again.

The inbox

PARA as Forte describes it doesn't technically include an inbox, but most people need one in practice. A holding area for information that arrives faster than you can sort it, a temporary staging ground before items move into the four categories.

If you find yourself interrupting focused work to file every incoming item, an inbox solves that. Capture everything into the inbox, process it in batches during a natural break or daily review. The key is keeping it temporary. If items sit there for more than a day or two, it's not an inbox anymore, it's a junk drawer.

Common mistakes

Confusing projects and areas

This is by far the most frequent problem people run into. "Get healthier" is an area. "Complete Couch to 5K by September" is a project. If your project list is full of vague, never-ending goals, you've conflated the two. The fix: every project needs a verb, a noun, and a finish line.

Too many projects

If you have 30 active projects, something has gone wrong. Either you're listing tasks instead of projects (sending an email is a task, not a project), or you're carrying zombie projects that should be archived. Look at each one and ask when you last made progress. If the answer is "I can't remember," that's an archive candidate.

Over-organising resources

Resources is the category most prone to hoarding. It's tempting to save everything that looks vaguely interesting, but a resources section with 500 unsorted items isn't useful to anyone. Periodically review and archive anything you haven't looked at in six months. Better yet, use a tool with semantic search so that even a large, loosely organised collection remains findable.

Building the system instead of using it

There is a real and present danger of spending more time configuring your PARA setup than doing actual work. The system should be simple enough to explain in five minutes and set up in an afternoon. If you're three days into Notion template design and still haven't filed a single real document, you've crossed the line from organising to procrastinating.

Strengths

Simplicity. Four categories. Easy to remember, easy to apply. There's no learning curve to speak of, which means the system can be running within an hour.

Tool-agnostic. PARA works in Notion, Obsidian, Google Drive, Apple Notes, a physical filing cabinet, or any digital workspace. The same four-folder structure applies everywhere, which means you maintain one mental model across multiple tools.

Actionability as the axis. This is the core insight, and it's a good one. Organising by what you're doing with information rather than what the information is about keeps the most relevant material closest to hand.

Flow between categories. Information moves between states as your circumstances change: active project to archive, casual interest to real project. The system accommodates this rather than forcing everything into a permanent home.

Limitations

It's still manual. PARA requires you to make a filing decision for every item. Where does this go? Which project? Which area? Individually these decisions are small. Cumulatively they're significant, especially for people who struggle with executive function or who process large volumes of information daily. The "just-in-time" approach helps, but the cognitive overhead of constant micro-decisions is real.

Folder structures create silos. A note filed under one project isn't visible from another, even when the two are related. A note about a client's pricing expectations might be relevant to both the "Q3 proposal" project and the "client relationships" area, but in a folder structure it can only live in one place. Some tools work around this with links and databases, but the fundamental tension between hierarchical organisation and networked knowledge remains.

Retrieval is the weak spot. PARA tells you where to put things. It's less helpful when it comes to finding them again, especially months or years later. If you can't remember which project or area you filed something under, browsing the folder structure is slow and frustrating. This is where search, particularly semantic search that understands meaning rather than matching keywords, becomes essential as a complement.

Ongoing maintenance. Projects complete, areas shift, resources go stale. Without regular review, whether weekly, monthly, or at least yearly, the system decays. Completed projects clutter the active list. Defunct areas linger. The system doesn't maintain itself, and for some people, that maintenance is the first thing to slip.

The area/resource boundary is fuzzy. In theory, areas are responsibilities and resources are interests. In practice, plenty of things are both. Is "cooking" an area (you're responsible for feeding your family) or a resource (you're interested in cuisine)? The answer depends on the person. That's fine for flexibility but can cause real decision paralysis during setup.

Who PARA works best for

PARA tends to suit people who manage multiple projects simultaneously. Knowledge workers, freelancers, students juggling coursework, research, and personal commitments. It's particularly useful if you work across multiple tools and want a consistent organising principle that applies everywhere.

It works less well for people whose information is primarily creative or associative rather than project-based. Writers, researchers, and designers often find that the hierarchical folder structure doesn't map naturally to how they think. For these people, a more networked approach like Zettelkasten or evergreen notes may be a better primary system, with PARA as a complementary layer for the project-management side.

People with ADHD often find PARA's simplicity appealing in theory but struggle with the ongoing filing decisions in practice. If the manual organisation step is the barrier, consider pairing it with a tool that handles auto-tagging and semantic organisation so you get the same structure with fewer decisions to make.

PARA and other systems

PARA isn't a complete productivity system. It's an organisation method. It tells you where to put information but doesn't tell you how to decide what to work on, how to manage your time, or how to capture ideas in the first place. Most people who use PARA successfully combine it with something else:

Getting Things Done provides the capture, clarify, and review habits that PARA doesn't address. PARA's Projects maps to GTD's project list. Areas roughly maps to GTD's "areas of focus" horizon. The two systems complement each other naturally: GTD handles the workflow, PARA handles the filing.

Building a Second Brain is Forte's own broader methodology, of which PARA is one component. BASB adds capture (collecting information), distillation (progressive summarisation), and expression (creating output) on top of PARA's organisational foundation.

Zettelkasten organises by connection rather than actionability. The two can coexist comfortably: PARA for project and area management, Zettelkasten for long-term knowledge development and idea networking.

Pomodoro handles the doing, which PARA doesn't touch. Once you know what your projects are and where your materials live, Pomodoro helps you actually make progress on them.

Time blocking allocates calendar time to specific projects or areas, bridging the gap between PARA's "what do I have" and the practical question of "when will I actually do it."

Getting started

If you want to try PARA, the minimal starting point is this:

Open whatever tool you use most for notes and files. Create four sections: Projects, Areas, Resources, Archives.

Write down your current active projects. Be specific, be honest about what's actually active, and archive anything that's been sitting idle. List your areas of responsibility.

Don't try to file your entire backlog. Start fresh and file things as they come in. If you have years of unfiled documents, consider declaring inbox bankruptcy: archive everything in a recoverable way and begin the system from today.

Set a recurring reminder to do a quick review: are your projects current? Is anything complete that should be archived? Are any resources becoming active enough to become projects? A weekly review is ideal but even monthly is better than never.

That's really all you need to get going: four folders, a list of active projects, and the habit of filing things as they arrive. Everything else you can figure out as you go.

Frequently asked questions

What's the difference between PARA and GTD?

GTD (Getting Things Done) is a complete workflow system that covers how to capture, clarify, organise, reflect on, and engage with your commitments. PARA is specifically an organisation method, it tells you where to put information but doesn't prescribe how to decide what to work on or how to manage your time. Many people use both together: GTD for the workflow, PARA for the filing.

Can I use PARA with Notion / Obsidian / Apple Notes / Google Drive?

Yes, and that's one of PARA's strengths. The four-category structure works in virtually any tool. You create four top-level folders or sections (Projects, Areas, Resources, Archives) and file things into them. Some tools make this easier than others, and tools with strong search reduce the pressure to file things perfectly, but the framework itself is tool-agnostic.

How many projects should I have at once?

Tiago Forte recommends between 10 and 15 active projects. If you have significantly more, you're probably listing tasks as projects (sending an email is a task, not a project) or carrying inactive projects that should be archived. If you have fewer than five, you might be thinking too broadly and could benefit from breaking larger efforts into smaller, more concrete projects.

What if something belongs in two categories?

File it where it's most immediately useful, which is usually the active project. When that project completes and moves to the archive, you can move the document to an area or resources if it has ongoing value. Some tools also let you link or tag items across categories, which avoids duplication.

How often should I review my PARA system?

A light review weekly is ideal for keeping projects and areas current. A deeper review monthly or quarterly helps catch things that have drifted. And a full yearly review is worth doing to realign your system with your actual goals and priorities. The weekly review is the most important of the three.

Is PARA good for people with ADHD?

The simplicity of four categories appeals to a lot of people with ADHD, but the ongoing filing decisions can be a barrier. If the manual organisation step is where things break down, consider pairing PARA with a tool that handles auto-tagging so you get the structure without the decision overhead. See also our post on ADHD-friendly productivity systems.

What goes in the someday/maybe list?

PARA doesn't have an explicit someday/maybe category the way GTD does. Most people put aspirational ideas and vague future plans in Resources, since they're interesting but not currently actionable. If a someday/maybe item becomes concrete enough to have a deadline and a clear outcome, it graduates to Projects.

Should I use tags or folders for PARA?

Folders are the more natural fit because PARA's four categories are mutually exclusive, and an item can only be in one folder at a time, which forces you to decide what it's most relevant to right now. Tags can supplement this (a handful of broad tags like "work," "personal," "urgent" can help with filtering) but try not to build an elaborate tagging taxonomy on top of the folder structure, as that adds maintenance overhead without proportional benefit.

This guide is part of a series on the PARA method. See also: PARA in practice and the weekly review guide. The PARA method was created by Tiago Forte.