CARDA Quality Control Programme

The CARDA Quality Control Programme establishes the systems, processes, responsibilities, and continuous improvement mechanisms used to ensure the reliability, integrity, usability, and operational effectiveness of the CARDA platform.

The programme applies to all stages of system development, deployment, operation, maintenance, and support.

1. Purpose

The purpose of this Quality Control Programme is to:

  • Ensure consistent system performance and reliability
  • Minimise operational and technical risk
  • Detect defects and issues early
  • Support accountability and traceability
  • Maintain confidence in evidence collection and reporting outputs
  • Drive continuous improvement across the CARDA platform

2. Quality Objectives

CARDA quality activities are guided by the following objectives:

  • Reliability — systems operate consistently and predictably
  • Usability — interfaces remain clear, intuitive, and accessible
  • Integrity — collected evidence and metadata remain accurate and protected
  • Availability — platform uptime and responsiveness are maintained
  • Traceability — changes, issues, and actions are recorded and reviewable
  • Continuous Improvement — lessons learned are incorporated into future development

3. Scope

This programme applies to:

  • Application development
  • User interface changes
  • Database and reporting systems
  • Evidence object handling
  • API and integration functions
  • Hosting and infrastructure
  • User support and issue response
  • Operational monitoring and maintenance

4. Quality Governance

4.1 Responsibilities

Role Responsibility
Directors Oversight of quality strategy and operational standards
Developers Implementation quality, testing, and defect resolution
Administrators Monitoring, reporting, and operational review
Users Feedback, issue reporting, and workflow validation

Quality is considered a shared responsibility across the organisation.

5. Quality Assurance Activities

5.1 Requirements Verification

All development work is assessed against documented objectives and operational requirements prior to release.

  • Requirements must be understandable and testable
  • Ambiguities are clarified before implementation
  • Changes are reviewed for operational impact

5.2 Code Review

Where practical, code changes are reviewed before deployment to:

  • Identify defects
  • Maintain consistency
  • Reduce unintended behaviour
  • Improve maintainability

5.3 Functional Testing

Testing verifies that features operate as intended under expected operating conditions.

Testing includes:

  • User workflows
  • Evidence submission processes
  • Reporting outputs
  • Permissions and access controls
  • Error handling
  • Mobile and desktop compatibility

5.4 Regression Testing

Existing functionality is reviewed after significant changes to ensure updates do not introduce unintended defects.

5.5 User Acceptance Validation

Operational users may be engaged to validate usability, workflow suitability, and real-world practicality before major release adoption.

6. Defect and Issue Management

Defects, incidents, and operational concerns are recorded within the CARDA case management framework.

Issues are categorised by:

  • Severity
  • Operational impact
  • Risk level
  • Priority

Each issue follows a controlled lifecycle:

Open → Acknowledged → Investigating → Resolved → Closed

Corrective actions and resolution outcomes are documented to support traceability and continuous improvement.

7. Change Control

Changes to the CARDA platform are managed through controlled processes designed to minimise disruption and operational risk.

7.1 Change Assessment

Changes are assessed for:

  • Technical risk
  • User impact
  • Security implications
  • Data integrity considerations
  • Rollback requirements

7.2 Release Management

Releases are structured and documented.

  • Major changes are tested before deployment
  • Critical systems may be released incrementally
  • Rollback capability is maintained where practical

8. Risk-Based Quality Control

Quality assurance effort is proportional to operational risk.

Higher-risk components receive:

  • Additional testing
  • Greater review depth
  • Increased monitoring
  • Enhanced verification requirements

Risk assessment tools may include:

  • Risk matrices
  • Bowtie analysis
  • Operational impact assessment
  • Failure mode review

9. Monitoring and Performance Review

Operational performance is monitored continuously to identify emerging issues and improvement opportunities.

Monitoring activities may include:

  • System uptime monitoring
  • Error and exception logging
  • User feedback review
  • Case trend analysis
  • Performance metrics
  • SLA compliance review

10. Continuous Improvement

CARDA operates under a continuous improvement philosophy.

Improvement activities are informed by:

  • Operational experience
  • User feedback
  • Incident analysis
  • Support trends
  • Observed workflow inefficiencies

Lessons learned are incorporated into future development and operational practices wherever practical.

11. Just Culture and Reporting

CARDA promotes a Just Culture approach to quality and issue reporting.

  • Users and staff are encouraged to report issues openly
  • Honest mistakes are treated as learning opportunities
  • Focus is placed on improving systems and processes
  • Reckless or deliberate misconduct is not acceptable

This approach supports transparency, trust, and early identification of operational risks.

12. Documentation and Records

The following records are maintained where applicable:

  • Issue and incident logs
  • Change records
  • Release notes
  • Testing outcomes
  • Risk assessments
  • Support and feedback records
  • Operational review notes

Records support traceability, accountability, and future review activities.

13. Programme Review

This Quality Control Programme is reviewed periodically to ensure continued suitability, effectiveness, and alignment with operational requirements.

Reviews may be triggered by:

  • Major system changes
  • Operational incidents
  • Emerging risks
  • Legislative or compliance changes
  • User or stakeholder feedback

Summary

The CARDA Quality Control Programme establishes a structured and risk-aware framework for maintaining system reliability, usability, and operational effectiveness.

The programme combines:

  • Structured engineering discipline
  • Continuous improvement principles
  • Risk-based decision making
  • Operational accountability

The objective is simple:

Deliver systems that are reliable, understandable, and trusted in real-world use.