The PARA method, and the simpler version I actually use

Filed under Guide

By Gerald · 7 August 2026

An open drawer of a card catalog filing cabinet packed with labelled index cards

PARA works. I want to say that up front because most of what follows is a list of problems with it, and none of those problems change the fact that Tiago Forte solved a real one: most people file notes by topic, and topic-based filing collapses the moment two topics overlap.

Here is the short version. Use PARA if you already run projects with clear deadlines and you will actually do the weekly review. Use a lighter two-container version, which I will describe below, if you keep abandoning folder systems after a few weeks. Both beat sorting notes by subject.

PARA's real insight isn't the four folders. It's organizing by whether something is active, not by what it's about.

What PARA is meant to solve

Tiago Forte's PARA method groups everything into four containers: Projects, Areas, Resources, and Archives. Forte's own definitions, from fortelabs.com, are specific. A project is a "short-term effort you take on with a certain goal in mind" and it has a deadline. An area is "an ongoing responsibility you want to manage over time" with no end date: health, finances, a role at work. Resources are reference material and interests you keep for later. Archives hold anything from the first three categories that has gone inactive.

The organizing principle is actionability, not topic. That is the actual idea worth keeping. A note about a client goes wherever the client project lives, not into a general "clients" folder, because you need it when you are working the project, not when you are thinking about clients in the abstract.

I used full PARA for about a year and a half. It was the first system that made sense of the mess a decade of subject folders had produced. Then it started to fail in a specific, predictable way.

Where the four folders break down

Woven storage baskets on a shelf with handwritten labels reading everyday and other categories — A two-container system works the same way these baskets do: a few clear buckets, not one bucket per topic.

Every new note asks you a question: is this a project or an area? Most of the time the answer is obvious. Sometimes it genuinely is not, and that ambiguity is where the system leaks.

A recurring client relationship is not a project, because it never finishes, but it does not feel like an area either, because it is not really "ongoing responsibility" in the same sense as your health or your finances. Forte has addressed this kind of edge case in his own writing, which tells you it comes up often enough to need addressing.

The bigger issue is not the edge cases. It is the tax on every single note. Four categories means four live folders to check before filing anything, and a filing decision you have to make correctly or the note becomes unfindable later. That is a small cost per note and a large cost across a few thousand notes.

Archiving is the part that quietly dies first. PARA depends on a habit: when a project ends, you move it to Archives, and when an area goes dormant, same thing. I did this for maybe four months before real work crowded it out. After that, Projects and Areas both filled up with dead weight, and the whole point of the system, keeping active material separate from inactive material, stopped being true.

The two-container version I use instead

What I run now has two live containers instead of four: Active and Reference. Active is anything I am doing something with right now, whether that is a project with a deadline or an ongoing responsibility. Reference is everything else: material I want to keep but am not actively working.

That is the entire folder structure. Two buckets, one filing decision (am I doing something with this right now, yes or no), and tags carry the distinctions PARA used four folders to express.

The filing decision collapses from "which of four categories" to "active or not," which is a question almost every note answers instantly. A meeting note for a live project: active. An article I saved to read someday: reference. A completed project: I do not even move it. I just remove the tag that marked it active, and it falls out of my working view without a physical move.

This is close to what Forte himself has floated as a lighter starting point in later PARA material, sometimes called a two-bucket approach, though I built mine independently and it may not match his version exactly. The instinct is the same either way: fewer containers means the system survives contact with a busy month.

Tags do the work folders cannot

Folders answer one question well: where does this note live. Tags answer a different question: what is this note about, and that question usually has more than one right answer.

A note can be tagged client-acme and invoicing and q3 at the same time. It cannot be filed in three folders at once. PARA's Areas and Resources categories were partly trying to do topic-based organization inside a system that is fundamentally about activity status, and that is where the two ideas fight each other.

Once tags carry the topic, the folder only has to carry the activity status, and two folders is enough. In Flow this looks like a task or note living in one place with several tags on it, and the Tags page pulling everything with a given tag together regardless of which project it sits under. I use it daily and it replaced what used to be a Resources folder entirely.

When you should use full PARA

Full PARA is the better choice in specific conditions, and I want to be straight about when those apply, because the simplified version is not automatically correct for everyone.

If you run several genuinely distinct areas of responsibility, work, a business, a household, a creative practice, and you need to see each one's active state separately, the extra folder gives you that separation for free. If you already do a weekly review as a habit unrelated to your note system, the maintenance cost that kills PARA for most people is not a cost for you.

Full PARA also earns its keep in team settings, where a shared vocabulary for "this is a project, not an area" prevents arguments about where something belongs. Two containers work well for one person's judgment call. They work less well when five people need to agree on the same call.

Migrating an existing mess into either version

Do not try to re-sort everything on day one. Migrate on contact instead.

Start by creating the containers you are moving to, whether that is the full four or the simplified two, and leave your old structure exactly where it is. Every time you open a note for an actual reason, decide its new home then, tag it, and move on. Within a month or two the notes you actually use will have migrated themselves, and what is left behind is, almost by definition, the material you were never going to need again. That leftover pile is your answer to whether Archives (or Reference) needs anything at all: usually it just needs to exist, not be curated.

Do not batch-migrate a large notebook in one sitting unless you enjoy that kind of task. It burns a weekend and produces a filing scheme you have not tested against real use yet.

Who this is for

Full PARA: people managing several distinct areas of responsibility who already do a regular review
Two-container plus tags: people who keep abandoning folder systems and need something that survives a busy month
Anyone moving off subject-based folders for the first time, either version is a real improvement

Frequently asked questions

What do the letters in PARA stand for? Projects, Areas, Resources, Archives. Tiago Forte defines projects as short-term efforts with a deadline, areas as ongoing responsibilities with no end date, resources as reference material for your interests, and archives as anything from the first three categories that has gone inactive.

What is the difference between a project and an area in PARA? A project has a defined endpoint and a specific goal, like shipping a redesign or renovating a room. An area has no endpoint and needs ongoing maintenance, like your health, your finances, or a role you hold at work. If you can finish it, it is a project. If it just continues, it is an area.

Does PARA work with tags instead of folders? Yes, and it works better for a lot of people. Tags can carry the topic and cross-reference (client, subject, quarter) while a small number of folders carry only activity status. This removes the multi-category filing decision that causes most PARA systems to lapse.

How often should I archive in PARA? Forte's original method assumes a weekly or monthly review where you move finished projects and dormant areas to Archives. If you will not realistically do that review, a two-container system with tags avoids the need for a formal archiving step entirely, since removing an "active" tag does the same job without a folder move.

Is PARA better than Zettelkasten? They solve different problems. PARA organizes material by whether you are actively using it. Zettelkasten is about building linked, atomic notes for original thinking over years. Most people benefit from a PARA-style container system for storage and a trimmed version of Zettelkasten's linking habits for the notes where real thinking happens.

My verdict

Keep PARA's real idea, organize by activity, not topic, and drop the part that assumes you will maintain four folders forever. Two containers plus tags gets you the same result with a filing decision that takes a second, not a debate.