Stability Documentation & Record Control: Step-by-Step Guide

This guide turns the scenario-driven approach into an actionable rollout. Follow the steps in order; each includes action, owner, deliverable, and acceptance so you can execute and verify.

Step 1 — Publish the Two-Minute Rule

Action: Set the program’s North Star: any stability value reported publicly can be traced to its native record in ≤ 2 minutes.

• Owner: QA + Stability Lead
• Deliverable: One-page policy (approved in eQMS)
• Acceptance: Visible on the quality portal; referenced in SOPs

Step 2 — Lock the Vocabulary (Glossary)

Action: Freeze terms for conditions, units, model names, and time/date formats.

• Owner: Stability Lead + Regulatory
• Deliverable: Controlled glossary artifact
• Acceptance: Terms match across protocols, summaries, and submissions

Step 3 — Build the Footer Library

Action: Create copy-ready footers for assay, degradants, dissolution, appearance—before any figures/tables are added.

Footer (required):
LIMS SampleID ###### | CDS SequenceID ###### | Method METH-### v## | Integration Rules INT-### v##
Chamber Snapshot: CH-__/__-__ (monitor MON-####, ±2 h)
SST: Resolution(API:critical) ≥ 2.0; %RSD ≤ 2.0%; retention window met

• Owner: QA Documentation
• Deliverable: Word templates with locked footer blocks
• Acceptance: New reports cannot be saved without a footer (template macro or pre-check)

Step 4 — Connect Systems by IDs (No Re-Typing)

Action: Ensure LIMS sample IDs flow into CDS sequences; CDS writes SequenceID/RunID back to LIMS; eQMS events store hard links.

• Owner: IT/CSV
• Deliverable: Validated import/export or API link; configuration record
• Acceptance: Zero manual typing of IDs during routine runs (spot checks pass)

Step 5 — Create the Stability Records Index

Action: Nightly job builds a single index mapping Product → Lot → Condition → Time → Document Type → File/URI → LIMS SampleID → CDS SequenceID → Method/Rule versions → Monitoring link.

• Owner: IT/CSV + QA
• Deliverable: Controlled CSV/database view with change log
• Acceptance: Two random table values traced to raw in ≤ 2 minutes using the index

Step 6 — Shallow Repository, Short Filenames

Action: One shallow product container; short neutral filenames with version suffix (_v##). IDs live in footers and the index, not filenames.

• Owner: QA Documentation
• Deliverable: Repository standard + auto-archive of superseded versions (read-only)
• Acceptance: Path length < 120 characters; filenames stable and human-scannable

Step 7 — Raw-First Review Workflow

Action: Make reviewers start at raw data every time.

Raw-First Reviewer Checklist
1) Open CDS by SequenceID; confirm vial → sample map
2) Verify SST (Rs, %RSD, tailing, window)
3) Inspect integration events at the critical region (reasons present)
4) Export audit trail (attach true copy)
5) Compare to summary; record decision + timestamp

• Owner: QC + QA
• Deliverable: SOP + training module; checklist in use
• Acceptance: Audit evidence shows reviewers attach audit trails and note raw-first checks

Step 8 — One-Page Event Skeletons (Excursion, OOT, OOS)

Action: Standardize event files so they read the same way every time.

Trigger & rule → Phase-1 checks → Hypotheses → Tests & outcomes → Decision & CAPA → Evidence links

• Owner: QA
• Deliverable: Three controlled templates (Excursion / OOT / OOS)
• Acceptance: New events fit on one page plus attachments; decisions cite rule version

Step 9 — Time & DST Discipline

Action: Synchronize clocks via NTP; encode pull windows with timezone/DST rules; store timestamps with offsets; display absolute dates (YYYY-MM-DD).

• Owner: IT/Engineering + Stability
• Deliverable: Time-sync SOP; validated controller/monitor settings
• Acceptance: Post-DST audit shows no missed/late pulls due to clock drift

Step 10 — Chamber Snapshot Linkage

Action: Auto-attach the ±2 h chamber log reference to each pull record; reference in report footers.

• Owner: Stability + IT/CSV
• Deliverable: LIMS configuration or script to tag pulls with snapshot IDs
• Acceptance: Every pull reviewed shows a working chamber link

Step 11 — True Copy Strategy

Action: When records leave source systems, export with hash, export time, operator, and a pointer to native IDs; qualify viewers for old formats.

• Owner: QA + IT/CSV
• Deliverable: SOP + viewer qualification report; hash manifest
• Acceptance: Random legacy files open cleanly; hashes match

