Project: OPEN DWP - Social Benefits

P369 — OPEN DWP: Social Benefits is an independently governed PHC Community Assurance project concerned with the lived operation of UK social-benefit administration, initially focusing on Universal Credit and DWP interactions.

The project will test whether voluntary, supported PHC records can connect activity, correspondence, barriers, decisions, Concerns, actions and consequences strongly enough to help participants understand their experience and to generate credible system learning. DWP is a principal stakeholder, evidence source, respondent and potential user of findings, but does not need to commission or control the work.

P369 is not yet an operating participant service. Current work is project definition, platform preparation and conversion of the project lead's own documented experience into an initial evidence case. No delivery host, funder, participant cohort, safeguarding lead or qualified welfare-rights partner is confirmed.

The strategy is therefore evidence-gated: define the safe minimum service; obtain independent challenge and funding; test it with a deliberately small micro-pilot; review both benefit and harm; and replicate only where capability and evidence justify doing so. Order Efficiency Ltd is the proposed contracting vehicle for a funded PHC assignment rather than the beneficiary organisation or a substitute public authority.

The service presently exists as a defined concept supported by PHC Port capability, not as a proven public-facing operation. Proposed components include participant-controlled activity and correspondence records, PHC timechunks, CLAMPED entity records, maintained Concern narratives, supported reviews, comment-derived evidence, institutional right of reply, specialist referral and anonymised assurance reporting.

The project lead's own Universal Credit experience provides a relevant development case, including journal correspondence, administrative demands, unanswered questions and apparent ambiguity about claim closure. It can be used to test record structure and public-interest reporting, but one founder case cannot establish prevalence, participant usability or general impact.

Important service boundaries remain unresolved: eligibility, consent, safeguarding, welfare-rights referral, urgent-distress response, accessibility, data retention, publication control, mentor competence, complaints and withdrawal. Until these are approved, P369 is a development project rather than a claimant support service.

The intended service is a bounded, repeatable assurance model through which people can preserve and understand their administrative experience while recurring barriers are converted into evidence for service learning and public accountability.

Each pilot will provide a defined minimum service, accessible participation routes, clear referral boundaries, versioned evidence, proportionate support and periodic reporting. Participants will know what information is private, shared with the delivery team, anonymised for learning or proposed for public use. DWP and other criticised organisations will have a usable route to respond and correct facts.

The mature model is not a national database of grievances or a parallel benefits authority. It is a network of locally grounded, independently governed pilots using common evidence standards while retaining local referral knowledge and safeguarding capability. Any comparison between pilots will acknowledge selection effects, different local circumstances and changes in policy or administration.

Progression into PHC learning or project roles may be offered separately where appropriate, but it will not be portrayed as an entitlement, inducement to disclose personal information or predetermined outcome of participation.

Phase 0 — Evidence and definition: complete the core definition documents; structure the initial founder case; establish the first Concerns, evidence sources and rights of reply; and test whether PHC outputs remain factual, intelligible and proportionate.

Gate 0 — Definition decision: proceed only if the service purpose, exclusions, participant proposition, foreseeable harms and evidence model can be explained plainly without implying DWP affiliation, legal representation or guaranteed outcomes.

Phase 1 — Safe minimum service design: appoint or engage competent safeguarding, welfare-rights referral, data-protection and accessibility input; design consent, withdrawal, complaints, referral, publication and urgent-response procedures; define roles and capacity; and complete a funded PHC 7-Day Review or equivalent readiness review.

Gate 1 — Recruitment readiness: no external participant recruitment until named accountable roles, approved procedures, tested systems, insurance/contract requirements, funded capacity and a local referral map are in place.

Phase 2 — Micro-pilot: onboard only the small number of participants supportable by demonstrated capacity; test multiple access routes; monitor harm, workload and withdrawal as closely as output quality; and hold frequent assurance reviews.

Gate 2 — Controlled continuation: expand to a larger bounded pilot only if independent review finds evidence of usefulness, manageable risk, adequate support, credible measures and participant-informed improvements. Otherwise modify, pause or stop.

Phase 3 — Replication: document the minimum operating model, local prerequisites, cost base and evidence limits; invite additional locations and funders; and approve each new pilot separately rather than treating replication as automatic.

PHC Port supplies a development platform for timechunks, CLAMPED records, Concerns, comments and reporting. Order Efficiency Ltd can administer access to the PHC environment. This demonstrates technical possibility, not production readiness for sensitive benefit-related case data.

