From working document to training tool
A protocol contains something shadowing doesn't transmit: the why. At the chair a junior sees the gesture and infers the reasons; reading the document they see the explicit reasoning, from the starting point observed through to the choice of technique and the planned upkeep.
From that comes a simple, effective exercise: have whoever is training read the protocols of an experienced colleague, grouped by type of service. After a couple of dozen documents the recurring criteria emerge, and they become questions — why two sessions here and one there? — which is exactly the conversation that builds skill.
The second use is cross-review. Once a month two colleagues swap a few protocols and flag what's missing: a datum not recorded, upkeep not stated, an alternative not planned. It works better than top-down correction because it's symmetrical.
What actually transfers skill
The chart is qualitative and compares how much each format transmits technical reasoning rather than just the gesture.
What changes in the first months
The table compares onboarding a new team member with and without systematic use of protocols.
| Aspect | Shadowing only | Shadowing plus protocols |
|---|---|---|
| Time to run a consultation alone | Months | Weeks, with supervision on the document |
| Consistency with the rest of the team | Depends who did the shadowing | Aligned on common criteria |
| Verifiability of progress | Subjective impression | Comparable documents over time |
| Load on the experienced colleague | High and continuous | Concentrated in the review |
Using protocols to train
Group them by service
The comparison only emerges that way.
Have them read
Twenty documents show the reasoning.
Set up cross-review
Twenty minutes a month, symmetrical.
Measure completeness
Of documents produced, not course hours.
How to set it up
- Group protocols by type of service, not chronologically.
- Set a short, symmetrical monthly cross-review.
- Measure document completeness, not training hours.
Grouping by service type is what makes the exercise useful. Reading five balayage protocols in a row shows the constants and the variations far better than twenty mixed documents, because the comparison is immediate.
Keep the review short. Twenty minutes a month in which two people swap three documents and flag what's missing produces more effect than a full training day, and above all it doesn't require closing the salon.
From discourse to guided consultation
Saloria connects consultation and protocol, so the team sees the logic behind each look plan. It doesn't replace management software, doesn't promise realtime AR and doesn't turn look plan into certainty. It brings method into the moment when client and professional decide the look together.
Frequently asked questions
Do you need an external trainer?
Not for this part. The salon's own protocols already contain the criteria used: the job is making them readable and comparable.
How long does cross-review take?
Twenty minutes a month per pair, on three documents. If it takes longer, the checklist is too long.
How do you measure progress?
On the completeness of protocols over time: which data get recorded, whether upkeep is stated, whether alternatives are planned.