Skip to content

How to write CIMA PER experience descriptions, with STAR examples

How to write each CIMA PER example in the STAR format, with worked examples for a fictional management accountant and the gaps that get examples sent back.

All levelsTechnique

Most of the CIMA practical experience requirement (PER) is writing. You describe your roles, then write a short case for each professional achievement you claim: three of the five core activities and all five skills and behaviours. That is eight examples, each checked by a supervisor and then by CIMA's assessors.

This article explains how CIMA asks you to write them, then works through two examples for a fictional management accountant. The examples are illustrations in our own words. Use them for the shape, not the content: your examples must be your own work.

For the rules in full, see our guide to the CIMA PER and CIMA's own guidance for applicants, linked from CIMA's PER page.

The STAR format

CIMA gives you a template for each example, built on STAR:

  • Situation. The context: the organisation, the problem and why it mattered.
  • Task. Your own role and responsibility in that situation.
  • Action. What you did, and how it shows the activity or skill you are claiming.
  • Result. What changed because of your work, and what it was worth to the organisation.

CIMA asks for 500 to 750 words per template. Your role and organisation descriptions are shorter, 150 to 200 words each. CIMA suggests full sentences rather than bullet points, and using the word count you have.

Write for a stranger

Your supervisor knows your work. The assessor doesn't. CIMA tells supervisors to judge only what is written, not what they remember, and assessors have nothing else to go on.

So name the business problem plainly. Explain any system or team name the first time you use it. Give figures where you can: how many sites, how big the budget, how long the delay. A reader who has never visited your office should be able to follow every step.

Choose the example before you write it

A weak example cannot be saved by good writing. Before you start, check three things:

  1. Is it big enough? CIMA's first reason for "not achieved" is a situation too small to show a professional achievement. A routine monthly journal is too small. Redesigning the month-end process is not.
  2. Does it fit the heading? An example filed under "measuring performance" must be about measuring performance. CIMA notes that a performance example must be about the organisation's performance, not staff appraisal.
  3. Did you do it? Pick work where you can say what you personally did. If the honest answer is "the team did it and I helped", choose another example.

CIMA's guidance lists self-reflection questions and sample activities for each achievement. Read them before you choose. They show the scale of example CIMA has in mind.

Worked example 1: a core activity

Core activity C: managing performance and costs to aid value creation. The writer is a fictional management accountant at a fictional company that makes garden furniture. This is shortened. A real template would add detail to reach 500 words.

Situation. The company makes wooden garden furniture in one factory and sells through garden centres. Timber prices rose sharply over one year. The production director wanted to know which products were still profitable, but the standard costs were two years old and the monthly report showed one margin for the whole range.

Task. As the factory's management accountant, I was asked by the finance manager to update product costs and give the production director a margin for each product line, so he could decide where to act.

Action. I started with the bills of materials for the twelve best-selling lines and checked them with the production planner, who found two that no longer matched how the products were built. I updated timber and hardware costs from the latest supplier invoices. For labour, I used three months of timesheets rather than the old standard times. I then compared each line's new cost with its price and its sales volume. Three lines had fallen below a 10% margin. I wrote a two-page note for the production director with the figures, the assumptions behind them and three options for each weak line: a price rise, a design change to use less timber, or dropping the line. I presented it to him and the sales manager together, so both views were in the room.

Result. The production director chose a price rise on one line and a design change on another, and kept the third for one more season while sales tested a higher price. Standard costs are now updated every six months, using the method I set up. The finance manager asked me to repeat the analysis for the rest of the range.

Why it works

  • The situation is significant: a cost shock across the range.
  • The task is the writer's own, and it is clear who asked.
  • Every action starts with "I", and the steps show judgement: checking the bills of materials, choosing better labour data, setting out options.
  • The result says what the business decided and what changed afterwards.

Worked example 2: a skill or behaviour

Skill iv: professional scepticism. Same fictional writer, a few months later. Again shortened.

Situation. The sales team's forecast for the next year showed a 25% rise in sales to garden centres. The forecast fed the production plan and a request to hire six more factory staff.

Task. I was responsible for building the budget from the sales forecast, and for checking that the inputs were reasonable before it went to the board.

Action. The rise looked high against the last three years, which had grown by less than 5% a year. I asked the sales manager for the detail behind it. Most of the rise came from one new customer, a chain of garden centres, which had been in talks but had not signed. I checked past forecasts and found that unsigned customers had been included twice before, and neither had come through. I raised this with the sales manager first, then with the finance manager. I proposed a base budget without the new customer and a separate scenario with it, with the extra hiring linked to the contract being signed.

Result. The board approved the base budget and the scenario. The hiring was held until the contract was signed. The customer signed four months later at a lower volume than forecast, and the factory took on three staff rather than six.

Why it works

The example shows each part of scepticism CIMA describes: questioning the data, looking for the cause of an inconsistency, and using judgement on what to do about it. It also shows tact: the writer went to the sales manager before going over his head.

Common gaps, and how to fix them

CIMA's criteria for "not achieved" are the best checklist you have. These are the gaps we would look for first:

  • "We" instead of "I". CIMA marks down team actions described in place of your own. Rewrite each action as something you did.
  • A result that is just "the report was delivered". Say what the business did with it, and what changed.
  • A task that is missing. Many drafts jump from the situation to the actions. Add one or two sentences on your role.
  • The wrong heading. A growth mindset example must be about your own development, not the organisation's. CIMA says so in its guidance.
  • Too short. A 250-word template rarely gives enough detail. Use the 500 to 750 words.

Before you send it to your supervisor

Read each template against CIMA's "achieved" criteria line by line. Then ask your supervisor to read a draft before you send it for sign-off. Supervisors can give feedback and send a section back for redrafting, so an early read saves a round trip.

Two more things matter. Ask each supervisor before you enter their details. And write your own words: CIMA checks applications for originality, and colleagues who worked on the same project must each write their own account.

For a full list of checks, see our PER checklist before you submit. For how the PER fits with your exams, see the CIMA PER and the case studies.

More insights