No participant equipment pool, assisted-digital location or confirmed community base exists. Participant ownership of a smartphone, computer, data allowance, private space, literacy or confidence cannot be assumed. Remote-first delivery may reduce premises cost while increasing exclusion and privacy risk.

The required information-security and operational evidence is incomplete, including a formal data inventory, access model, hosting and processor record, backup/recovery testing, retention and deletion schedule, incident response, export control, accessibility assessment and supported offline route.

The service operates through a secure, accessible and proportionate environment in which each user sees only what their role requires. Consent choices and publication status are visible in the record; material changes are auditable; data can be corrected, exported or deleted in accordance with approved rules; and loss of connectivity does not destroy continuity.

Trusted local facilities provide private, assisted access where required, while telephone, paper or other reasonable alternatives prevent the portal from becoming an eligibility barrier. Physical locations are selected for confidentiality, accessibility and safeguarding—not merely offered because a room is available.

Capacity increases through tested infrastructure, support and local capability. It is not assumed that cloud hosting alone makes a sensitive service scalable.

Complete a data-protection and information-flow assessment covering collection, lawful basis, consent choices, access, sharing, public comments, AI-assisted narrative generation, version history, retention, deletion, breach response and participant rights. Record precisely which data must never enter public or AI-processing routes.

Define minimum security controls, administrator responsibilities, audit logging, backup and recovery tests, account closure, export review and incident escalation. Conduct accessibility and usability testing with people who were not involved in building PHC Port.

Create a supported-access specification for local hosts, including private space, devices, scanning, staff boundaries, safeguarding, opening arrangements and secure destruction of temporary paper. Establish telephone and offline continuity before relying on portal access.

Run technical and human onboarding rehearsals using synthetic data. Gate live use on resolved critical findings, documented residual risk and named acceptance authority. Reassess capacity and controls before every material increase in participants or locations.

David Winter is the project lead and originator of PHC. Order Efficiency Ltd is the proposed contractual and administrative vehicle. Wider PHC Consortium participation is prospective; it must not be represented as a staffed delivery team until named people accept defined roles and funded commitments.

No safeguarding lead, welfare-rights specialist, data-protection lead, accessibility lead, local host, independent evaluator or funded participant-support team is confirmed. This is the principal readiness gap.

The project has strong foundations in project risk, governance, maintained evidence and platform development. It does not currently demonstrate all professional competencies required for work with potentially vulnerable participants. Founder experience gives urgency and insight but can also create confirmation bias, excessive identification with angry participants and pressure to interpret new cases through the founder's dispute.

Each pilot has a named accountable lead; competent safeguarding and participant-support oversight; qualified welfare-rights referral capability; data-protection and accessibility responsibility; trained PHC record support; operational administration; and independent challenge proportionate to pilot risk.

Participants are collaborators in learning, not raw material for a case against DWP or marketing assets for PHC. They can disagree with PHC interpretation, restrict disclosure, withdraw and complain without losing access to their own agreed records.

PHC mentors and administrators work to written role boundaries, manageable caseloads, supervision, escalation rules and wellbeing protections. Their contribution, paid status and any humanitarian allocation are transparent. No unpaid effort is described in a way that implies guaranteed future payment or employment.

Founder authority reduces as formal governance matures. Decisions affecting participant safety, publication, complaints and conflicts are not left to the founder alone.

Produce a responsibility and competence matrix covering project direction, PHC assurance, participant contact, safeguarding, welfare referral, data protection, accessibility, finance, system administration, publication, complaints and independent review. Mark every role as confirmed, interim or vacant.

Recruit the safety-critical and specialist functions before recruiting participants. Complete proportionate identity, reference, conflict and vetting checks; issue role descriptions and agreements; and train everyone in safeguarding, distress response, benefits-advice boundaries, consent, data handling, accessibility, evidence classification and right of reply.

Set caseload and contact limits from rehearsal evidence rather than optimism. Establish supervision, incident review, absence cover and a route for staff or volunteers to challenge the project lead.

Use participant advisory input to test language, consent and burden. Review role performance and workload at every gate. Suspend intake when supervision, response times or safeguarding capacity fall below agreed thresholds.

