Digital learning solutions
A shared view of the applications that support teaching and learning
An instructional application ecosystem includes more than a list of products. It connects educational purpose, people, student access, data, contracts, support, and ongoing review. A shared tracker gives district and school teams a practical place to begin.
Applications Purpose People Data Support
Why a shared application inventory matters
Applications are often selected, purchased, configured, and supported by different people. A common inventory helps those teams work from the same information and ask better questions together.
See the whole environment
Identify which applications are active, which schools or programs use them, what they support, and where similar tools may overlap.
Clarify ownership
Name the instructional, technical, school-site, privacy, and fiscal contacts who can answer questions and act when something changes.
Manage commitments
Track licenses, renewal dates, funding responsibilities, usage evidence, and the decisions needed before a contract automatically continues.
Understand access and data flow
Document sign-on, account provisioning, rostering, integrations, and the systems that send or receive authorized information.
Support responsible review
Keep privacy, security, accessibility, age appropriateness, instructional fit, and local approval visible throughout the application’s life.
Improve over time
Use implementation, support, accessibility, usage, and outcome information to decide what to expand, improve, replace, or retire.
One tracker, several perspectives
No single department sees the entire application ecosystem. The inventory becomes more useful when each team contributes the information it knows best.
Instructional leaders
Connect each application to an instructional purpose, intended learners, curriculum, implementation expectations, and evidence of usefulness.
School leadership
Confirm which applications are used locally, identify a school-site champion, coordinate staff support, and surface access or implementation concerns.
Information technology
Document authentication, account provisioning, rostering, integrations, device or network dependencies, support ownership, and deprovisioning.
Data, privacy, and security
Review which information is collected or exchanged, who can access it, why it is needed, how it is protected, and what happens when use ends.
Accessibility and student services
Consider whether students and staff with disabilities can use the application and whether accommodations, assistive technology, language access, or alternate workflows are needed.
Procurement and finance
Track licenses, costs, funding sources, contract dates, renewal conditions, fiscal contacts, and the steps required to end or change an agreement.
Think in terms of an application lifecycle
An application does not become part of the ecosystem only when it is purchased. The work begins with a need and continues until access, data, and contractual obligations have been closed responsibly.
- IdentifyDefine the instructional or operational need.
- ReviewConsider fit, accessibility, privacy, security, and evidence.
- ApproveName owners, conditions, funding, and responsibilities.
- ConfigureSet up access, rostering, integrations, and safeguards.
- ImplementPrepare educators, students, families, and support teams.
- MonitorReview access, usage, support, outcomes, and contract dates.
- Renew or retireMake an informed decision and close the lifecycle.
Start where you are. A district does not need every field completed before an inventory becomes useful. Begin with active applications, owners, users, access methods, and renewal dates. Add depth as teams review and improve the information together.
Sample resource
Digital Learning Tracker for Paid Apps
This contributed workbook demonstrates one way a district can bring application, access, contract, and ownership information into a shared working document. Use it as a starting point and adapt the names, roles, fields, and review process to local needs.
-
Tab 1: Digital Learning Systems Master
A districtwide view of applications, including how students sign in, how accounts or rosters are created, and whether an application connects with the district learning management system.
-
Tab 2: Active App Contracts Master
License types and quantities, contract dates, renewal status, school-site champions or owners, and the contacts responsible for contracts and payment.
-
Tabs 3–6: School-Based Views
School-specific reference views populated from the contract master so leadership teams can see the applications associated with their sites.
-
Tab 7: Roles for App Access
A role-based reference that can help teams determine which systems and applications new employees may need to perform their work.
Information a district may choose to track
The right fields depend on local policy, capacity, and purpose. The categories below can help teams identify useful gaps without turning the inventory into an unmanageable form.
Purpose and users
- Instructional or operational purpose
- Grades, courses, programs, or roles served
- Schools or departments using the application
- Status: proposed, approved, active, limited, or retired
Ownership and support
- District program owner
- Technical owner
- School-site champion or contact
- Vendor and support contacts
Access and integration
- Single sign-on or authentication method
- Account provisioning and deprovisioning
- Rostering method and source system
- Learning platform or other integrations
Data and safeguards
- Data collected, created, or exchanged
- Purpose and authorized users
- Privacy and security review status
- Retention, deletion, and incident contacts
Accessibility and implementation
- Accessibility review and documentation
- Assistive technology or accommodation concerns
- Training and implementation expectations
- Known support issues or alternate workflows
Contract and lifecycle
- License type, quantity, cost, and funding source
- Contract start, expiration, and notice dates
- Renewal owner and decision status
- Exit, data return, and deletion requirements
A practical way to get started
Build the inventory as a shared operational resource—not a one-time collection exercise.
- Agree on the initial purpose. Decide which immediate questions the tracker should answer, such as active contracts, student access, application ownership, or upcoming renewals.
- Bring together existing lists. Start with purchasing records, single sign-on catalogs, rostering configurations, school lists, curriculum resources, and support documentation.
- Name a responsible owner for every active application. When ownership is unclear, record that as an issue to resolve rather than leaving the field silently blank.
- Reconcile the information with school and department teams. Central records may not show every locally purchased, freely adopted, pilot, or no-longer-used application.
- Prioritize time-sensitive gaps. Address applications with approaching renewals, unknown data practices, unclear ownership, access problems, or unsupported use first.
- Set a review rhythm. Decide who updates the tracker, how changes are approved, and when leaders receive information needed for decisions.
Keep the inventory useful
A tracker is most trustworthy when updates are tied to ordinary work rather than saved for one large annual cleanup.
Update operational facts
Record new approvals, ownership changes, contract amendments, access methods, integrations, incidents, and retirement decisions.
Prepare for a decision
Review usage, instructional value, accessibility, support experience, privacy and security changes, cost, overlap, and implementation needs.
Reconcile the ecosystem
Confirm active applications with schools and departments, retire obsolete entries, verify owners, and identify gaps that require follow-up.
Authoritative resources for deeper review
Local requirements vary. These official resources can support the teams responsible for privacy, accessibility, cybersecurity, and interoperability review.
- U.S. Department of Education: Privacy and Education Technology — Guidance and evaluation resources for understanding how online educational services collect, use, transmit, and protect student information.
- W3C Web Content Accessibility Guidelines overview — Standards and supporting materials for making digital content and applications more accessible to people with disabilities.
- 1EdTech OneRoster — A K–12 interoperability standard for exchanging roster, course, enrollment, resource, and results information through supported services.
- CISA K–12 Cybersecurity Acquisition Guidance — Cybersecurity considerations for incorporating risk and service expectations into technology procurement.
Continue exploring
Digital Learning Systems
The application listings below can help teams discover products already represented in the SDLA systems directory. A directory entry is a starting point for learning—not evidence that a product is approved, appropriate, accessible, secure, interoperable, or suitable for a particular district. Apply local review before adoption or use.