Using People Data in 3CO02, Explained

You have opened your 3CO02 brief and found a task built around data: perhaps a small table of absence figures, or an instruction to show how people data could inform a decision. If your first instinct is that you are not a numbers person, this guide is for you. Making sense of people data at Level 3 needs nothing beyond everyday arithmetic, and the marks come from thinking, not calculating.

This is the deep-dive companion to the 3CO02 complete guide on this site. It covers what people data actually is, simple ways to make sense of it, how to present it clearly, and the pattern that links a number to a decision, which is the skill the whole unit is really about. In plain terms, this is 3CO02 people analytics without the jargon.

In this guide you'll learn

• What people data is and where organisations get it
• Five simple ways to make sense of a set of numbers
• How to choose between a table, bar chart, line chart and pie chart
• The data-to-decision pattern that turns figures into answers
• A worked example comparing a weak answer with a strong one

What people data is and where it comes from

People data is simply information about people at work. The main types you will meet in 3CO02 are absence data, such as days off and how often they happen; turnover data, meaning how many people leave over a period; recruitment data, such as numbers of applicants and time taken to fill roles; survey data, capturing how people feel about their jobs; and performance data from appraisals and reviews.

Organisations gather this information as a natural by-product of employing people. HR and payroll systems record absence and leavers, application systems log recruitment activity, surveys run once or twice a year, and managers record performance conversations. Nothing exotic is happening: the everyday admin of employment creates the data. For your assignment, you can use figures supplied in your brief or invent a small, clearly fictional set for an example organisation.

Simple ways to make sense of numbers

Counts are the starting point: how many people left, how many days were lost, how many applied. Counts are easy but can mislead on their own, because ten leavers means something very different in a team of twelve than in a company of a thousand.

Percentages fix that by putting a count in proportion. If 5 people leave from a team of 50, that is 10 out of every 100, or 10 percent. Percentages let you compare fairly between teams of different sizes, which is why turnover is almost always quoted this way.

Averages give you a typical figure for a group. If five colleagues took 2, 3, 5, 5 and 10 days of absence, the total is 25 days, and dividing by five people gives an average of 5 days each. Notice that one person's 10 days pulls the average up, which is worth a sentence of caution in any answer.

Comparisons over time show direction. An absence average of 6 days means little by itself, but if it was 4 days last year and 5 the year before, something is drifting upwards and deserves attention.

Comparisons between teams show where to look. If three teams average 4, 5 and 9 days of absence, the interesting question is why the third team is different. Most useful analysis at this level is exactly this: put numbers side by side and ask why they differ.

Presenting data clearly

Choose the display that fits the job. A table suits a small set of exact figures the reader may want to check. A bar chart is best for comparing groups, such as absence by team. A line chart is best for change over time, such as turnover across three years. A pie chart shows shares of a whole, such as the reasons people gave for leaving, and works only when the slices are few.

Whatever you choose, label it properly: a clear title, named axes or columns, and units so the reader knows whether they are looking at days, people or percentages. Then keep it simple. One chart making one point beats a crowded graphic making three, and decoration adds nothing a marker can credit.

Finally, never let a chart stand alone. Every table or chart in your assignment should have at least a sentence underneath saying what it shows, because the display is only evidence for the point you are making.

Interpretation: where the marks live

Interpretation means answering two questions in plain English: what does this number suggest, and what should the organisation do about it? A figure on its own is inert. The sentence that says evening-team absence is nearly double the daytime figure, which suggests the shift pattern or its supervision needs a closer look, is where an answer starts earning.

Good interpretation at Level 3 is cautious. Data suggests; it rarely proves. Saying the figures might indicate a problem with the night shift, and recommending that the organisation investigates before acting, shows more understanding than a confident leap to a single cause.

Linking data to a decision

The pattern to memorise has three steps. First, what the data shows: one or two plain sentences of description. Second, what it might mean: a sensible interpretation, ideally with more than one possible explanation. Third, what to do next: a realistic recommendation for the organisation, with a way of checking later whether it worked.

Run every data task through this pattern and your answers will automatically do the thing the unit rewards, which is connecting information to a real people-practice decision rather than leaving numbers stranded on the page.

Handling data responsibly

3CO02 also expects a practical grasp of using data responsibly, described in everyday terms. Keep personal information safe and share it only with those who need it. Use data only for proper work purposes, meaning the purpose it was collected for. Protect privacy when presenting: report team-level figures rather than naming individuals, and anonymise any real examples. And be honest, presenting figures fairly rather than choosing only the ones that flatter your argument.

A simple method for a data task

1. Read the task and identify the decision it is really about, such as reducing absence or improving retention.
2. Gather your figures, either from the brief or by inventing a small, clearly fictional set for your example organisation.
3. Do the simple arithmetic: totals, percentages or averages, with a calculator or spreadsheet doing the work.
4. Choose one clear display, a table or a chart that fits the point, and label it fully.
5. Write your interpretation using the three-step pattern: what it shows, what it might mean, what to do next.
6. Add a sentence on handling the data responsibly if the task touches on it, and check the answer against the criteria in your brief.

A worked example: weak versus strong

Ashfield Homeware is an invented retail chain, and the figures below are fictional, used purely to illustrate the method. A learner is asked to show how survey data could inform a decision. The staff survey scored overall satisfaction at 7 out of 10, but the question about workload scored 4 out of 10 in the two city-centre stores and 7 everywhere else.

A weak answer restates: the survey shows satisfaction is 7 out of 10, and workload scored 4 in city-centre stores and 7 in other stores. Every sentence is accurate, but it interprets nothing and recommends nothing, so it leaves most of the available marks on the table.

A strong answer follows the pattern. The data shows overall satisfaction is reasonable but workload scores are much lower in the two city-centre stores. This might mean those stores are understaffed at busy times, or that rotas there are less predictable, and because only two sites are affected the cause is likely to be local rather than company-wide. Ashfield could investigate by talking to the store managers and comparing staffing levels against footfall, trial extra cover at peak hours, and re-run the workload question in three months to see whether scores improve.

Same data, completely different value. The strong version describes, interprets, recommends and builds in a follow-up check, which is the whole of this unit in four sentences.

Common pitfalls

The traps to avoid: restating numbers without interpreting them; using a pie chart for comparisons it cannot show; leaving charts unlabelled; quoting averages without noticing an unusual figure distorting them; over-claiming certainty from small numbers; and forgetting the responsible-handling point entirely. Each has appeared in this guide's advice, so a final read-through against this list is a quick way to check your draft.

Go deeper

When you have the method down, 3CO02 Assignment: The Complete Guide puts it in the context of the whole unit, including how it is assessed and a full worked scenario, and 3CO02 FAQs: Your Questions Answered deals quickly with the questions learners ask most, from maths anxiety to word counts. As always, check your own current brief and your centre's guidance, since formats and word counts vary.

If you would like calm, ethical help with the data side of this unit, our 3CO02 support includes coaching on interpreting and presenting figures, structure guidance, referencing help and honest feedback on your drafts. Coaching and review only: the work you submit is always your own.