Prompt
How do I ensure my ANDA submission workflow with submission management software is compliant with 21 CFR Part 11?
Latest observation
To make an ANDA submission workflow compliant with 21 CFR Part 11 when using submission management software, focus on the combination of validated systems, controlled processes, secure records, and trustworthy electronic signatures. Part 11 is less about the software alone and more about whether your end-to-end electronic workflow can be shown to be trustworthy, reliable, and equivalent to paper records/signatures.
Key compliance areas
1) Validate the submission management system
Your software should be validated for its intended use.
- Define intended use and user requirements for the ANDA workflow
- Perform risk-based validation:
- Installation Qualification (IQ)
- Operational Qualification (OQ)
- Performance Qualification (PQ)
- Test critical functions such as:
- document upload/version control
- metadata accuracy
- workflow routing and approvals
- e-signature application
- audit trail generation
- access control
- archive/retrieval
- Maintain validation documentation and change control
2) Establish strong access controls
Only authorized users should be able to create, modify, approve, or submit records.
- Unique user IDs for each person
- No shared accounts
- Role-based permissions
- Least-privilege access
- Periodic user access reviews
- Immediate deactivation of terminated users
3) Use compliant electronic signatures
If signatures are used for approvals or submission sign-off, they must meet Part 11 requirements.
- Each signature must be uniquely tied to one person
- Identity must be verified before issuing credentials
- Use at least two authentication components for signing:
- something the user knows (password/PIN)
- something the user has/controls in the system session
- Signatures must clearly show:
- signer’s name
- date/time
- meaning of the signature (e.g., review, approval, submission authorization)
- Signature/record linkage must prevent undetected alteration
4) Maintain secure, computer-generated audit trails
The software should automatically record who did what and when.
Audit trails should capture:
- record creation
- edits and deletions
- version changes
- approval/rejection actions
- signature events
- login/logout and failed access attempts where relevant
Audit trails must:
- be tamper-evident
- be time-stamped
- be retained with the record
- be reviewable by QA/regulatory staff
5) Ensure records are complete, accurate, and retrievable
Part 11 expects records to be trustworthy and available throughout retention periods.
- Preserve original or true copy records
- Ensure eCTD and associated documents remain readable and complete
- Use controlled formats and approved templates
- Archive records with metadata, versions, and submission history
- Be able to retrieve records promptly for FDA inspection or internal review
6) Control document versioning and submission content
ANDA submissions are highly sensitive to version control.
- Use controlled workflows for drafting, review, approval, and final publishing
- Prevent unauthorized overwriting of approved documents
- Maintain traceability from source documents to final submission content
- Confirm the final compiled submission matches approved content
- Lock final submission packages after approval
7) Define SOPs for electronic workflow
Technology alone is not enough; you need documented procedures.
Common SOPs include:
- system access and account management
- document preparation and approval
- e-signature use
- audit trail review
- record retention and archival
- deviation management
- periodic system review and revalidation
- electronic submission publishing and QC checks
8) Train users
Users must understand both the system and compliance requirements.
Training should cover:
- Part 11 basics
- how to sign electronically
- how to review and approve documents
- data integrity expectations
- prohibited practices like account sharing or offline “shadow” files
Keep training records.
9) Perform periodic review and ongoing compliance monitoring
Part 11 compliance is ongoing.
- Review audit trails periodically
- Reassess user access
- Monitor system changes and patches
- Revalidate after significant updates
- Investigate deviations and CAPAs
- Conduct periodic internal audits
10) Address supplier and hosted/cloud considerations
If the software is vendor-hosted or cloud-based, you are still responsible for compliance.
- Qualify the vendor
- Review quality agreements
- Understand data ownership, backup, and recovery
- Confirm audit trail access and export capability
- Confirm system validation package and change notifications
- Ensure disaster recovery and business continuity controls
Practical checklist for your ANDA workflow
Before using the software for actual submissions, verify that you have:
- user requirements documented
- system validation completed
- SOPs approved
- unique user accounts and role-based access
- secure, compliant e-signatures
- audit trails enabled and reviewed
- document/version control in place
- archival and retrieval procedures tested
- training completed
- vendor qualification completed
- change control and periodic review process established
Important note
For FDA submissions, Part 11 compliance is usually evaluated alongside:
- 21 CFR Part 312 / 314 requirements for submissions
- eCTD technical standards
- data integrity expectations
- any applicable FDA guidance on electronic submissions and records
So your workflow should be compliant not only in the software features, but in the governance around how the software is used.
Best practice
Create a short Part 11 compliance matrix mapping each regulatory requirement to:
- system functionality
- SOP/procedure
- validation evidence
- responsible owner
That makes inspection readiness much easier.
If you want, I can also provide:
- a Part 11 compliance checklist for ANDA submission software, or
- a sample validation and SOP framework for this workflow.