Start a chapter
Bring DiagDebug to your region
Chapters are recognized, not franchised. Here is exactly how that works, what you get, and what we ask of you before you apply.
The three-step recognition gate
We are honest about this up front because the bar is the point. Recognition is what makes a DiagDebug badge mean something.
Interest application
You tell us about yourself, your region, and why you want to lead. We review for fit against the trust rules and the practitioner-chair requirement.
Three-event probationary period
You run three events on a regular cadence under the DiagDebug charter. This is where a chapter proves it can hold a room, not just fill a form.
Steering committee recognition vote
The practitioner steering committee votes to recognize the chapter. Recognition is recorded in the network directory and git history.
What DiagDebug provides
- A charter template and a chapter playbook
- The DiagDebug brand kit
- A region subdomain of diagdebug.com (for example pnw.diagdebug.com)
- Guidance on running your Luma calendar
- A place in the network directory once recognized
What is expected of you
- A practitioner chair who is not a Fortinet employee
- Adherence to the six trust rules at every meeting
- A regular event cadence, not a one-off
- Willingness to complete the probationary period before recognition
Chapter interest application
This starts the conversation. It is not a commitment on either side. We read every application and reply by email.