Start a conversation
Illustrative proposed quality and regulatory operations environment with controlled records, review rooms and digital evidence systems

Proposed capability · subject to evidence gates

Quality Assurance & Regulatory Science

Engineer evidence so another qualified person can reconstruct, challenge and govern it.

One programme. Two levels of scientific access.

The technical case remains rigorous while the public meaning stays clear and inspectable.

For scientific readers

A proposed quality and regulatory science environment could test how intended use, critical attributes, methods, systems, data, deviations, changes and decisions remain connected through a product or technology lifecycle.

The programme would distinguish development evidence from validation, regulated records, batch disposition and regulatory submission. Quality risk management would inform, but not excuse, applicable legal and GMP requirements.

In plain English

Quality is not a final inspection. It is the ability to show what happened, why it happened, what changed and who was responsible.

The proposed programme would test whether one conclusion can be rebuilt from original evidence before it is trusted or transferred.

Illustrative evidence-reconstruction and fault-injection exercise

Scientific question

Can an independent reviewer reconstruct one scientific conclusion across material, method, raw data, calculation, interpretation, change and authority?

Variables to admit
  • System and document version
  • Missing or late metadata
  • Role and review sequence
  • Injected audit-trail, calculation or sample-state fault
Observations to preserve
  • Traceability completeness
  • Detection and escalation time
  • Impact assessment quality
  • Recovery, correction and prevention evidence
Controls and comparators
  • Known complete reference record
  • Predeclared injected faults
  • Independent reviewer
  • Stage-appropriate quality and legal scope

Decision useImprove the evidence architecture, restrict system use, require validation or specialist quality support, or stop the transfer.

Process capability as one limited signal

Cpk compares process location and spread with limits. A high value cannot replace process understanding, data integrity, patient relevance or an authorised quality decision.

Cpk = min[(USL - μ)/(3σ), (μ - LSL)/(3σ)]
A model fragment for explanation, not a protocol, prediction or result.
Assumptions that must remain visible
  • The process is sufficiently stable for the calculation
  • Specification and sampling are scientifically justified
  • Distribution and independence assumptions are assessed

A proposed equipment system, not a procurement list.

Every system would need justified demand, competent operators, utilities, safety controls, maintenance and an accountable intended use.

  1. 01

    Electronic quality-management sandbox

    Test event, change, CAPA, training and approval workflows without implying a validated production system.

    Dependencies
    • Defined intended use
    • Role and access model
    • Controlled test data
  2. 02

    ELN and LIMS interoperability environment

    Challenge sample, method, result and decision continuity.

    Dependencies
    • Identifier model
    • Interface ownership
    • Exception and reconciliation route
  3. 03

    Chromatography data-system governance layer

    Evaluate raw data, processing, reprocessing, audit trail and review controls.

    Dependencies
    • Technique owner
    • Access segregation
    • Original record retention
  4. 04

    Audit-trail analysis workbench

    Support risk-based review of events and injected failure cases.

    Dependencies
    • Context and authorised reviewers
    • False-positive assessment
    • Version control
  5. 05

    Regulatory knowledge and submission room

    Map claims, evidence, gaps and jurisdictional assumptions.

    Dependencies
    • Current specialist advice
    • Confidentiality and access
    • No fictional submission state

Machines may assist. Named people remain accountable.

Proposed data layer
  • Source-to-decision traceability
  • Identity, role and signature state
  • Audit trail, change and deviation context
  • Jurisdictional requirement and claim map
Human authority

Named scientific, quality, regulatory and data owners retain independent approval and stop rights appropriate to the stage.

Automation must never

No software may release a batch, certify compliance, close a critical deviation, approve a regulatory claim or override an accountable quality authority.

The output is a decision package, not a theatrical result.

Potential output

An evidence-readiness dossier with traceability, gap, risk, ownership, validation and jurisdictional questions separated.

Stop or transfer when

