B2B Web  ·  Gov / Public Sector

The Planning
Inspectorate.

The Planning Inspectorate oversees applications for major UK infrastructure projects, like wind farms and airport expansions.

As Lead UX Designer, I led the end-to-end design process to overhaul their legacy case management system, making it faster, simpler, and ready to scale.

Category
B2B Web
Sector
Government / Public Sector
Date
Jun 2022 – Jun 2023
Team
6 engineers, 5 designers (inc. myself), 1 PM + more
Role
User Research Wireframing Prototyping Product Design Strategy Responsive Web Dev Handover
Impact

What we shipped.

  • Re-designed and shipped the full case management system from discovery to delivery
  • Cut case admin time from days to minutes
  • Boosted user satisfaction by 35% (SUS)
  • Helped secure a £9M contract renewal
  • Led 100+ hours of research and testing
  • First case live in March 2024
Background

A creaking legacy system unfit for purpose.

The Planning Inspectorate's legacy system Horizon was used for managing and publishing planning application documentation. It was costly, had been in use for over 15 years and was nearing the end of its contract.

Not only that, the system wasn't built for purpose. The planning application process was incredibly slow, with applications often taking years to complete. This current system did nothing to help speed things up.

Horizon legacy case management system showing case details, work items, and document folders for a planning application.

Previous case management system on Horizon.

The goal

Rebuild the system from scratch.

Our team was hired to build a case management system from scratch to replace the existing system. The redesign was set against a strategic government ambition for the department:

  • Speed up the planning application process
  • Reduce errors and costs
  • Improve the user experience
Initial challenges

Sifting through complexity and frosty relationships.

Redesigning the system required getting up to speed fast, understanding both the complexity of planning applications and the differing needs of inspectors, case workers and other users. Beyond the workflows, previous failed transformation efforts had left stakeholders sceptical of another agency.

To cut through this, I ran exploratory research: interviews, stakeholder conversations and group sessions, unpacking processes, roles and the current system while navigating the underlying politics.

Flow diagram: NSIPS planning process from pre-application advice through decision, aligned with the case team journey (create case, receive documents, upload and redact files, edit metadata, publish to the website).
Process

A simplified view of a complex and strict planning application process alongside the case team's behind-the-scenes journey.

Core pain points

Inefficient and time‑consuming processes.

Working within a complex system and tight deadline, I focused on high-impact decisions, what to keep and what to redesign. By mapping workflows and pain points and prioritising key opportunities, the Case Admin team emerged as the most critical group to improve.

Buried actions

Actions such as editing and publishing were buried behind multiple clicks, with high interaction costs.

Lack of status visibility

Documents had to be manually checked and renamed, with lack of visibility of status before redaction.

Inability to bulk edit

Every task had to be done one file at a time, adding to the workload and timeframe for completing the work.

Scale

Multiply this by thousands of files per case, the time and interaction costs were enormous.

Hypothesis

If we enable the ability to edit and publish documents in bulk it will make it quicker to upload and publish files and speed up the planning application process.

Optimising flows

Mapping out the file publishing flow to reduce steps.

Previously, every file had to be edited and published one by one. In the redesign, I streamlined the flow with bulk editing and publishing, cutting the steps down dramatically.

Repeat steps per document · ×1000s of files

Tasks complete · Done once for 1000s of documents

1.0 Document received
  1. 1.1 Document redacted and re-uploaded

Can’t mark as redacted

2.0 Edit document
  1. 2.1 Select document
  2. 2.2 Right-click → Properties
  3. 2.3 Categories
  4. 2.4 Edit Properties
  5. 2.5 Edit details → Save

No way to set status to checked

3.0 Set to publish
  1. 3.1 Select document
  2. 3.2 Right-click → Properties
  3. 3.3 Publishing options
  4. 3.4 Status → Publish

Can’t track status across many docs

4.0 Publish
  1. 4.1 Publish documents
  2. 4.2 Whole queue goes live

Can’t pick which docs publish

Can’t track many docs at once

Legacy Horizon flow versus bulk-first steps in the redesign. Toggle Show changes to compare.

