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
        • Writing Scripts with the Seal Module
        • 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
    • 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
  • General
  • Revalidation
  • Documentation
  • Misc
  1. Validation

Common Validation FAQs

General

How long does validation take?

Seal has automated a large portion of the validation process, making this quick and easy - no more waiting for weeks and months! There is also little work from the customer end.

Speak to our Seal Team for a better gauge of timeframe.

When should I validate my system prior to use?

This would largely depend on your implementation timelines, and when you want to start using various modules in Seal.

In our experience, we recommend validating when implementation is fully completed, with everything built and set up.

We, however, have customers that prefer validation in phases.

How do you ensure that validation is compliant with regulatory standards?

Let the Seal team know which regulatory standards you need to be compliant to.

Our Seal experts will be able to ensure the correct compliance validation is carried out.

Will Seal provide support if I would like to conduct validation myself?

Yes, we do provide support if you prefer to conduct validation yourself. Seal's documentation can be re-purposed to fit your QMS.

Revalidation

If Seal performs tests on the platform, does that mean I don’t need to validate the system myself?

Seal provides baseline validation testing for all our customers. You could perform a repeat of these functionality tests, although we tend to not recommend this as this would be a repeat of validation work.

The additional testing required would be due to specific system configurations that are built into Seal, to fit your organisational workflows. Speak to our team to find out how we can help with this process.

How often do I need to revalidate?

You will need to re-validate when any changes have been made within your platform.

Not to worry, Seal makes this easy as we have productised automatic system re-validation into our platform. It is largely automated - re-validate your platform with just a click of a button!

Do I need to revalidate if I add new templates and make changes to workflows?

Whilst one would need to validate the template (or changes made), we’ve made this process incredibly easy within our system, productising much of the work!

You will also have access to our Seal's Team for any technical or general support.

Do I need to revalidate my system if my organisation moves to a new site?

As there would be no change in the physical server locations, databases, or in the core system architecture upon moving, this should not be needed.

Our Customer Success team can support you in the creation of any risk assessments required.

Documentation

Does Seal provide validation templates and reports?

We tend to gravitate to using customer templates as they have internal QMS requirements that need to be fulfilled. We do however have in-house templates to leverage on, if necessary.

Does Seal provide User Acceptance Tests?

We have guidelines for Basic User Acceptance Tests, if needed.

We often work together with customers to validate specific functionality and usability, based on their platform configurations.

Misc

How do I view the current Seal version number?

The current version number can be seen within the Settings page in the Seal Platform.

Do I have to validate features that are not enabled within my Seal platform?

In short - no.

If they are not enabled within your Seal platform, they have been turned "off", and your platform will not have any interaction with this feature.

How does my API tie in with validation?

The API will enable data flow within Seal but does not change the behaviour of the Seal Platform. It is on the customer to document the set-up and configuration of the API, including the risk assessment aspects.

The API itself, is tested within routine Seal testing.

Last updated 2 months ago