What writing my PER taught me about how far I’d actually come

The key ideas, at a glance.
- My mistake: Putting off my Practical Experience Requirements (PER) application because it felt like more admin after the exams.
- What helped: Writing about my own contribution clearly, using situation, task, action and result to organise each example.
- What I learned: Looking properly at my work helped me recognise skills I had been too busy using to appreciate.
I thought I was just filling in a form
After so much studying, the idea of sitting down to write about work wasn’t especially exciting. I wanted to feel finished. Instead, there was another task waiting for me.
For a while, I treated PER as something standing between me and the end of the journey. That made it very easy to postpone.
What I hadn’t expected was how useful the process of remembering would be. It gave me a chance to notice progress that had happened gradually, beneath the much more obvious milestones of exam results.
“we” was hiding my contribution
At work, I was used to describing things as a team effort. We improved a report. We investigated a problem. We helped a manager make a decision.
That was often fair, but it didn’t explain which part I had done.
I needed to be more specific. Had I checked the data, spotted the problem, chosen an approach or explained the findings? What judgement had I used? What happened because of the work?
Writing “I” felt uncomfortable at first. I didn’t want to claim everyone else’s achievement. Gradually, I realised I could acknowledge the team and still describe my own contribution honestly. Neither false modesty nor inflated claims would help someone understand my experience.
Giving each example a clear shape
The situation, task, action and result structure, usually called STAR, helped me stop wandering around the story.
I needed enough background for a reader to understand the problem, then a clear explanation of what I was responsible for. The action section was where I could explain what I actually did and why. The result showed what followed, including anything I learned.
I found it more useful to ask whether that sequence was clear than to force every example into identical sentence lengths. I also needed to check CIMA’s current guidance and requirements rather than rely on somebody else’s shortcut to approval.
As the examples came together, I began seeing work I had previously dismissed as “just part of my job”. Handling a difficult question, improving information and explaining an issue were all things I had learned to do.
I kept the finished examples as a reminder and as useful preparation for interviews. They helped me talk about experience with evidence instead of vague claims about being hardworking.
CIMA requires at least three years of verified relevant practical experience. I would use its current PER guidance to check eligibility, the evidence needed and the submission process, rather than wait until the final exam to begin recording work.
Give your experience the attention you gave your exams. Writing it down can help you see how much you've developed, as well as what you still want to learn.
Exam information checked 9 November 2026. Use the current CIMA exam blueprints, exam timetable and Pearson VUE guidance for your sitting. Images are editorial illustrations. This is an independent student website, not affiliated with CIMA.



