HOW WE MEASURE TRUST
A plain-language walk through the methodology underneath every RFUTR instrument — how a community's trust architecture gets read, at the structural level, before it becomes any specific tool.
Every RFUTR instrument, whatever it's called, is reading the same three-part structure underneath. This primer explains that structure on its own — not as a product, a tool, or a pitch, but as the methodology itself. If you want to see the specific decision tools built on top of it, that's a separate piece; this one stays at the level of how the read actually works.
Every community already has a structure — who talks to whom, which organizations carry weight, which channels actually reach people. Most outreach guesses at this. Structure is where the read happens directly, before anyone designs a message or a program around it.
A structure can exist and still pull in different directions. Alignment is whether the trust already present is oriented toward the ask being made — and whether trust earned in one domain (a church, a school, a clinic) actually transfers to this new one, or has to be rebuilt from zero.
Structure and alignment can both be present and a community still won't move — or will move once and then collapse back. Trust is the ceiling on how far it can go, and the margin for error once it does. This is the variable most engagement approaches skip entirely.
Read together, the three produce Cohesion — a measurable read on whether a community moves as one, or fragments under pressure. It's the single output every instrument in this platform is ultimately built to inform.
The Five Variables Underneath
What Structure measures — existing organizational and channel strength in a place.
Whether a community banks trust vertically, through institutions, or horizontally, through peer networks.
Whether trust earned in one domain carries into a new one, or has to be rebuilt.
How far a community's trust can stretch to absorb a new ask before it breaks.
Derived from Elasticity and Transferability — the margin for error once a community does move.
What This Primer Is — and Isn't
This is the methodology layer, not a claim of what it's proven to predict everywhere. Some of these variables are well-tested (Trust Orientation, floor-identification); others are newer, structural estimates still being validated against real-world behavior. Where a specific engagement makes a claim built on this framework, that claim carries its own tested-against record — this page is the shared grammar underneath all of them, not a substitute for checking each one.
Each Lens Adds a Layer.
One Prescription.
Five variables. Five questions. Together they produce something no single question could — a complete picture of how trust actually moves in a community.
A constructed example built to show the method — not a documented case or client result. "Block A," "Block B," and "Miss Carmen" are composites, not a real place or a real person. We're using them to show how the five lenses build on each other — and, just as important, where the read stops and where real human fieldwork has to start.
Most tools ask communities what they think. CI asks five behavioral questions about how trust moves. Each question can only be asked after the prior one is answered. Skip one and the prescription is wrong.
What looks obvious at Phase 1 often looks different by Phase 2. The neighborhood that looks unreachable may turn out to be worth a second look; the one that looks enthusiastic may turn out to have no staying power. Trust Elasticity (Phase 2) is a structural estimate still being validated against real-world behavior — a signal worth testing, not yet a confirmed prediction. This illustration treats it that way throughout.
Block B: High inward orientation. They trust their neighbor. They don't trust the flyer on the telephone pole.
Answer
Launch through Block B, not Block A. Route the ask through a relational channel, not a flyer — in our story, that's Miss Carmen. Pair the school newsletter for Block A. Skip the channel with no current leverage. Build a stewardship role into the program design from day one. Without that, the garden lasts two years. With it, it's still there a decade later.
This is what five structural lenses produce that one survey question never could — and where the read hands off to real people doing real fieldwork.
Block A looked easy. The full read suggests it may be the less sustainable option. Block B looked closed. The full read suggests it may be more reachable than it first appears. You only get that picture by running all five structural lenses — not by stopping at the first one.
Not all trust is portable, and the structural read tells us exactly which channels transfer and which don't. It never hands us a name — finding the actual Miss Carmen in a real neighborhood is deliberate, qualitative fieldwork that follows the read, not something the instrument outputs on its own.
Phase 4 finds the sustainability condition before a dollar is spent. A garden program without a built-in long-term stewardship role is not a program — it's a temporary installation.
Everything the instrument itself produces is derived from aggregate behavioral signals at the census-tract level. Zero personally identifiable information is collected, stored, or used at any stage. The instrument cannot name, identify, or count specific individuals — not Miss Carmen, not anyone.
The unit of analysis is always the community, never the person. Finding an actual person like Miss Carmen — in a real engagement, not this illustration — is separate, deliberate human fieldwork that follows a structural read. It's never a direct output of the data itself.
We don't own the community data we work with — nor do our partners. The community does. We believe this is the only ethical way to do this kind of work.
It's also, as it turns out, a genuinely stable and predictive way to work: place-level architecture holds up without a customer file and raises no privacy questions of its own.