P369 has no confirmed dedicated grant, sponsor, operating budget or participant-service income. Previous figures such as £200 per participant are unvalidated estimates and must not be used as a funding proposition until scope and safe staffing have been costed.

Current development includes contributed PHC and founder time. That contribution should be recorded as project evidence but not confused with cash income, a funded delivery commitment or proof that the model can operate indefinitely without payment.

The project may attract humanitarian, philanthropic or CSR funding. It may also benefit from cross-support associated with commercial PHC work. Neither route is presently committed, and both require transparent treatment of overhead, consultant pay, contributed time, humanitarian allocations, conflicts and funder influence.

P369 is financed through defined assignments or pilot stages with sufficient resources to deliver the minimum safe service, including safeguarding, specialist referral support, accessibility, data protection, administration, platform operation, evaluation, insurance and contingency—not merely visible participant activity.

Funders receive a continuously maintained evidence base showing delivery, expenditure, Concerns, changes, limitations and outcomes. They can challenge scope, value and governance and decide whether to fund a further stage. They cannot purchase favourable findings, suppress adverse evidence or direct individual cases.

Costs become comparable only after actual pilot evidence exists. Unit cost is reported alongside participant needs, service intensity, withdrawal, adverse events, donated contribution and overhead, preventing a deceptively low headline cost from rewarding under-support.

The project aims for financial continuity without making participant welfare dependent on speculative future sponsorship. Every pilot includes a funded and dignified closure route.

Build the first budget from the responsibility and minimum-service model. Separate definition/7-Day Review, setup, micro-pilot, evaluation, continuation and closure costs. State assumptions for caseload, duration, specialist input, local facilities, technology, travel, accessibility, insurance, contingency, PHC overhead and contributed time.

Define sponsor terms covering payment gates, permitted influence, conflicts, publication, evidence access, intellectual property, participant protection, early termination, underspend, overspend and funded closure. Refuse funding conditions that compromise consent, evidence integrity or right of reply.

Use progressive funding gates tied to verified readiness and delivery evidence rather than releasing all funds against recruitment numbers. Maintain project-level cost, commitment, forecast and variance records alongside operational Concerns.

After each phase, report total and unit costs with context; compare forecast with actual; identify unfunded dependency; and obtain an explicit continue, change, pause or stop decision before incurring the next stage.

Current outreach is founder-led through PHC Port, direct relationships and professional social media. The evolving P369 record and the founder's Universal Credit experience can demonstrate the method and stimulate discussion, but they do not yet constitute a validated service case.

The name “OPEN DWP” may be mistaken for a DWP programme or official service. Every public presentation should state prominently that P369 is independent and not affiliated with or endorsed by DWP unless a later written agreement changes that fact.

No confirmed host, funder, participant group or institutional supporter should be implied. Public anger may attract attention, but attention is not the same as trust, representative evidence or fundable demand. Participant stories must never become the price of access or the project's promotional fuel.

P369 earns attention through transparent evidence: clear project definitions, visible governance, maintained Concerns, documented institutional responses, honest pilot reports, cost evidence and accessible explanations of what changed and what did not.

Different propositions are made to different audiences. Participants are offered supported record-building with clear limits. Hosts are offered a governed local pilot and referral relationship. Funders are offered independent evidence and progressive funding control. DWP and other public bodies are offered structured learning, correction and right of reply. The public is offered evidence with privacy and uncertainty preserved.

Growth comes from credible pilots and responsible referral, not outrage metrics, mass data collection or claims that PHC has already proven a systemic diagnosis. Public communication remains possible during delivery, but publication decisions are governed independently of sponsor preference and promotional opportunity.

Create a minimum evidence pack comprising the Project Information, Framing Questions, Manifesto, Strategic Plan, Business Case, PHC Proposal, initial Concern portfolio, evidence-classification standard, privacy/safeguarding summary, indicative stage budget and example assurance output.

Publish a plain-language independence statement and audience-specific explanations of what P369 is and is not. Test whether people confuse it with DWP, benefits advice, campaigning, employment or a complaints service; revise messaging until those misunderstandings materially reduce.

Approach a small number of relevant funders, community/welfare hosts, specialist advisers and public bodies. Record responses, objections, non-response and conflicts as evidence rather than treating outreach solely as sales activity.

During any pilot, publish only within the approved consent and evidence framework. Report adverse findings and limitations alongside progress. After each gate, use the maintained evidence base to invite the next funder or location without presenting replication as inevitable.