What Counts as a Reading Session? (And How to Track It)

Does Five Minutes Even Count?

It's 11:40pm, you're already in bed, and you open the book anyway. You get one page in – maybe two – and your eyes start closing. The book slips a little in your hand. You put it down and go to sleep. And somewhere in the back of your head there's this small, slightly nagging voice: that wasn't really reading. One page doesn't count. It only counts if it's a proper chunk – a whole chapter, thirty pages, an hour on the sofa with a coffee. Anything less feels like it doesn't make the cut.

I lived inside that voice for years, and here's what I eventually figured out: it's wrong, and it's expensive. There's no reading police. A "session" is whatever you decide to count – and the looser you make that definition, the more you'll actually read. That's the whole trick of this article. So here is why the session is the right thing to track in the first place, and three ways to track it.

What Actually Counts as a Reading Session

Here's my definition, and it's generous on purpose: a reading session is any intentional, continuous-ish stretch of reading you decide to log, at any length. That's it. The only real test is "was I actually reading?" (not "was it long enough?"). Five minutes counts. One page before sleep counts. Consistency beats duration every time, and a definition that lets you check the box on a bad night is worth more than a strict one that talks you out of reading at all.

Skimming and re-reading both count if you were genuinely engaged – if the book had your attention, it was a session. The one thing I honestly wouldn't count is the book being open while you scroll your phone with the other hand. That's just being honest with yourself. But that's really the only line I'd draw. Everything above it counts.

And audiobooks? They count if you want them to – it's your log, not mine. I read almost entirely ebook-only these days, but I used to mix in audio on walks and at the gym, and I never once felt the need to gatekeep it as "not real reading." I wrote some more about this whole debate in audiobooks vs reading. My take: count what you want to count.

Why Sessions Beat "Time Spent Reading”

Once you accept that a session can be tiny, the next question is why bother framing it as a "session" at all – why not just vaguely aim to "read more"? Because a session is countable, and vague good intentions are not. A session has a date, a length, and a page count. That means it can stack into a streak and show up on a dashboard, where "I read sometimes" can't be counted, can't be streaked, and can't be improved. The unit is what makes progress visible. You can read more about streaks here: why reading streaks work.

Sessions also reveal patterns that vague time never will. When I started logging every single one, two things surfaced that I sort of knew but had never seen in data. First, my actual rhythm: almost all my reading happens in two windows – a few pages in bed at night and a few more before I get up in the morning. Seeing that made the habit obvious to protect. Second, my real reading speed – and I mean the honest one, averaged across every session I've ever logged, not the flattering snapshot I got when I took a speed test out of curiosity. That deeper "why bother tracking" argument is its own article: how to track your reading progress.

A session is exactly where your speed lives – pages per minute over one real sitting. A one-off test tells you your pace under good conditions; tracking every session tells you your pace on tired Tuesdays and travel days too, which is the number that actually predicts when you'll finish a book. Start with one measured session, though – it's the fastest way to see your real number.

How to Track a Reading Session (3 Ways)

You don't need a fancy system. The lowest-friction method you'll actually keep up is good enough. Here are three, from least to most hands-off.

1. The notes-app line. One line per session: date, minutes, pages. Zero setup, works on any phone, and it's genuinely fine. The catch is that you have to remember to do it, and you won't, some days. I know this one intimately – my early "tracking" was a scatter of Apple Notes and reminders that got cluttered and untrustworthy fast, right alongside the ever-growing to-read lists I've confessed to in earlier posts on this blog.
2. The paper log. A notebook or a printable reading tracker. It's satisfying and screen-free, which some people really love. Same forgetting problem as the notes app, plus the math (streaks, totals, averages) is entirely on you.
3. An app that times it for you. Start a timer when you start reading, log the page when you stop. This is where ReadingHabit fits – and honestly where I started, because before I built anything I was leaning on Apple Books' built-in streak and session-length features as a side effect of just reading there. An app captures the session, the pages, and rolls it into your streak and stats automatically, so the five-minute read never goes uncounted the way it does when tracking depends on your memory.

Tiny Experiments

by Anne-Laure Le Cunff

Read it in January and it rewired how I approach anything new: instead of deciding to become something, you run a tiny experiment – start small, honestly, and see. Which is basically what a single reading session is. A great one to start tonight.

Est. read: 5h 4m

Get your reading estimate →

Why I Built ReadingHabit Around the Session

Most trackers are built around the book – books finished, books this year, the big satisfying number. I built ReadingHabit around the session instead, and the reason comes straight out of the habit-formation thesis I keep coming back to (BJ Fogg's "make it embarrassingly small" is the north star). Habits are built from reps, not big milestones. A finished book is a milestone – you might achieve it a few times a month. A session is a rep – you get to do one every day. And daily is where habits actually live, so daily is what I wanted the app to measure.

I didn't arrive at that in the abstract, either. I noticed it using Apple Books: it already had a little streak and a per-session timer, and those two tiny features did more for my consistency than any "books read this year" tally ever had. That was the seed. Build everything around the rep, and the good stuff follows – streaks that actually mean something, stats that move tonight instead of next month, and a month-end recap that's really just your sessions added up. The finished books stop being the goal and become the byproduct, which is exactly the right way round.

Tiny Habits

by BJ Fogg

The actual science behind making a habit so small you can't talk yourself out of it – then letting it grow on its own. I read it while writing my thesis on habit formation.

Est. read: 5h 6m

Get your reading estimate →

Small Sessions, Real Books

So, back to that one page before sleep. It counts. It's not a lesser session, and it's definitely not cheating – it's the session that keeps the whole thing alive on the day everything else falls apart. I've got two versions of that day. One is being so wiped at night that a single page is genuinely all I've got, so I read the one page – the tiniest unit possible – and keep the momentum. The other is travel, which reliably wrecks my routine: the iPad mini isn't on its usual nightstand, the cue that normally triggers me to read just isn't there, and I still find a few pocket pages somewhere in the day. In both cases, keeping it minimal is precisely what got me over the bad day. That's not a loophole in the system. That is the system.

So decide what counts for you, and decide generously. Then go count tonight's session, however small – one page, five minutes, ten pages. The books add up from there, quietly.