I am hoping someone can help me with my quandary here. Currently, I use a single .txt file to hold and organize my list of projects, next actions, waiting for, and someday/maybe items. For example: @PROJECTS - item 1 - item 2 - etc. @AGENDAS #PERSON x - item 1 - item 2 - etc. #PERSON y - item 1 - item 2 - etc. @ANYWHERE - item 1 - item 2 - etc. The good: By using one master list, I don't have to go back and forth between lists. An item should only be on my calendar or on that master list. The bad: With such a large list, it's easy to become overwhelmed by and numb to the list. For capture, I either use 3x5 index cards or Google Keep, depending on what I have available. I'm a psychotherapist, and I can't readily use my phone or other electronic devices to capture thoughts in the middle of a session with someone. Most people don't mind if I make a note on paper, thankfully. I have an @AGENDA for every client. It's not unlike me to have 50+ agendas at a given time. I've considered going lo-tech and using a binder and divider tabs to separate my lists. Part of me thinks it would be nice to have a separate page dedicated to a particular person under the @AGENDAS divider and tab. However, carrying around a large binder doesn't seem all that practical. A .txt in Dropbox seems like it would be much more ubiquitous. (I use .txt because it's easily accessible on any electronic device, ubiquitous, easy to back up, and not dependent on software.) I've also considered making separate .txt files (like separate pages in a binder), but that seems somewhat unwieldy, unlike sheets of paper, especially given the large number of @AGENDAS I manage. ----- I don't want my questions to get lost in the weeds above, so here they are: Do you use ONE master list that's separated by @contexts or multiple context lists? Why do you keep the lists the way you do? For those of you that have an extensive list of @AGENDAS, how do you manage those? Has David ever addressed this? If so, where can I find that information? Thank you!