'Make information on development applications open, accessible and usable for residents, professionals and government.’
This section covers the two newest products in the ODP ecosystem - the Digital Site Notice (DSN), and the Digital Planning Register (DPR). As of 2025, the DSN is no longer in active development, with features and functionality rolled into, or planned to be rolled into, the DPR.
This presentation provides a comprehensive overview of the challenges DPR was designed to address and the methodology adopted to overcome
You can see the LPAs that are using the production (live) version of the DPR by visiting the website https://planningregister.org/. Clicking through to one of the council pages will take you to their individual planning register.
Some pages of note are the comment submission page on applications that have consultations in progress. The documents page, showing a paginated view of all documents. A determined application with decision notice next to the applications progress. An application with specialist comments and one with comments from members of the public.
Development of the DPR
Development of the DPR has been undertaken to date by TPXimpact, in conjunction with Camden, Lambeth and Gateshead as LPA partners. One of the key development artefacts is the coded prototype that can be seen here (password - DSN-PI-TPX-DLUHC). This is an example of some of the future elements of the DPR. It includes features that have been designed but not yet implemented, such as enforcements and impact measures.
In the summer of 2025, the DPR team reviewed the platform’s architecture as part of our work into adding legacy data into the DPR. At the time the DPR was tightly coupled with BOPS. We identified that this dependency limited flexibility and required complex conditional logic within the application’s frontend to handle gaps in the BOPS API that should be handled on a system level. To address this and help achieve our goal of easily supporting legacy data from other endpoints in the future, the team refactored DPR in the autumn of 2025 to establish its own backend, enabling it to interface cleanly with multiple ODP schema-compliant systems and treat all data sources equally. This approach ensures the DPR can continue to support BOPS effectively while better aligning with the ODP goal of a modular, sustainable planning software ecosystem. Much of the thinking behind that work is summarised here. There is also some work detailing future DPR technical architecture available here.
What's Next for DPR?
DPR development is on hiatus until January 2026 as Camden works through re-procurement for the next stage of DPR development.
During that time, LPAs are experimenting with using data middleware tools such as FME to explore getting data from systems such as Uniform into DPR directly by converting the data into the ODP Post-submission published application format. There will be more to say on this when the next stage of DPR development begins in 2026
During this hiatus, DPR will continue to be supported, and new LPAs can be onboarded as usual.
Click here to start onboarding independently.
Contact Nora Constantinescu at Camden in the first instance to find out more.