The PARA system in practice

The gap between theory and practice

The PARA method is easy to understand. Four categories, organised by actionability, file things as they come in. Most people grasp the framework in ten minutes.

The hard part is what happens on Tuesday morning when you're staring at a PDF attachment and you really don't know whether it belongs in a project, an area, or resources. Or when your project list has quietly grown to 25 items and you can't tell which ones are real and which are wishful thinking. Or when you realise you haven't looked at your resources section in three months and have no idea what's in there.

This guide is about all of that. The day-to-day reality of running PARA, the decisions it forces you to make, and how to handle the situations where the framework's clean categories meet the mess of actual life.

What a populated PARA system looks like

Theory is easier to follow when you can see it. Here's what a working PARA system might look like for someone who works in marketing and has a few personal projects on the side:

Projects (active, with deadlines)

• Q3 brand campaign (launch September 1)

• Redesign company newsletter template (done by end of month)

• Plan Mum's 60th birthday party (August 12)

• Complete Google Analytics certification (before next review cycle)

• Flat move (lease starts October 1)

Areas (ongoing, no end date)

• Content strategy (work)

• Team management (work)

• Health and fitness

• Finances

• Flat maintenance

• Relationship

Resources (interesting, not currently active)

• Typography and type design

• Behavioural psychology

• Email marketing best practices

• Travel ideas

• Cooking

Archives

• Q2 brand campaign (completed)

• Previous flat (moved out)

• Photography course (completed last year)

• Old job role materials

A few things to notice. The project list is short, just five items, each with a clear finish line. The areas are broad life and work domains rather than specific tasks. Resources are interests, not responsibilities. And the archive contains things that were once active but have run their course.

The whole thing fits on a single screen, which is part of the point. If your PARA system needs scrolling to see the top-level view, it's probably too granular.

The daily workflow

PARA doesn't prescribe a specific daily routine, which is both a strength (flexibility) and a weakness (no guardrails). But most people who stick with the system tend to settle into something like this:

Morning. Open your workspace and look at your project list. Pick the one or two projects that need attention today. If you're not sure, look at which ones have the nearest deadlines or which ones you've been neglecting. Open the relevant project folder and see where you left off. If you left yourself a note about the next step, even better.

Throughout the day. As things come in, whether that's emails, documents, articles, ideas, or meeting notes, file them into the right category. The question is always the same: what is this most relevant to right now? If it connects to an active project, it goes there. If it relates to an ongoing area, it goes there. If it's interesting but not currently actionable, resources. If you're not sure, drop it in your inbox and sort it later.

End of day (optional but useful). Spend five minutes clearing your inbox if anything accumulated. Glance at your project list and note where you left off on whatever you were working on. This takes almost no time but makes the next morning much smoother, because you don't have to reconstruct your mental state from scratch.

The key to all of this is that filing decisions should take seconds, not minutes. If you're spending a long time deliberating about where something belongs, that's a sign the categories need adjusting or you're overthinking it. When in doubt, just pick the most plausible option and move on. You can always move it later.

Processing: the moment of decision

The processing step is where PARA lives or dies. A piece of information arrives and you have to decide what to do with it.

Forte suggests running through the categories from the top down, since Projects are the most actionable:

1. Does this relate to an active project? If so, file it there.

2. Does this relate to an ongoing area of responsibility? File it there.

3. Is this something I'm interested in or might find useful later? Resources.

4. None of the above? Either skip it entirely or archive it.

In practice, most items are obvious. An email about the Q3 campaign goes in the Q3 campaign project. A bank statement goes in the finances area. An article about typography you found interesting goes in resources.

The tricky cases are the ones that could plausibly belong in two places. A client research report might be relevant to both the "Q3 campaign" project and the "content strategy" area. Forte's advice is to file it where it's most immediately useful, which is usually the active project. When the project completes and moves to the archive, you can decide whether to copy or move the document to the area for longer-term reference.

Some people handle this by linking rather than filing. If your tool supports it, you can put the document in the project and create a link to it from the area. This avoids the duplication problem, though it does add a small amount of maintenance overhead.

Edge cases and how to handle them

"Is this a project or an area?"

The most common source of confusion in the whole system. The test is simple: does it have an end? If you can picture yourself being done with it, it's a project. If it's something you'll maintain indefinitely, it's an area.

Some grey areas:

