One intent. Many local realities.
Development depends on whether central intent survives the journey into the field.
Standards need interpretation
A central program can define eligibility, service commitments and reporting requirements. Local teams encounter different capacities, languages, access constraints and needs. Trace a beneficiary journey before assuming that one template produces the same experience everywhere. Document where local adaptation preserves the promise and where it silently changes it.
Separate delivery from continuity
A completed activity proves that something happened. It does not establish that support remained accessible, that the intended people were reached or that the next step had an owner. Follow referral, response and follow-up; ask who can resolve an exception and what the person understands about the path.
Make field feedback consequential
A reporting channel is useful when an observation can change a decision. Connect recurring friction to its source, an accountable reviewer and a bounded test. Preserve dissent and missing coverage alongside the central summary. Training should help local teams use the path and explain it, with feedback from actual practice.
Compare without erasing context
Agree definitions for referral completion, unresolved exceptions and follow-up continuity before measuring. Compare like conditions and retain local explanations. A common evidence structure can support learning across sites without turning unequal starting points into a simplistic league table. The institution owns the review and the next observation.