Thursday, 12 November 2026

Clinical-development handoffs: a sponsor checklist for scope and decision ownership

By Margaret Emerson | BioBoston CRO

Why a handoff is a decision problem, not merely a document transfer

A clinical-development handoff can look complete while important work remains unowned. A clinical operations team may have shared the timeline, the vendor may have received the latest protocol, and the project manager may have closed the meeting minutes. Yet the downstream group may still lack a named person who can accept the deliverable, resolve an exception, or approve a change before the next milestone.

For an emerging sponsor using a primary contract research organization (CRO) and specialist vendors, the problem becomes more complicated. One organization prepares an output; another checks it; a third depends on it; and an authorized sponsor representative may need to make a decision that has not been delegated to a vendor. A useful handoff therefore records not just what was transferred but who is authorized to decide what happens next.

The checklist below is a practical project-control method. It should be tailored to each study's protocol, agreements, quality management system, stage of development, applicable regulations and critical-to-quality factors. It does not replace contractual transfer-of-activities documentation, clinical judgment, safety reporting, or sponsor oversight.

1. Define the handoff item precisely

Avoid descriptions such as 'data ready' or 'medical writing complete.' Write the item so that the recipient knows what to inspect. Identify the deliverable, its version, format, source system, owner, due date, intended use, and destination. For example: 'final reconciled laboratory transfer specification, version 2.1, for data-management acceptance before test transfer,' rather than 'lab files.'

For each item, separate three dates: the creator's planned completion date, the receiving team's acceptance date, and the downstream decision or milestone date. Those dates can differ, and a single green status can conceal a critical gap.

2. Name four different responsibilities

A simple handoff record benefits from four explicit roles:

· Preparer / performer: Produces the item or performs the agreed activity.

· Reviewer: Checks technical completeness and identifies discrepancies within their defined remit.

· Approver / decision owner: Has the delegated authority to accept the item or approve a relevant change. Where sponsor approval is required, identify the sponsor role rather than assuming a CRO project manager may approve it.

· Recipient / downstream owner: Takes possession of the accepted item and confirms that its dependencies are understood.

One person can hold several roles only when the study's procedures, contracts and required independence allow it. Use named individuals or defined role owners with a clear escalation substitute; a generic 'team' address rarely makes an adequate decision owner.

3. Agree on acceptance evidence before work begins

A handoff cannot be measured only by whether a file was uploaded. Define a small set of acceptance criteria proportional to the item's risk and intended use. Examples include the correct approved version, reconciliation to source records, inclusion of required tables or signatures, disposition of open comments, system access for the recipient, and documented approval when applicable.

Specify who will decide whether a deviation from the criteria is acceptable. If the deliverable will be used for clinical or regulatory decisions, incorporate the appropriate quality, medical, regulatory, data, or safety review rather than relying solely on project-manager acknowledgement.

4. Record dependencies, not just dates

Create one dependency entry for every item that can prevent another workstream from proceeding. A useful dependency states the upstream item, downstream activity, owner on each side, acceptance condition, target decision date, consequence of delay, and recovery option.

For example, a statistical programming output may depend on a finalized dataset and approved analysis rules. Rather than reporting both vendors as 'on track,' the project team should identify the exact evidence that unlocks the downstream work and who can resolve conflicts between the two schedules.

5. Separate an issue from a scope change

An operational issue is a problem with delivering an agreed obligation. A scope change alters the agreed obligation, assumptions, schedule, cost or approach. When an issue triggers a possible change, record both: the immediate containment or workaround and the proposed change with its impact on quality, timing, cost, resources, records and downstream deliverables.

Ask the vendor to document the options and assumptions. Keep approval of sponsor-controlled scope, budget, clinical, safety and regulatory decisions with the designated authorized sponsor owners. Update the applicable contract, statement of work, responsibility matrix, and plan when the approved change requires it.

6. Maintain a short decision log with visible closure

A useful decision record contains: a unique identifier; the question; options considered; essential evidence and version; authorized decision maker; date required; decision and rationale; affected workstreams; actions triggered; and location of the controlled record. A meeting note saying 'discussed offline' is not a closed decision.

