Project: OPEN DWP - Social Benefits

P369 — OPEN DWP: Social Benefits is an independently governed PHC Community Assurance project concerned with how UK social-benefit administration is experienced in practice. Its initial focus is Universal Credit and interactions with the Department for Work and Pensions.

The project arose from a practical observation: a claimant may accumulate months of instructions, journal messages, evidence requests, warnings and decisions without obtaining a coherent account of what happened or why. When a claim is closed, the official workflow and communication channel may end even though questions, hardship, anger and system learning remain unresolved.

The project lead's own Universal Credit record provides an immediate development case. It includes repeated requests for information during a period of zero entitlement, questions about the consequences of closure, later closure messaging and an apparent conflict in the recorded closure chronology. That case is sufficient to justify structured examination; it is not sufficient to establish the prevalence of similar experiences or prove general DWP failure.

P369 proposes to test whether PHC timechunks, CLAMPED records, maintained Concern narratives, evidence classification, participant support and institutional right of reply can create a more usable and accountable record. DWP is a principal stakeholder, evidence source, respondent and potential user of learning, but is not required to commission or control the work. Funding may be provided by humanitarian, philanthropic or responsible-business sponsors under independence safeguards.

P369 currently has an increasingly coherent definition set, an available PHC platform, relevant founder evidence and a proposed evidence-gated strategy. It does not yet have an operating participant service, confirmed funding, local host, safeguarding lead, qualified welfare-rights referral partner, data-protection approval, accessibility validation, independent evaluator or costed delivery capacity.

The target position for a first live test is deliberately modest: a safe minimum service supporting only the number of participants that confirmed people, systems and funding can sustain. The service must provide informed consent, participant-controlled disclosure, clear evidence classification, competent safeguarding and referral, accessible alternatives, secure records, manageable support, institutional right of reply and a funded closure route.

The principal gap is therefore not software development or participant recruitment. It is the absence of the independent human capability, governance, operating procedures, cost evidence and external challenge required before potentially vulnerable people can be invited to rely on the service.

A secondary gap is evidential. The project has plausible hypotheses about fragmented administration, loss of claimant voice and the value of maintained records, but no representative needs assessment, comparison evidence, tested participant pathway or demonstrated causal benefit. The first investment must close these knowledge gaps rather than assume them away.

The operating opportunity is to create an assurance layer that sits outside benefit entitlement and DWP case administration while preserving information those processes may not connect well: what a person was asked to do, what they did, what prevented progress, what was decided, what followed and what remains unresolved.

For participants, the opportunity is a more intelligible and portable record and earlier recognition that an issue requires official action or specialist advice. For community and welfare organisations, it is a structured way to identify recurring administrative barriers without rebuilding each case from fragmented correspondence. For DWP and policymakers, it is a fair source of independently maintained experience, including corrections and explanations rather than criticism alone. For funders, it is a progressively funded evidence base showing activity, Concerns, cost, learning, limitations and decisions.

The model may be replicable across UK locations because PHC provides common entity and evidence structures. However, local referral knowledge, participant needs, host capability and administrative practice will differ. The opportunity is therefore a governed network of locally grounded pilots—not immediate national rollout or a central repository of unverified complaints.

If the first test shows that PHC adds burden, duplicates existing services, excludes the people most in need or cannot influence useful action at proportionate cost, that finding still has value. It prevents larger expenditure and further participant burden.

The problem P369 is designed to address is the loss of continuity between administrative activity and human experience.

Official systems are necessarily designed around eligibility, tasks, decisions, payments and case status. They may not produce a single, participant-usable narrative connecting communications, effort, unanswered questions, practical barriers, emotional consequences and the rationale for subsequent action. Community support may help individuals, but learning is often dispersed across case notes, staff memory, complaints and informal testimony.

This creates several potential failures:

• people cannot readily explain or evidence the sequence of their experience;
• important questions and barriers disappear among repetitive transactions;
• anger or distress can cause otherwise relevant evidence to be dismissed;
• isolated testimony cannot be distinguished confidently from recurring patterns;
• public criticism may overstate what evidence actually proves;
• institutional explanations and corrections are not retained alongside allegations;
• case closure removes communication without necessarily producing understanding or referral; and
• funders and policymakers receive retrospective reports rather than a maintained evidence base.

P369 does not claim that better records will correct benefit decisions, remove poverty or reform DWP. It tests the narrower proposition that maintained, classified and fairly challenged evidence can improve individual understanding, referral, assurance and system learning.

The investment case is for progressive learning, not immediate scale. Each stage should purchase enough evidence to justify—or reject—the next stage.

Option 1 — Do nothing: retain the founder's experience as private correspondence and take no project action. This has no new delivery cost but loses the opportunity to test the apparent closure contradiction, develop a reusable evidence method or discover whether others face comparable barriers.

Option 2 — Publish the founder case only: create a factual P369 Concern portfolio, invite DWP response and produce a public learning report. This is achievable at relatively low participant risk and should form part of the initial evidence stage. Its limitation is that a founder-led single case cannot validate accessibility, support needs, wider prevalence or participant benefit.

Option 3 — Open an unrestricted public submission platform: invite large-scale stories or comments before a support and safeguarding model exists. This may generate attention but creates unacceptable risks of disclosure, misinformation, distress, unmanageable moderation and mistaken reliance. It is not recommended.

