Write the report and decide every proposed range
- Each edge drawn against its runs
- Sourced rewrites for disproved sentences
- Tables built from the notebooks
A process development report in which each proposed range is drawn against the notebook, kilo-lab and plant runs behind it, each sentence opens the runs that prove it, and the client answers section by section in fields.
See one crystallization stage weighed against its runs ↓A drug substance development report is assembled by one chemist from hundreds of notebook entries, the kilo-lab reports, the first plant batch records and a design study. Tables are retyped from spreadsheets. Proposed ranges creep wider than the runs behind them: an edge reached only in a one-liter flask is called proven, a strong word rests on a single run, and a sentence carried over from an earlier draft contradicts an experiment done since.
Each of those becomes a comment from the client's CMC reviewer, a question from the agency after filing, or a PPQ acceptance criterion the plant cannot meet. The same ranges are then typed again into the impurity risk assessment and the PPQ protocol, and when one document changes the others quietly fall behind.
Built forProcess development chemistsProcess development group leadsMSAT leadsAnalytical development scientists
A range edge reached only in a flask gets written up as proven, and the client's reviewer finds it before the author does.
Assembled by hand from
Built-in controls
One sourced set of claims carries the report, the impurity assessment and the PPQ protocol, and the next client's report starts from it.
The salt formation and crystallization stage of one drug substance report, read by the agents, decided by the chemist, released by the group lead and answered by the client.
demoThe CDMO, its client, the people, the records and the figures are sample data.
Who writes, checks and releases one development report.
Write the report and decide every proposed range
Approve each report and release its sections to the client
Agree the scale claims for the receiving plant
Verify the results the report quotes
A notebook run at 45 °C with fast cooling gave Impurity B at 0.21% against NMT 0.15%; the design study showed the effect only when seeding low and cooling fast.
A kilo run supporting the fastest cooling edge used the unmilled seed from the earlier route; struck out, that edge now rests on lab runs only.
The sulfonate ester rose about 0.5 ppm an hour during the hold, and no run at any scale went past 4 hours; the hold was narrowed to 2 hours.
The draft gave 88–92% at plant scale; the five plant batch records read 86.4% to 89.7%.
demoSample data, from the working solution.
Around the report: the client's portal, sign-off, the claims list, versions, the audit log and the scale rule.
demoSample data, from the working solution.
Seven agents read and propose; the chemist decides and the group lead approves.
Reads each notebook experiment's charges, conditions, observations and results, and places it on each range it informs.
Reads kilo-lab reports, plant batch records and certificates, and checks seed lot, equipment and scale for each.
Fits the design study and explains its effects and interactions in plain words.
Ties each sentence to the runs that prove it and marks claims that are weaker than their words or lab scale only.
Reads each sentence against the runs and the model, and opens the record that disproves it.
Proposes a narrower range, lab scale only wording or a named experiment for each gap, and assembles the client package.
Plays the client's CMC reviewer and the agency against the draft and against the agents' own links.
A process development report records how a drug substance process was developed: the route and its history, the critical quality attributes, each stage's studies and the proposed normal and proven ranges. For a CDMO it is owed to the client, and it underlies the manufacturing process development section of the client's filing.
Following ICH Q11: a narrative summary of attributes and parameters, the process history linking each batch to its stage of development, and each study with its ranges discussed against the proposed operating conditions.
Under the scale rule the MSAT lead set, only when a run at kilo or plant scale reached the edge and met every attribute. An edge reached only in the lab is narrowed, labeled lab scale only, or given a named experiment, and the chemist decides which.
The analyst fits the study and states interactions in plain words. When an impurity rises only with low seeding and fast cooling, the proven range for one is written with the other inside its normal range.
The process development chemist decides each range; the agents only propose. Analytical development verifies results, the MSAT lead agrees scale claims and plant QA checks the GMP batch data. The group lead releases each section and approves the report, and nobody approves their own.
In a portal showing only that client's released sections. The client's CMC reviewer accepts or questions each one with a reason from a fixed list; a free-text comment goes to the author and blocks approval until a person reads it.
No. They read the notebook, the chromatography system, LIMS, the batch records and the documents; nothing is written back to any of them. A change after a signature clears that section's signatures.
Only the methods a new chapter truly binds are revised, each tested on the lab's own runs before the day it becomes official.
1-min demoNitrosamine Risk AssessmentRisk that travels between products through shared solvent, water and equipment is found before a batch tests positive.
1-min demoAPI Impurity Profiling & InvestigationInvestigations that start from the chemistry, with a rising unknown caught before a limit.
1-min demoSend one stage's notebook entries, kilo-lab reports and the draft section; we will draw each proposed range against its runs.