Step 2: Explore Councils — Digital Planning Register Walkthrough

Browse the list of configured councils and understand the multi-council model

Step 2 of 4 • 3 minutes

Step 2 3 minutes

Explore Councils

Browse the list of configured councils to see how the register serves multiple local authorities from a single application.

The homepage lets residents select their council to start browsing planning applications

Expected outcome

• ✓ Council selection page shows multiple configured councils
• ✓ Each council has its own dedicated section
• ✓ Per-council routing is visible in the URL structure

Understanding the multi-council model

1. Browse the council list

   The homepage shows the councils configured in this register instance. Each council has its own data source — a BOPS API endpoint that provides planning application data.

   The register is pre-configured with 9 councils:

   • Barnet
   • Buckinghamshire
   • Camden
   • Gateshead
   • Lambeth
   • Medway
   • Newcastle
   • Southwark
   • South Gloucestershire
2. Select a council

   Click on any council to enter their planning register. Notice the URL changes to include the council name — each council gets its own namespace (e.g., /camden/).

3. Understand the architecture

   Each council's data comes from their own BOPS API. The register is a read-only aggregation layer — it doesn't store any data itself. This means:

   • No database to manage or back up
   • Data is always fresh from the source system
   • New councils can be added by configuring a new API endpoint
   • The register scales independently of the back-office systems

One register, many councils: This is the key design principle. Rather than each council building their own public-facing register, they share a common application that connects to their individual BOPS back-office systems. This reduces duplication and ensures a consistent experience for residents.

Need help?

If you're stuck, check the troubleshooting section or contact us.

Press Escape to close