A first cell-therapy BLA, filed on the planned date
A cell-therapy company's first biologics licence application (BLA) depended on manufacturing, quality, regulatory, R&D, clinical and supply work converging on one date. Opyflow led the programme office that held those commitments together and brought the filing in on the planned date.
When Opyflow was called in, each of the six functions was working to its own plan, and nobody was running the path to submission as a whole. Production slots were contested by studies, qualification and clinical supply, which also drew on the same specialists and the same review capacity.
As lead of the programme office across the six teams involved, Opyflow tied requirements to plans, tested scenarios and tracked approvals. Each decision went to the owner who had to make it.
First BLA filed on the planned date · Six functions run on one integrated plan
The challenge
The filing rested on a chain of evidence. Material from manufacturing went into studies, and the study results then had to become reviewed and approved reports before the submission sections could be finalised. A delay at any link could use up the time that every team downstream was counting on.
The same operation was also carrying clinical supply, training, maintenance and inspection readiness, and any run or study might have to be repeated. Leadership needed to see the consequences, and the options still open, while there was time to act on them.
Opyflow's work
Opyflow started from the requirements. The first mapping tied 43 activities to submission, qualification and related obligations and put them in one programme plan, each with its owner, operational needs, dates and risks. Manufacturing schedules were linked through to laboratory results and on to report writing, review, approval and publication. Each team could then see who was waiting on its work, and what its own delays did to the teams downstream.
The programme office then tested the plan against disruption. For qualification runs, stability studies, shipping validation and documentation, best, base and worst-case scenarios set out the assumptions and the contingencies. Alternative shutdown sequences were compared for their effect on production and clinical supply, and the reviews showed where a plan lacked a contingency and what a repeat run would do to later milestones.
Documents were managed as closely as manufacturing. In one critical preparation window the programme office tracked 29 reports, and regulatory colleagues picked out 12 that had to take priority to protect section review. Each report had its owner, review status, approval status and target date recorded, and daily tracking and joint comment-resolution meetings kept them moving.
Supply readiness for a planned fourfold production expansion sat in the same plan. After the filing, that plan went on holding outstanding studies, inspection preparation, capacity planning and launch activities together.
What changed
The BLA was filed on the planned date. Leadership also had a working basis for stepping in: it could see which report needed a decision, which approval was blocking the next activity, which production slot was contested and what a delay would change. The plan was managed at the level of individual runs, reports, reviewers and handovers.
Why run a BLA as one programme across six functions?
A functional plan covers one team's work, so the knock-on effect of its delays on the teams downstream stays out of sight. One programme plan connected each issue to its owner, its timing and its downstream consequence, and its reviews covered the evidence still needed, the approvals outstanding and the contingencies available.
See the capability: Complex project delivery →