diff --git a/surveys/2026-collaborator-health-survey.md b/surveys/2026-collaborator-health-survey.md
new file mode 100644
index 0000000..52a65c0
--- /dev/null
+++ b/surveys/2026-collaborator-health-survey.md
@@ -0,0 +1,204 @@
+# Collaborator health survey
+
+## A bit about you
+
+### How long have you been contributing to the project? (single-select question, can we also establish skip logic here specifically for people who answer less than 1 year OR 1-2 years? Forthcoming skipped questions are identified)
+
+- less than 1 year
+- 1-2 years
+- 2-5 years
+- 5-10 years
+- 10+ years
+
+### Which working groups or teams do you participate in? (multi-select question)
+
+- Security team
+- Diagnostics working group
+- Build working group
+- Performance team
+- Release working group
+- Website team
+- Next 10 working group
+- TypeScript team
+- uv wasi team
+- node api team
+- Test runner team
+- Userland migrations team
+- Other (specify)
+
+### Is contributing to Node.js part of your job ?
+
+- Yes (if yes please specify what % or what tasks (new features, bug fixes, etc))
+- No
+
+## How did you get involved
+
+### How did you first get involved ? (single-select question, skip for collaborators who have contributed for less than 1 year OR 1-2 years)
+
+- Attended Node.js Conference
+- Attended collaborator summit
+- Code and learn
+- Joined working group
+- Issues/PR(s) to address problems I was having
+- PR(s) to add new features I wanted
+- PR(s)/Issue(s) because I wanted to get involved in the project
+- PR(s) to improve code coverage
+- PR(s) to improve tests
+- PR(s) to fix flaky tests
+- Pulled in by other collaborators
+- Other (specify)
+
+### Why did you get involved ? (multi-select question, skip for collaborators who have contributed for less than 1 year OR 1-2 years)
+
+- Hobby, wanted to contributed to a key open source project
+- Using Node.js personally wanted to contribute
+- Work for a company that uses Node.js, encouraged to contribute
+- Joined a team at the company I work for that contributes
+- Other (specify)
+
+### What would have made it easier to get involved ? (multi-select question, skip for collaborators who have contributed for less than 1 year OR 1-2 years)
+
+- More documentation
+- Easier ways to contact existing collaborators
+- Easier ways to get guidance/direction from existing collaborators
+- Faster build time
+- Easier build process
+- Mentoring
+- Better identification of work that needs to be done across the project
+- Other (specify)
+
+## What keeps you around
+
+### What makes you want to continue contributing to the project? (multi-select question)
+
+- Working Groups / Teams
+- Features development
+- Bug fixes
+- Recognition in the larger community ecosystem
+- Other (specify)
+
+### What makes you less likely to continue contributing to the project? (multi-select question)
+
+- Code reviews are to strict
+- Code reviews are too slow
+- Code reviews are too lax
+- CI is flaky
+- CI takes a long time
+- Builds take a long time
+- My work is not valued
+- Required process to get a PR landed
+- PRs take too long to land
+- Long discussions on PRs
+- Having to deal with AI slop contributions
+- Problematic peers
+- Other (specify)
+
+## Level of contribution
+
+### How many hours do you dedicate to the project in an average week? (single-select question)
+
+- 0-5 hours
+- 5-10 hours
+- 10-40 hours
+- 40-80 hours
+- 80+ hours
+
+### Are you able to contribute as much as you would like? (single-select question)
+
+- Yes
+- Almost
+- A bit
+- No
+
+### If you are not able to contribute as much as you would like, what is preventing this?  (multi-select question)
+
+- My company actively interferers with Open Source contributions
+- My company does not support my contributions
+- Competing work or professional obligations
+- Competing personal obligations
+- Contributor burnout or fatigue
+- The review and PR process is slow or discouraging
+- My contributions are frequently rejected or go unreviewed
+- Lack of required technical expertise in certain areas
+- Local development or testing environment challenges
+- Having to spend too much time dealing with AI slop
+- Other (specify)
+
+### How frequently do you encounter poor-quality AI-generated contributions ("AI slop") in your Node.js collaboration work? (single-select question)
+
+- Never
+- Rarely (a few times per year)
+- Occasionally (a few times per month)
+- Frequently (once or twice per week)
+- Very frequently (several or more times per week)
+
+### On average, how much of your Node.js contribution time is spent reviewing, addressing, or closing AI slop? (single-select question)
+
+- None
+- Less than 1 hour per month
+- 1 – 3 hours per month
+- 4 – 8 hours per month (roughly 1–2 hours per week)
+- More than 8 hours per month (more than 2 hours per week)
+
+### Please rate your agreement with each statement below. (1 = Strongly Disagree, 5 = Strongly Agree, randomize options so positive & negative responses are shuffled)
+
+- Vibe-coding helps my contributing experience and/or makes my contributions more productive
+- Agentic-coding makes my contribution time more productive
+- AI slop contributions negatively affect my experience as a Node.js collaborator
+- Dealing with AI slop has reduced my motivation to continue contributing to Node.js
+- Because of AI slop, I am considering reducing how often I review certain contribution types
+- Because of AI slop, I am considering stepping back from reviewing entirely
+- I would support introducing an official AI slop label for flagging and tracking these contributions
+- An AI slop label would meaningfully help the team manage contribution quality
+- AI tools have been very useful for improving the quality and/or efficiency of my Node.js contributions
+- This question does not apply to me
+
+### How do you use AI tools in your own Node.js contributions? (multi-select question)
+
+- I do not use AI tools in my contributions
+- Code generation or completion (e.g., Copilot, Cursor, CodeRabbit)
+- Debugging or error analysis
+- Writing or improving documentation
+- Writing or reviewing tests
+- Researching unfamiliar APIs or concepts
+- Drafting issue descriptions or PR summaries
+- Other: ___________
+
+## Plans going forward
+
+### Are you planning to keep contributing this year?
+
+- Yes
+- No (specify)
+
+### Are you planning to keep contributing for the next 5 years?
+
+- Yes
+- No (specify)
+
+### What would you like to change to improve the current environment?
+
+## Node.js as an organisation
+
+### Please rate your agreement with each description below about **project governance**. (1 = Strongly Disagree, 5 = Strongly Agree)
+
+- It's fairly governed
+- The model is fair
+- The model works well
+
+### Please rate your agreement with each description below about **project policies**. (1 = Strongly Disagree, 5 = Strongly Agree)
+
+- They're clear
+- They're fair
+- They're working well
+
+### Please rate your agreement with each description below about **internal problems**. (1 = Strongly Disagree, 5 = Strongly Agree)
+
+- They're adequately dealt with
+- They're fairly dealt with
+
+### Please rate your agreement with each description below about **collaborator nomination requirements**. (1 = Strongly Disagree, 5 = Strongly Agree)
+
+- They're clear
+- They're fair
+- They're working well