A useful local practice is not yet a network standard.
Transfer the conditions that made a practice work before copying its form.
Read the conditions of success
A local team may resolve a recurring problem through a short approval path. Another site copies the form and sees no movement because its authority, staffing or dependencies differ. Document who could decide, what information was available, which workload the practice faced and how the result was observed. A transferable practice includes these conditions. Without them, a network spreads a format while leaving the cause of success behind. Keep the local team involved in explaining what it actually did.
Design the shared and the variable
Agree a common promise, evidence definitions and escalation boundary. Allow local adaptation in scheduling, role allocation or implementation details where the promise remains intact. Test the practice in a second setting and explicitly record what had to change. Differences are useful evidence about the operating conditions; they are not automatically noncompliance. The center should know what is comparable and the field should know which adaptation it can make without waiting for a new central decision.
Adopt after the test
Treat the first practice as a hypothesis for wider use. Compare baseline and follow-up in each setting, retain failures and review with the responsible owners. Adopt a shared standard only when the evidence supports its scope. The playbook records the reason, tested conditions, approved local variation and review date. This gives the next team a way to learn without treating the current standard as permanent truth. Scaling means keeping one intent coherent across different realities, not making those realities identical.
Free templates: record the decision and observe the friction