Option 4 — Fund readiness followed by a gated micro-pilot: commission a PHC 7-Day Review or equivalent definition/readiness assignment; engage the missing specialist capabilities; test systems with synthetic data; approve the minimum safe service; then support a small live pilot only if the recruitment gate is passed. This is the recommended option.

Option 5 — Launch a large cohort or seek official integration immediately: this would create the appearance of scale before cost, safety, demand and effectiveness are known. It would also risk DWP dependence or perceived endorsement. It is not recommended at the present stage.

Under the recommended option, the sponsor buys a continuously maintained evidence base and decision process—not merely a review document. Funding is released by stage, and the project may be modified, paused or stopped without needing to defend the original concept.

The following are expected or testable benefits, not established outcomes.

Participant-level hypotheses:

• a clearer chronology of actions, communications, barriers and decisions;
• greater ability to explain an experience to DWP or an appropriately qualified adviser;
• earlier identification of formal deadlines, specialist-support needs or unresolved questions;
• improved sense of agency through control of a usable record; and
• reduced need to reconstruct the same history repeatedly.

Service and system hypotheses:

• better distinction between isolated dissatisfaction, process misunderstanding and recurring administrative friction;
• retention of DWP explanations, corrections and responses alongside criticism;
• earlier visibility of accessibility, communication and referral failures;
• more specific improvement questions than those produced by generalised complaint or outrage; and
• a reusable evidence structure across locally different pilots.

Funder and governance hypotheses:

• progressive funding decisions supported by current evidence rather than promotional claims;
• visible relationship between expenditure, contribution, barriers, action and learning;
• early stop/change decisions where risk or cost exceeds demonstrated value; and
• credible public reporting that includes uncertainty, adverse findings and non-achievement.

Measures should include participant-reported clarity and burden, record completeness and usability, timely referrals, withdrawal and exclusion, institutional responses and corrections, Concern movements, adverse events, staff workload, accessibility failures, forecast-versus-actual cost and evidence of any practical service change. Benefit awards, website traffic and record volume must not be used as standalone proof of success.

No responsible total or per-participant cost can yet be stated. Earlier indicative figures were not derived from the minimum safe operating model and should not be used for solicitation or value claims.

The first costed stage should cover:

• PHC definition and readiness review, including the 7-Day Review where adopted;
• project leadership, assurance, administration and financial control;
• competent safeguarding and participant-support oversight;
• qualified welfare-rights referral input and a local referral map;
• data-protection, consent, information-security and accessibility work;
• system preparation, testing, user support, backup and incident response;
• local host or assisted-access provision where required;
• training, supervision, absence cover and workload protection;
• independent challenge or evaluation proportionate to the pilot;
• participant access needs, reasonable adjustments, interpretation or connectivity support;
• insurance, legal/contractual advice, contingency and funded closure; and
• transparent PHC/OE overhead and contributed-time reporting.

A stage budget should distinguish cash cost, committed expenditure, contributed time, overhead, contingency and potential humanitarian allocation. Pilot size must follow the funded staffing and support model; it must not be chosen first and made affordable by underestimating care or depending on unpaid labour.

Value for money should be assessed against alternative uses of the same funds, including direct support through established welfare organisations. P369 is justified only if its maintained evidence function adds value those alternatives do not already provide.

P369 operates where personal vulnerability, administrative power, public criticism, founder experience, sponsor interest and commercial PHC development intersect. Good intentions do not neutralise the conflicts created by that combination.

Governance is required to ensure that:

• participant welfare takes priority over evidence collection, publicity and scale;
• PHC personnel remain within competence and make timely specialist referrals;
• the project lead's own experience informs but does not predetermine interpretation;
• facts, testimony, inference, allegation and institutional response remain distinguishable;
• consent is specific, revisable and not treated as blanket permission for publication;
• DWP and other criticised parties receive fair right of reply without controlling findings;
• funders cannot direct individual cases, suppress adverse evidence or buy endorsement;
• data access, AI-assisted processing, retention, deletion and incident response are controlled;
• complaints about PHC can be raised outside the direct project relationship;
• financial decisions, conflicts, contributed time and OE/PHC interests are visible; and
• each gate produces an explicit continue, change, pause or stop decision.

The PHC method provides the project-control framework, but PHC cannot assure itself solely through its founder. Independent safeguarding, specialist and participant-informed challenge is essential to credibility.

Approve P369 to proceed only to a funded definition, evidence and readiness stage.

This stage should:

1. complete and cross-check the Project Information, Framing Questions, Manifesto, Strategic Plan, Business Case and PHC Proposal;
2. structure the project lead's own case as a factual Concern and evidence portfolio, including unresolved closure chronology and a documented DWP right of reply;
3. conduct a PHC 7-Day Review or equivalent readiness review;
4. obtain competent safeguarding, welfare-rights referral, data-protection and accessibility input;
5. define the minimum safe service, roles, operating procedures, measures, costs and funded closure route;
6. test PHC workflows with synthetic data and independent users;
7. seek a suitable local host and responsible funder under published independence terms; and
8. issue a formal Gate 1 recommendation: recruit a micro-pilot, revise and retest, pause, or stop.

Do not approve a fixed cohort size, national expansion, public submission campaign or official integration at this stage. Do not recruit external participants merely to strengthen the funding case.

The immediate funding proposition is therefore modest but real: finance the work required to discover whether P369 can become a safe, useful and proportionate pilot. If that work produces a negative answer, the sponsor will still have purchased valuable assurance and avoided a larger unsupported intervention.