SystemContract Manufacturing (CDMO)

CDMO Project Tracking & Status Reports

CDMO project management for drug-substance client projects: agents read the weekly call minutes line by line, place each open item on the side that owes the next move under the milestone it blocks, and compute the slack before a date moves. A change said on a call goes to its owner as a request, and the weekly status report is tested from the client's side before two people sign it.

See one client project's week, call to Friday report ↓
Watch with transcript →
The problem

The client's late answer reads as the plant's delay, and nobody sees the slack

Each client project runs on a weekly call, minutes typed the same evening, a tracker kept in a spreadsheet and a status report rebuilt by hand every Friday. What the client owes and what the plant owes sit in the same list, so a reference standard the client promised weeks ago looks like one more overdue line on the plant's side.

A sentence said on the call, such as agreeing to run validation at a larger batch size in a bigger reactor, lands in the minutes as a decision. The process owner has not assessed it, and the client has not asked for it in writing. Friday's report calls the protocol on track because nobody worked out that the slack before it is already gone.

Built forClient project managersMSAT leadsAccount directorsHeads of client project management

The Problem Today

Client and plant items share one tracker, and a change said on a call enters the minutes as agreed.

Kept by hand every week

  • Minutes
  • Tracker
  • Emails
  • Reports
  • Slack nobody computesA late answer looks harmless until the milestone moves
  • On track, untestedFriday's status is typed from memory, not checked against dates

The Solution

  1. Minutes read line by lineEach decision, action and question with who said it and on which line
  2. A change becomes a requestA batch size or reactor called agreed goes to its owner to assess
  3. Each item on the side that owes itUnder the milestone it blocks, with its age and the slack left
  4. Read from the client's side, then signedFriday's report read as the client would read it; two people sign

Built-in controls

  • A process change is never recorded as a decision
  • Nothing reaches the client until a person sends it
  • The maker of a report does not approve it

What You Get

The client sees each week what waits on it, and a late answer is caught while the date can still be saved.

  • Clients answer in their portalEach item they owe, why it matters and what closes it
  • Statuses that hold on MondayEach on track checked against the slack before it is sent
  • Every project reports on FridayMinutes read and reports drafted across all client projects
Features

CDMO project management for one scale-up heading into validation

A drug substance moving to commercial readiness: the project manager runs the week, the MSAT lead assesses a change said on the call, and the account director approves and sends the report.

demoEvery name, project, date and quantity on these screens is invented for the sample.

  1. 01Two sides

    Client project tracker splitting what the CDMO and the client owe

    • Each item on the side that owes the move. A client's late answer no longer reads as the plant's delay, in the tracker or in the report.
    • Under the milestone it blocks. The project manager sees which open item holds the protocol, the engineering batch or the first validation batch.
    • Age and the longest wait marked. The item that has waited longest stands out before it becomes the reason a milestone slips.
  2. 02Minutes

    Meeting minutes action items extracted line by line, with who said each

    • The minutes as filed, tinted by kind. Decisions, actions and questions are labeled on the line where they were said, so nobody retypes them into a tracker.
    • A promise with no date stays dateless. When the client says a standard should ship next week, the item records no date given and the chaser asks for one.
  3. 03Change screen

    A batch size change said on the call filed as a request, never a decision

    • Checked against the quality agreement's change list. A batch size outside the agreed range or a new reactor needs the client's prior written approval, so it cannot enter the minutes as agreed.
    • The batch records cited. The screener shows the largest batch actually made, so the request carries the reason it needs an assessment.
  4. 04Assess

    Process change assessment by the MSAT lead before anyone agrees

    • Records opened before the decision. The MSAT lead reads the batch records, the master production instructions and the reactor's record before choosing an outcome.
    • A drafted answer the owner can edit. The client's question on the engineering batch gets a draft the MSAT lead may rewrite, and a second signer checks it before it leaves.
  5. 05What-if

    Validation schedule what-if for a requested batch size change

    • Each milestone played forward. The cost of a change said on the call is on the table before anyone agrees to it.
    • What the sum leaves out, named. Protocol rework, calorimetry at the new charge and a cleaning limit for the new reactor are listed for the MSAT lead to size.
    • Editable assumptions. Lab days, client review days and release testing days recompute the dates when the project manager changes them.
  6. 06Requests

    Client requests drafted in fixed fields, sent only when the manager chooses

    • One request per item the client owes. Each says what is needed, by when, and which attachment or field closes it, so the client knows exactly what to send.
    • Outside email held for a person. An email from the client changes nothing until a person opens and files it.
  7. 07Challenger

    Project status report checked from the client's chair before signing

    • Every on track tested against the slack. The challenger caught the report writer calling the protocol on track when it holds only if the standard arrives by Friday of next week.
    • Waiting on you comes first. The report opens with what the client owes, each with when it was asked and what it blocks.
  8. 08Sent

    Weekly status report approved by the account director, then sent

    • Prepared by one person, approved by another. The project manager marks the report prepared; the account director checks the order book, approves and sends it.
    • A later change clears the signatures. An edit after signing moves the version and the report must be signed again.
  9. 09Client portal

    CDMO client portal where the client answers its own items

    • Only what a person has sent. The client sees its own project, the items it owes and the signed report, and none of the agents' drafts.
    • Answers in fixed fields. Status, date and attachment close an item only when the right document is attached.

