Study

Book Summary Template for Book Notes

A book summary is worth writing when it answers three questions a year later: what was the argument or story, what did I make of it, and what did I change because of it. Copy the template, or start from the example closest to the book on your nightstand.

Updated 2026-10-27

Copy and adapt

The template

Book summaryTemplate

[Book title] by [Author]

Read: [date started] to {{date}}, [print / ebook / audio] Why I picked it up: [the question or problem you brought to it] Related: [[Author name]], [[Topic]] #book

The book in one sentence

[The whole argument or story, in your words.]

The book in three sentences

[Setup or problem]
[Main argument or turn]
[Conclusion or resolution]

Key ideas (nonfiction) or story and characters (fiction)

[Idea or plot point] (p. [X])
[Idea or plot point] (p. [X])
[Idea or plot point] (p. [X])

Passages worth finding again

p. [X]: [what the passage says, paraphrased, and why it stuck]

Where I disagree or doubt it

[Claim] because [your reason or counter-example]

What I will do differently

[One concrete change, with a date to check it] @due(YYYY-MM-DD)

Verdict

Rating: [x/5]. Who should read it: [person or situation]. Skip it if: [situation].

Questions for later

[Question the book raised but did not answer]

5 examples

Examples for different situations

The same structure, filled in for the situations people actually bring to it. Copy the one closest to yours.

1.Business book read by a new manager

When it fits: Use this when you are reading a management or business book because of a job you just started, and the notes only matter if they change what you do on Monday.

Business book read by a new managerExample 1

High Output Management by Andrew S. Grove

Read: 2026-10-05 to 2026-10-19, paperback Why I picked it up: Promoted to lead a team of six on Oct 1. I have never run a 1:1 or written a review. Related: [[Andrew Grove]], [[Management]], [[Team Atlas]] #book #management

The book in one sentence

A manager's output is the output of the people and teams they influence, so the job is choosing the activities with the most leverage, not doing more work yourself.

The book in three sentences

Grove treats management like running a factory: find the limiting step, measure it early, and fix problems where they are cheapest to fix.
A manager's tools are information gathering, decisions, nudges and meetings, and each one should be judged by how much it multiplies other people's work.
How much you direct someone should depend on how experienced they are at that specific task, not on how senior they are overall.

Key ideas

Leverage: one hour spent on a decision that six people depend on is worth more than one hour of my own tickets (opening chapters).
Indicators should come in pairs so that pushing one does not quietly damage another, e.g. speed paired with error rate (the breakfast factory section).
1:1s belong to the report; the manager listens and asks follow-up questions (meetings section).
Task-relevant maturity: tell a new person how, coach a middling one, set goals for an expert (motivation section).

Passages worth finding again

Training chapter, near the end: the argument that teaching your own reports is one of the highest-leverage things a manager can do, and should not be handed off.

Where I disagree or doubt it

Written in the 1980s for a chip maker. The production analogy works for our release pipeline, less for design work where the output is not countable.

What I will do differently

Start weekly 1:1s with all six, agenda owned by them @due(2026-10-27)
Pick one paired indicator for the team: lead time plus escaped bugs @due(2026-11-07)

Verdict

Rating: 5/5. Who should read it: anyone in their first year of managing. Skip it if: you want a book about culture rather than mechanics.

Questions for later

How does task-relevant maturity work for someone who is senior overall but new to our codebase?

2.Novel for a book club meeting

When it fits: Use this when you are reading fiction for a group, you will be asked what you thought in two weeks, and you want discussion questions ready instead of a vague feeling.

Novel for a book club meetingExample 2

Middlemarch by George Eliot

Read: 2026-09-01 to 2026-10-24, ebook (it is long, about 800 pages) Why I picked it up: Thursday book club pick, meeting 2026-11-05 at Celeste's. Related: [[George Eliot]], [[Thursday book club]] #book #fiction #bookclub

The book in one sentence

In a provincial English town around 1830, several people with large ambitions marry the wrong person or make the wrong bargain, and the book follows what that costs them.

Story and characters

