Count Workdays in a Repeating On-Off Roster
A repeating roster rarely lines up with a calendar month. Count full cycles plus the unfinished final cycle rather than multiplying a weekly average by four.
1 · roster option | consecutive workdays | consecutive off days
FIRST-LOAD
Research prototype — checkout unavailable. 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.
Data note: Everything runs in this browser tab on the roster-cycle strip: your roster option | consecutive workdays | consecutive off days stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.
Perspective: Before: A different starting phase can change the short-horizon count. After: the roster-cycle strip shows the working beside each named row so the reader can change the assumption and inspect the consequence.
2 · Read the roster-cycle strip
Pattern arithmetic, not a fatigue assessment or employment entitlement calculation. Review rest requirements and the actual dated roster with the responsible scheduler.
Paid layer: roster-cycle strip print and history
one-time step · the free reading above stays complete
Free tier
- one complete roster-cycle strip run in the app
- three samples plus unlimited article-demo runs
- unwatermarked result text and an explicit, user-triggered state link
What $4 one-time adds
- print the roster-cycle strip with its row workings
- CSV of scheduled workdays and row explanations
- last five reading summaries saved in this browser profile
$4 once for repeated filing of the roster-cycle strip, not for a better answer. Illustrative time basis: avoiding one five-minute manual reformat per saved reading; no market-price or guaranteed-savings claim.
Local history (this device)
- No saved runs yet — your first run files here.
Checkout is unavailable until a payment link is configured. The optional unlock is browser-local, profile-scoped and best-effort, not server-verified access. Clearing browser data can remove it; there is no account or cross-device recovery.
Boundary and sources
Pattern arithmetic, not a fatigue assessment or employment entitlement calculation. Review rest requirements and the actual dated roster with the responsible scheduler.
- Method: Workdays = floor(horizon ÷ cycle) × on-days + min(on-days, horizon mod cycle). Four on/four off over 30 days yields 16 workdays, while five on/two off yields 22.
- 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.
Mechanism: competence-autonomy-loop
Optional AI formatting, not calculation
For this roster-cycle strip, 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 roster-cycle strip. Return plain rows only: roster option | consecutive workdays | consecutive off 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: roster option | consecutive workdays | consecutive off days. No AI response is executed as code.