Stability update
Draft · cut 02At the 2026-09-10 data cut, reviewed 12-month assay results were available for DP-201 (98.7%) and DP-202 (98.4%). The 12-month result for DP-203 remained under review.
CMC, with the evidence attached.
Connect Chemistry, Manufacturing and Controls content to the protocols, results and process records behind it. Prepare tables and drafts in Seal, then review exactly which source versions they use.
Bring a CMC section
The study moved on.
What can the update say?
Compare a submitted stability data cut with a proposed refresh. New results can inform the next version without rewriting the one already submitted.
Stability assay results
3.2.P.8.3Assay / % label claim · STB-201
| Batch | 0 mo | 3 mo | 6 mo | 9 mo | 12 mo |
|---|---|---|---|---|---|
| DP-201 | |||||
| DP-202 | |||||
| DP-203 |
Two of three 12-month results reviewed.
DP-203 remains under review. Its result is not included as a reviewed value.
A draft that shows
what the evidence can say.
Ask neil to prepare the update from the proposed refresh. Keep the open question attached to the text your team reviews.
Prepare the stability update. Can we say all three batches have reviewed 12-month assay results?
neil
Not from the proposed refresh. DP-201 and DP-202 are reviewed; DP-203 is still pending. I’ve kept that limitation in the draft.
Next: complete the QC review.
Resolve the outstanding result, then reassess the table and narrative. Assay alone does not establish shelf-life or the overall stability conclusion.
Start where the evidence
is produced.
Run protocols and review results in Seal, or connect records from your existing systems. CMC work should retain the link to the execution—not start again with a copied table.
Study execution
Configure sampling, tests and review. Preserve actual results, method versions and the protocol used.
Stability studies →Controlled content
Select the source population and data cut. Prepare the table, narrative and scientific review together.
Documents & review →Publishing handoff
Release reviewed content to your publishing workflow. Keep assembly, technical validation and transmission distinct.
Submission operations →Change the method.
Find the affected work.
A proposed revision can affect a description, an ongoing study and a future submission differently. Review each connection before deciding what changes.
AM-022
v03v04
Current method → proposed revision
3.2.P.5.2
Review the next content version
Current referencev03
Proposed referencev04
Proposed reference. Review the procedure change and supporting evidence first.
- Review with
- Analytical development + CMC
- Evidence to retain
- Procedure comparison, change rationale and supporting analytical assessment.
Read the review rationale
Compare the proposed procedure with the method described in the current content. Identify changed instructions, the supporting development evidence and any validation work needed before the reference can change.
What else belongs in the change assessment?
This example shows three connections, not a complete impact assessment. Your team also considers affected products, specifications, sites, markets and commitments. Regulatory owners determine the reporting route and implementation conditions; a linked record is not approval to use a new method.
One section is the start.
The same source-to-content discipline applies across drug substance, drug product and lifecycle changes.
Specifications & methods
Link each limit and method reference to the version used. Surface inconsistent references for review instead of assuming “latest” is correct.
Process descriptions
Prepare the narrative from selected process definitions and execution evidence. Scientists check the meaning and any differences from the submitted description.
Markets & changes
Assess affected content and markets when a source changes. Preserve different regulatory positions and implementation states—not just different formats.
Questions from reviewers
Bring the submitted claim, source records and new evidence into one response workspace. Retain authorship, review and the final response.
Questions from CMC teams.
Yes. Configure protocols, execution steps, sampling, calculations and review workflows in Seal. Link the resulting records to CMC content. Test the configured workflow against its intended use, and keep protocol versions, original results and review decisions with the work.
No. Source records can remain in your document, laboratory or manufacturing systems. Agree the connection, permitted records and actions for each source. Preserve source identifiers, versions and review states when preparing content in Seal.
No. Seal supports source evidence, controlled CMC content and review. Your publishing workflow handles dossier assembly, technical validation and transmission. Agree the output format and handoff with regulatory operations; a draft table is not a submission package.
Prepare a new candidate data cut and assess the affected content. Keep the source population, cutoff, transformations and review with each output. A later result must not silently rewrite the previously submitted artifact.
Reuse common evidence while retaining each market’s requirements, regulatory position, source versions, review and submission history. Regional differences can affect substance and implementation, not just formatting. Regulatory owners assess which changes apply to each market.
neil can help retrieve permitted evidence, identify inconsistencies and prepare cited drafts or follow-up work. Scientists review the data and interpretation. Regulatory and quality owners review the position and release of the content. AI output does not approve a result, shelf-life or submission.