Dorothea Brooke, idealistic and young, marries the much older scholar Casaubon, expecting a life of shared purpose. His great work turns out to be going nowhere.
Lydgate, a reforming young doctor, marries Rosamond Vincy and is pulled into debt by her expectations and his own pride.
Bulstrode, the pious banker, has a past that a returning acquaintance threatens to expose, and Lydgate is caught in the fallout.
Fred Vincy and Mary Garth are the smaller, steadier love story the others are measured against.
Casaubon's will tries to control Dorothea after his death; she chooses Will Ladislaw anyway and gives up the money.

Passages worth finding again

Finale, last paragraph: the idea that ordinary unremembered lives do much of the good in the world. Read it aloud at the meeting.

Where I disagree or doubt it

The narrator explains characters' motives at length. Hannah will love this; I found it slowed the middle third.

Questions for the club

Is Dorothea's ending a defeat or a choice? The narrator seems unsure.
Who is more responsible for Lydgate's failure, Lydgate or Rosamond?
Does Bulstrode deserve any sympathy by the end?

Verdict

Rating: 4/5. Who should read it: people who like long novels about marriage and money. Skip it if: you need plot to move fast.

3.History book read for a talk

When it fits: Use this when you are reading history to explain it to other people later, so the notes need dates, causes and the author's interpretation kept apart from the facts.

History book read for a talkExample 3

The Guns of August by Barbara W. Tuchman

Read: 2026-10-10 to 2026-10-26, library hardcover, due back 2026-11-07 Why I picked it up: Giving a 40-minute talk at the community library on Nov 11 about how the First World War began. Related: [[Barbara Tuchman]], [[World War I]], [[Library talk Nov 11]] #book #history

The book in one sentence

The first month of the First World War was shaped by plans drawn up years earlier, and by leaders who followed those plans after the conditions behind them had changed.

The book in three sentences

Germany's plan depended on going through Belgium and beating France in about six weeks before Russia could mobilize.
Belgian resistance, French losses at the frontiers, and the British arriving earlier than expected slowed the German right wing.
By the Battle of the Marne in September, a fast war was no longer possible, and the trenches followed.

Key ideas

Plans became commitments: once mobilization started, no general would accept a change of course (early chapters).
France's doctrine of attack cost huge casualties in August.
Russia's early invasion of East Prussia ended in defeat at Tannenberg but pulled German troops east at a key moment.

Facts vs Tuchman's interpretation

Fact: Germany invaded Belgium in early August 1914. Interpretation: the plan's authors underrated the political cost. Check against a second source before the talk.

What I will do differently

Build the talk around three decisions, not a timeline @due(2026-11-01)
Return the book after copying page refs @due(2026-11-07)

Verdict

Rating: 5/5. Who should read it: anyone who wants the war's opening told as a story. Skip it if: you need recent scholarship; it was published in 1962.

4.Self-help book read with a skeptical eye

When it fits: Use this when a popular book makes confident promises, you want to keep what is useful and test it, and you need a date to check whether it actually worked.

Self-help book read with a skeptical eyeExample 4

Atomic Habits by James Clear

Read: 2026-10-12 to 2026-10-20, audiobook plus the ebook for page refs Why I picked it up: Third attempt this year at a morning writing habit. The first two lasted nine and fourteen days. Related: [[James Clear]], [[Habits]], [[Morning writing]] #book #habits

The book in one sentence

Small habits compound, and you build them by changing your environment and your sense of identity rather than relying on motivation.

Key ideas

Aim to be a certain kind of person, not to hit a single goal; each repetition is a vote for that identity.
Four levers: make the cue obvious, make the habit attractive, make it easy, make it satisfying. Reverse each to break a bad habit.
Habit stacking: attach the new habit to an existing one.
Two-minute rule: shrink the habit until starting is trivial, then grow it.

Where I disagree or doubt it

Many claims rest on anecdotes and stories of athletes. The identity idea is persuasive but I cannot tell how well it is tested.
The 1 percent better every day arithmetic is a metaphor, not a measurement.

What I will do differently

Stack: after the coffee machine starts, open the draft note and write one sentence @due(2026-10-21)
Leave the laptop open on the kitchen table at night
Check the streak and decide keep, change or drop @due(2026-11-20)

Verdict

Rating: 3/5. Who should read it: someone who keeps restarting the same habit. Skip it if: you want research reviews rather than practical advice.

Questions for later

Did the two-minute version ever grow past two minutes? Answer on Nov 20.

5.Technical book read chapter by chapter

When it fits: Use this when a dense technical book takes months, you read it in sessions, and each chapter needs to connect to the systems you actually work on.

