Split a Book Across Club Meetings by Whole Pages — Free
'We'll just split the pages evenly' lasts until someone does the division and finds two leftover chapters. Whole pages, named remainder convention, one number for the heaviest meeting.
The proof surface
Word-budget tools carve a manuscript into sections. This chart carves a finished book into meetings: integer division with the remainder assigned to the earliest meetings, and a per-book heaviest-meeting load. It does not respect chapter breaks or estimate reading time.
InputBook code | total pages | meetings; per-meeting reading cap (pages)
Rare deviceWord-budget tools carve a manuscript into sections. This chart carves a finished book into meetings: integer division with the remainder assigned to the earliest meetings, and a per-book heaviest-meeting load. It does not respect chapter breaks or estimate reading time.
Output artifactHeaviest meeting load with row-by-row context
Cost$0 local calculation · no card, paid key, subscription or signup · proposed filing price is not for sale
Sample, not your facts: Illustrative inputs: Novel | 320 | 6; Memoir | 180 | 6. Per-meeting reading cap (pages) = 60. Heaviest meeting load: 84 pages in heaviest meeting. All records are invented.
Before using the page-split chart
Enter the edition's actual page count — different printings of the same book disagree, and an ebook location count is not pages. Meetings are the number of reading sittings the club has committed; if a meeting covers two books, give each book its own row and accept that the split is per book, not a global schedule. Remainder pages always go to the earliest meetings by the chart's convention; a group that prefers them last can re-run mentally by swapping the first and last assignments. The cap is your own 'too much for one sitting' mark for flagging, not a reading-speed claim. Chapter boundaries, difficulty and member schedules remain outside the arithmetic.
Why the flat version breaks
Splitting by chapters without counting pages
Chapters vary wildly; six chapters can be a light month or an impossible one. Count pages first, then let chapter breaks fine-tune the boundary by a page or two. The chart gives you the page truth the chapter-only view hides.
Floating the remainder each time you meet
If remainder pages are assigned ad hoc, two members will hold two different schedules by week three. Fix the convention once — earliest meetings absorb the remainder — and print the schedule where everyone can see it.
Using the average as the plan
An average of 53.3 pages is not a schedule; somebody reads 54. The whole point of the heaviest-meeting figure is that it names what the busiest member actually faces, so plan the discussion order and snack budget around that number, not the mean.
How to work the page-split chart
Use the real edition's page count
Read the number from the copy the club will actually share — the printed total, not the last numbered page if there are unnumbered appendices you intend to include or exclude. Decide once whether front matter and afterword count, and use that rule for every row.
Count real meetings, not hopeful ones
Enter only the meetings the club has actually scheduled around this book. If the calendar is still open, run the tool once with the minimum plausible meetings and once with a more relaxed figure; the heaviest-meeting number is what your busiest month will feel like.
Divide, then place the remainder
Whole pages per meeting is total ÷ meetings rounded down; remainder is total mod meetings. Assign the remainder pages one each to the earliest meetings, making them the heaviest. That one convention is what makes the schedule reproducible without a spreadsheet — anyone can rebuild it from the same two numbers.
Check the heaviest meeting against the cap
If the heaviest meeting exceeds your group's reading appetite, add a meeting, shorten the book or split that meeting's share explicitly at a chapter break near the boundary. The chart flags against your supplied cap, but a flagged row can still be the right choice when the group knowingly accepts a heavy week.
What the page-split chart separates
Question
Before
Inspect this instead
Splitting by chapters without counting pages
Chapters vary wildly; six chapters can be a light month or an impossible one. Count pages first, then let chapter breaks fine-tune the boundary by a page or two. The chart gives you the page truth the chapter-only view hides.
Count real meetings, not hopeful ones
Floating the remainder each time you meet
If remainder pages are assigned ad hoc, two members will hold two different schedules by week three. Fix the convention once — earliest meetings absorb the remainder — and print the schedule where everyone can see it.
Divide, then place the remainder
Using the average as the plan
An average of 53.3 pages is not a schedule; somebody reads 54. The whole point of the heaviest-meeting figure is that it names what the busiest member actually faces, so plan the discussion order and snack budget around that number, not the mean.
Check the heaviest meeting against the cap
This page-split chart replaces a manual count or calculation, not source verification or the responsible person’s review.
Run it on the samples, right here
FIRST-LOAD
HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.
Reading-plan arithmetic only, not reading-speed advice or a claim about any edition. Confirm page counts against the physical copy the group shares, and let members adjust for their own reading circumstances.
Data note: The page-split chart processes Book code | total pages | meetings locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.
Go deeper: the companion app files the same reading as a plotted bar chart sheet
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the page-split chart reading, and holds your drafts on this device — one complete free app run; the proposed $4 one-time filing layer is not for sale.
The page-split chart answer stays complete for free. The proposed $4 one-time filing layer adds row CSV, print and five local reading summaries, not hidden answers. Checkout is unavailable; the article demo remains unlimited.
Reading-plan arithmetic only, not reading-speed advice or a claim about any edition. Confirm page counts against the physical copy the group shares, and let members adjust for their own reading circumstances.
What this is built on
Method: Whole pages per meeting is total ÷ meetings rounded down; remainder is total mod meetings. Assign the remainder pages one each to the earliest meetings, making them the heaviest. That one convention is what makes the schedule reproducible without a spreadsheet — anyone can rebuild it from the same two numbers.
All sample records, dates, quantities and labels are invented. No outside policy, contract, rate, clock offset, measurement or accessibility standard is represented as verified.
Google’s official pricing documentation, fetched 2026-10-01, says AI Studio is free in available regions. Optional formatting may require a Google account; manual local entry requires none. Limits can change and free-tier content may be used to improve products. Do not send private records.
Before: the split was an average nobody could schedule. After: whole pages per meeting, remainder placed early, heaviest meeting named.
Three worked readings, with different inputs
Sample A — typical inputs
Novel | 320 | 6
Memoir | 180 | 6
Setting: Per-meeting reading cap (pages) = 60. Expected summary: 84 pages in heaviest meeting.
The 320-page novel divides into six meetings of 53 pages with 2 left over; the two remainder pages go one apiece to the first meetings, making the heaviest meeting 54 pages. The 180-page memoir divides exactly into six meetings of 30, heaviest 30. The chart sums the heaviest-meeting load per book: 54 + 30 = 84. Remainder pages land early by convention, so every member can hold the same schedule.
Sample B — changed plan
Guide | 100 | 3
Setting: Per-meeting reading cap (pages) = 60. Expected summary: 34 pages in heaviest meeting.
One hundred pages over three meetings gives 33 each with 1 remainder, so the first meeting carries 34 and the chart reports 34. If your group prefers to bank remainder pages at the end instead, that is a different convention — the chart names its own rather than hiding the choice.
Sample C — boundary convention
Pamphlet | 12 | 12
Setting: Per-meeting reading cap (pages) = 60. Expected summary: 1 pages in heaviest meeting.
Twelve pages across twelve meetings leaves one page per meeting and no remainder. The boundary shows the most spread-out legal split, where every meeting is equally light. It also quietly confirms the chart's convention when the remainder is zero: nothing to distribute changes nothing.
Optional AI formatting, never the calculation
Manual entry completes this page-split chart for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.
Format only these fictional or non-sensitive notes for a page-split chart. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are Book code | total pages | meetings; the setting is Per-meeting reading cap (pages). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.
An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.