Welcome to Agentic Academic Calendar thatholds every add, drop, census, and refund date in one source.

The academic calendar lives in six places and agrees in none, and every mismatch becomes an appeal the institution loses. Risely's agents hold the dates as one source and compute the ripple of any change. The registrar and the provost approve before anything moves.

Academic calendar · spring

in agreement

Faculty senate moves the spring drop deadline 3 days

new drop deadline · Mar 8

the refund tier boundary moves with it

census stays fixed · flagged as now closer to drop

held for the registrar and the provost
·SIS enforcement date
·Aid office R2T4 calendar
·Student-facing pages
·48 syllabi with the old date

Every date has one definition.

Add and drop, census, refund tiers, and withdrawal deadlines are defined once and versioned. Every downstream system reads the same truth, and the catalog stops disagreeing with the SIS.

The calendar of record

versioned

·Add / drop deadlineone definition
·Census pointone definition
·Refund tiersone definition
·Withdrawal deadlineone definition

Every downstream system reads this source. The catalog stops disagreeing with the SIS.

The ripple is computed before the vote.

Moving one deadline moves a refund tier and crowds the census. Risely's agents render the full consequence map first, so the senate votes on the whole picture and the registrar approves with the effects already known.

Refund tier boundarymoves with the deadlineCensus pointflagged as now closerSIS enforcementwould change the same dayPublished pagesevery copy identifieddrop deadlineproposed movethe full map renders before the senate votes

An approved change lands everywhere the same day.

SIS enforcement, the aid office's federal calendar, and every student-facing page update together. No office enforces a date another office retired.

Propagation

running

·SIS enforcement date
·Aid office R2T4 calendar
·Catalog and student pages
·Syllabus owners

No office enforces a date another office retired.

The stale copy is found where appeals start.

The documents still carrying the old date get flagged to their owners the day the change lands. A student who trusts a published date is never wrong, so a whole category of appeals never forms.

Still carrying the old date

swept after every change

A syllabus template·
A department advising guide·
An orientation checklist·

The mismatch that seeds appeals hides in a document someone copied. The sweep finds it first.

One thing moves. The calendar propagates.

A senate vote, a state rule, a term compressed by a storm closure. Any of them moves a date other systems enforce, and every one runs the same way.

  1. The senate moves the drop deadline

    3 days later in the spring term

  2. The ripple computes

    the refund tier moves, and the census crowds

  3. The registrar and the provost approve

    both approvals land on the log

  4. Every system updates the same day

    SIS, aid calendar, student-facing pages

  5. The stale copies get flagged

    the syllabi still carrying the old date

What changes, and how it runs.

Every system enforces the same date

The catalog, the SIS, and the syllabus finally agree.

Changes land with their consequences known

The senate sees the full map before it votes.

The mismatch appeals disappear

A published date and an enforced date are the same date.

The technical read

Connects read-only to your SIS and catalog systems to start

The registrar and the provost approve every date change

Every change lands on an append-only log with its approvals

SOC 2 Type IIFERPAGDPR

Runs alongside what you have. Nothing rips out.