Leadership SCS Example — 750-Word Statement

Leadership SCS 750 words Last reviewed:

At Senior Civil Service level assessors expect visible leadership of whole systems: departments, cross-government programmes or national networks, sustained over years. Show how you set a compelling direction, built coalitions at permanent secretary or chief executive level, developed the next generation of leaders, and stayed honest under public pressure, with institution-level results.

Example statement

742 / 750 words

SI was appointed senior responsible owner for a cross-government programme to modernise how departments share corporate services such as payroll, procurement and human resources. Nine departments were involved, around 4,000 staff would ultimately be affected, and the timescale was 18 months to first delivery. Two earlier attempts over the previous decade had failed expensively, permanent secretaries were openly sceptical, spending controls were tight, and several departments had quietly built their own rival solutions rather than wait for the centre. Confidence in the programme, inside and outside government, was close to zero when I arrived, and my own programme team of 60 was demoralised after a difficult first year.

TMy job was to provide the visible, confident leadership that would keep nine sovereign departments aligned behind one direction, deliver the first shared platform on time and on budget, rebuild trust in the idea that government could do this at all, and leave behind me a leadership team capable of finishing the work without me.

AI began by making the case for change in person. In my first six weeks I met every permanent secretary individually, listened to what had made them sceptical, and asked what success would have to look like for their department. I used those conversations to shape a simple, compelling narrative: one platform, designed with departments rather than imposed on them, with savings reinvested in front-line services. I repeated that narrative at every board, every briefing and every site visit for 18 months, because at this scale people only believe a direction when they hear it consistently from the same visible person. I built a coalition of departmental champions at director level, people with credibility in their own organisations, and gave them genuine influence over design decisions so the programme belonged to the network, not to me. Governance had to be real rather than decorative, so I established a programme board with named senior owners from each department and actual decision rights, meeting monthly with a short, honest dashboard: progress, money, risks, decisions needed. I published the minutes to all nine departments, which was uncomfortable at first but killed the corridor rumours that had poisoned earlier attempts. Where a department's concerns were legitimate, I adapted the design rather than overruling them; the payroll module was resequenced twice to accommodate one department's live pay dispute, which cost us time but kept them inside the programme. I invested deliberately in leadership capability within the programme, recruiting three experienced delivery leaders, personally mentoring two high-potential deputies who had never worked at this scale, and rotating promising people through the toughest workstreams so they grew. When staff in affected teams faced transfer, I insisted on early, honest communication, proper consultation and fair treatment, visiting two of the largest affected sites myself to answer questions directly. I challenged scope creep constructively, saying no to four well-argued additions that would have jeopardised the core delivery, and explaining each decision openly. When we hit problems, including a failed data-migration test three months before go-live, I told the board the same day with a recovery plan rather than letting bad news travel slowly, and I stood in front of the whole programme team to explain what had happened and what we would do differently. I made sure early wins were celebrated publicly, with credit going to departments and named teams rather than to the centre, building the confidence that kept everyone at the table. When one department's minister publicly criticised the programme, I briefed them privately with the evidence and turned a critic into a cautious supporter. I also protected time to think, keeping a monthly day with my deputies to review direction rather than firefight. Throughout, I modelled the behaviour I asked of others: honest reporting, calm under pressure, and decisions made on evidence rather than hierarchy.

RThe core platform went live on time, with all nine departments onboarded as planned. The programme identified £25 million of annual savings, transferred 1,100 staff smoothly and fairly and without a single formal grievance, and held staff engagement steady in affected teams throughout the change. Independent assurance rated delivery confidence as high for three consecutive reviews. It has since been cited across government as a model for cross-departmental delivery, the follow-on phases were funded without challenge, and 12 members of my leadership team were promoted into senior roles across government during the programme's lifetime, which matters as much to me as the platform itself, because programmes end but leaders remain.

Use this as a model, not a script. This is an original example written for this site. Adapt the structure to your own experience — copying it word for word risks plagiarism and will not reflect your evidence.

Why this scores well

  1. This is Senior Civil Service scale: nine departments, 4,000 staff affected, £25 million annual savings, and delivery under national scepticism.
  2. Exhibits system leadership: a repeated narrative over 18 months, real shared governance with published minutes, coalition-building, and transparent handling of failure.
  3. Invests in the leadership of others (mentored deputies, 12 promotions), which is what distinguishes SCS from Grade 6 in assessors' scoring.

What SCS level requires

What Leadership looks like at each level
GradeWhat assessors expect
Grade 7At Grade 7, leadership means leading across teams and functions: translating strategy into clear direction, developing other leaders, and keeping people confident and delivering through change.
Grade 6At Grade 6, leadership means setting vision for a broad area: leading senior leaders, shaping culture across boundaries, and inspiring confidence in people and partners you do not directly manage.
SCS ← this pageAt SCS, leadership means system-wide leadership: setting compelling direction for whole departments or cross-government programmes, building leadership capability for the future, and inspiring trust at the most senior levels.

Common mistakes at this level

Frequently asked questions

Next step

Get the free SCS statement template pack — the same STAR structure used in this example.

Download the template pack