Technical book read chapter by chapterExample 5

Designing Data-Intensive Applications by Martin Kleppmann

Read: 2026-08-03 to 2026-10-25, print, one chapter per weekend Why I picked it up: Our team is splitting the orders database in Q1 and I could not explain the tradeoffs in the design review. Related: [[Martin Kleppmann]], [[Distributed systems]], [[Orders DB split]] #book #engineering

The book in one sentence

Most data systems are built from the same handful of ideas (storage, replication, partitioning, transactions, consensus), and each comes with tradeoffs you have to choose on purpose.

Key ideas by chapter

Ch. 3 Storage: log-structured stores favor fast writes, B-trees favor predictable reads. Our write-heavy events table is the first case.
Ch. 5 Replication: replication lag means a user can read their own write and not see it. This is the bug support reported in September.
Ch. 6 Partitioning: hashing a key spreads load but makes range queries expensive. Partitioning orders by customer keeps one customer's orders together.
Ch. 7 Transactions: isolation levels differ across databases even when they share a name. Check what ours actually guarantees.
Ch. 9 Consensus: avoid needing it unless something must be agreed by every node.

Where I disagree or doubt it

Published in 2017. Some product examples are dated; the principles are not.

What I will do differently

Write a one-page note on read-your-own-writes for the design review @due(2026-11-06)
Check our database docs for the real isolation level @due(2026-10-30)

Verdict

Rating: 5/5. Who should read it: backend engineers before their first big data migration. Skip it if: you want copy-paste configuration.

What belongs in a book summary

Most book notes fail the same way: they are written once, on the day you finish, and they record what the book said without recording what you thought. A year later the note reads like the back cover. A book summary template earns its place by forcing three answers that survive time.

The book in one sentence. The test of whether you understood it. If the sentence comes out as a list, keep reading or reread the conclusion.
The book in three sentences. Setup, turn, conclusion. For fiction: situation, conflict, how it resolves.
Key ideas or story, with page numbers. Four to six bullets in your own words. Page numbers make the note a map back to the book.
Doubts and disagreements. This is the section people skip, and the one that makes the note worth rereading. A book you agreed with completely was either very good or read too fast.
What you will do differently, with a date. One concrete change and a day to check it.
Verdict and who it is for. So you can recommend it, or warn someone off, without rereading.

Book summary, book report or book review

Search for a book summary template and most results are school book report worksheets: title, author, main character, favorite part. That format exists to show a teacher you read the book. The template on this page is for adults keeping notes for themselves. It drops the plot-in-order structure and adds the two sections a worksheet never asks for: where you disagree, and what you will change. If you are writing a review for other readers, keep the Verdict section and expand it; if you need a report for a class, follow the format your teacher gives you.

How to fill it in without slowing your reading

While reading, mark, do not write. A pencil tick, a highlight, a page number in your phone. Two or three words per mark at most.
Within a day of finishing, write the one-sentence version first. Then go back through your marks and keep only the ones that support it or contradict it.
Write the doubts section before the takeaways. Disagreeing first keeps the takeaways honest.
Close with one dated action. For fiction, three questions instead.

For long technical books, keep one summary note and add a short note per chapter session, linked to it. The fifth example shows the shape.

Making book notes findable a year later

None of the top-ranking templates answer this, and it is the reason most reading notes go unused. A summary you cannot find is a summary you did not write. Three habits fix it:

Link the author and one or two topics. After a dozen books, the topic note shows every book that touched it, and patterns between authors appear without effort.
Tag by kind. #book plus #fiction, #history or #engineering is enough. More tags than that stop being used.
Revisit on a date. The dated task in What I will do differently is the review. When it comes due, open the note, record what happened, and the book summary becomes evidence instead of a memory.

Common mistakes

Summarizing chapter by chapter. It produces a table of contents, not an understanding. Summarize the argument, then cite chapters as evidence.
Copying long quotations. Paraphrase and keep the page number.
No reaction. A summary with no disagreement and no action is the publisher's blurb with extra steps.
One giant reading file. One note per book, linked by author and topic, scales. A single document of every book you read does not.

When to use a different template

If you only want to track what you read, how many pages and when, the reading log template is lighter. For academic sources you will cite, the research notes template keeps quotations and citations exact, and the literature review template is where those notes become a written synthesis. For the longer habit of collecting ideas across many books, see how to remember what you read.

