PCP
Begin with the public service
A portal is useful when people can complete a procedure, understand the answer and correct an error. Without examining the responsible office, a new interface may shift data entry to users while leaving internal work unchanged. The PCP wants time and obstacles assessed across the whole process.
Digital access must not become the exclusive condition for a right. Human assistance and suitable alternatives need funding alongside the service. Languages, disability and available devices belong in initial design.
Open code as a control instrument
The Federal Chancellery explains EMBAG publication for software developed or commissioned by covered federal authorities. Third-party rights and important security grounds require assessment. This means neither publishing every purchased product nor identical duties for all cantons.
Code can be inspected, reused and developed under its licence. Application data do not thereby become public. The PCP supports takeover by other teams and sharing between authorities, backed by documentation and real maintenance. An abandoned repository does not ensure continuity.
Connect systems without centralising everything
I14Y catalogues metadata, interfaces and services. The underlying data remain with responsible bodies. National coordination therefore need not require a central collection of every personal file.
The PCP supports documented interfaces and shared definitions for necessary exchanges. Technical possibility is not legal authority. Purpose, authorised people, necessary data and duration must be defined. Avoiding repeated entry does not justify unlimited circulation.
Protect data from the design stage
The FDPIC guide connects privacy by design and default with limited collection and exposure. This concerns architecture, access and settings. A privacy statement does not compensate for excessive collection.
The PCP wants explainable access rights and corrections. Tests should not unnecessarily copy real files. Retention, archiving and deletion need planning under the applicable regime. Sharing a tool does not merge processing responsibilities.
Prepare an exit before dependence
Contractual data ownership is insufficient if exports are incomplete or unusable. Formats, deadlines, documentation, costs and skills must be specified. Takeover should be tested before contractual breakdown; otherwise ownership remains theoretical captivity.
The PCP wants feasible competition in maintenance and hosting within service constraints. Private suppliers can be compatible with public control if they deliver continuity requirements. Public suppliers must equally demonstrate quality, security and reversibility.
Assess continuity and the ability to act
Account counts alone do not establish success. Completed procedures, necessary assistance, interruptions and development without total reconstruction matter. Failures need responsibility and proportionate continuity arrangements.
The PCP wants stronger public and user agency. Expected savings must include maintenance, training, assistance and supplier changes: the material conditions of useful common infrastructure.