"Learning Spanish" could be either. If you're taking a specific course with a completion date, that's a project. If you're just gradually picking it up with no particular goal, it's more like a resource (an interest you're pursuing).

"Health" is an area. "Train for the marathon" is a project within it. "Go to the gym regularly" is arguably neither, it's a recurring habit that belongs in your task management system rather than your information system.

"Write a book" is a project (it has an end, even if the deadline is vague). "Writing" as a practice or craft is an area.

"This doesn't fit anywhere"

Sometimes you encounter information that doesn't connect to any current project, area, or interest. A random article someone sent you, a screenshot you took absent-mindedly, a PDF you downloaded for unclear reasons.

You have two options: put it in resources as a general reference item, or skip it entirely. Not everything needs to be kept. One of the quiet skills of running any organisational system is learning to let things go rather than hoarding everything just in case.

"My project list is too long"

If you have more than 15 active projects, some of them aren't really active. Go through the list and be honest with yourself. When did you last make progress on each one? If something has been sitting untouched for more than a few weeks, it's not an active project, it's an aspiration. Move it to resources as a "someday/maybe" item, or archive it. You can always reactivate it later.

The emotional difficulty here is that archiving a project can feel like admitting failure, but it's really just acknowledging that you have finite time and attention, and that keeping zombie projects on your active list doesn't make them more likely to get done. If anything it makes everything else harder, because the list becomes so long that you can't see what actually matters.

"I keep forgetting to check the system"

This is less a PARA problem and more a habit problem. The system only works if you use it regularly. Some things that help: keep your workspace open throughout the day rather than tucked away in a tab you never look at, set a daily recurring task to check your project list, or pair it with an existing habit (check PARA right after your morning coffee, for example).

Borretti's concept of visual field management is relevant here: if the system isn't in your visual field, it effectively doesn't exist. Out of sight, out of mind. Keep it visible.

The review

PARA without a review is a system that slowly rots. Projects complete without being archived, areas shift without being updated, resources accumulate without being pruned. The categories stop reflecting reality, and once that happens, you stop trusting the system, and once you stop trusting it, you stop using it.

Forte recommends pairing PARA with a regular review, and most people find that weekly works well, though fortnightly or monthly is better than nothing.

A PARA review doesn't need to be elaborate. You're answering a few questions:

Projects. Are all of these still active? Has anything been completed that should be archived? Are there any new projects that need to be created? For each active project, is the next step clear?

Areas. Am I neglecting any area? Has anything changed in my responsibilities that should be reflected here? Are there areas that are no longer relevant?

Resources. Is anything here actively interesting enough to become a project? Is anything stale enough to archive?

Archives. You generally don't need to review archives. They're there if you need them, and search can surface things when they become relevant again.

The whole thing should take 15 to 30 minutes. If it's taking longer than that, your system is probably more complex than it needs to be.

For a deeper look at annual reviews and how to use them to realign your PARA categories with your actual priorities, see the yearly review guide.

Keeping it sustainable

The biggest threat to any organisational system is the maintenance burden quietly exceeding what you can sustain. PARA is simpler than most, which helps, but it still requires ongoing attention. A few things that help keep the overhead manageable:

Don't over-nest. A project folder with three subfolders is fine. A project folder with twelve subfolders, each containing more subfolders, is a filing system within a filing system and defeats the purpose. Keep things flat where you can.

Don't over-tag. If your tool supports tags, use them sparingly. A handful of broad tags (work, personal, urgent, reference) can be useful. Fifty granular tags create a taxonomy that's harder to maintain than the folder structure it's supposed to complement.

Let search do the heavy lifting for retrieval. The more you can rely on search to find things rather than browsing through folders, the less pressure there is to file things perfectly. If your tool has semantic search that understands what you're looking for rather than just matching filenames, you can afford to be much looser with your filing and still find what you need.

Archive aggressively. When a project is done, move the whole thing to archives immediately. Don't leave completed projects cluttering up your active list because you might need something from them later. You can always pull things back out of the archive, and in practice you rarely need to.

Accept imperfection. Some things will end up in the wrong category. Some items will sit in your inbox for a few days before getting sorted. Some projects will linger too long before being archived. All of this is fine. The system works at 80% adherence. Chasing 100% is where the maintenance burden starts to outweigh the benefits.

When to revisit the structure

Your PARA categories should evolve as your life changes. A job change means new areas and new projects. A shift in interests means resources gets reshuffled. Major life events (moving, having a child, starting a business) can reshape the whole system.

When this happens, don't try to incrementally patch the existing structure. Set aside an hour, review everything from the top, and reorganise. Archive what's no longer relevant, create new areas and projects that reflect your current reality, and start fresh where needed. This is essentially a deeper version of the regular review, and doing it deliberately at moments of transition prevents the system from drifting out of alignment with your actual life.

Frequently asked questions

How long does it take to set up PARA?

An hour or less if you start with what's active rather than trying to reorganise your entire digital life. List your current projects, list your areas of responsibility, create the four sections in your tool of choice, and start filing things as they come in. Don't pre-create empty folders and don't try to process your backlog on day one.

What do I do with my existing files and notes?

Don't try to sort them all into PARA retroactively. Either leave them where they are and start fresh with the new structure, or archive everything into a single "pre-PARA" folder and move on. This is what Fernando Borretti calls inbox bankruptcy, and it works because the alternative (spending a weekend filing years of accumulated documents) will put you off the system before you've started.

I keep forgetting to use the system. What should I do?

This is almost always a visibility problem. If your PARA workspace isn't open and visible during your working day, it might as well not exist. Keep it open in a tab or window you actually see, set a daily recurring reminder to check your project list, and try pairing it with an existing habit like your morning coffee.

How do I handle email in PARA?

Email is a capture point, not a category. When an email contains something relevant to a project or area, extract the useful information and file it into the right PARA category. The email itself can then be archived. If you treat your email inbox as part of your PARA system it gets messy fast, because email mixes actionable items with noise. Better to pull things out of email and into your workspace where they belong.

What's the difference between a project and a task?

A task is a single action: send the email, buy the groceries, call the dentist. A project is an outcome that requires multiple tasks: launch the website, plan the holiday, write the report. PARA operates at the project level. Individual tasks belong in your task management system, which might be separate from your PARA setup or integrated into it depending on your tools.

My resources section is overwhelming. How do I manage it?

Resources tends to grow faster than any other category because saving interesting things is easy and letting them go is hard. Two things help: do a periodic purge (quarterly or during your yearly review) where you archive anything you haven't looked at in six months, and rely on search rather than browsing so a large resources section doesn't need to be perfectly organised to remain useful.

Can I use PARA for both work and personal life?

Yes, and most people do. Your projects, areas, and resources will naturally include both. Some people keep them in separate sections for clarity, while others prefer a single unified system. Either works as long as you can see everything in one view when you need to.

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.