Naeha Rashid, November 2020
The once-only policy (OOP) is increasingly seen by some digital government experts as central to establishing a national digital government strategy and as a gateway to next-generation government services. Once-only is so called because users (citizens, residents, and businesses) have to provide diverse data only one time when in contact with public administrations; after the initial data transfer, different parts of government can internally share and reuse this data to create public value and better service for users.
Members of the digital government community are excited by the potential of OOPs to create public value and reduce the cost of government, and I want to help governments harness this potential. I am also deeply concerned by the potential for OOPs to concentrate and increase state power and the negative impact this could have on individuals’ privacy, freedoms, and capacity to dissent.
The goal is to harness the benefits of OOP while minimizing the risks, to create a world in which the power of the state is counterbalanced by the power of its citizenry. This document outlines the key policy questions and concerns that must be addressed by governments intending to implement an OOP. It is designed to help stakeholders—including policymakers in government and interested parties in civil society—ask key questions during the development of OOP-facilitating infrastructure, specifically identity- and data-sharing mechanisms, and the development of OOP strategy.
This document is not to intended to encourage or prescribe a specific pathway of development, but to consolidate and present a compendium of the key considerations at each stage. This work is based on an extensive literature review across the areas of privacy, identification, data sharing, and OOP; interviews with experts in the field; and mini case studies highlighting different lessons of implementation from five countries—the Netherlands, Estonia, the UK, Canada, and Australia—with diverse approaches and at very different stages of OOP maturity.