The project manager runs the week, the MSAT lead owns any change

Who buys and runs client projects at a contract manufacturer.

Client project managers

Run each client project's call, minutes, open items and Friday report

  • Minutes read and items placed for them
  • Slack computed for each milestone
  • A report drafted and challenged first
MSAT leads

Assess each process change said on a call before anyone agrees

  • Requests with the batch records attached
  • The schedule cost shown before deciding
  • Answers to clients they can edit
Account directors

Approve and send the weekly report and own commercial items

  • Statuses tested before they sign
  • The order book one click away
  • Nothing sent in their name unread
Heads of client project management

Oversee every client project and approve learned rules and settings

  • Each project's report status in one list
  • Reports drafted in bulk
  • Rules that change behavior only once signed

The report writer's own on track was the first thing the challenger flagged

A protocol called on track with no slack left

The standard it waits on was asked forty days ago; the protocol holds only if it arrives by Friday of next week.

A larger batch called agreed on the call

No batch near that size had been made, and the quality agreement needs the client's written approval first.

A promise that named no date

A promise that the standard should ship next week was recorded as no date given, and the chaser asked for one.

A missing purchase order checked in the order book

The report said none had arrived; the account director opened the order book and confirmed it before approving.

A change screener keeps a call's agreement out of the minutes as a decision

Seven agents read, place, rehearse, chase, draft and challenge; people sign what leaves the company.

Minutes reader

Extracts each decision, action and question from filed minutes and opened email, with speaker, line and confidence.

  • Reads no email a person has not opened
  • Invents no date nobody said
Change screener

Checks decisions against the quality agreement's change list and the batch records, and files changes as requests for their owner.

  • Records no process, filing or agreement change as a decision
  • Assesses no change itself
Court keeper

Places each item on the side that owes it under the milestone it blocks, with its age and the slack.

  • Closes no item without its closing record
  • Types no slack by hand
Schedule rehearser

Plays options forward with assumptions the project manager can edit.

  • Changes no agreed schedule
  • Calls no rehearsal a plan
Chaser

Drafts one structured request per client item on its clock and reads replies only as fields and attachments.

  • Sends nothing before the project manager approves
  • Reads no client free text
Report writer

Drafts the weekly report with what waits on the client first, each line from an item or a record.

  • States no status without its source
Client challenger

Reads the report the way the client's external manufacturing lead would, testing each on track against the slack.

  • Fixes nothing itself
  • Speaks for no client
More screens

Seventy client projects, and nine with no minutes since the last report

Around the one project: the portfolio, the agents and their rules, the trail and the settings.

Every client project's Friday report in one listProjects across five plants with what each side owes, the longest wait and this week's report status; a project with no minutes filed is blocked, and the screen says why.
Corrections become rules only once signedEach agent's plan, conclusion, sources and hand-off; a rule learned from the project manager's corrections waits for the head of client project management to approve it.
Who sent what to the client, and whenAgents and people on one trail with session and signature meaning, from the minutes approval to the report's delivery receipt, downloadable as a CSV file or evidence pack.
Which changes said on a call need which ownerChase clocks, signer reading time and the change list: batch size and equipment go to the MSAT lead, a supplier to the QA head, each needing the client's prior approval.

demoSample data, from the working solution.

A batch size said on a call stays a request until the MSAT lead assesses it

Agreeing a process changeThe MSAT lead assesses it, and the client asks for it in writing under the quality agreement before anything changes.
Approving the minutesThe project manager approves them, and a line typed by hand waits until the account director has read the exact words.
Sending the weekly reportThe account director approves and sends it, after the project manager prepared it; neither signs the other's step.
Answering a quality questionThe MSAT lead signs the answer, and a second signer countersigns or sends it back before the client sees it; an approved rule makes that the plant QA head.
Changing a rule or a clockThe administrator proposes and the head of client project management approves with a signature.

What CDMO project managers ask about CDMO project management

What is CDMO project management?

CDMO project management is running a client's program at a contract manufacturer: the weekly call, minutes, open actions on both sides, milestones and the status report. Here agents read the minutes, place each item on the side that owes it and draft the report, and people approve what is sent.

Why split what the client owes from what the plant owes?

Because a late answer from the client and a late task at the plant need different actions. Shown on one list, the client's delay reads as the plant's, and nobody asks the client in writing while the date can still be saved.

What happens when a change is agreed on a call?

If it touches the process, equipment, a specification, a filing or the agreement, it is filed as a request for its owner, never as a decision. The quality agreement and ICH Q7 ask for the client's approval before such changes are made.

How is the weekly status report checked?

A challenger reads the draft from the client's chair and tests each on track against the slack. The project manager fixes what it finds and marks the report prepared, and the account director approves and sends it.

What does the client see in its portal?

Its own project only: the items it owes with what closes each, the milestones and the signed weekly report. Agent drafts stay out of the portal until a person sends them, and the client answers in fixed fields.

Does it replace the project tool we use?

It reads the minutes, email a person has filed and the plant's own records, and works beside the schedule. What it adds is the side each item sits on, the slack before each milestone and a report tested before it is sent.

Bring one client project
and last week's minutes.

Send the minutes, the tracker and the schedule; we place each item on its side and draft Friday's report.