Assessing Skills Across a Multi-Site

In summary

In a multi-site network, skills assessment scatters almost naturally: no shared reference framework, frequent changes of assessor, ground-level evidence that isn't comparable from one site to the next.

Trying to force an identical training pathway everywhere is a false solution: site diversity often has good reasons to exist.

The right approach rests on 3 targeted adjustments: separate what can vary from what shouldn't, give a common format to ground-level evidence, and make sure this framework survives a change of person.

Harmonising assessment doesn't mean erasing differences between sites, it means agreeing on a narrow shared foundation.

How do you assess people the same way when they don't work under the same conditions? That's the question a network's management ends up asking itself, one way or another. 2 employees hold the same role, in 2 different parts of the network. They're expected to reach the same level of proficiency on the same topics. But nothing in how each site operates guarantees they've been assessed with the same rigour, or even against the same criteria.

This isn't a matter of discipline or good intentions. It's a direct consequence of how a multi-site network builds up over time: each site adapts to its own context, and that adaptation, entirely legitimate, ends up affecting even how a skill is judged to be acquired.

Diversity that makes sense, up to a point

Take a network of shops located in high-traffic areas, stations, airports, mixing company-owned outlets and franchises. The manager of an outlet has a particular status: employee or "entrepreneur", employer of their own small team. What's sold can also change from one site to another, some offer games, others takeaway food, others coffee. Training therefore can't be identical everywhere: it rests on a common core plus modules that get added or not depending on the site's actual offer.

This kind of diversity isn't a problem. It's even a strength: it lets the network fit very different local realities rather than imposing a single, theoretical model. The problem starts when that same diversity, legitimate at the level of the offer, also spreads to how you check that an employee can actually do what's expected of them. That's where assessing skills across a multi-site network becomes concrete, and urgent.

Why assessment ends up scattering

3 mechanisms explain why, in a multi-site network, skills assessment desynchronises almost naturally from one site to another, even when no one decided it that way.

The absence of a shared reference framework. A skills development manager at one such network admits it plainly: training gets built around whatever's needed at the moment, site by site, with no basis for comparison between them. Each site knows what it needs locally, but no one knows whether the level reached at one site matches the level reached at another.

The person doing the assessing changes. They might change partway through a pathway, simply because the first one is no longer available: schedule changes, transfers, absence. Follow-up then starts again with someone else, who doesn't necessarily have the same standards, or the same way of noting what they observe. This isn't a pedagogical choice. It's a direct consequence of the network's dispersion, something no one decided but that everyone ends up dealing with.

Evidence that stays local. Evidence that a skill has been acquired does exist on the ground, but it stays in whatever format each assessor chose to give it. A note, a photo, a verbal remark quickly forgotten. This evidence is real but comparable to nothing: it lives and dies on the site where it was produced. 2 different assessors, at 2 different sites, can judge the same task as mastered with a very different level of rigour, without either one being wrong: each is applying their own benchmark, for lack of a shared one.

These 3 mechanisms stack up, and it's their combination that makes assessment hard to harmonise unless you tackle it directly. This isn't a question of individual rigour. It's a question of structure.

Harmonising assessment without standardising practices

The classic mistake is trying to solve this by forcing an identical pathway everywhere. That's both pointless and often doomed to fail: pointless, because site diversity often has good reasons to exist; doomed to fail, because a framework that's too rigid usually ends up being worked around locally, wherever it doesn't match the site's reality.

The right approach rests on 3 more targeted adjustments.

Separate what can vary from what shouldn't. An outlet keeps training its teams on what it actually sells, without unnecessary constraints. But on the few critical skills touching on safety, compliance, or customer relations in sensitive situations, every site must be assessed against the same criteria, regardless of location. Harmonisation isn't about everything, then, it's about a deliberately narrow foundation.

Give a common format to the evidence the ground already produces. This isn't about asking assessors to do more work, they've always observed and noted things. It's about giving them a simple template: exactly what to look at within this shared foundation, how to record whether it's acquired or not. It's this shared format that finally makes two assessments, done at two different sites, comparable. In this context, AFEST (workplace-based training) offers a useful, shareable approach.

Make sure this framework survives a change of person. In a dispersed network, the assessor will change sooner or later. If the assessment framework depends on the person applying it, every change of assessor introduces a break. If the framework is written down, shared and identical for everyone, the continuity of the pathway no longer depends on a single person, but on a method that outlasts them. This is also what brings this logic closer to an organisation built around skills rather than around irreplaceable people.

What this changes in practice

Once these 3 adjustments are in place, nothing has changed in the network's real diversity. A site that sells games keeps training on games. A site that doesn't, doesn't bother with it. What has changed is that network management can finally answer a simple question, whatever the site: on what really matters, is this employee assessed and supported the same way as their colleagues elsewhere in the network?

It also changes the nature of the dialogue between head office and the ground. Today, when there's doubt about an employee's real level, there's often nothing objective to look at together, only impressions, those of whoever happened to be assessing at the time. With a shared language, a shared foundation, and a shared assessment format, that doubt can be checked, and it's easier to align.

What Daylindo brings to harmonisation

Separating the shared foundation from the rest, giving a shared format to ground-level evidence, making this framework survive a change of person: these 3 adjustments need a tool that carries them day to day, not just a framework frozen in a document. That's the role the Daylindo platform plays: it structures ground-level skills data, keeps a record of each assessment that holds up as evidence, and lets a new assessor pick up follow-up exactly where the previous one left off, with no break in method.

Evidence from multi-site networks that have put this kind of shared foundation in place mainly shows a change in the nature of the dialogue between head office and the ground: exchanges are based on shared findings rather than individual impressions. Funding for these pathways is also worth considering in parallel, particularly when the shared foundation comes alongside a broader skills upgrade across teams.

The essential point

Harmonising assessment doesn't mean erasing differences between sites. It means agreeing on a shared framework and system that everyone can converge on, while still allowing what has good reason to stay different at each site to remain so.

FAQ

Do you need to standardise every practice to harmonise skills assessment across a multi-site network?

No. Harmonisation only applies to a narrow foundation, often linked to safety, compliance or customer relations. The rest of the practices can keep varying according to local context.

Why does skills assessment naturally scatter in a multi-site network?

Mainly for 3 reasons: no shared reference framework between sites, frequent changes of the person doing the assessing, and proof of competency that stays in a format specific to each assessor, so it's not very comparable.

How do you define the shared foundation to assess the same way everywhere?

By identifying the few skills that touch on safety, compliance or sensitive situations with customers, and reserving strict harmonisation for that scope rather than for all skills.

Does a change of assessor necessarily create a continuity problem?

Only if the assessment framework depends on the person applying it. A written, shared framework lets a new assessor pick up follow-up with no break in method.

Can AFEST serve as a basis for this shared assessment format?

Yes, a well-structured AFEST approach offers a shareable framework that helps give a common shape to ground-level evidence that was previously scattered from one site to another.

Can network management measure whether harmonisation is actually working?

Yes, by checking whether the dialogue between head office and the ground is based on shared, verifiable findings rather than individual impressions specific to each assessor.