Daily logs on the Agenda: routines and tools

I want to begin with a distinction between actionable items in the structured context of a project vs the more or less “atomic” day-to-day “to do” items.

I’ve found that Agenda is out-of-the-box excellent for the first kind of planning, but I had doubts it would work as a good substitute for a paper Bullet Journal I’ve been keeping for the last six months, where I was successfully handling my “to do’s”. On the other hand, I wasn’t delighted with the Bullet Journal for more complex project planning (the device of creating “collections” for this purpose didn’t do the job for me). Additionally, we’re able to do a lot of efficient tricks when we keep daily tasks on a computer, such as linking tasks to emails and files and many kinds of automation. With that in mind, I decided to try to implement in the Agenda what I thought was the best of bullet journalling: the artifact of a Daily Log and its related routines, in particular the ability to quickly register contextualized thoughts and tasks, the process of daily and monthly reviewing the items, including the feature of task migration from a month to the next, and the possibility, through mindful reviewing, of deciding whether or NOT to do specific tasks.

The setup

I number my categories of projects so that I can keep them in an order which is meaningful to me (as the app alphabetically sorts them). The first category is numbered zero, and is dedicated to general planning (let’s say “0. Planning”). Inside this category, I keep a project called “Journal”.

This project is a collection of notes appearing in the following order:

  1. Inbox (pinned to top)
  2. Month Plan (“July 2019”, assigned to 1-31 July)
  3. Week Plan (“Week 28”, assigned to 8-13 July)
  4. Today’s log ("12 Jul | Fri”, assigned to Today)
  5. Yesterday’s log and before…

I expect to discuss weekly planning in another post (it involves time boxing, with the help of BusyCal, and is related to the other kind of planning – for complex projects – which we won’t discuss here).

The Inbox is a sort of generic input buffer resting in a place which I’m confident it will stay visible every day. For the time being, its real use has been for information and tasks captured with Drafts on my iOS devices. It should, of course, be emptied as quickly as possible.

The Month Plan note’s anatomy is divided into Goals for the month (also basically related to the big projects) and Pending Tasks (migrated from last month).

What required some thinking – and the invention of tools – were the Daily Logs. I liked, first, having my paper notebook opened in a page with today’s log, where I would briefly register thoughts (for later elaboration), tasks and information. The process of reviewing and checking tasks in the context of a daily journal proved to be more efficient, and more meaningful than the usual to do lists in task managers.

Drawing from this experience, the first thing to notice is that it is difficult to compete with paper in terms of its resolution. We can put a lot of information in a two-page spread using a regular notebook. That means we have even more reason to be economical when doing digital note-taking if we want to avoid excessive scrolling (and anxiety). We should also keep that in mind for the design of note titles (and I didn’t find Agenda’s default date format particularly fortunate in this respect). I tried to find a formula for compact, homogeneous and meaningful displaying of each day’s date (“12 Jul | Fri”).

Creating Today’s log

The point is then to mimic the nice routine developed with the company of a paper notebook. I start the day (after reviewing the Week Plan) with the creation of a note for Today’s log. I do it with the help of a Keyboard Maestro Macro which will create the appropriate note, with the customized date formula (for those who might prefer it, there’s an equivalent keyword in the Alfred Workflow, a-today):

So, I start with the creation of Today’s daily log by pressing CTRL+CMD+N T. I take the opportunity to write down some reflections, or jot down some tasks I have on my mind.

This note will be evident in both the “Today” and “On the Agenda” views, which I will use through the day. But I found it convenient to create a shortcut to invoke it directly, with a global macro triggered by CTRL+CMD+F7:

I also have another global trigger to activate/deactivate the Agenda, assigned to CMD+F7. Inside the Agenda, I can also invoke the “Journal” project by pressing CMD+3. (All the Agenda macros are included in the KM file attached to this post.)

Adding entries to Today’s log

When dealing with the Daily Log, we’re working with a list of entries of different kinds: informational notes, tasks, or contextual headings usually associated with events.

By using the Alfred workflow with the a keyword, I can quickly create those entries (an informational “-“ item by default, a task with the CMD modifier, or a heading with the SHIFT modifier).

The experimental al keyword will add an entry with a link previously stored in the clipboard (it doesn’t work with URLs containing parameters).

Migrating tasks

Finally, I thought it would be essential to keep the review process at the end of the month and to have a practical way to “migrate” pending tasks to the following month’s log. This I think is the best feature of the Bullet Journal method: doing a periodical “clean up” of your task list, instead of accumulating them indefinitely.

Due to some limitations on Agenda’s x-callback-url mechanism, we can’t simply move entries elsewhere without changing the focus to the destination note (thus completely perverting the idea of concentrating in the review of the ending month’s items). I came with a solution inspired on emac’s kill/yank commands, which is to keep items to migrate in a sort of buffer, during the review, and then to “yank” them to the destination note, i. e, to the “Pending Tasks” section in next month’s Plan.

With the cursor over a task to migrate, I press CTRL+CMD+K M to have that entry added to the buffer. The macro also marks the item as checked, and prepend a bracket (❯) to indicate it is then to be found somewhere else “in the future”.

After the review, I’ll go to the next Month’s Plan and “yank” the migrated items (CTRL+CMD+K Y) inside that note.

The same process may be used to move things around to a particular project in the Agenda.

As a bonus, there’s also a macro for merely “killing” (CTRL+CMD+K K) entries for later “yanking”, and another one (CTRL+CMD+K T) for moving entries to Today’s log (this is particularly useful for cleaning the Inbox).

Last but not least…

Last but not least, I could not forget one of the best of the Bullet Journal’s routines, which is to register, with a strikethrough, the decision NOT to do a particular task, and enjoy the liberating effects of such a decision. This I think is the missing shortcut in the Agenda: Mark as Cancelled (CTRL+CMD+X). :slightly_smiling_face:

I hope some of you may enjoy these ideas and tools. Please note that you’ll have to review the Keyboard Maestro macros to see if it suits you (verify the project name and date format). The Alfred workflow should work out of the box, but you’d better set up its variables (using the workflow configuration panel).

I look forward to comments and feedback after your experimentations.

Agenda Daily Alfred Workflow

KM Agenda macros for Daily Logs


It’s always interesting to hear how other people plan their work and use such tools.

I’ve never understood the rationale for a monthly review - it seems to postpone planning until too late. I tend to do a weekly ‘look ahead’ for the next few weeks instead, even if it’s just glancing at my calendar for upcoming events if I know that I’m on top of my projects.

I tried bullet journaling but was driven mad by endlessly rewriting tasks! The flexibility of Reminders or cut and paste in Agenda resulted in me moving to a computer solution. I do however use pencil and paper for planning my day - essentially blocking out time for tasks and project. I find doing this on paper is somehow makes it feel more like a commitment than just marking a task as Today in software.


Great post! I’ve moved it to the Talk section of the community as I think it has a wider reach and more people can benefit from a lot of the ideas, even if you don’t use the shortcuts. Would be great if indeed you could describe your Week Plan workflow as well, thanks for sharing!

I too have something of a similar (manual) routine with my daily journal, that I’m now trying to incorporate into Agenda.

I make a list of “to-do” things for the day, it’s a running list.

Each day’s list is then pushed into an archive category.

I have greater detail as separate notes. I use the “Copy Agenda Link” to relate relevant ‘dot points’ in each day’s list to their respective details. See detail samples below.

However, as soon as I move some detail (note) into another category/project, that “Agenda Link” changes, which means I lose track of everything.

Is it possible to retain a note’s “Agenda Link” as a unique, persistent - and immutable - entity, no matter where it goes after it’s created? If that’s not possible, then it’s back to a manual journal for me, despite the attractiveness of Agenda. I’ve got the full version, as I assumed it would be something as polished as Papers… I have enjoyed using Papers for years.

Thank you, with fingers crossed



Do you have an Alfred workflow that works in V3?



@andy_s I didn’t realize that v. 4 workflows weren’t backwards compatible. I’m adding an Alfred 3 version to the repository.

Did you experiment with Ryder Carroll’s bullet journal method? Except for things moved to special projects, I only migrate to-do items – the pending ones – once per month, constantly reviewing daily logs since the beginning of the month. It works great on paper and also in the Agenda, as the circle bullets are visible enough. I do keep a list of weekly goals for the big projects, though.

Hi Bruno,
I must acknowledge and admit complete ignorance of the bullet journal method, until you mentioned it in your thread.

Much like @trebso, it would have sent me bonkers reviewing, rewriting and ‘migrating’ things (whatever those ‘things’ may be).

At first glance, Agenda seemed ideally suited to me going electronic with my journalling habits. All that was needed was the “Agenda Link” for a note to be immutable once it was created. That would allow a note to be tracked, no matter where it went , with its “Agenda Link” being a unique Object-ID.

I’ve attached the start of a day’s journal entry below. The dot-points are always on the left hand side of a page, with details starting on the right, continuing for however many pages are required. This way, dot-points can grow as a day progresses (I’d seriously worry if dot-points needed more than one page).

If/when a dot-point is complete for a particular day, I circle the asterisk in red. The remainder (even partially completed - they get marked slightly differently) roll over to next day’s dot-points, unless I’ve decided not to pursue an activity (or it’s too late, whatever).

This mechanism has served me well for decades, except for finding when something started and tracking its history. A unique “Agenda Link” would have permitted me to do all of that electronically. I would have had a note’s complete history tracked from inception to completion. No reviews, etc. Migration would be the equivalent of moving a note into a different category/folder in Agenda. I’ve kind of described what I was trying to do in my initial post/reply to this thread.

I understand implementation minutiae could explain why a note’s link changes when it moves. I’ve met this sort of thing before - many times. For example, I’ve had deep discussions over many years with developers of a very mature network monitoring and management system. I was looking to also use it as an on-line inventory management system of anything within our purview that was visible on a large, multi campus network. The biggest problem? As soon as a device had to move from one location to another, it lost its uniqueness. In essence, a device couldn’t ‘move’, it could only be ‘copied’.

So yes, implementation details may explain why a note’s ID changes when it moves from hither to tither. It doesn’t reflect life events or activities, not the way I see them anyway.

I repeat my plea to the Agenda developers … Please consider a unique and immutable identity for each note.


Thank you,


1 Like

Fantastic. Really appreciate the prompt response Bruno!

I agree with you, a Unique Identifier should be preserved for the note, no matter what. That’s the way DEVONthink and other software do, and it’s very useful (also for integration with other apps using links).

See this topic: