Welcome to Agentic Case Management & Sanctions thatbooks the hearing inside the notice window.
A conduct case is a sequence of windows with a person at the end of each one. Risely schedules, drafts, logs and verifies. The conduct officer and the panel decide, and the file records which of them did.
Case file
open · every window ahead
queued
Case opened
the day the report lands
the conduct officer
queued
Notice delivered
inside the notice window
the conduct officer
queued
Hearing held
inside the hearing window
the hearing panel
queued
Decision issued
inside the decision window
the conduct officer
queued
Sanction verified
before the case closes
the provider roster
Precedent for this violation, last three years
shown before the choice
The hearing lands inside the window.
Risely's agents collect the panel's availability, find the slot the whole panel shares, and draft both parties' notices with the date already on them. The scheduling thread that used to run for a week never starts.
Hearing, inside the window
collecting availability
Tuesday, the only slot the whole panel shares
Notices to both parties drafted with the date on them.
The officer sees the range before choosing.
Risely surfaces what this violation type drew over the last three years and stops there. Consistency across a rotating board comes from everyone seeing the same band, and the record keeps the version the officer saw.
This violation type, last three years
Risely shows the band and stops there. The conduct officer chooses inside it, and the record keeps what they saw.
A sanction counts once somebody checks.
Risely's agents read the provider's completion roster and record the result against the sanction. The workshop that was assigned and never verified is the reason a repeat report looks like a first offense.
Sanction completion
verified at the source
An educational sanction that nobody verified taught nobody anything, and a repeat report cannot tell the difference.
The appeal file is finished before the appeal arrives.
Every notice with its delivery confirmation, every window with its date, and the precedent band the officer worked from. The office's fairness is real, and this is what makes it provable.
Appeal file
assembling
The file assembles while the case is open, so an appeal reviews a process instead of exposing one.
One thing moves. The case re-runs.
A reschedule request, a panelist who withdraws, an appeal filed on the last day. Any of them moves the case, and every one runs the same way.
A party asks to reschedule
two days before the hearing
Risely re-books inside the window
the panel's shared slot decides it
Both notices redraft
new date, same delivery method
The conduct officer sends them
one review, two letters
The appeal file records the change
the reason and the date are on it
Agentic Case Management & Sanctions never works alone.
What changes, and how it runs.
Every case lands inside its windows
The scheduling thread never starts, and the date holds.
Sanctions sit inside the precedent band
A rotating board reads the same history every time.
The appeal reviews a process
The file was complete before anyone asked for it.
The technical read
Connects read-only to your conduct system, SIS, and calendars to start
A conduct officer issues every decision
Every action lands on an append-only log
Runs alongside what you have. Nothing rips out.