Maintain a committee’s recurring meeting schedule

Purpose

A recurring calendar reduces the work of maintaining a committee’s regular meetings. Staff manage the schedule and inspect the occurrences it produces.

How It Works

Staff enter a title, a recurrence, a time zone, a meeting duration and the first eligible date. Optional end dates and exclusions limit the calendar. Physical and video meeting details supply defaults for newly generated occurrences. Creation generates the initial calendar, while staff can request another generation without waiting for the daily process. The series remains distinct from its individual meetings. Editing it can update or cancel eligible occurrences, but does not reset completed meetings. Current generation calls every new occurrence immediately. The approved direction instead calls for drafts followed by lead-time calling. Restoring cancelled occurrences after resumption and protecting individually moved meetings are also approved directions that the current implementation does not fulfil.

Relationships

Meeting scheduling supplies the records generated by a series. Attendance work uses the participant snapshot attached to each occurrence.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Regular meeting dates are generated from a shared scheduleRepeating calendar generation creates no duplicate occurrencesSchedule changes affect eligible future meetings
Surfaces: apijob
Preconditions: The owning committee is recorded and has not been dissolved.
Intent sources: services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#D3services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#D12

Controls

28 controls apply, from the corpus control catalogue.

TC-IAM-006 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-SEC-001 TC-SEC-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-AVL-004 TC-MON-001 TC-MON-002 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002

Permissions

Key	Checked at	Scope
`committees.meetings.read`	api	tenant
`committees.meetings.manage`	api	tenant

Business Rules

11 rules, 9 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	A recurrence supports daily, weekly or monthly frequency, an interval, applicable weekdays or month days, a start hour with optional minutes, either a count or an end date, and excluded dates; unsupported combinations are rejected with an explanation. ✓ Meet at 19:00 on the second Tuesday each month.✗ Request annual recurrence or omit the start hour. no proof recorded yet	validation	api, service	test services-committees:modules/meetings/tests/unit/services/recurrence-rule.spec.ts#refuses a yearly rule
`02`must prove Proposed	A series requires a recognised time zone, a duration from 1 through 1,440 minutes, and an end date on or after its first day when an end is supplied. no proof recorded yet	validation	api, service, database	observed services-committees:modules/meetings/services/persistence/meeting-series.ts
`03`must prove Proposed	An active series generates at most one meeting for each occurrence from the later of today and its first day through eighteen months from today, subject to its end date. no proof recorded yet	calculation	service, database	test services-committees:modules/meetings/tests/integration/services/meetings.integration.spec.ts#creates one meeting per occurrence of the window, on the second Tuesdays
`04`must prove Proposed	The daily process generates occurrences for active series in active workspaces and reports failed series while continuing with the others. no proof recorded yet	lifecycle	service	test services-committees:modules/meetings/tests/integration/services/meetings-jobs-tenant.integration.spec.ts#makes a series’ occurrences over the 18-month window, one a week
`05`must prove Proposed	Changing a series updates the title, time, time zone and duration of its future draft or scheduled occurrences, cancels dates removed from the schedule, and preserves held or cancelled occurrences. no proof recorded yet	lifecycle	service	test services-committees:modules/meetings/tests/integration/services/meetings.integration.spec.ts#rewrites the future unheld occurrences to the new time
`06`must prove Proposed	The product should create series occurrences as drafts and call them at the committee’s lead time, initially thirty days before, with an option for staff to call them earlier. origin: CMTE-M3 D3 (Andrew 2026-10-21, services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#Decisions) no proof recorded yet	policy		documented services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#Decisions
`07`must prove Proposed	The product should restore eligible occurrences when a paused series resumes or its end date is extended, after cancelling future occurrences on pause. origin: CMTE-M3 D12 item 1 (Andrew 2026-10-21, services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#Decisions) no proof recorded yet	lifecycle		documented services-committees:docs/milestones/plans/CMTE-M3-plan.md#D12. Smaller rules to approve as a group
`08`must prove Proposed	The product should preserve meetings that staff rescheduled individually when their series changes. origin: CMTE-M3 D12 item 2 (Andrew 2026-10-21, services-committees:docs/milestones/CMTE-M3-meetings-and-minutes.md#Decisions) no proof recorded yet	policy		documented services-committees:docs/milestones/plans/CMTE-M3-plan.md#D12. Smaller rules to approve as a group
`09`must prove Proposed	Creating a series for a dissolved committee is refused. no proof recorded yet	validation	service	observed services-committees:modules/meetings/services/persistence/meeting-series.ts:createSeries
`10` Proposed	A generated occurrence receives the series’ default physical and video meeting details.	policy	service	observed services-committees:modules/meetings/services/persistence/meeting-series.ts:materializeSeries
`11` Proposed	Staff can generate any missing occurrences in the current window without waiting for the daily process.	policy	api	observed services-committees:modules/meetings/aws/api/meetings.routes.ts:materializeMeetingSeries

Scenarios

Id	Given	When	Then	Provenance
`01`	A board has a monthly second-Tuesday schedule at 19:00 New York time, lasting ninety minutes	Staff save the recurring schedule	Occurrences through the rolling eighteen-month window are created in scheduled status	test services-committees:modules/meetings/tests/e2e/meetings.e2e.spec.ts#creates every occurrence scheduled
`02`	Occurrences already exist for the current generation window	The same series is generated again	No additional occurrence is created	test services-committees:modules/meetings/tests/integration/services/meetings.integration.spec.ts#creates nothing when it runs again

Edge Cases

Id	Given	When	Then	Provenance
`03`	A Pacific-time Sunday series starts at 02:30 across the spring clock change	The calendar occurrences are generated	The missing local hour shifts forward to 03:30; other Sundays start at 02:30	test react-console:acceptance/committees/playwright/journeys/meetings/CMT-ACC-0253.spec.ts#CMT-ACC-0253

Planning

Maintain a committee’s recurring meeting schedule ​

Purpose ​

How It Works ​

Relationships ​