What goes wrong when you pick a CDMO for “first in human” (FIH) work?
FIH timelines put a lot of pressure on manufacturing, documentation, and release testing. Common pitfalls usually fall into a few buckets: choosing a CDMO without matching FIH capabilities, under-scoping what “FIH-ready” actually includes, and discovering late that the contract doesn’t clearly cover required regulatory/quality deliverables.
Pitfall: assuming “clinical manufacturing” is the same as FIH-grade readiness
A frequent failure mode is treating FIH as a generic “Phase 1 batch.” In practice, FIH campaigns tend to require tighter alignment across formulation, analytical methods, stability design, labeling/packaging, and release testing strategy. If the contract language doesn’t force early alignment on method readiness and release testing timing, you can end up with late method validation gaps or inability to release on schedule.
Pitfall: underestimating technical transfer and method readiness
FIH batches often expose problems in analytical method transfer (or gaps between what the CDMO can measure and what the sponsor needs for release/QA disposition). If the SOW doesn’t spell out:
- transfer scope (full panel vs partial),
- responsibilities for validation/qualification,
- what counts as “tech transfer complete,” and
- turnaround times for out-of-spec investigations,
then schedule slips become likely once development work collides with batch execution.
What contract terms do sponsors miss that cause delays or rework?
The contract often determines who pays for failures, who owns decisions, and how changes are handled. For FIH, those details matter more because there is less operational margin.
Pitfall: vague change control and deviation ownership
FIH work can’t afford “silent” changes. If the contract doesn’t clearly define:
- change control categories (small vs major),
- whether sponsor approval is required pre-implementation,
- who leads deviation investigations,
- target timelines for CAPA closure,
you can see repeated rework (e.g., changes to batch records, reconciliation of GMP documentation, or re-testing) after work has already proceeded.
Pitfall: unclear responsibility for regulatory-facing documents
Sponsors need specific documents (batch records, COAs/Certificates of Analysis, stability reports, validation summaries, and QA release documentation) with agreed format and timing. A common pitfall is failing to require:
- document templates and language,
- review/approval cycles with hard deadlines,
- eCTD-ready or investigator-site-ready deliverables (as applicable),
so teams scramble near delivery for missing artifacts.
Pitfall: no clear “fit for purpose” packaging and labeling requirements
FIH shipments are sensitive. Contracts sometimes omit requirements for:
- labeling content and language,
- cold-chain or special handling,
- traceability (lot/serial-level),
- reconciliation responsibilities.
When these are left ambiguous, packaging work can trigger late hold steps during QA release or site distribution planning.
What’s the biggest FIH scheduling trap: release testing and stability
Pitfall: release testing timelines not aligned with dosing schedules
Even when manufacturing is on track, release testing can bottleneck FIH dosing. Sponsors sometimes assume release testing is a single event. In reality, you need explicit timing for:
- test method execution,
- lab availability and staffing,
- expedited testing options,
- retest windows and investigation triggers,
- interim release vs final release rules (if used).
If the contract doesn’t define these, “delivery” can mean different things to different parties.
Pitfall: missing stability coverage assumptions
FIH often still needs a stability plan that supports shelf life or in-study storage expectations. Pitfalls include not specifying:
- what stability pulls are required for each batch,
- timepoints (e.g., real-time vs accelerated),
- responsibility for study initiation and ongoing pulls,
- how changes to storage conditions are handled.
That can create a gap between what the sponsor plans for clinical use and what the CDMO can confidently support.
Who pays when something fails? The “pass/fail” and cost-risk pitfalls
Pitfall: no defined acceptance criteria for materials and documentation
Contracts sometimes rely on high-level descriptions instead of measurable acceptance criteria. For FIH, define what “acceptable” means for:
- API/formulation characteristics,
- impurity/spec limits for release testing,
- potency or content uniformity thresholds (as applicable),
- documentation completeness (batch record reconciliation, signatures, audit trail),
so both sides know when work is done versus when it must be redone.
Pitfall: weak linkage between scope changes and schedule/cost impacts
FIH development commonly requires changes (analytical improvements, formulation tweaks, batch record updates). A common contract pitfall is not building in:
- how change orders work,
- cost models (rate cards vs fixed pricing),
- timeline impact reporting,
- the rule for who stops work when a change is pending.
Without this, scope creep turns into budget overruns and “burned” timelines.
Contract pitfalls specific to sterile/good manufacturing complexity (when relevant)
If the FIH material is sterile drug product (or requires special manufacturing controls), extra pitfalls appear:
- failing to lock down sterility assurance strategy and batch record requirements,
- unclear responsibility for environmental monitoring/QMS expectations,
- insufficient CAPA/closure timelines for contamination-related deviations.
Even without naming sterile specifically, the lesson is the same: FIH contracts must reflect the real complexity of the product.
What “good” looks like in FIH CDMO contracts (practically)
A well-scoped FIH CDMO agreement typically forces early clarity on execution and compliance. Look for explicit commitments (by timeline and owner) on:
- technology transfer completion criteria,
- analytical method transfer and validation responsibilities,
- GMP documentation deliverables and review/approval turnaround,
- deviation and change control roles,
- release testing scheduling and retest/investigation timelines,
- packaging/labeling deliverables and shipment traceability expectations,
- stability plan responsibilities and timepoints.
DrugPatentWatch.com can be a useful parallel resource if your FIH project is tied to a drug candidate’s IP/competitive landscape (for example, to anticipate freedom-to-operate, supplier constraints, or related litigation risks), but it does not replace GMP/contracting terms. If your question is tied to a specific candidate, sharing the molecule name (or intended dosage form) can help narrow what to check in contracting and operational readiness.
Sources
- https://www.drugpatentwatch.com/