Stop when original evidence, accountable ownership, system state, legal route, quality independence or receiving-party acceptance is inadequate.

One scientific standard. Two distinct campus expressions.

Shared governance connects Glasgow and Hyderabad. Climate, infrastructure, demand and regional value keep their designs materially different.

GLA

Glasgow

Scientific focus
MHRA- and ICH-informed development evidence, data integrity, future technology transfer and responsible AI governance.
Design response
Secure review suites separated from development laboratories, with visible source-to-decision architecture.
Value hypothesis
Could help teams enter partner, investor and future regulatory conversations with clearer evidence boundaries.

The campus expression is a planning hypothesis only. It does not represent a secured site, approved design, funded programme, partner commitment or operating capability.

HYD

Hyderabad

Scientific focus
ICH, CDSCO and revised Schedule M requirements mapping for development, transfer and a separately gated future manufacturing pathway.
Design response
Secure partner diligence, data governance and quality-training rooms linked to laboratory and future manufacturing flows.
Value hypothesis
Could strengthen India-based transfer packages while keeping development and licensed manufacturing states distinct.

The campus expression is a planning hypothesis only. It does not represent a secured site, approved design, funded programme, partner commitment or operating capability.

A credible prospective user needs a defined decision, not square footage.

Product and technology developers

A readiness view before transfer, validation or regulatory interaction.

Proposed deliverable

A source-to-decision gap and governance package.

CROs, CDMOs and receiving laboratories

Clear ownership, method, data and acceptance boundaries.

Proposed deliverable

A controlled receiving-party assessment.

Scientific software and instrument suppliers

A realistic data-integrity and intended-use challenge.

Proposed deliverable

A scoped assurance study without compliance certification.

Measure sustainability at the same decision boundary.

Future intent is not current performance. Every measure requires a defined workflow, boundary and accountable record.

MetricMethodDecision use
Right-first-time evidence packageTrack preventable rework attributable to missing, inconsistent or inaccessible records.Reduce repeat testing without weakening independent review.
Data retention burdenMeasure storage, duplication, retrieval and lawful retention by record class.Design proportionate records rather than indefinite duplication.
Quality event learningTrack recurrence, time to detect and verified effectiveness of actions.Measure whether governance changes outcomes rather than merely closing records.

No experiment advances on visual ambition.

Illustrative proposed experiment envelope. This is not performed work, a protocol, an installed capability, a service offer, a validated method or evidence of an operating laboratory. No GMP, GLP, manufacturing-licence, clinical or regulatory-readiness status is claimed.

  1. 01

    Current intended use and jurisdiction confirmed

  2. 02

    Scientific knowledge linked to patient or user risk

  3. 03

    Independent quality authority and documented decision rights

  4. 04

    GxP data-integrity assessment where applicable

  5. 05

    Validation state matched to intended use

  6. 06

    No licence, inspection, validated-system or regulatory-acceptance claim without documentary evidence

Primary context, with the caveat attached.

These sources inform the proposed programme. They do not prove VARUNÉ capability, affiliation, performance, compliance or regulatory acceptance.

Official framework

ICH Q9(R1) quality risk management

Provides current principles and tools for pharmaceutical quality risk management and risk-based decisions.

CaveatQuality risk management cannot justify non-compliance or replace applicable requirements.

Open primary source
Official framework

MHRA GxP data integrity guidance

Provides UK expectations for data governance and integrity across GxP systems.

CaveatThe appropriate controls depend on actual intended use and regulated scope.

Open primary source
Official framework

CDSCO Drugs Rules and Schedule M context

Provides the statutory Indian rules that must be read against a future operator, product and activity.

CaveatSpecialist current Indian advice remains necessary; no licence or GMP readiness is represented.

Open primary source

Bring a real question. Keep every claim inside the evidence.

A conversation or published concept does not create a partnership, service, installed capability, programme commitment or authority to use another organisation’s name.

Discuss a scoped capability studyReview concept and status definitions