Skip to main content

Application support & operations

Recommended Annual App Lifecycle

Seven milestones for keeping educational applications useful, correctly licensed, connected to district systems, and ready for each school-year transition.

Use this operational companion alongside the Annual Timeline for Digital Learning Support, which also addresses educator development and school partnership.

Plan locally; coordinate the overlaps

These are recommended planning windows. Evaluation continues while renewal decisions begin; summer access, rollover, and rostering may run in parallel for different apps or programs. Work backward from each vendor’s notice periods, renewal dates, export deadlines, and rollover requirements, even when action must begin earlier than the windows below.

Name an owner for each app and each transition. Assign the local decision maker, technical lead, backup, and vendor contact. Curriculum, IT, student information system (SIS), purchasing, privacy, records, and school teams may share the work. Record who approves a change, who performs it, and who verifies the result.

Keep one shared app record: license scope and dates; integrations and sync schedule; affected users; summer exceptions; export and retention decisions; change window; and completion evidence. Keep credentials in the district’s approved secure system.

The seven milestones

1. Evaluate

October–March

  • Review usage by school, program, and licensed population; distinguish provisioned accounts from active use.
  • Gather stakeholder feedback and evaluate instructional impact alongside usage data.
  • Review licensing, costs, overlapping tools, and support workload.
  • Check recurring access or integration problems and unresolved accessibility or privacy concerns with the responsible teams.

Checkpoint: Document an evidence-based recommendation, unresolved questions, and a decision date for each app.

2. Renew or Retire

January–April

  • Renew approved contracts and reduce or expand licenses to match anticipated needs.
  • Identify apps being discontinued; confirm replacement plans, dependencies, and transition support.
  • Check auto-renewal and cancellation notice dates before committing to the local schedule.
  • Communicate approved changes, effective dates, alternatives, and data-saving steps to stakeholders.

Checkpoint: Record the authorized decision and vendor confirmation, with an assigned transition owner for retired apps.

3. Prepare for End of Year

April–May

  • Confirm vendor rollover requirements, dependencies, and the sequence of SIS, identity, and app changes.
  • Set access end dates and communicate data-saving deadlines before accounts or classes change.
  • Plan summer school access, including approved users, license coverage, roster source, and support contacts.
  • Identify required exports and verify they are readable in approved storage before the transition.

Checkpoint: Agree on a change schedule, summer exceptions, required records, and a recovery approach if rollover fails.

4. Turn Off or Modify Access

May–June

  • Disable graduating students’ access on approved dates after required transition and export steps.
  • Suspend apps not needed during summer and remove access for users who are no longer eligible.
  • Maintain approved summer-program access, with a named owner and a review or end date for each exception.
  • Coordinate app accounts, single sign-on, and roster rules so the next sync does not restore removed access.

Checkpoint: Test that ineligible users cannot enter and approved summer users still can. Disabling access does not by itself delete stored data.

5. Rollover

June–July

  • Archive prior-year classes and move apps into the new academic year using the vendor’s supported process.
  • Update school-year settings, term dates, and school mappings; protect active summer classes.
  • Confirm which historical records remain available, to whom, and for how long under district retention decisions and applicable agreements.
  • Separate archiving from deletion: route deletion through the local approval process after required records and any holds are resolved.

Checkpoint: Verify the new year and sample historical records. Record any vendor-dependent recovery limits before resuming affected integrations.

6. Roster

July–August

  • Verify SIS data readiness, identifiers, school and course mappings, and dates before starting the new-year automated roster feed.
  • Sync teachers, students, schools, and courses; confirm class membership and staff roles.
  • Reconcile expected counts and check missing, duplicate, transferred, or incorrectly assigned users.
  • Complete quality assurance before school starts: test representative student, teacher, and support-role access, including licensed content.

Checkpoint: Confirm successful syncs and correct access with the app owner; document remaining exceptions and their resolution dates.

7. Monitor & Stabilize

August–September

  • Resolve access issues and monitor sync errors, stale feeds, and unexpected changes in roster counts.
  • Support late enrollments, withdrawals, staff changes, and schedule changes within the expected sync cycle.
  • Confirm all users have appropriate access; review temporary privileges and summer exceptions.
  • Track recurring issues, assign escalation contacts, and update support instructions with verified fixes.

Checkpoint: Agree locally when service is stable, assign ongoing monitoring, and carry lessons into the next evaluation cycle.

Keep the essentials running year-round

Enrollment and staffing changes, access reviews, sync monitoring, incident response, and vendor updates continue throughout the year. Use the milestones to concentrate preparation and review, then keep routine support active between windows.