Three tanks with different routines, perhaps a tropical community, a shrimp tank, and a coldwater setup, fail in record books for one predictable reason: entries drift into a single chronological stream, and within a month nobody can tell which water change, test result, or new arrival belonged to which tank. The tidy solution is structural, not effortful. One book, three completely separate sections, each running the same layout, so you only ever learn one system while the tanks' data never touches.
Give Every Tank the Same Header Page
Open each section with a header that captures everything stable about that tank: its name or colour code, size, filter and lighting, full stock list with arrival dates, feeding schedule and amounts, water-change rhythm, and the test ranges that are normal for this tank, not for aquariums in general. A planted tropical tank and a hard-water setup have different normal readings, and writing each tank's own baseline at the front of its section is what turns a later odd result into an obvious signal instead of a guessing game.
Update the header only when something structural changes: new filter, changed stock, different food, or a revised change schedule. Cross the old entry out with a single line and date the new one rather than erasing, because six months later the question is often when the change happened, not just what the current setup is.
Dated Entries, One Line Each
Below the header, log events in the same short format every time: date, what was done or measured, and anything unusual in a few words. Test results, water changes and how much was changed, livestock added or lost, plants pruned, anything your vet has advised on, and behaviour or appearance changes all qualify. One line per event is deliberate; a book that demands essays gets abandoned, while a book of single lines survives busy years and still answers the questions that matter, such as when a decline began relative to a new arrival.
Use the tank's colour code or name on every entry, even inside its own section. Pages get photocopied, photographed for a sitter, or carried to a shop, and a loose page without the tank's name on it is useless. If you keep the book digitally, keep the same discipline: one document or tab per tank inside a single folder, identical headings, no merged master log.
The Shared Front Page for Cross-Tank Events
Some events genuinely affect all three tanks: a new batch of food opened, a change in your tap water reported by the supplier, a heatwave week, or equipment shared between tanks. Log those once on a shared front page, dated, so you do not write them three times or, worse, in only one section where the connection is later missed. Illness deserves a specific note here too: if a fish in one tank becomes unwell, record what equipment, nets, or plants moved between tanks and when, because that movement history is the first thing you will need when deciding whether the other tanks are at risk.
Review each section briefly at a fixed moment, such as during the last water change of the month. Skim for slow drifts the daily lines hide: a test value creeping across several entries, changes becoming less frequent, or one tank quietly demanding far more interventions than the others. That review is also when sitter instructions get updated, since a sitter should receive the relevant tank's header plus the last few entries, not a verbal summary from memory.
Kept this way, the book stays genuinely portable, and KinsLe's Pet Passport keeps each tank's header details and recent records together in one packet, so a sitter, a covering friend, or a covering helper can read one tank's complete story without three routines bleeding into each other.