GratisAI learning · split a book across club meetings by whole pages · local-first FREE TIER 1 Free Run Available
page-split chart · plotted bar chart sheet

Split a Book Across Club Meetings by Whole Pages

'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.

1 · Book code | total pages | meetings

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.

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.

Perspective: Before: the split was an average nobody could schedule. After: whole pages per meeting, remainder placed early, heaviest meeting named.

2 · Read the page-split chart

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.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

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.

Boundary and sources

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.

Mechanism: competence-autonomy-loop

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.