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
    • 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?
  3. How do I know if my system is compliant to a standard?

Setting up your System

Last updated 21 days ago

This page provides guidance for ensuring the setup of Seal Platform is configured appropriately before conducting compliance validation. Note that this guide does not serve as legal counsel for achieving absolute compliance for auditory purposes.

1

Documentation Upload and Organisation

Ensure that all required documentation is uploaded into the Seal Platform. This includes all quality-related documents, such as SOPs, policies, work instructions, risk assessments, and relevant records.

Optional - ensure that uploaded documents have the following:

  1. Document Metadata: Metadata fields, such as document title, author, and effective date are filled out accurately for each document

  2. Relevant tags and/or in Saved views

    Documents should be organised in a logical structure according to categories that match your organisation’s QMS framework. Common categories may include:

    • Document Control

    • CAPA (Corrective and Preventive Actions)

    • Audit Management

    • Risk Management

    • Nonconformance Reporting

  3. Published Versions Ensure that documents are published and assigned a version.

Refer to Seal documentation on:

Missing a document? View our list of templates here.

2

Workflow Setup and Configuration

Procedures must be properly set up to ensure that workflows can be executed smoothly through necessary reviews and actions.

Configure workflows in the system and ensure that relevant connections are set-up, such as (but not limited to):

  • Document Review and Approval

  • Corrective and Preventive Actions (CAPA)

  • Change Control

  • Nonconformance Handling

For workflows requiring user approval and sign-off, assign relevant reviewers to each procedure, based on your QMS framework.

Refer to Seal documentation on:

3

User Setup and Role-Based Permissions

Ensure that all team members who will interact with the QMS are added to the Seal Platform, including administrators, reviewers, and view-only access users. Set up appropriate roles and permissions. Each user’s access level should align with their responsibilities within the QMS.

Setting up correct permission levels will ensure that users with the relevant roles can access the documents they need, and unauthorised access to sensitive documents will be restricted, to ensure compliance with privacy standards.

Refer to Seal documentation on:

4

Documentation of Setup and Pre-Validation Activities

Note that the Seal Platform has a built-in an audit trail that documents all actions and changes made in the system. In addition, Seal recommends customers to create a summary document to document all pre-validation activities to to confirm all elements are set up appropriately.

5

Checklist

Documentation:

Procedures:

User Roles and Permissions

Need help? Email our team at support@seal.run.

How to upload files and documents
Extracting metadata from files using AI
Batch procedures
How to setup review cycles
How to add users, setup roles and permissions