1EdTech Contributing Member Call for Participation:
CLR 2.0 Task Force
We're looking for representatives from K-12 and higher-education institutions, technology providers, and workforce partners that consume CLR data to join a focused, time-limited task force dedicated to strengthening the implementation of the Comprehensive Learner Record (CLR) Standard 2.0.
The first meeting of this task force is on November 11, 2026, at 10:00 AM EST.
If you are interested in participating or want to learn more, please contact Rob Coyle, manager of digital credentials programs and ecosystem enablement, at rcoyle@1edtech.org.
CLR Standard 2.0 Task Force
Purpose
1EdTech is proposing a focused, time-limited CLR Task Force to strengthen implementation of the Comprehensive Learner Record Standard (CLR Standard) 2.0 and prepare a clearer roadmap for future CLR work.
CLR adoption is growing, but implementers continue to face questions around consistency, record complexity, and how receiving systems find and interpret key information.
The task force would give CLR dedicated attention without permanently separating it from broader 1EdTech Digital Credentials work.
Proposed Scope
The first priority is to build out and clarify the use cases CLR 2.0 already supports, rather than immediately begin work on a new version of the specification.
The CLR Task Force would review the use cases already defined in CLR 2.0, identify where additional implementation guidance or more consistent patterns are needed, such as CLR for admissions, institution, or district transfer, and workforce or talent marketplaces, and determine whether existing guidance, such as the CLR 2.0 Transcript Guide, can be extended or reused, or whether a new guide or profile may be needed.
The work will consider both the issuer perspective and the receiving/verifying system perspective.
Future CLR Work
As the CLR Task Force reviews the existing use cases, it will also identify scenarios that are genuinely missing or insufficiently represented in CLR 2.0.
These would become a future version use-case backlog. Identifying a missing use case does not mean the task force will immediately design or implement a change to the CLR specification.
Expected Outputs
- A CLR 2.0 use-case matrix organized around key education and workforce transitions.
- Clearer implementation patterns or guidance for existing CLR 2.0 use cases.
- A prioritized inventory of current pain points for implementers and verifiers.
- Recommendations for where implementation guides, profiles, examples, or other guidance would improve consistency.
- A defined backlog of genuinely missing use cases for consideration in the next version of CLR.
- Recommendations on whether any identified issues ultimately require changes to the core CLR specification.
Coordination and Boundaries
CLR and Open Badges should continue to coordinate where they share data models, credential structures, security, or other architecture. The combined Digital Credentials Product Steering Committee should remain in place.
API, transport, and credential-movement work is outside the primary scope of this task force. Questions involving wallet-to-wallet exchange, platform-to-platform exchange, bulk transfer, authorization protocols, or transport profiles should continue through the separate digital credentials API and transport work.
Participation
Participation should include K-12 and higher-education institutions, CLR implementers, receiving and verifying systems, credential platforms, and relevant workforce and ecosystem partners—particularly organizations that consume CLR data, not only those that issue it.
Meetings and Initial Timeline
The CLR Task Force will begin meeting on November 11, 2026, at 10:00 AM EST. During the initial phase, the group is expected to meet 2-4 times per month, depending on participant availability. The group will establish the longer-term meeting schedule and cadence together once the work is underway.
The immediate goal for November and December is to convene the group, validate the scope and priorities, and complete the charter before the end of 2026. This will position the group to begin substantive implementation and use-case work at the start of 2027.
Timing and Outcome
The CLR Task Force is intended to be a focused, time-limited initiative working through the identified CLR implementation and use-case priorities during 2026–2027.
Upon completion of its chartered work, CLR activity should revert to the combined Digital Credentials Project Group unless members determine that maintaining a separate CLR workstream continues to provide value.