For institutions
Bring DataSquad to your institution
Starting a DataSquad means adopting a proven model and joining a network of peers, not buying a system. Here's the path from "interested" to "running."
Express interest →-
Tell us you’re interested
Open an interest issue (or email us). Where you are in the process is fine, just exploring counts.
-
Talk it through
A network lead meets with you to understand your campus, talk about fit, and answer questions.
-
Get the starter kit
Role descriptions, a service-scope policy you can adapt, onboarding patterns, and a shared reading list.
-
Stand up your local setup
Choose your own tools for scheduling, request tracking, and funding. We share what we use; you decide what fits.
-
Join the community
Plug into the network’s GitHub Discussions and Projects, and the announcements list, to learn from other squads.
-
Launch, then share back
Run your first consultations, and let your wins feed the blog and help the next institution adopt.
The starter kit
A concrete checklist of what you need to launch: the roles to fill, a service-scope policy to adapt, the local decisions to make, and a shared reading list for new analysts.
See the starter kit →How the network coordinates
We run on tools the leads already use. GitHub Projects tracks shared work and GitHub Discussions is where squads ask questions, share projects, and propose ideas, searchable and open, so new adopters can read the back-catalog. A low-volume announcements list covers anyone who'd rather not check GitHub.
Start a conversation →Not an institution?
- Students, if your campus has a DataSquad, contact your local program. If it doesn't, the interest form has a "get involved" option.
- Researchers, find a squad near you in the institutions directory and request help there.