Dossiers. Agency questions. Inspections. Seal Submissions. Your dossier, drawn from the record.
In Seal Submissions, Neil drafts dossier sections and agency answers from the published record, each line linked to its source, for a person to sign.

3.2.P.5.1 Specification(s)
- ClarityClear to slightly opalescentQCM-002 v3
- ColourColourless to slightly yellowQCM-003 v3
- Visible particlesPractically free of particlesQCM-005 v4
- pH5.7 to 6.3QCM-007 v2
- Osmolality270 to 330 mOsm/kgQCM-008 v2
- Extractable volumeAt least the labelled volumeQCM-011 v2
- IdentityMatches the reference standardQCM-018 v3
- Assay95.0 to 105.0%QCM-014 v5
- Monomer, SE-HPLCAt least 95.0%QCM-021 v6
- CE-SDS, reducedAt least 95.0%QCM-023 v4
- CE-SDS, non-reducedAt least 92.0%QCM-023 v4
- Charge variants55.0 to 75.0%QCM-025 v3
- Potency, cell-based80 to 125%QCM-041 v5
- Binding, ELISA70 to 130%QCM-038 v4
- Polysorbate 800.15 to 0.25 mg/mLQCM-027 v2
- Subvisible particlesAt most 6,000 and 600 a vialQCM-012 v3
- Closure integrityNo leak in the sampleQCM-016 v2
- EndotoxinAt most 0.5 EU/mLQCM-031 v4
- SterilityNo growthQCM-033 v5
Neil's draft
For H. TanakaCharge variants
SPEC-DP-24 v3 gives 55.0 to 75.0% and does not say of which peak. QCM-025 v3 reports the main peak; lot 26-0917 read 64.1% main peak.
Every line, back to its source.
Today a section is pasted together from copies on a shared drive, and nobody can say which version a number came from.
| Compared on | Today | Seal Submissions |
|---|---|---|
| A dossier section | Pasted into Word from copies on a shared drive | Drafted by Neil from the published entities |
| A number in it | Checked by hand against a PDF | Linked to its entity and version |
| Who says it is right | Whoever saw the last copy | Its owner, who signs it |
| The agency's question | Chased round QC and QA | Answered from the record, each statement linked |
| The inspection | A war room and a binder of copies | A read-only room in the record itself |
The agency asks. The record answers.
Neil drafts the answer from the entities it rests on, each statement linked at its version, and a person approves it before it is sent.
Question 3
Explain how inhibition of the endotoxin test by the drug product is detected, and how it was resolved.
Drafted by Neil, 14:05
Every run of QCM-031 v4 is spiked, and a run whose spike recovery falls outside 50 to 200% reports no result.source 1
On lot 26-0917, run R-1005-02 recovered 31%. H. Tanaka, the QC manager, approved its assessment on Tue 10 Nov: the product inhibited the test.source 2source 3
The retest, R-1005-03 on Fri 13 Nov, was diluted further within the method's maximum valid dilution and read 0.12 EU/mL, against at most 0.5 EU/mL.source 4source 1source 5
Sources
Due Mon 7 DecThe inspector reads the record itself.
A read-only room scoped to what the inspection covers, keeping every request made in it and what was shown for each.

Line 2, from Tue 22 Sep
- 10Line 2's deviations since Tue 22 SepShown 09:15
- 11Training on SOP-FIL-007 v13, for Line 2's operatorsShown 09:26
- 12Media fill MF-26-02 and the interventions it coversShown 09:31
- 13The settle, contact and glove plates of lot 26-0917's fillShown 09:40
- 14How was lot 26-0917 released after an intervention its record did not show?Shown 09:58
- 15CAPA-019 and the feed track it replacedOpen
Request 14
Shown by S. Amato, 09:58Questions about Seal Submissions.
Can we buy Seal Submissions today?
Not yet: it is a proposal. What it rests on is shipped: published documents at a version with their sign-offs and history, changesets, read-only access, sharing a published document with a named person, and Neil's drafts, which a person signs.
Does Neil submit anything?
No. Neil drafts and says what it could not find; a person approves, signs and sends.
Who signs a section or an answer?
The person who owns it, in Seal, with their password or passkey, as every signature in Seal is given. Neil signs nothing.
Is it an eCTD publishing tool?
No. Your publishing tool still builds and validates each sequence; Seal gives it each approved section, as a PDF at its version.
Can we keep our publishing tool and gateway?
Yes. Seal does not connect to an agency: your people send each sequence through your own gateway, as they do today.
What does an inspector see, and change?
Only what the inspection covers, read-only: they read and make requests, and cannot edit, sign or comment. Read-only access in Seal today blocks creating, editing, running, commenting and signing.
Can Neil be wrong?
Yes. Every statement opens at its source and version for the person who approves it to read, and where Neil cannot tie a line to a source it says so rather than filling it in.
We make for clients. Who files?
Your client. You draft each section or answer from your own record, approve it and send them a read-only copy, and they file it; nothing else of yours is open to them.
How does it relate to RIMS?
RIMS keeps registrations and each market's approved state, in Seal's RIMS blueprint or the one you have. Submissions is where a section's or an answer's content comes from: the record.


See your process in Seal.
Working 48 hours after we agree its scope: tested, with evidence your QA approves.