The school-district student-information ART runs Inspect and Adapt only once a year, after the last PI. When should the RTE place the event?
Select an answer to reveal the explanation.
Short Explanation
A once-a-year Inspect and Adapt is a yearbook, not a feedback loop. Each PI is supposed to end with demo, measures, and problem-solving while the work is still warm. Wait until June and the student-information train has already shipped three more PIs of the same mess.
Full Explanation
Place Inspect and Adapt at each PI boundary as the closing event for that Planning Interval on the school-district student-information ART. Annual-only I&A is a yearbook, not a feedback loop; each PI should end with demo, measures, and problem-solving while the work is warm. Waiting until after summer break only delays learning across mid-year SIS releases. Using I&A as an emergency substitute whenever a state reporting deadline slips confuses cadence with crisis response. Running I&A once every two PIs if enrollment looks stable skips half the learning opportunities. Exam caveat: make-up sessions after a true emergency are acceptable if the full I&A still occurs before the next PI Planning. Operational check: schedule I&A inside every IP iteration on the district calendar and refuse annual-only consolidation so student-information quality issues are corrected PI by PI. In municipal and civic service contexts, record the rationale in the ART working agreements or improvement backlog so future PIs preserve the control, and re-validate after the next Inspect and Adapt against resident-facing outcomes rather than activity theater. Confirm owners, success measures, and a re-check date so the practice remains inspectable.