Leveraging and adapting the GDS system

Applying standards while meeting user needs.

Because this was a GOV.UK service, I had to use the Government Design System to guarantee accessibility, inclusivity and consistency, and to cut down training needs. But case management is very different from the step-by-step form journeys the system is designed for. Since this wasn't public-facing, I had more flexibility. The challenge was knowing when to stick with GOV.UK patterns and when to adapt or extend them to better fit complex workflows.

Where components needed to deviate from the system, I evidenced this with robust research findings.

GOV.UK Design System overview: applying GDS components and patterns to the case management service.

GOV.UK Design System, extended where research demanded it.

Design, test and iterate

Sometimes showing more is better, early minimalism gave way to clarity.

Through four rounds of usability testing with case admin teams, I refined the document storage and publishing journey. Early minimalist designs evolved from feedback, with a stronger focus on easy access to core actions.

Before testing Document storage before usability testing: Reports folder table with colourful status badges, icon-only download column, and bulk actions behind a dropdown.
DESIGNS BEFORE TESTING
  • Download/view CTAs unclear to users
  • Colour coding too distracting for common tasks
  • Bulk actions buried in a dropdown
After testing Document storage after usability testing: Documents view with neutral status text, visible bulk action panels, and labelled View/edit properties and Download links.
DESIGNS AFTER TESTING
  • Neutral statuses - reducing visual noise while maintaining clarity.
  • Bulk actions visible - improving task speed and reducing confusion.
  • Clearer download/view CTAs with text labels
Publishing queue

Giving case admin teams more control, and reducing errors with the publishing queue.

One of the core issues was the time taken to publish files and errors made along the way. I added new functionality to the publishing queue, collaborating with the front-office team so internal tooling lined up with what went live on the public site.

Benefits
  • Easy bulk management, speeding up processes and saving case team hours
  • Edit files before publishing, reducing errors
  • Full control over release order, reducing rework

Publishing queue interface: hover or tap a marker for design notes.

Publishing queue table with bulk Publish documents actions, document rows with metadata, View/edit details and Remove links, and pagination.

Callouts match usability annotations from testing, with the same UI as the built queue without burned-in labels.

User testing feedback
“That’s straightforward, and much easier than what we’re doing now.”
Case Admin worker The Planning Inspectorate
End results

Delivering a fully redesigned system that speeds up the planning application process.

From this journey alone we were able to deliver on some of the key objectives set from the outset:

  • Reduced upload/publishing time from days to minutes
  • Improved SUS score by 35%
  • Designed a system aligned with GDS, with bespoke components where needed
  • Met business goals of accessibility and scalability

I was also able to win over sceptical users and stakeholders who had been hesitant at the start of the journey.

User testing feedback
“We are so looking forward to everything being rolled out, you and the team are the first group of consultants who listen and deliver what we actually want, plus other good things thrown in as well.”
Case Admin user The Planning Inspectorate
Scaling the team

From a tiny team to a big team.

After a year growing the project from a small discovery team into a scaled operation, we delivered a fully redesigned system, from creating a case to publishing cases and documents on the Planning Inspectorate website, helping the agency secure a larger project during discovery.

The new system launched with its first live case in March 2024, fully integrated with the new public-facing Planning Inspectorate website.

The Planning Inspectorate project team photographed together in the studio, including remote teammates on screen, representing the scaled, multi-discipline crew shipping the live service.

From a small discovery crew to a multi-discipline team shipping the live service.

Project leadership
“Zena has been driving the design and user interaction on the service… From a chaotic starting point, she’s gone above and beyond, engaging stakeholders, aligning the team and delivering with clarity.”
Project Manager The Planning Inspectorate
Reflections

One small piece of a bigger body of work.

The file publishing process was just one small part of the system overhaul, which involved shipping 10+ epics, scaling and leading a design team and integrating with the public-facing website.

One learning that stood out was the importance of building strong relationships with stakeholders and users: the earlier you can build trust, the more willing people are to cooperate toward a shared goal.

Overlapping NSIP Applications mockups: documents folder workflow and project overview.

More to explore.

Email copied to clipboard