# TNN Asset and Commitment Survey

**Populates the Asset and Commitment Map (Deliverable D2)**
**Draft v1.0 — June 18, 2026**

> Design intent: short enough that a slammed person finishes it in one sitting. Two halves. The first half is what you have (the declared system). The second half is what you are committed to give (the functional system). The second half is the part most asset maps skip, and the part that makes this one usable.
>
> Target completion time: under 12 minutes. Resist adding fields. Every question past the point of fatigue costs response rate, and a half-filled directory is worse than a short one.

---

## Intro text (shown to respondents)

At the retreat, the most-wanted thing to be able to hand someone was a clear picture of who does what across the network, and what we can actually offer each other. This survey builds that. It has two parts. The first asks what your organization does and has. The second asks what you are willing to commit, concretely, because a directory of capabilities only helps if the help is actually there when someone reaches for it.

Be specific in Part 2. "Happy to help" is not a commitment. "Ten hours a quarter on facilitation design" is.

---

## Part 1 — What you have (declared)

### A. Basics
1. Your name.
2. Organization or context.
3. Your role.
4. Region or grouping (National, State, Regional, or describe).
5. One sentence: what your organization does.

### B. Capabilities
6. What is your organization genuinely good at? List up to five.
7. What are your current strengths in this season? (resources, programs, relationships, reach)
8. Where are you thin or stretched? Where would help from the network matter most?
9. What programs or bodies of work are you running right now that others might learn from or plug into?

### C. Offerings to the network
*(These feed the shared offerings directory. Think: what could be offered to another member's people, not just to the member.)*
10. What could you offer to other members' communities or constituencies? (a workshop, a template, an introduction, a seat in a cohort, data, space, anything concrete)
11. Is any of that already packaged, or would it need to be built out?
12. Are there things you offer transactionally today that you would rather offer relationally? (for example, moving from "we provide X" to "we build Y with you")

### D. Bench
13. Who in your context, but not in the retreat room, holds expertise or relationships the network should know about? Name them and what they bring.
14. Are any of them people you could bring into a conversation or a working group if asked?

---

## Part 2 — What you are committed to give (functional)

*This is the half that makes the map real. For each line, give a concrete amount, not a willingness.*

15. **Time.** How many hours, over what period, are you committed to give to shared network work? (for example, "8 hours a quarter")
16. **For what.** What kind of work is that time for? (facilitation, fundraising case-building, peer hot seats, onboarding new members, a working group, the database, something else)
17. **Hot seat.** Would you commit to bring a live challenge to a peer hot seat, or to sit on one for others, or both? How often?
18. **Crisis brain trust.** If a member hit a crisis and a small group convened quickly, would you commit to be reachable for that? With what notice?
19. **Resources beyond time.** Anything concrete you can commit (funds, pass-through capacity, space, tools, a named program slot). State the amount or the conditions.
20. **Grant tie-in.** If the network's next grant includes commitments from members, what would you be willing to have written down next to your name? This is the line that turns "I'm willing" into "I'm committed."

---

## Part 3 — What you want to get

21. What do you most need from the network from the seat you hold? (be concrete; this shapes what gets built for you)
22. What would make a network call or convening worth your time when you are underwater?
23. What is one thing you would want a member who wasn't at the retreat to be able to see or use right away?

---

## Notes for the build (not shown to respondents)

- **Map Part 1 to the directory, Part 2 to the commitment layer.** The directory is browsable. The commitment layer is the field that gets checked before anyone is asked to deliver.
- **Question 20 is the keystone.** It is the difference between an aspirational map and one that survives contact with a real ask. If response rate on it is low, that is itself a finding worth reporting.
- **Question 12 surfaced live at the retreat** (the house-versus-neighborhood shift). Keep it; it tends to produce the most honest answers.
- **Keep the form to these 23 items.** If a field is tempting to add, put it in a later round instead. Survey fatigue was named in the room as a real cost.

---

*v1.0 — June 18, 2026. First draft. Field after the One-Pager (D1) ships, so respondents have the shared definition in hand before they answer.*