Interactive Tool

Next Book Workflow Generator

Setup day is the easy part. Getting the next book โ€” on your own, after the helper has left โ€” is where things actually go wrong. This tool builds you a plain-language step-by-step routine for your exact setup, plus a rescue plan when the usual path fails.

Answer 3 quick questions. You'll get your primary route, exact steps, and a printable leave-behind sheet.

Tell us about your setup

Pick whichever best describes your main way
This changes which steps need to be ultra-simple
What triggered you to use this tool?
Your next-book workflow

Answer the questions on the left, then click Build my workflow to see your personalised steps.

Why getting the next book is harder than setup

Families and caregivers can usually muscle through a one-time device setup. The real failure happens the following Tuesday, when the reader's current book ends and nobody can remember what they clicked to borrow it. Or when a hold notification arrives with a 72-hour action window and no one is around to action it.

This tool is built around the four most common breakdown points in Canada:

๐Ÿ”„ Kobo/Libby sync mismatch

A book borrowed in Libby may not appear on Kobo if the library's edition differs from the Kobo catalogue entry. The fix is specific โ€” most generic help articles miss it.

๐Ÿƒ Multi-card complexity

Holding cards from two libraries sounds like a longer waitlist shortcut. In practice it creates login confusion, mismatched accounts, and failure at the worst moment.

โฐ The 72-hour hold window

When Libby notifies you a hold is ready, you have 72 hours to borrow or suspend. Many seniors and caregivers miss this, losing their spot and restarting a multi-week wait.

๐Ÿ“ž Low-tech routes dismissed too late

Phone-first borrowing, home delivery, CELA/NNELS audio, and DAISY formats are often treated as a last resort. For many seniors they should be the first suggestion.

The tool above accounts for all four scenarios and recommends the simplest reliable path for your setup โ€” not the path that works best for a power user.