NHS Project Charter Development and Authorization SOP

Standard Operating Procedure: NHS Project Charter Development & Authorization

Document ID: SOP-TR-NHS-042
Effective Date: October 24, 2023
Version: 3.2
Review Cadence: Annual / Post-Gateway Review
Author: Julian Vance, Chief Architect, Template Registry

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the mandatory engineering lifecycle for authoring, validating, and authorizing a Project Charter within National Health Service (NHS) trusts, Integrated Care Systems (ICS), and arm's-length bodies. The purpose of this document is to eliminate operational ambiguity, enforce alignment with the NHS England (NHSE) Oversight Framework and clinical governance standards, and ensure capital and revenue investments demonstrably improve patient safety, clinical throughput, and resource optimization.

Adherence to this protocol is mandatory for all internal change agents, external systems integrators, and clinical project leads operating within Template Registry-governed architectures.

---

2. Scope & Prerequisites

2.1 Scope

This SOP applies to all service transformation, digital infrastructure, clinical pathway redesign, and estate development projects requiring formal governance gateway approval (Gate 0 / Gate 1) under the NHS Integrated Assurance and Approval Process (IAAP).

2.2 Prerequisites & Tooling

• Project Management Toolchain: MS Project Online / Jira Enterprise configured for NHS PRINCE2 Agile or Agile Delivery methodologies.
• Documentation Repository: Template Registry Secure Workspace (ISO/IEC 27001 certified).
• Clinical Safety Standard Compliance: Familiarity with DCB0160 (Clinical Risk Management: its Application in the Deployment of Health IT Systems) and DCB0129.
• Financial Modeling: NHS-approved Better Business Cases (BBC) 5-case model workbook template.

---

3. Roles & Responsibilities (RACI Matrix)

---

4. Step-by-Step Procedure

Phase 1: Initiation & Strategic Alignment

• 1.1 Extract the current NHS Project Charter master template from the Template Registry secure repository.
• 1.2 Define the project’s Strategic Context, explicitly mapping objectives to the local Integrated Care Board (ICB) Joint Forward View and NHS Long Term Plan mandates.
• 1.3 Identify the Executive SRO and obtain written acknowledgment of accountability.

Phase 2: Scope, Objectives & Clinical Justification

• 2.1 Define unambiguous In-Scope and Out-Of-Scope parameters to prevent scope creep across clinical boundaries.
• 2.2 Formulate SMART (Specific, Measurable, Achievable, Relevant, Time-bound) objectives tied directly to clinical Key Performance Indicators (KPIs) (e.g., 4-hour A&E wait reduction, Referral-to-Treatment [RTT] 18-week compliance).
• 2.3 Conduct an initial clinical impact assessment to determine if DCB0160/DCB0129 standards apply.

Phase 3: Stakeholder Analysis & Governance Architecture

• 3.1 Map all key stakeholders using a Power/Interest grid, explicitly detailing engagement pathways for clinicians, operational managers, and patient representatives (PPI - Patient and Public Involvement).
• 3.2 Establish the Project Board reporting hierarchy, frequency of highlight reporting, and escalation tolerances.

Phase 4: Risk, Constraints & Assumptions Management

• 4.1 Populate the initial Risk, Assumptions, Issues, and Dependencies (RAID) log within the charter.
• 4.2 Ensure high-severity clinical and operational risks include mitigation strategies and designated risk owners.
• 4.3 Validate resource, technical, and scheduling constraints with departmental clinical leads.

Phase 5: Financial Sourcing & Resource Allocation

• 5.1 Insert the capital and revenue expenditure (CapEx/RevEx) summaries vetted by the Finance Business Partner.
• 5.2 Document efficiency savings, productivity metrics, and Cash-Releasing/Non-Cash-Releasing Efficiency Savings (CRES/NCRES) projections.
• 5.3 Secure sign-off signatures from the SRO, Finance Lead, and Information Governance Officer prior to formal submission.

---

5. Quality Assurance & Pro-Tips

5.1 Best Practices

• Clinical Engagement First: Do not draft operational workflows without direct input from the designated clinical lead. Systems designed without the floor-level clinicians invariably fail adoption metrics.
• Living Document: Treat the project charter as a baseline control document. Use formal Change Request (CR) procedures for any alterations post-baseline.

5.2 Common Pitfalls to Avoid

• Vague Benefits Realization: Avoid qualitative-only benefits. Every stated benefit must have a baseline metric, a target metric, a measurement methodology, and a designated tracking owner.
• Ignoring IG/Caldicott: Failing to engage the Information Governance lead early introduces critical path delays during Information Governance Toolkit / Data Security and Protection (DSP) Toolkit audits.

5.3 Metric Thresholds

• Charter Review Cycle: Must be completed within 15 working days from initiation to SRO sign-off.
• Benefit Realization Variance: Any forecasted variance exceeding ±10% against the approved business case triggers an automatic audit by the Trust PMO.

---

6. Frequently Asked Questions (FAQ)

Q1: What should be done if the Clinical Safety Officer (CSO) refuses to sign off on the project charter?
A1: The project charter cannot proceed to the Project Board for baseline approval. The Project Manager must log the hazard objection in the RAID log, convene a risk-mitigation workshop with the CSO and SRO within 48 hours, and adjust the technical or operational scope to resolve the clinical safety hazard.

Q2: How do we handle multi-trust or cross-ICS project charters where governance frameworks overlap?
A2: Deploy the federated appendix template located within the Template Registry. The lead trust's SRO retains overarching accountability, but local sub-charters must be ratified by the respective Caldicott Guardians and Finance Directors of each participating trust before master baseline locking.

Q3: Is a full DCB0160 Hazard Log required for non-clinical administrative projects?
A3: No. If the project introduces zero changes to patient-facing software, clinical workflows, or diagnostic data pathways, the Project Manager may submit a formal "Null Clinical Impact Statement" countersigned by the Chief Medical Officer (CMO) to bypass full clinical safety hazard logging.