Customization tips

Write the one-sentence summary first
Before any other section, write the whole book in one sentence. If you cannot, you are not ready to summarize it yet, and the key ideas list will turn into a table of contents.
Swap one section for fiction
For a novel, replace Key ideas with Story and characters and replace What I will do differently with Questions for discussion. The rest of the template stays the same, as the Middlemarch example shows.
Paraphrase, then add a page number
Copying long passages feels productive and teaches you little. Restate the passage in your words and note the page so you can find the original wording if you ever need to quote it.
Give every change a date
A takeaway without a date to check it is a nice thought. One dated task ("check the streak on Nov 20") turns a book summary into an experiment you can evaluate.
Link the author and the topic
Put the author and one or two topics in links on the Related line. After ten books, the topic note lists every book that touched it, and you can see where authors agree.
Book club version
For a group, add the meeting date and host to the Why line and three open questions at the end. Questions that start with "who is more responsible" or "is the ending a defeat" get better discussion than "did you like it".

In the app

How to do this in Scribelet

Open Desk Settings, then Templates, tap Add Template, paste the template above and set #book as a default tag. Put {{title}} or the book name in the title and every summary starts the same way.
Write the author and topics as [[Andrew Grove]] and [[Management]]. The author's note then shows every book of theirs you summarized in its backlinks panel, and a topic note collects every book that touched it.
Turn takeaways into tasks: - [ ] Check the streak @due(2026-11-20). They show up in the Tasks view and on that day's daily note, so the book gets a follow-up instead of a shelf.
Photograph a page or a margin note and attach it. Scribelet extracts the text so it is searchable alongside your summary.
Months later, ask the AI chat "what did I note about habits across the books I read this year?" It answers from your own book notes with citations to each note.

Templates, template variables and AI generation are documented in Note templates.

Frequently asked questions

How do you write a book summary?

Write the book in one sentence, then in three, then list the four to six ideas or plot points that carry it, each with a page number. Add one section for your own reaction: where you disagree and what you will do differently. The reaction is the part that makes the summary yours rather than a shorter copy of the book.

How long should a book summary be?

For personal notes, one screen: a one-sentence take, a three-sentence summary and five to eight bullets. Long summaries get written once and never reread. For a dense technical book, keep one summary note and add short notes per chapter linked to it.

What is the difference between a book summary, a book report and a book review?

A book summary is for you: what the book says and what you will do with it. A book report is a school assignment that usually asks for plot, characters and themes in a fixed order. A book review is written for other readers and ends in a recommendation. Many of the printable book summary templates online are book report worksheets for children; this one is for adult reading notes.

Should I take notes while reading or after?

Both, briefly. While reading, mark pages and jot a few words per idea. Within a day of finishing, write the summary from those marks. Waiting a week loses the reasoning behind the ideas, and summarizing every chapter as you go slows reading enough that many people stop.

Can I use this as a book club notes template?

Yes. Replace What I will do differently with three questions for the group, add the meeting date and host, and bring the Passages worth finding again list so you can point people to pages. The Middlemarch example above is set up this way.

Remember the books you finished, not just their titles

Save this book summary template in Scribelet, link each book to its author and topics, and turn takeaways into dated tasks. Next year, ask your notes what you learned instead of rereading the book. Encrypted, free to start.

Start your first book summary

or get the app

Download on theApp Store

Free plan, no credit card. See pricing

Study

Reading Log Template

A reading log is a running list: what you read, when, how far you got, and one line on what you thought. Copy the template below for a year of books, or pick the example that matches you: an adult goal, a child's nightly minutes, a book club, or one long book on a deadline.

Research

Literature Review Template

A literature review is an argument about what is known, built from sources, not a list of summaries. This template takes you from scope and search, through a source matrix, to one section per theme with agreement, disagreement and gaps. Pick the example organized the way your sources group.

Research

Research Notes Template

Research notes go wrong in two ways: you cannot tell where a claim came from, or you cannot tell whether it is still true. This template ties every finding to a source and a confidence level, keeps observation apart from interpretation, and records when you last checked.

Article

Literature notes

From the Scribelet blog

Article

How to remember what you read

From the Scribelet blog

Article

Commonplace book

From the Scribelet blog