Updates to the CNCF Adopter Interview Process for Moving Levels
The TOC has updated the Due Diligence Guide to clarify expectations for adopter interviews during the moving levels process. These changes aim to reduce delays, improve the quality of adoption signal, and give projects a clearer picture of what to prepare before applying.
Here is a summary of what changed and what it means for projects and TOC members.
What changed
Adopter submission is now a formal application requirement
Projects applying to move levels are required to submit 5-7 potential adopters as part of their application. This is not new guidance, but it is now explicitly documented in the Due Diligence Guide with a direct link to the submission form.
Projects should submit their adopter contacts via the Adopter Submission Form before or at the time of application. The TOC will select a minimum of three adopters from the submitted list for interviews, but may request additional interviews depending on the diversity of perspectives represented.
Reference Architectures and Case Studies can replace individual interviews
Submitting adopters with the application remains a requirement. The TOC is clarifying the forms of validated adoption evidence that satisfy it. A project's inclusion in a published TAB Reference Architecture or a published CNCF Case Study may serve as a replacement for an individual adopter interview. Both represent validated, production-level adoption by the submitting organization and can provide equivalent signal to a traditional interview. When evaluating either, the TOC member confirms that it demonstrates an independent organization's operational use of the project, rather than relying solely on the project team's or a vendor's account.
It is at the TOC member's discretion who is leading the Due Diligence for Moving Levels to determine whether the Reference Architecture or Case Study meets the necessary standards and includes the requisite information the Due Diligence requires to determine whether the project meets the requirements of the level in process. Where it does, TOC members should note the Reference Architecture or Case Study in the adoption section of the Due Diligence in place of the interview summary it replaces. This gives projects with strong adoption evidence a faster path through the adoption assessment while maintaining the quality of evidence.
Why these changes matter
Adopter interviews are one of the most time-consuming parts of the Due Diligence process. Scheduling, conducting, summarizing, and getting approval on interview summaries can add weeks to a project's timeline. By requiring adopter submissions up front and recognizing reference architectures and case studies as equivalent evidence, we reduce avoidable delays while maintaining the standard of adoption signal the TOC and the community expect.
What projects should do now
If your project is planning to apply to move levels:
- Prepare your adopter list early. Identify 5-7 adopters who use the project in an operational or production capacity. Prioritize contacts who are not project maintainers or governance participants.
- Submit via the Adopter Submission Form. Do this before or at the time you file your application issue.
- Check if your project appears in a TAB Reference Architecture or a CNCF Case Study. If it does, note this in your application. If your adopters are interested in submitting one, see the TAB Reference Architecture process or the CNCF Case Study guidelines.
Questions?
Reach out in #toc on the CNCF Slack or file an issue on the TOC repo.
