The Seal Platform
WebsiteGet StartedContact Us
The Seal Platform
  • Website
  • Contact Sales
  • Logging in & System Requirements
  • Get Started Here
  • Moving to Seal
    • Migration
    • Implementation
  • Manage
    • Where do I start?
    • Creating Types
      • Documents
      • Work Done
      • Files
        • Extracting Fields with AI
      • Scripts
        • Script Action Buttons
      • Charts
      • Converting Between Types
    • Adding Content and Fields
      • Computed Titles
      • Formatting Text
      • Formulas
      • Numbered Lists
      • Setting Assignees
      • Setting Out-of-Specifications
      • Setting Review Requirements
      • Submission Tables
    • Writing Scripts with the Seal Module
    • Executing Types: Test Instances
    • Work Instructions
    • Change Sets
    • Checks
    • Active Versions
    • Training
    • API
  • Operate
    • Where do I start?
    • Re-executing Instances
    • Reviewing
  • MISC
    • Glossary
    • Inbox
    • Search Page and Saved Views
    • User Permissions and Roles
    • Tags
    • Github Integration
    • Change Management
    • Seal Changelog
  • Video Guides
    • Creating Templates
    • Creating and Reviewing Instances
    • Sending and Completing Trainings
  • Validation
    • Why do I need to validate my platform?
    • What is needed from my end for validation?
    • How is my system validated?
      • Baseline Validation
      • Configuration Validation
      • Compliance Validation
      • What about IQ, OQ, or PQ?
      • Automatic Revalidation
        • Change Controls
      • How do I know if my system is compliant to a standard?
        • Setting up your System
        • Performing Compliance Validation
    • GxP Validation for enterprise customers
    • Can I download a Validation Report?
      • Software Functionality Verification
    • Common Validation FAQs
  • Product Quality
    • Seal's Guarantee of Quality
    • Product Development Lifecycle
    • Platform Operation Tests
    • Incident Procedure
  • IT & Security Policies
    • Seal's Tech Stack
    • Data Storage and Security
    • Cloud Servers vs On-Premises File Servers
    • Data Backup and Disaster Recovery
    • Disaster Recovery Plan
    • Handling Confidential Data
    • Common IT FAQs
  • Regulatory Standards
    • 21 CFR Part 11
    • EU Volume 4 Annex 11
    • ISO 13485 Medical Devices
    • Clinical Laboratory Improvement Amendments (CLIA)
  • Support
    • Contact us
Powered by GitBook

Copyright © Seal 2025. All Rights Reserved.

On this page
  1. Validation
  2. How is my system validated?

Automatic Revalidation

Using Seal's Automated System Validation

Last updated 2 months ago

In Seal, the system undergoes Automated System Validation, after changes are made. This ensures that any change made to the system is re-validated.

Automated System Validation leverages on Change Controls. It is integrated into the Seal platform software - no changes can be made until a Change control has been performed and approved, ensuring that any change in Seal has no impact on other functionality of the overall system.

How do Change Controls tie in with re-validation?

In GxP companies, Change Control is a structured process used to manage, document, and implement changes in a controlled and systematic manner - this ensures that any modifications have been evaluated for their potential impact on quality and compliance.

Changes to the Seal Platform can disrupt critical functionalities and alter system behaviour. Change control ensures that:

  • What is changed in Seal has no impact on other functionality of the system

  • To document evidence of tests to show that system functionality is still the same

Having change control built into the Seal Platform ensures that any modifications to the system are documented, reviewed, and have been re-validated - ensuring your platform is consistently at a validated state.

Change Controls