A practical study guide to inclusive programme design, identifying barriers and checking after implementation whether an initiative is reaching the people it is intended to reach.
AC 2.2 focuses on the practical work involved in making a people initiative genuinely inclusive. In the Plyton scenario, the initiative is a new employee benefits programme that may later be rolled out across the organisation.
The criterion has two equally important parts: strategies used during design to make the programme fair and inclusive, and strategies used after implementation to check whether it is actually as inclusive as intended. The official brief specifically says you do not need to design the benefits programme itself.
An initiative can be intended for everyone yet still create barriers for particular employees. Eligibility rules, communication channels, working patterns, accessibility or the way employees enrol can all influence who can realistically participate.
Inclusive practice therefore involves anticipating barriers before launch and examining evidence after launch. Intention is not enough; the organisation needs to understand employees’ actual experience of the programme.
Before designing an inclusive initiative, the People Team needs a clear understanding of the workforce groups it is intended to serve. The assessment guidance suggests considering groups such as shift workers, part-time employees, disabled employees and different demographic groups.
The purpose is not to assume that a particular group will experience disadvantage. It is to ask systematically whether aspects of the programme could create different levels of access or participation.
Consultation can reveal needs and barriers that designers may not anticipate. For Plyton, consultation should involve a sufficiently varied group rather than only employees who are easiest to reach.
Possible approaches could include focus groups, short surveys, individual conversations or existing employee forums. The important issue is representation: feedback from office-based employees alone, for example, may not reveal difficulties experienced by people working different shifts.
Consultation is more useful when employees understand what input is being sought and can see how their feedback influences design decisions. Asking broad questions such as “Do you like the programme?” may produce little actionable insight.
More focused questions can explore accessibility, communication preferences, eligibility, likely barriers and whether different employees understand how they would use the programme.
Accessibility should be considered before implementation rather than added after employees encounter problems. This includes how information is presented, how employees access the programme and whether the process relies on a single channel or format.
For example, if information or enrolment is available only through a digital system, the team should consider whether all intended employees can access and use it effectively. Accessibility also includes communication clarity and the needs of employees who may require reasonable adjustments.
The People Team should examine whether proposed eligibility rules unintentionally disadvantage groups of employees. Criteria linked to working hours, service length, contract type, location or working pattern may have different effects across the workforce.
This does not mean every benefit must be identical for every employee. The important question is whether differences have a legitimate rationale and whether unnecessary barriers can be removed.
A benefit cannot be inclusive in practice if eligible employees do not know about it or cannot understand how to access it. Communication planning should therefore consider language, clarity, timing, format and channel.
At a manufacturing organisation such as Plyton, relying on a single office-based communication method could miss employees whose working arrangements differ. Multiple appropriate channels and opportunities to ask questions can improve reach.
Inclusive design benefits from challenge. People involved in designing the programme can become familiar with their own assumptions and overlook barriers that are obvious to others.
Bringing together relevant people-practice, operational and employee perspectives can help test proposed arrangements. The aim is not to make the design process unnecessarily large, but to ensure that important perspectives are not absent.
The assessment guidance identifies equality impact assessment as a relevant approach. In practical terms, this means reviewing the proposed initiative to consider whether it may affect groups differently and whether potential disadvantages can be prevented or reduced.
The review is most useful when it influences decisions before implementation. Treating it as a formality after the design has already been fixed limits its value.
An inclusive benefits programme does not necessarily give every employee exactly the same experience. Employees can have different needs, working patterns and barriers.
Fairness is better considered in terms of justifiable access and treatment. Where differences exist, the People Team should understand why they exist and whether they create avoidable exclusion.
Launching the programme does not prove that the design was inclusive. The second half of AC 2.2 requires learners to explain how Plyton will check inclusion after implementation.
This means gathering evidence about who is participating, who is not, what employees experience when trying to use the programme and whether the original design assumptions were accurate.
Participation data can show whether the programme is reaching the workforce. Overall take-up provides a starting point, but a single organisation-wide percentage can conceal important differences.
Where appropriate and lawful, Plyton can examine patterns across relevant workforce groups. If one group has noticeably lower participation, this does not automatically prove discrimination or exclusion, but it provides a reason to investigate further.
Quantitative take-up data shows what is happening but may not explain why. Employee feedback can help identify reasons for low participation or dissatisfaction.
Short surveys, focus groups, employee forums or targeted conversations can explore whether people understood the programme, encountered access problems, considered the benefits relevant or experienced barriers that were not identified during design.
The team should return to the objectives and assumptions established during design. If a communication approach was intended to reach shift workers, for example, post-implementation evidence should help determine whether it actually did.
This creates a useful feedback loop: design assumption → implementation → evidence → adjustment. Inclusion becomes an ongoing management process rather than a one-time statement of intent.
If data shows different participation rates between groups, the People Team should avoid jumping directly to a cause. Lower take-up might reflect communication, eligibility, accessibility, perceived relevance or other factors.
Combining participation data with employee feedback provides a stronger basis for deciding whether the programme needs to change.
Monitoring only creates value if findings can lead to action. Where evidence identifies an avoidable barrier, the team should consider appropriate changes and then continue monitoring whether those changes improve access.
This may involve revising communication, changing a process, improving accessibility or reconsidering a design feature. The appropriate response depends on the evidence rather than being predetermined.
Monitoring inclusion may involve employee information. Data should therefore be handled appropriately, with attention to confidentiality and the risk of drawing conclusions from very small groups.
The purpose of analysing participation is to identify patterns that may require further investigation, not to stereotype employees or assume that every member of a demographic group has the same needs.
Plyton is piloting a new employee benefits programme with the possibility of wider rollout. This makes both stages particularly important. Inclusive design can reduce foreseeable barriers before launch, while post-implementation evidence can identify issues before the programme is extended more widely.
The People Team should therefore be able to explain to the Board not only what it plans to do, but how it will know whether the programme has achieved the intended reach.
The official task asks for draft notes for a Board meeting, not a full essay. A practical structure is to separate the response into two clear areas: strategies for fair and inclusive design and strategies for checking inclusion after implementation.
Within each area, explain the strategy and its purpose. Avoid merely writing labels such as “consult employees” or “monitor data”; the assessment guidance expects explanation of how, who and why.
This study guide explains practical approaches for designing and evaluating an inclusive initiative. For AC 2.2, you are not required to invent the contents of Plyton’s employee benefits programme. Focus instead on the strategies you would use to make its design inclusive and the evidence you would use after implementation to determine whether it has reached the employees it was intended to reach.
Continue through the individual 5CO03 assessment criterion study guides.
Specialist support for CIPD Level 3, Level 5 and Level 7 learners, with guidance from HR professionals.
