OF3 and folders

Curious on how others are using folders now that multiple tags (contexts) can be attached to projects and items. I’ve removed all of my folders and am using an additional tag and perspectives exclusively. So far so good.

OF3, for me, is close to perfect. I haven’t had any significant problems with the MacOS beta. I’m really impressed with how well it works across all the platforms.

Well done.

I love OF3! I love multiple tags and the new customized perspective rules! And I really look forward to automation! My folders are unchanged - folders for work/personal/other and under work I have sub-folders for each client, then projects for each client’s matter/project. I’ve actually simplified my tags, removing the hierarchy in many cases, although this may change as I make better use of the more powerful custom perspectives more: I have applescripts and workflows to automatically build new projects for each client when they are assigned, with dates milestones, etc., so client folders and projects make a lot of sense to me.

Interesting. Sounds like you have a good use for folders. I just don’t need/want that much structure. I’d rather do it all with perspectives. That does require more tags, but I’m having fun seeing if I can make it work after years of having only folders and a single context for each project and item to work with. Thanks for the reply.

Keep in mind that you can also use folders in custom perspectives.

I use folders to divide different areas of life so I can, for example, focus only on work activities or only personal activities. Actions are stored in sequential/parallel projects if they contribute to a defined outcome (e.g. “Plan Trip to Vancouver”) and are contained within single action lists if they’re one off items related to a specific area of life (e.g. “[Car Maintenance]”).

Side note: I enclose the name of single actions lists in square brackets to make them visually distinct. This can also be helpful when creating certain perspectives.

Adding tags to actions and projects further defines their characteristics. For example, adding a tag of “phone” indicates that an action represents a phone call. And a tag of “today” could represent something I’d like to get done today, even if it’s not technically due. Tags can represent GTD-style contexts, but aren’t limited to being used for contexts.

The combination of folders and tags makes it possible to automatically generate specific lists.

For example, you could have OmniFocus show you all of the personal phone calls that you’d like to get done today by creating a custom perspective that shows all available tasks contained within the “Personal” folder that are tagged with both “phone” and “today” (I’d probably include due items as well, for good measure).

I’ve put together some examples of tags here: http://learnomnifocus.com/tags/ And I’m planning to add more in the coming weeks as I continue to experiment with the many wonderful ways that tags can add convenience and efficiency.

You’ll also find some examples of how tags can be used in perspectives here: https://learnomnifocus.com/perspectives/. I’ll be adding more examples soon.


Thanks Tim. I appreciate your reply. What you’re describing is the way I used folders prior to 3.x. I might end up going back to that structure, but I’ll continue to replace those folders with a tag and then use perspectives for a bit longer. I’ll check out your link too. You really do exceptional work thoroughly examining every nook and cranny in OmniFocus!


The only scenario in which I use more than one tag at this point is if I mark something as “Priority,” which is my Forecast tag. I actually go back and remove it at the end of the day so that recurring tasks don’t inherently have it assigned.

I’m too reliant on folders from a view perspective to ditch them. I have a folder for work (day job) and personal, another for my consulting business (part time), one for personal goals-related tasks, and another for reminders and lists of things like travel destination, shows to watch, someday/maybe things, etc.