Almost every Civil Service application I have sifted was written by someone who did not know how it would be scored. For a long time, so were the ones I wrote myself. This is the scoring sheet, from the inside.
If you are applying for a Civil Service role, or for many of the public bodies and arm's length organisations that use the same framework, you will meet Success Profiles. Five elements: Behaviours, Strengths, Ability, Experience and Technical. The one that decides most sifts and most interviews is Behaviours, and it is the one candidates most consistently misunderstand, because they write for a reader and the panel reads for a rubric.
I have sat on both sides of it: as the candidate writing 250 words at eleven at night, and as a panel member and chair scoring dozens of statements and then hours of interviews against the same criteria. What follows is the panel's side, explained plainly, and what it changes about how you should prepare.
I have written this statement myself, and I recognise every step of what follows. You have the job advert open. It lists four behaviours, say Making Effective Decisions, Communicating and Influencing, Working Together and Delivering at Pace. You have 250 words for each. You pick the biggest, most impressive project you have worked on and you try to make it cover everything, because surely the panel wants to see the scale of what you have done.
You write "we" a lot, because it was a team effort and claiming it all felt dishonest. You spend eighty words on the background so the panel understands why it mattered. You run out of space just as you get to the good bit, trim the ending, and submit. It reads well. A friend says it sounds impressive.
Weeks later, the outcome: not shortlisted, or a score of three on a behaviour you thought was your strongest. No detailed feedback. You have no idea what went wrong, so next time you do the same thing with a different project.
Here is what is happening with your statement. It has arrived in a batch, sometimes of forty or more. At least two panel members are reading it independently, and each has in front of them the same thing you could have looked up: the published Civil Service Behaviours framework, with a written description of what each behaviour looks like at the grade you applied for. Not in general. At that grade.
Each behaviour is scored on a seven-point scale. One is "not demonstrated". Four is "acceptable demonstration", which is normally the pass mark. Seven is "outstanding". The panel is not asking "is this person impressive?" They are asking "how much of the level descriptor for this behaviour can I find evidence for in these 250 words?" and then choosing a number.
Everything turns on that word, evidence. A scorer cannot give marks for what you implied, what your team did, or what would have been obvious if they knew the context. They can only score what you personally did, described specifically enough to be matched against the descriptor. Eighty words of background is eighty words that score nothing. "We delivered" tells me the team delivered. I still don't know what you did.
Then the two scorers compare. If they are more than a point apart they talk it through, and the question in that conversation is always the same: "Where in the statement is the evidence for a five?" If neither scorer can point to the line, the higher score comes down.
Where the marks go missing
I have done this many times, and the same handful of problems accounts for most of the gap between a three and a five.
The example is about the project, not about you. The most common one. Scale does not score. A modest example where every sentence describes your own decisions, actions and judgement will beat a national programme described from the outside.
The example demonstrates a different behaviour. Candidates reuse one strong story across four behaviours. But a story about delivering under pressure does not automatically show Communicating and Influencing, however good it is. The panel reads it against the descriptor for the behaviour it was submitted under, finds two lines that fit, and scores accordingly. Pick the example for the behaviour, not the other way round.
The wrong level. The framework is written by grade band. An example that shows Leadership at a supervisory level, when the role is at a level where the descriptor talks about setting direction across teams, will be read as evidence for a lower grade. Read the descriptor for the grade you are applying for and check your example against it, line by line.
No result, or a vague one. Every descriptor is about effect. "The stakeholders were happy" is not a result the panel can score. "The decision was taken two weeks earlier than planned and the backlog was cleared before the deadline" is.
The structure is missing. Most panel members read with Situation, Task, Action, Result (STAR) in their heads, whether or not anyone told them to. If the action is buried in the middle of a paragraph, it is easy to miss on a fast read, and sifts are fast reads.
The same rubric, at interview
If you are shortlisted, the interview runs on exactly the same basis, with one important difference: the panel can now probe. Each behaviour question will be followed by one or more follow-ups, and the follow-ups are where the scoring happens. "What did you personally do?" "What was the alternative?" "What would you do differently?" are not the panel being difficult. They are the panel trying to find the evidence for a higher score, because a bare STAR answer rarely gets past a four on its own.
From the panel's chair, the strongest interview candidates pick an example that fits the behaviour and its level rather than the biggest thing they have done, keep the situation to two or three sentences, and spend the time on their own actions and reasoning. When the follow-ups come, they answer them fully rather than defensively.
Strengths questions are different and worth a separate piece. The short version is that they are scored on the day for how naturally and energetically you respond, and the panel is specifically trained to notice a rehearsed answer. Prepare your behaviours thoroughly. Do not script your strengths.
How to write for the scoring sheet
Start from the descriptor, not from your CV. Print the behaviour description for your grade. Underline the phrases. Then choose an example that lets you hit as many of them as possible with things you personally did. If you can only hit two, choose a different example.
Use "I" and make it specific. "I proposed", "I decided", "I redrafted", "I challenged". Where the team did something, say what your part was. That isn't arrogance. It's the only way a scorer can give you the marks.
Ration the situation. Two sentences, three at most. If the panel needs more context than that to understand the example, the example is too complicated for 250 words.
End on a measurable result and, if you have the space, a line of reflection. The higher scores in most descriptors involve learning, adjusting or improving. "Afterwards I changed how we ran the weekly review so the same issue could not recur" is one sentence that often lifts a four to a five.
Read it back as a scorer. Go through your statement with the descriptor beside it and mark every phrase you can truthfully tick. If you are ticking on the basis of what you meant rather than what you wrote, rewrite the sentence.
A Success Profiles behaviour example is scored one to seven against a published descriptor for your grade, by at least two people, who can only count what you personally did. Write for the descriptor, ration the background, use "I", finish on a result, and choose each example for the behaviour rather than for its size.
None of this is secret. The framework is published and so is the scoring scale. What is missing for most candidates is having sat on the other side and watched the number being chosen. Once you have, you never write a behaviour statement the same way again.