Escalate early when a decision is missing, particularly when the downstream work has an irreversible commitment or a subject-safety implication. Set explicit triggers for escalation - for example, acceptance overdue beyond the agreed threshold, an unresolved data-integrity concern, or a change that could affect a trial's critical-to-quality factors. The threshold should be agreed in the project's governance plan, not invented retrospectively.

7. Make handoff completion a documented two-way event

A robust closeout includes the preparer's delivery confirmation and the recipient's acceptance or qualified rejection. Record the transfer location, accepted version, open exceptions, new owner, next action and planned follow-up. A partially accepted deliverable should be marked as such, with the exceptions assigned and tracked.

For personnel or vendor transitions, also transfer the live issue, risk, decision and action logs; contractual and budget assumptions; system and record-location knowledge; planned meetings; contact and escalation routes; and any outstanding oversight or quality actions. Resolve access changes through authorized procedures, not informal password sharing.

A one-page handoff record sponsors can adapt

Field	Minimum entry
Workstream and deliverable	Specific item, version, source system and intended use
Planned delivery / acceptance	Two distinct dates; downstream milestone date separately
Performer, reviewer, approver, recipient	Names or controlled roles, including sponsor decision authority
Acceptance criteria	Required content, evidence, quality checks and review outcome
Dependencies	Upstream inputs and downstream use; blocker thresholds
Open issues / changes	IDs, proposed action, risk and authorized decision route
Evidence and record location	Controlled file/link and version history
Result	Accepted, accepted with conditions, or rejected, with date
Next owner and escalation	Named role, deadline and alternate escalation route

A short scenario: when 'delivered' does not mean 'ready'

A central laboratory provides a revised transfer specification to the data-management vendor on schedule. The data-management team can open the document, but one analyte mapping remains unresolved. The project manager's dashboard shows delivery as complete. The downstream build, however, cannot be finalized without a medical or scientific decision on the mapping.

The better record separates file delivery from acceptance, assigns the mapping question to the appropriate scientific decision owner, logs the required decision date, documents any impact on the downstream build and records the final accepted version. It is a modest control, but it prevents a handoff from becoming a hidden dependency.

Regulatory context and practical boundary

ICH E6(R3) Good Clinical Practice emphasizes documented agreements covering transferred trial-related activities, sponsor oversight of service providers, and appropriate essential-record management. In the European Union, the EMA identifies the Principles and Annex 1 of E6(R3) as effective from 23 July 2025. As of November 2026, the consolidated version incorporating Annex 2 has a future EU effective date of 15 January 2027. The operational checklist above is an implementation aid, not a substitute for the applicable guideline, local laws or study agreements. Regulatory applicability and implementation dates should be checked for the jurisdiction and trial concerned.

Primary sources: European Medicines Agency, ICH E6 Good Clinical Practice guideline and current version information: https://www.ema.europa.eu/en/scientific-guidelines/ich-e6-good-clinical-practice

U.S. Food and Drug Administration, E6(R3) Good Clinical Practice (GCP), Final Guidance for Industry (September 2025): https://www.fda.gov/regulatory-information/search-fda-guidance-documents/e6r3-good-clinical-practice-gcp

U.S. eCFR, 21 CFR 312.52, Transfer of obligations to a contract research organization: https://www.ecfr.gov/current/title-21/chapter-I/subchapter-D/part-312/subpart-D/section-312.52

Further reading (affiliated, contextual): BioBoston CRO explains its approach to defined project-management scopes, sponsor decision ownership and workstream handoffs: https://biobostoncro.com/services/project-management/clinical-project-management/ . This is a company-affiliated reference, not independent validation of outcomes.

