How SALO-F™ works

 

SALO-F™ is designed to be practical, achievable, and manageable for schools.

 

It is not a long-term programme with frequent visits, large staff cohorts, or heavy demands on release time. Instead, SALO-F™ provides a clear framework that senior leaders use to strengthen leadership, professional practice, and improvement through the work they already do.

 

A deliberately light-touch model

​

The framework is built around a small number of structured contact points, with the real impact coming from how leaders apply the framework within existing school routines.

 

The model is intentionally designed to minimise overload and reduce pressure on staff and timetables.

​

Who leads the framework

​

The framework is led by the senior leadership team.

 

Typically involved:

 

• Headteacher

• Senior leaders

• A small number of key middle leaders where appropriate

​

There is no expectation to:

 

• create large core teams

• repeatedly release teachers or support staff from class

• run whole-staff training sessions

• add additional meetings or initiatives

​

Staff experience the framework through the benefits of clearer leadership, consistency, and improved ways of working — not through extra training days.

​​

The framework phases: Build and Embed

​

SALO-F is applied through two connected phases: Build and Embed.

 

Each phase has a clear purpose and outcome. Together, they provide a structured yet flexible way for schools to translate the framework into everyday practice without overloading staff or creating dependency.
 

The Build phase: establishing the foundation

​

The Build phase establishes the shared foundation on which the SALO-F rests.

 

This phase focuses on leadership clarity, professional expectations, and coherence across the school. It brings together existing thinking, priorities, and practice into a single, shared framework that leaders can use consistently.

 

The Build phase typically involves:
 

• A structured leadership day with the senior leadership team

• Clarifying purpose, values, and professional expectations

• Establishing the school’s Core Framework as a shared reference point for leadership and improvement

​

The outcome of the Build phase is not a set of initiatives, but clarity:
 

• clearer leadership messages

• greater alignment across priorities

• a common language for professional practice

• a stable foundation for improvement

​

Existing work is brought into alignment rather than replaced.

 

Indicative timing:
 

Most schools find that the Build phase spans two terms, allowing time to establish shared clarity, engage leaders meaningfully, and align existing priorities without rushing.

 

The Embed phase: translating clarity into practice

 

The Embed phase focuses on embedding the framework into everyday leadership and professional practice.

 

This is where the framework moves from shared understanding to sustained application. Drawing on experience from over 130 schools, leaders introduce and embed a small number of proven routines and tools that translate theory into practice in ways that fit their context.

 

The Embed phase typically involves:

 

• A structured leadership day later in the cycle

• Reviewing how the Core Framework is showing up in leadership behaviour, professional relationships, and daily practice

• Selecting and embedding a limited set of practical routines that strengthen leadership, culture, and improvement

​

The aim is not to add activity or bureaucracy. It is to introduce only what is needed, embed it properly, see impact, and ensure it is used consistently.

 

Through the Embed phase, the framework supports schools to strengthen:
 

• professional dialogue and collaboration

• professional learning and development

• staff wellbeing through clearer expectations and reduced overload

• engagement and shared responsibility for improvement

• the consistency and impact of improvement activity

• review and self-evaluation, with clearer evidence of intent, implementation, and impact

​

Embedding happens through everyday leadership practice, not through additional programmes.

 

Indicative timing:
 

The Embed phase is paced by the school and typically unfolds across three or more terms, as routines are introduced, refined, and embedded into everyday leadership and professional practice.
 

How schools work between Build and Embed

​

Between the Build and Embed phases, schools are not expected to deliver the framework as a formal training programme for staff.

 

Instead:
 

• leaders use the framework as a lens for existing leadership decisions and improvement work

• one or two priorities are focused on at a time

• changes are tested, stabilised, and refined before moving on

​

This approach keeps demand realistic, supports staff wellbeing, and allows impact to accumulate over time.

What SALO-F does not require

 

To be explicit, the framework does not require schools to:

 

• commit to multi-year delivery

• host frequent external visits

• release large groups of staff from classrooms

• complete every element of the framework

 

Schools choose how deeply and how quickly they work with the framework, within clear guardrails.
 

How SALO-F supports inspection and improvement

 

The framework helps schools organise and explain their improvement work more clearly.

 

By strengthening coherence across leadership, culture, and professional practice, the framework supports schools to:

 

• evidence intent, implementation, and impact

• demonstrate consistency and sustainability

• articulate improvement priorities with confidence

​

This supports inspection readiness and reduces additional workload.

​

Why schools choose SALO-F

​

Schools use SALO-F because it:

 

• respects capacity and context

• reduces fragmentation rather than adding initiatives

• strengthens distributed leadership

• supports improvement that is realistic and sustainable

 

The framework is designed to help schools work better, not work more.

 

In summary

​

The framework provides:

 

• a clear, practical framework

• a pragmatic way of working with it

• limited, realistic, and purposeful contact

• leadership-led application

• flexibility within the structure

 

It is intentionally designed to be achievable, scalable, and manageable for all.

​

​Schools engage with the framework at different levels, depending on their context, capacity, and priorities. This includes Build only, or Build and Embed together, with varying levels of support.​