GSK breach upheld on taskforce website: sponsorship not clearly acknowledged “from the outset” (Clause 25.3)

📅 27 February 2026 | 🖉 Dr Anzal Qurbain
📊

Key facts

Case number AUTH/3845/11/23 (CASE/3845/11/23)
Respondent GSK UK Limited
Complainant Anonymous, contactable complainant
Issue Disclosure of sponsorship/funding on a taskforce website and related materials; whether acknowledgement was clear “from the outset”.
Context Grant funding to a patient organisation to support a therapy-area taskforce; multiple funders; GSK contribution stated as ~10% of total required.
Applicable Code 2021
Breach Clause 25.3
No breach Clauses 2, 5.1, 27.2
Appeal Yes (GSK appealed Clause 25.3); unsuccessful; breach upheld.
Sanctions Undertaking received; additional sanctions not stated.
Complaint received 2 November 2023
Case completed 13 March 2025

Download the full case report (PDF)


Reviewed by Dr Anzal Qurbain (FFPM) — ABPI Final Signatory

🤖

Got a question about this case?

Ask one of our 13 specialist ABPI advisors — instant answers, 24/7.

Ask AskAnzal AI
📋

What happened

  • An anonymous complainant alleged GSK funded a patient organisation to support a therapy-area taskforce, but the taskforce website and related materials did not clearly declare GSK’s support “from the outset”.
  • GSK said the funding was an unsolicited grant (about 10% of total), provided at arm’s length with no editorial control, and that the grant agreement required the patient organisation to acknowledge GSK funding prominently.
  • The Panel reviewed screenshots of the website (including an “About” page listing multiple company funders and stating they had no editorial rights) and considered whether visitors would see funding information at the start of their journey.
  • GSK appealed the Clause 25.3 breach, arguing a “Funding Acknowledgement” link existed on every page (in the footer) and had always been present.
  • The Appeal Board found the footer “Funding acknowledgement” link (small font, bottom left) was not sufficient to be “from the outset” because users could navigate without noticing it.
⚖️

Outcome

  • Breach of Clause 25.3 (Panel ruling upheld on appeal).
  • No breach of Clause 27.2.
  • No breach of Clause 5.1.
  • No breach of Clause 2.
  • GSK’s appeal was unsuccessful; no procedural error found; case closed.
📖

Clauses

  • Clause 25.3 – Breach: Failing to ensure that all sponsorship is clearly acknowledged from the outset and that the wording of the declaration of sponsorship is unambiguous and accurately reflects the extent of the company’s involvement and influence over the material.
  • Clause 2 – No breach: Requirement that activities or materials must not bring discredit upon, or reduce confidence in, the pharmaceutical industry.
  • Clause 5.1 – No breach: Requirement to maintain high standards at all times.
  • Clause 27.2 – No breach: Requirement for a written agreement when providing donations, grants or sponsorship to patient organisations.
🔴

Sanctions

  • Undertaking received.
  • Additional sanctions: Not stated.
🔍

ABPI signatory lens

Why this matters

  • “Arm’s length” funding still counts as sponsorship under the Code’s broad definition; transparency obligations apply even where the company has no editorial control.
  • For patient-facing websites, “from the outset” is interpreted strictly: users should not have to hunt (or scroll to a small footer link) to understand pharma funding.

Where teams slip up

  • Relying on a footer link (or an “About” page) as the primary disclosure mechanism.
  • Assuming that because multiple companies fund an initiative, a separate sponsors page is enough without an upfront cue on key landing pages.
  • Over-focusing on contract wording and under-checking real-world implementation and prominence on live materials.

Control that would have prevented it

  • A mandatory “above-the-fold” funding statement on the homepage and key content pages (or a persistent banner/header disclosure) stating pharma funding and linking to details.
  • A pre-launch and periodic live-site compliance check against Clause 25.3 prominence expectations (not just presence).
  • Clearer contractual requirements specifying placement/format (e.g., header disclosure, minimum font size, no-scroll visibility) plus evidence of monitoring.

What I’d check in an audit

  • Whether patient organisation / third-party websites funded by the company display funding disclosure on the homepage and top-level pages without scrolling.
  • Whether disclosures are prominent on mobile as well as desktop (footers can be even less visible on mobile).
  • Whether the wording accurately reflects involvement (e.g., “financial support only; no editorial control”) and is consistent across pages/materials.
  • Evidence of company oversight: screenshots at launch, periodic checks, and documented follow-up where disclosures drift over time.
  • Grant/sponsorship agreements: do they specify not just that disclosure must occur, but how and where it must appear to meet “from the outset”?
  • Governance trail: approval, certification, and signatory review of third-party materials where applicable.
🔴

What the sanctions tell you

  • This was treated as a transparency/prominence failure rather than a systemic standards failure (no breach of Clauses 5.1 or 2).
  • Having a compliant written agreement helped (no breach of Clause 27.2), but it did not protect against a Clause 25.3 breach when the live disclosure wasn’t sufficiently upfront.
  • The key risk signal: PMCPA expects companies to “ensure” acknowledgement from the outset, even when the website is hosted/managed by a patient organisation.

3 questions to ask your team this week

  • On every patient/public-facing page we fund, can a first-time visitor see pharma funding disclosure immediately (without scrolling or clicking)?
  • Do our grant/sponsorship templates specify prominence requirements (placement, font, “above the fold”), and do we verify implementation post-launch?
  • Who owns ongoing monitoring of third-party sites/materials we fund, and what is our evidence that checks are happening?

📰 Weekly PMCPA Case Breakdown

One real case. One key lesson. Every week — free.

Subscribe Free