All audiencesFor superintendents

Compliance across the estate.

A single dashboard for every branch. SOPs versioned centrally. Evidence packs ready before the inspector knocks.

Talk to sales

A superintendent in a multi-branch group is accountable for clinical and operational standards across every site. Without tooling that role becomes paper-shuffling: chasing branches for SOP acknowledgements, asking each manager whether their fridge log is up to date, finding out the day before an inspection that one branch never trained the new starter. WE4Pharmacy gives you one console where every branch reports the same evidence in the same format, with timestamps and signatures attached.

What you get

  • Cross-branch SOP publishing and acknowledgement tracking
  • Estate-wide compliance log roll-up
  • GPhC inspection readiness scored per branch
  • PQS and NHS service contract evidence tracking
  • Training matrix across all staff, all branches
  • Audit trail: who did what, when, where

A typical week

  1. 1

    Publish a new or revised SOP from the group console. Each branch sees it in the morning briefing, the responsible pharmacist signs to acknowledge, and the acknowledgement is timestamped against their GPhC number.

  2. 2

    Pull the cross-branch compliance dashboard. Branches scoring below 80% surface at the top with their three weakest areas (fridge log gaps, missed near-miss reviews, expired credentials).

  3. 3

    Review the training matrix. New starters in week one show as amber until their mandatory modules complete; the matrix automatically reminds branch managers.

  4. 4

    When the GPhC announces an inspection at a branch, generate the evidence pack from the group console. It assembles SOPs, training records, RP rota, near-miss log, CD audit and service evidence in the order inspectors usually request them.

Common questions

Can I scope what each branch manager sees?

Yes. Group-level roles control whether a branch manager sees only their own site or has cross-branch visibility. The default for a branch manager is their own site plus read-only on the group SOP library.

How do you handle SOPs that differ between branches?

The group SOP library is the canonical source. Individual branches can mark an SOP as having a local override — the override is shown alongside the canonical version, and inspectors see both with the reason for divergence.

Does evidence-pack generation cover NHS services?

PQS evidence, Pharmacy First sign-offs, contraception PGDs, and the BCG/flu/COVID service records all roll up into the per-branch evidence pack with the supporting competency declarations.

Ready to get started?

Talk to sales