GratisAIfamily · field guide · local-first · no account
hold shelf timer

See the Slack Left on Every Library Hold — Free

Holds expire quietly on different branch windows. Subtract the days a hold has waited from its own pickup window and see which family errand is already overdue.

The proof surface

Document renewal boards track expiry dates you own. This tracks shelves you do not: each branch’s pickup window minus the days already elapsed, with a reminder lead you set.

Inputhold | days since ready | branch pickup window days; reminder lead in days
Rare deviceDocument renewal boards track expiry dates you own. This tracks shelves you do not: each branch’s pickup window minus the days already elapsed, with a reminder lead you set.
Output artifactdays of slack per row with transparent workings
Cost$0 · local-first · one free run · samples labelled
Sample, not your facts: Illustrative sample: Novel | 2 | 14; Picture book | 8 | 10. With reminder lead in days set to 3, smallest slack is 2.00 days of slack.

Why the flat version breaks

Assuming one window fits all branches

Each branch sets its own shelf time.

Counting from the request date

The clock starts when the hold is ready.

Letting the summary hide a negative

The worst row is the one to act on first.

How to work the hold shelf timer

Read each branch’s window off the notice

Windows differ by branch and can change; enter the days the library actually gave each hold. The novel has fourteen days and has waited two, leaving twelve.

Count the days honestly

Use the ready date from the notification. The picture book waited eight of ten days — two left, at or inside the three-day reminder lead, so it is flagged for this week’s run.

Treat negative slack as overdue

The biography waited ten days on a seven-day window: minus three. The summary reports the smallest slack across holds, so the worst shelf leads the list. Confirm with the library whether an expired hold can be renewed or must be re-requested.

Set the lead to your real routine

If you shop on Saturdays, a three-day lead means Wednesday’s warning still makes the trip. The tool does not know your calendar; the lead is the knob that fits it.

What the hold shelf timer replaces

QuestionBeforeVisible working
Assuming one window fits all branchesEach branch sets its own shelf time.Count the days honestly
Counting from the request dateThe clock starts when the hold is ready.Treat negative slack as overdue
Letting the summary hide a negativeThe worst row is the one to act on first.Set the lead to your real routine

A local arithmetic aid replaces hand calculation, not expert review. No paid AI service is needed.

Run it on the samples, right here

FIRST-LOAD

Input is processed locally and a draft is saved automatically in this browser profile when storage is available. Reset to sample clears that draft; Pro history has its own clear button. A state link encodes your inputs in its URL: share only non-sensitive rows. Browser history, clipboard and anyone receiving the link may retain it. Optional AI use below leaves this device; it is not required.

Countdown arithmetic on notices you read yourself. Not connected to any library system; renewal rules and hold policies belong to the branch.

Data note: Everything runs in this browser tab on the hold shelf timer: your hold | days since ready | branch pickup window days stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.

Go deeper: the companion app files the same reading as a punched ticket stubs

The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the hold shelf timer reading, and holds your drafts on this device — one free run, then $ 4 one-time for the layer that keeps filing.

The hold shelf timer reading is complete for free. The optional $4 layer adds print, row CSV and the last five local reading summaries; it does not add hidden answers. Checkout is not configured yet; the article demo remains unlimited.

Open the see the slack left on every library hold companion

Boundary

Countdown arithmetic on notices you read yourself. Not connected to any library system; renewal rules and hold policies belong to the branch.

What this is built on

Before: Each branch sets its own shelf time. After: the hold shelf timer shows the working beside each named row so the reader can change the assumption and inspect the consequence.

Optional AI formatting, not calculation

For this hold shelf timer, use the free AI Studio interface only if available to you, with no paid API key. Manual entry completes the same workflow for free. Supply only fictional or non-sensitive notes. Review its output against the source; never paste unresolved questions into the numeric rows.

Format my non-sensitive notes for a hold shelf timer. Return plain rows only: hold | days since ready | branch pickup window days. Preserve supplied quantities exactly. Do not guess missing values; list questions separately. Do not calculate or add advice. I will check every row before pasting into the local tool.

Accepted schema: hold | days since ready | branch pickup window days. No AI response is executed as code.