The Bullet Journal Future Log: Three Layouts That Work

2026-09-28 · Yesterself

Sometime in February you find out you need a dentist appointment in May. There is no May page, and there will not be one until the last day of April, because that is how the method works: a month gets set up when you reach it. So the appointment has nowhere to go. It ends up on a sticky note, in a phone calendar you do not otherwise open, or nowhere at all.

The future log is the answer to that, and it has exactly one job: catching things dated beyond the current month and holding them until their month arrives.

What it is for

The classic version, from Ryder Carroll's method, is a spread near the front of the notebook divided into six equal blocks, one per month. Six, because a notebook often lasts something like that long, and because a longer horizon fills with guesses.

Nothing in it is a plan. It is a holding area. An entry sits there doing nothing until the month it belongs to arrives, at which point you copy it into that month's log and cross it off here. That single transfer is the whole mechanism, and everything below is about not breaking it.

What belongs in it

One question decides: does this have a date, and is that date after this month? Both halves have to be true.

Things that belong:

• Appointments and travel that are already fixed.
• Deadlines with a real date attached.
• Renewals and expirations — a passport, insurance, a registration, a subscription that will quietly renew in August.
• Birthdays and anniversaries you notice three days late every year.
• Things you have deliberately deferred: look at that job description again in October.
• A short note aimed at a later version of you, as long as it carries a date. If I still dread this project in November, say so out loud.

Things that do not:

• Anything happening this month. That is the monthly log's work.
• Undated tasks. Learn Portuguese has no date, so it has no month. It belongs in a collection.
• Goals and intentions. A future log full of those becomes a page you stop opening, because opening it makes you feel behind.
• Habit trackers, yearly reviews, anything that is really a project page wearing a calendar costume.

The boundary with the monthly log is worth stating plainly, because getting it wrong is the usual reason the spread quietly dies. The monthly log is the shape of the next four weeks and the short list of what must happen inside them. The future log is everything dated after that.

Three layouts

Choose by what you actually write, not by what photographs well.

Vertical thirds

Each page ruled into three tall columns, a month at the head of each, six months across the spread. Some people rule the same six blocks horizontally instead, giving short wide lines rather than long narrow ones. Same idea either way.

Good for general use, where most entries are one line with a day number in front. Weak when the year is uneven: every month gets identical room, whether it is a wedding-and-two-trips month or a month with one entry in it.

The twelve-month grid

Months across the top, days 1 to 31 down the side, one small cell per day. A whole year on one spread. Each cell holds three or four words at most.

Good when you need dates seen against each other — school terms, a rota, other people's travel, a run of birthdays. It answers what is happening the week of March 14th in one glance, which the six-box layout cannot do. Weak on anything needing detail, so most people run a grid plus a page of longer notes and accept the split.

The Calendex

A hybrid the community calls the Calendex. Same grid of months and days, but the cell holds a page number instead of an event. The event itself stays where you first wrote it — a line in a daily log on page 62 — and the March 14th cell simply says 62. The grid stops being a calendar and becomes an index by date.

Good if you take a lot of notes and hate transcribing: nothing gets copied twice, and each entry keeps the context it was written in. Weak in two ways. You cannot read the year at a glance, because reading means flipping. And it depends entirely on numbered pages and on your writing the number down in the moment; skip that once and the entry is gone from the system, though it is still in the notebook.

Where to put it, and how much room

Front of the book, immediately after the index. Index it anyway.

Give it more room than seems necessary — two spreads rather than one. A half-empty page costs nothing. A December block that ran out of lines in September costs you the entries you stopped bothering to write.

If you keep a six-month horizon, draw the next six before you reach the end of it. The month with no page yet is the month things fall out of.

How it feeds migration

A paper future log notifies nobody. It works only if something opens it on a schedule, and that something is migration, the month-end pass where open tasks are rewritten by hand or dropped.

Run the month-end in this order:

1. Open the future log first, before writing anything in the new month.
2. Read the incoming month's block, all of it, including entries you think you remember.
3. Copy each one into the new monthly log, onto its day where it has one.
4. Strike it out in the future log as you go — struck through, not ticked, so a later glance says it moved rather than happened.
5. Only then migrate last month's unfinished tasks.

The order is the point. Fixed dates first means seeing how full the month already is before promising it anything else. The other way around, you build a hopeful list and then find four appointments under it.

Traffic also runs backward. In the standard notation a task migrated to next month gets a right-pointing arrow, and one scheduled into the future log gets a left-pointing one. That second arrow is easy to abuse. Giving a long-carried task a real date and sending it forward is legitimate once. The second time, it is avoidance with better handwriting.

The seam between notebooks

Most lost entries go missing at a notebook change, not during a month. When a book fills, draw the new future log first and copy across every entry that has not happened yet. Then strike them in the old book, so a finished notebook does not look like it still holds live dates.

One honest limit: the future log has no alarm. Something genuinely time-critical — a flight, an interview — is safer in a thing that interrupts you. Let the notebook hold the year's shape and a device hold the few items where being late is expensive.

A note on where we sit in this. We make Yesterself, a journaling app, and it is not a bullet journal app — no bullets, no task states, and no plan to add them. Where it touches this page is the dated-forward idea: any sentence can be postmarked to a future date and arrives on that day, which is a future log entry that opens itself. It is end-to-end encrypted, with no account and no email address, and export is free forever. It is not released yet, so there is nothing to download — only a waiting list.

When it stops working

Three failure modes, all recoverable.

• It fills with wishes. Reread it and strike anything without a date. What survives is the future log; what you struck belongs in a collection.
• Nobody opens it. Make it the first written line of your month-end routine, above the migration step.
• Equal boxes, unequal months. Redraw with uneven blocks, or let a busy month spill into the margin.

A working future log is a dull page. Twelve short lines, half struck through, nothing to photograph. It is a mailbox for dates, and all it has to do is be there in April when you look for May.

Common questions

How many months should a bullet journal future log cover?

Six is the usual default, because a notebook often fills in about that time. Twelve works if you use a grid layout, but the later months get thin and you end up rewriting them anyway.

What is the difference between the future log and the monthly log?

The monthly log holds this month: its days and the short list of things that have to happen in it. The future log holds anything with a date after this month, and nothing else.

Where should the future log go in the notebook?

At the front, right after the index, and indexed like any other spread. Give it two spreads rather than one so a busy month is not squeezed into the same box as a quiet one.

Do I have to copy future log entries into the monthly log by hand?

Yes, and strike them out in the future log as you go. The transfer is the only moment the entry gets read, and the strike is what stops the same appointment living in two places.

What happens to the future log when a notebook ends?

Draw the new one first, before anything else, and copy across every entry that has not happened yet. The gap between two notebooks is where dated things disappear.