Two medspa locations can use the same logo and still teach a new colleague different ways to handle the same task. One team has a current guide, another uses an old printout, and a third version lives in a manager’s messages. The difference may stay hidden until somebody covers another location or a new hire asks which instruction to follow.
Start by separating the parts of the work that must be consistent from the details that genuinely vary by location. A shared standard should make that distinction visible. It should also tell the reader who owns it, which version is current and where to raise a question.
At a glance
- Keep one maintained starting point for shared resources.
- Document legitimate local differences alongside the common process.
- Test changes in a limited setting before distributing them more widely.
Define the common task before standardising the document
Choose one task with a clear beginning and end, such as transferring an unresolved administrative enquiry. Ask each location to describe its current approach using a fictional example. Look for differences in the information recorded, the person accepting responsibility and the way completion is confirmed.
Do not assume every difference is a mistake. A location may have different opening hours or a different designated contact. Conversely, a missing confirmation step may simply be a habit that nobody has examined. The discussion should reveal why the difference exists before deciding whether to preserve it.
AHRQ’s handoff guidance favours a standard approach that the team understands while recognising that a tool must fit the organisation. That is a useful principle for this administrative example, rather than a reason to impose one clinical workflow across every setting. Read the handoff guidance.
Give every resource an owner and a visible status
An editorial map for maintaining a shared resource. The labels describe responsibilities; they do not represent performance scores.
A useful resource header can be short: task name, owner, version or review date, the roles it applies to, and the location of the current copy. If a colleague downloads or prints it, they should still be able to tell where to check for an update. Decide how superseded copies will be marked or removed from routine use.
Place local details in an obvious section. For example, the shared process might require a named callback owner, while each location maintains its own current contact rota. Link those details from the shared resource instead of duplicating a contact list that will become stale in several places.
A worked example: a process that changes by location
Imagine a fictional two-location practice. Both teams record appointment changes in the same system, but one location confirms the receiving colleague directly while the other assumes a task notification is enough. A colleague covering both sites cannot tell when responsibility has transferred.
The managers agree on a shared requirement for explicit acceptance and ask one team to test a practical way to record it. The local contact names stay local. After the test, the team reports that acceptance is clearer but the notification wording is confusing. They revise the wording before trying the approach in the second location.
IHI recommends using small tests to learn how a change works locally before wider implementation. This example applies that approach to a routine administrative process; it is not a claim that a single trial proves the process is better. Read IHI’s guidance on testing changes.
Introduce a change as a task, not just an announcement
A message saying “new procedure attached” tells colleagues that a document exists. It does not show whether they can use it. Explain what changed, why it matters to their role, where the current version lives and what they should do differently on the next relevant task.
Use a short fictional example and ask colleagues to find the answer in the resource. This is also a usability check. If experienced staff search three folders before finding the right page, improve the route to the resource before interpreting the delay as resistance. Invite people from different shifts so the rollout reflects more than the manager’s working pattern.
Rollout prompt: “What is the next action in this example, where did you find it, and which local detail do you still need?”
Use a review checklist that separates consistency from sameness
- Can each location find the current shared resource?
- Is a named person responsible for maintaining it?
- Are local contacts and exceptions clearly identified?
- Can the relevant colleagues apply it to a fictional situation?
- Is there a route to report a problem or propose a change?
- Have outdated routine copies been dealt with?
A review should not become a competition between locations. Ask what made the task easier or harder in each setting. Record the context before comparing counts: a small location and a high-volume location may generate different amounts of work. Start with whether the shared process is understood and usable.
Let new hires reveal the hidden gaps
Someone new to the practice has not learned the shortcuts that experienced colleagues take for granted. Ask the new hire to show where they would find the resource and how they would identify the current version. Their hesitation can reveal a naming problem, an access problem or a local exception that nobody documented.
Keep those observations in the resource owner’s review list. Set a realistic review point and tell the person who raised the issue what changed. That small loop helps the shared library stay connected to the work rather than becoming an archive of instructions nobody is sure they can trust.
Begin with one process used at both locations and one responsible owner. Once that arrangement works, extend it deliberately. A confident first week offers a practical way to connect the resource to a new colleague’s learning plan.
Sources and further reading
- AHRQ TeamSTEPPS: Handoff — a consistent approach that fits the team.
- IHI: Testing Changes — learning from local tests before wider implementation.
Sample article for the V-Unite Learn preview. The two-location practice and resource map are illustrative. Sources checked 6 October 2026.