3CO02 Assignment Example - Principles of Analytics | CIPD Level 3

What is the CIPD 3CO02 Unit?

3CO02 Principles of Analytics establishes the data literacy foundations that every people professional needs. The unit is not about statistical analysis or complex modelling - at Level 3, analytics means being able to identify the right type of data for a people practice question, interpret what that data tells you, present your findings clearly, and use them to support a specific recommendation.

It is one of four mandatory core units in the CIPD Level 3 Foundation Certificate and connects directly to 5CO02 Evidence-Based Practice at Level 5. The assessment is a written portfolio; a pass requires all ACs to be addressed with applied examples. There is no merit or distinction grade at Level 3. Assessors are looking for evidence that you understand the difference between types of data and can explain how data informs a real people practice decision - not just that you can define "quantitative" correctly.

AC 1.1 - Types of Data Used in People Practice

People professionals work with two broad types of data - quantitative and qualitative - collected from two broad sources - primary and secondary. Understanding these distinctions is the foundation of good people analytics at any level.

Quantitative data is numerical and measurable. It can be counted, calculated, tracked over time, and compared across departments, time periods, or industry benchmarks. In people practice, quantitative data includes: headcount by department; labour turnover rate (calculated as leavers ÷ average headcount × 100); absence rate (days lost ÷ available working days × 100); time-to-hire (days from vacancy authorisation to accepted offer); cost-per-hire (total recruitment costs ÷ number of hires); engagement survey scores expressed as percentages; and the gender pay gap reporting figure. Quantitative data answers the question "how many?" or "how much?" at scale.

Qualitative data is descriptive and interpretive. It captures the meaning, context, and experience behind the numbers. In people practice, qualitative data includes: exit interview themes (what reasons do leavers give for their departure?); open-text responses in engagement surveys (what specific issues are employees describing?); focus group discussions (what is the employee experience of the new onboarding process?); and 360-degree feedback narratives (how do colleagues describe a manager's communication style?). Qualitative data answers the question "why?" - it explains the patterns that quantitative data identifies.

Primary data is collected directly and for a specific purpose. Examples: an engagement survey you design and send to employees, a focus group you run to understand a specific retention problem, or a structured exit interview with every leaver. Primary data is current and specific to your context - but it takes time and resources to collect.

Secondary data already exists and is used for a new purpose. Examples: HRIS (Human Resource Information System) records of absence and headcount, payroll data, CIPD annual labour market surveys, ONS employment statistics, and industry salary benchmarks from recruitment agencies. Secondary data is faster and cheaper to access - but it may not perfectly fit your specific question and may not be current.

AC 1.2 - How to Analyse HR Data: Methods and Approaches

Analysing HR data at Level 3 does not require statistical software. The most useful analytical methods for people professionals at this level are: trend analysis, comparison, and calculation of standard HR metrics.

Trend analysis examines how a metric changes over time. Plotting monthly absence rates over a 12-month period reveals whether absence is increasing, decreasing, seasonal, or linked to specific events (such as a management change or a period of high workload). A single data point tells you where you are; a trend tells you where you are going.

Comparison establishes context. Knowing that your organisation's labour turnover rate is 18% is not meaningful in isolation - knowing that the industry average is 12% tells you the organisation has a problem. Comparison may be against internal benchmarks (department vs department), historical baselines (this year vs last year), or external industry data (CIPD benchmarking reports, sector surveys).

Calculating standard HR metrics turns raw HR system data into insight. The most commonly used metrics at Level 3 are:

• Labour turnover rate: (Number of leavers in period ÷ Average headcount in period) × 100. Example: 15 leavers from an average headcount of 120 = 12.5% turnover rate.
• Absence rate: (Total days lost to absence ÷ Total available working days) × 100. Example: 45 days lost from 1,200 available days = 3.75% absence rate.
• Time-to-hire: Average number of days from job requisition approval to offer acceptance. A rising time-to-hire figure may indicate a recruitment process that is too slow, or a skills market that is tightening.
• Cost-per-hire: Total recruitment spend (advertising, agency fees, HR time, interviewer time) ÷ Number of hires. Useful for justifying changes to recruitment methods.

The analysis step is not complete when you have calculated the metric - it is complete when you have explained what the metric means and why it matters for a specific people practice decision.

AC 2.1 - Presenting Data and Findings to Stakeholders

Presenting HR data effectively means matching the format and language to the audience and to the nature of the data. The same analysis communicated differently will land differently - a table of precise figures serves an audience that needs to interrogate the numbers; a single headline statistic and a visual chart serves an audience that needs to make a quick decision.

Bar charts are most effective for comparing categories at a single point in time - comparing absence rates across five departments, or comparing time-to-hire across three job levels. The visual comparison is immediate.

Line graphs are most effective for showing change over time - tracking monthly turnover rates across a 12-month period, or plotting engagement scores following an intervention. Trends and inflection points are clearly visible.

Tables provide precision - use them when the audience needs the exact numbers, or when multiple variables need to be compared simultaneously. Tables are not good for communicating trends or priorities at a glance.

Narrative summaries translate data into plain language for non-HR stakeholders. The most effective structure is: here is what the data shows (the insight), here is what it means for the business (the so-what), and here is what we recommend doing about it (the action). This structure is also the foundation of an evidence-based recommendation in AC 2.2.

For senior leaders, lead with the business implication rather than the HR metric. "Our 18% turnover rate is costing approximately £180,000 per year in replacement costs" is more compelling than "our turnover rate is above industry average." The data is the same; the framing makes it actionable.

AC 2.2 - Using Data to Make Evidence-Based People Practice Recommendations

Evidence-based practice at CIPD Level 3 means making a people practice recommendation that is supported by data and reasoning - not by assumption, habit, or personal preference. The recommendation does not need to be complex; it needs to be justified.

The structure for an evidence-based recommendation follows three steps: identify the problem the data reveals, explain what is causing it (using qualitative data to interpret the quantitative signal), and recommend a specific action with a rationale.

Example application: Quantitative data shows that labour turnover in the customer service department is 28% - significantly higher than the company average of 14% and the industry benchmark of 16%. This is the signal. Exit interview data (qualitative) reveals that 70% of leavers cited poor management relationships and lack of development opportunities as their primary reasons for leaving. This is the explanation. The evidence-based recommendation is: a programme of line manager coaching and a structured development pathway for customer service advisors, with a six-month review of turnover rate to assess impact. This is justified by the data - it addresses the specific causes identified, not a generic retention problem.

What makes this recommendation evidence-based is not the sophistication of the analysis - it is the direct link between the data, the insight, and the proposed action. A recommendation that says "we should improve employee experience" without citing specific data is an opinion. A recommendation that says "we should introduce a line manager coaching programme for customer service team leaders because exit interview data shows that 70% of leavers in this department cited management relationships as a primary reason for leaving" is evidence-based.