Budget Weekly Laundry Time Before the Loads Pile Up — Free
A full basket is not the constraint; machine hours are. Multiply the loads each type runs in a week by its real cycle minutes and the ledger marks the row where your laundry window runs out.
The proof surface
Chore rotation boards share out who does which household job. This budgets the machine time itself — loads times cycle length against the hours you can really give laundry — so the overflow shows up before the weekend does.
Why the flat version breaks
Counting baskets rather than machine loads
Two half-baskets can be one load, while an overfilled drum needs a second cycle — count starts, not baskets.
Timing from the label rather than the programme
Real cycle times stretch with the chosen temperature, spin and load size, so read the display for the cycle you actually run.
Forgetting the drying and folding time
This ledger counts machine minutes only. Give hanging, drying and folding their own allowance so the window you enter stays honest.
How to work the laundry time ledger
Enter one row per programme you use: family wash, bedding and towels, sports kit, delicates. Splitting by type keeps the slow cycles visible instead of averaging them away.
Five mixed baskets that become four full loads are four loads. Count the starts you would really run in a normal week, including the second wash after a muddy game.
Use the duration on the machine for the cycle you press, at the spin and temperature you use — not the quickest eco figure on the energy label. A hot towel cycle with a long spin commonly runs around sixty minutes.
Enter the weekly machine hours you have, then read the ledger. In the sample the household runs 485 machine minutes against a seven-hour window; the sports kit row is where the week runs out of time, so that load needs a shorter cycle, a combined wash, or a later slot.
What the laundry time ledger replaces
| Question | Before | Visible working |
|---|---|---|
| Counting baskets rather than machine loads | Two half-baskets can be one load, while an overfilled drum needs a second cycle — count starts, not baskets. | Count machine starts, not baskets |
| Timing from the label rather than the programme | Real cycle times stretch with the chosen temperature, spin and load size, so read the display for the cycle you actually run. | Read cycle minutes from the programme you select |
| Forgetting the drying and folding time | This ledger counts machine minutes only. Give hanging, drying and folding their own allowance so the window you enter stays honest. | Set the window you can actually give laundry |
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.
Cycle-time arithmetic on loads and programme durations you enter. Not appliance, energy or fabric-care advice; check your machine manual for safe loads and cycles, and treat persistent overloading or damp loads as a maintenance question for a qualified technician.
Data note: Everything runs in this browser tab on the laundry time ledger: your load type | loads per week | cycle minutes 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 meter band gauge
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the laundry time ledger reading, and holds your drafts on this device — one free run, then $ 4 one-time for the layer that keeps filing.
The laundry time ledger 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 budget weekly laundry time before the loads pile up companionBoundary
Cycle-time arithmetic on loads and programme durations you enter. Not appliance, energy or fabric-care advice; check your machine manual for safe loads and cycles, and treat persistent overloading or damp loads as a maintenance question for a qualified technician.
What this is built on
- Method: Use the duration on the machine for the cycle you press, at the spin and temperature you use — not the quickest eco figure on the energy label. A hot towel cycle with a long spin commonly runs around sixty minutes.
- All sample records are invented examples. The app does not fetch measurements, policies, files or personal records.
- Google’s official pricing page, fetched 2026-09-29, lists free-tier access including AI Studio. Optional formatting only; limits and availability can change. Free-tier content may be used to improve products. Never paste private records there.
Before: Two half-baskets can be one load, while an overfilled drum needs a second cycle — count starts, not baskets. After: the laundry time ledger 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 laundry time ledger, 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 laundry time ledger. Return plain rows only: load type | loads per week | cycle minutes. 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: load type | loads per week | cycle minutes. No AI response is executed as code.