Step 12 — Protocol & Summary Templates (Locked)

Action: Protocols include machine-parsable pull windows and a declared analysis plan; summaries enforce footers and fixed units/codes.

• Owner: QA Documentation + Stability
• Deliverable: New templates with version control
• Acceptance: Reports cannot be finalized if footers/units are missing (macro or checklist gate)

Step 13 — OOT/OOS Investigation SOP

Action: Two-phase approach: Phase-1 hypothesis-free checks; Phase-2 targeted tests with orthogonal confirmation; list disconfirmed hypotheses.

• Owner: QA + QC
• Deliverable: SOP + job aids; training
• Acceptance: Case files show disconfirmed hypotheses and rule citations

Step 14 — Retention & Migration Plan

Action: Define retention by record class; keep native + PDF/A true copies with checksums; validate migrations with pre/post hashes; maintain a read-only image until sign-off.

• Owner: QA Records + IT/CSV
• Deliverable: Retention schedule; migration protocol & report
• Acceptance: Quarterly “open an old file” test passes 100%

Step 15 — Training that Proves Skill

Action: Replace slide decks with performance assessments: raw-first review drills, excursion decisions with numbers, integration challenges with reason codes.

• Owner: QA Training + QC
• Deliverable: Micro-modules (15–25 min) + scored drills
• Acceptance: Manual integration rate and pull-to-log latency improve post-training

Step 16 — Retrieval Drill SOP (Rehearse, Don’t Hope)

Action: Time the walk from summary value to native record.

Sample: 10 values/quarter (random)
Target: ≤ 2 minutes value → raw file & audit trail
Escalation: CAPA if > 10% exceed target

• Owner: QA + Stability
• Deliverable: SOP + dashboard
• Acceptance: Median retrieval time meets target; CAPA opened if drift occurs

Step 17 — Metrics & Dashboards

Action: Track leading indicators that predict inspection pain.

• Traceability drill time (median and tail)
• “Footerless” artifacts (target 0)
• Manual integrations without reason (target 0)
• Audit-trail review latency (≤ 24 h)
• Migrated file open failures (target 0)

• Owner: QA + IT
• Deliverable: Live dashboard
• Acceptance: Monthly review shows trends and actions

Step 18 — CTD/ACTD Output Without Retyping

Action: Export stability tables/footers directly into Module 3; include a standard paragraph for models/pooling; attach event one-pagers as appendices.

• Owner: Regulatory
• Deliverable: Export scripts/macros; authoring guide
• Acceptance: Two-click trace from dossier value to raw via footers and index

Step 19 — Governance Cadence

Action: Keep the system clean with short, frequent reviews.

• Monthly: one product “data walk” (trace two values, open one event, read one audit trail)
• Quarterly: retrieval drill + template check + privilege review

• Owner: QA + Stability + IT
• Deliverable: Minutes & action logs in eQMS
• Acceptance: Actions closed on time; metrics improve or hold

Step 20 — Pre-Inspection Sweep

Action: Run a focused, evidence-first sweep before any inspection.

• Pull two random summary values; walk to raw & audit trail in ≤ 2 minutes
• Open the latest excursion and OOT file; confirm rule citations and numeric rationale
• Open a legacy chromatogram from a retired system; verify viewer and hash

• Owner: QA
• Deliverable: Sweep checklist + fixes
• Acceptance: Zero “couldn’t find it” moments; all links and viewers functional

Copy-Paste Blocks (Use as-is)

Analysis Plan (Protocol)

Model hierarchy: linear → log-linear → Arrhenius, selected by fit diagnostics and chemical plausibility.
Pooling: slopes/intercepts/residuals similarity at α=0.05; otherwise lot-specific models.
OOT detection: 95% prediction intervals; sensitivity analyses for borderline points.
Events: excursions per EXC-003 v##; OOT/OOS per OOT-002/OOS-004.
Traceability: each value carries LIMS SampleID and CDS SequenceID in footers.

Event Summary (Report)

An overnight RH excursion (+8% for 2.7 h) occurred at CH-40/75-02.
Independent monitoring corroborated duration/magnitude; recovery met the qualified profile.
Packaging barrier (Alu-Alu) and pathway sensitivity indicate negligible impact on impurity Y.
Data included per EXC-003 v02; conclusions unchanged within the 95% prediction interval.

Finish Line. When these 20 steps are in place, your stability record becomes a living evidence chain: identity born in systems, echoed in footers, retrievable in two clicks, and durable across software lifecycles. That’s how reviews move faster and inspections stay calm.