Declared Duty Rotation Calendar

How to use Declared Duty Rotation Calendar

Turn an ordered list of people into a local shared-duty schedule under a rule everyone can inspect. The pointer moves after the last actual assignment, skips absent people and gives each person at most one slot per date. A CSV or printable schedule shows unfilled slots and per-person totals without inventing an optimal staffing plan.

1. Enter the inclusive date window, ordered people, exact weekdays, identical slot count and known absences.
2. Run JSON review to inspect cursor changes, assignments, shortages and totals.
3. Export a CSV or escaped printable document and review it with participants through your own approved process.

Good to know

• Use 1–20 distinct ordered names, 1–5 identical duty slots per selected date, 1,000 unique person/date absences and at most 1,000 final assignments. Dates are Gregorian 1900–9999 with an inclusive forward window of at most 366 dates. Weekday names are exact Monday–Sunday strings; all JSON numeric tokens must be exact integers.
• The first listed person starts. On each selected date, scan the circular order once, skip absent people and assign each person at most once. Advance after the last actual assignment; all-absent dates keep the pointer. Skipped turns are not saved as a later entitlement. Shortages are explicit blank CSV slots.
• This is one generic duty with identical slots and an explicit rotation policy, not an optimization solver. No role qualification, preference, consecutive-work, holiday, work-hour, timezone, labor-rule, global fairness or legally adequate staffing claim is made.
• No invitations, messages, calendars or accounts are contacted. Names/absence records and downloaded schedules can be private. HTML uses escaped text and fixed CSS; real browser/print review is needed before distributing a schedule.
• Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.