Pharmaceutical Microbiology Resources (http://www.pharmamicroresources.com/)

Tuesday, 10 November 2026

When antibiotics cause harm: Peggy Lillis’ story puts a human face on the C. diff threat

Antibiotics are among medicine’s greatest achievements. They have turned once-lethal bacterial infections into treatable illnesses and made surgery, cancer therapy and much of modern medicine possible. Yet every antibiotic prescription also carries risk. Sometimes that risk can have devastating consequences.

By Tim Sandle

Christian John Lillis knows this better than most. In 2010, his mother, Peggy Lillis, was a healthy 56-year-old kindergarten teacher when she underwent a root canal. According to her son’s account included in the new CDC Antimicrobial Resistance Threats Report, her dentist prescribed clindamycin. Four days later she developed diarrhoea. The family initially did not connect it with the antibiotic. Her condition deteriorated rapidly and, when she reached hospital, doctors diagnosed toxic megacolon caused by Clostridioides difficile, or C. diff, and septic shock. About a week after the dental procedure, she died.

That experience ultimately led Christian John Lillis and his brother to establish the Peggy Lillis Foundation, an organisation dedicated to C. diff education and advocacy. A 2025 poll commissioned by the foundation found that 54% of 1,000 US respondents remained unfamiliar with C. diff, highlighting the continuing gap between the infection's public-health importance and public recognition.

Now Christian John Lillis is bringing that patient and family perspective directly into the national conversation around antimicrobial resistance, participating in the CDC webinar Update to the Antimicrobial Resistance Threats Report: A Closer Look. His central message is deceptively simple: stewardship is not just about preserving antibiotics for the future. It is also about protecting the person receiving an antibiotic today.

What is C. diff?

Clostridioides difficile is a spore-forming bacterium capable of causing diarrhoea and inflammation of the colon. Severe disease can progress to complications including toxic megacolon, sepsis and death. Its hardy spores can also persist in the environment, facilitating transmission, particularly in healthcare settings. Its relationship with antibiotics is especially important.

The human intestine contains an extraordinarily complex microbial ecosystem. Collectively known as the gut microbiome, these microorganisms help occupy ecological niches and create what microbiologists call "colonisation resistance", making it harder for pathogens to proliferate.

Antibiotics can disturb that ecosystem. While killing the bacteria responsible for an infection, an antimicrobial can also eliminate susceptible members of the normal intestinal community. That ecological disruption can create an opportunity for C. diff to multiply and produce toxins that damage the intestinal lining.

The CDC therefore identifies recent antibiotic exposure as an important risk factor: the likelihood of developing C. diff is higher during antibiotic treatment and for up to three months afterwards.

This does not mean that taking an antibiotic inevitably causes C. diff. Most courses do not. Risk depends on the drug, duration of treatment, individual susceptibility, healthcare exposure, age and other factors. But epidemiological evidence consistently establishes antibiotic exposure as a major modifiable risk factor for infection.

A large 2023 case-control study published in Open Forum Infectious Diseases, for example, compared the risks associated with different antibiotics and described antibiotic exposure as the greatest risk factor for community-associated C. diff. Importantly, risk varied substantially between antibiotic agents.

Why clindamycin matters

Peggy Lillis' treatment is particularly relevant because the antibiotic involved was clindamycin. Clindamycin has a long-recognised association with C. diff. The CDC's current guidance for dental prescribers explicitly advises avoiding clindamycin when alternatives are available because it can cause more frequent and severe adverse effects, including C. diff infection.

This principle is also reflected in current American Dental Association antibiotic stewardship guidance. For odontogenic infections requiring systemic treatment, amoxicillin or penicillin V are listed as first-line options in appropriate patients, while clindamycin is reserved for circumstances in which alternatives such as azithromycin are unsuitable, specifically because of its high C. diff risk.

The issue goes beyond one drug, however. Cephalosporins, fluoroquinolones, co-amoxiclav and other broad-spectrum agents have also been associated with C. diff. NICE notes that no antibiotic can be entirely excluded from the risk.

A 2026 real-world analysis of 201,911 patients with C. diff further illustrates this point. Among the study population, 33.9% had recorded antibiotic exposure, with extended-spectrum penicillins, third-generation cephalosporins and aminopenicillins among the most frequently used classes shortly before diagnosis. The authors argue that stewardship therefore needs to extend across antibiotic classes rather than simply targeting historically notorious agents such as clindamycin.

A major public-health burden

C. diff is sometimes viewed primarily as a hospital infection. That picture is now incomplete. In its 2026 Antimicrobial Resistance Threats Report, the CDC estimates that there were 412,504 C. diff cases in the United States in 2023, including 223,568 classified as community-associated and 188,936 as healthcare-associated. The agency estimates 11,339 deaths among hospitalised cases and more than $6.4 billion in attributable healthcare costs.

Older adults remain particularly vulnerable. In 2023, the reported infection rate among those aged 65 and over was 351 cases per 100,000 people, compared with 75.5 per 100,000 among people under 65.

There has nevertheless been progress. The CDC previously classified C. diff as an "urgent" antimicrobial-resistance threat. Following reductions in infections since 2011, it is now classified as a serious threat. Yet the agency cautions against complacency, particularly because community-associated infections have increased slightly since the pandemic-era decline.

There is an apparent paradox here. C. diff is not primarily included in the report because it is intrinsically an antibiotic-resistant pathogen. Instead, it belongs in the antimicrobial-resistance conversation because antibiotic use and microbial transmission are forces driving both C. diff disease and antimicrobial resistance.

Reducing unnecessary antibiotic exposure can therefore produce two benefits: lowering selection pressure for resistant organisms and reducing the immediate possibility of antibiotic-associated complications such as C. diff.

Dentistry and the stewardship opportunity

Peggy Lillis' case also raises questions about antibiotic use in dentistry. Modern stewardship guidance stresses that antibiotics should not substitute for definitive dental treatment. The CDC advises dentists to prioritise procedures such as drainage, extraction, pulpotomy or root-canal treatment for most appropriate dental conditions and generally not to add an antibiotic when definitive treatment is available. Systemic antibiotics become appropriate when findings indicate spreading or systemic infection, such as fever or malaise with intraoral swelling.

The American Dental Association similarly recommends against antibiotics for most pulpal and periapical dental pain and localised swelling in immunocompetent adults when definitive dental treatment can be provided. This is what antimicrobial stewardship looks like at the individual level: first determining whether an antibiotic is actually required, then selecting an appropriate drug, dose and duration.

Crucially, stewardship is not an anti-antibiotic philosophy. The Infectious Diseases Society of America and Society for Healthcare Epidemiology of America define it as coordinated interventions to improve and measure appropriate antibiotic use, including optimisation of drug selection, dose, duration and route. Among the demonstrated benefits are reductions in adverse events, including C. diff infection. Withholding an antibiotic when one is genuinely required can itself be dangerous. The objective is therefore not simply fewer antibiotics, but better antibiotic use.

Putting patients back into antimicrobial resistance

This distinction explains why the patient voice belongs alongside microbiologists, epidemiologists and infectious-disease specialists in discussions about antimicrobial resistance. Resistance is frequently communicated through abstract measures: susceptibility percentages, resistant isolates, surveillance graphs and national estimates. These are indispensable for understanding the problem, but they can obscure what antimicrobial exposure means at the level of an individual patient and family.

Christian John Lillis's perspective provides the missing human element. The lesson from his mother's death is not that antibiotics themselves should be feared. Indeed, he has described them as "miracle drugs" underpinning modern medicine. Rather, his argument is that society must recognise their potential harms alongside their benefits if these drugs are to be used safely and remain effective. That is the deeper connection between C. diff prevention and antimicrobial resistance.

Every unnecessary prescription represents an avoidable biological intervention in a patient's microbial ecosystem. Every appropriately avoided prescription reduces an individual's exposure to potential adverse effects while also reducing antibiotic selection pressure at population level.

Peggy Lillis' death occurred in 2010, but the science that followed has made its lesson increasingly difficult to ignore. Antibiotic stewardship is not simply a strategy for conserving medicines for some hypothetical future patient. It is a patient-safety intervention for the person sitting in the dental chair, clinic or hospital today.

Key sources

Posted by Dr. Tim Sandle, Pharmaceutical Microbiology Resources (http://www.pharmamicroresources.com/)

Saturday, 7 November 2026

History of the contact plate

A microbiological history: Agar contact plates are simple yet scientifically refined tools for pharmaceutical environmental monitoring. Developed as alternatives to surface swabbing, their performance depends on plate design, agar properties and sampling technique. What next? Automation may now reduce operator variability and improve microbial recovery consistency: