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. MISC

Glossary

Last updated 28 days ago

  • A blueprint that defines the structure and behaviour of a particular kind of data or process

  • Purpose: Used to model entities such as documents, workflows, or tasks.

  • Relevance: Templates are created based on Types; Instances are executions of these Templates.

  • A predefined configuration of a Type, serving as a starting point for creating Instances.

  • Purpose: Ensures consistency and standardization across similar processes or documents.

  • Relevance: Derived from a Type; used to generate Instances.

  • A specific execution or occurrence of a Template, representing a real-world process or document.

  • Purpose: Tracks the progress and data of individual workflows or documents.

  • Relevance: Created from Templates; can be part of a Workflow.

Entity

  • Are types, templates, or instances.

  • Purpose: Represents the various components that interact within the system.

  • Relevance: Entities are defined by Types; Instances represent specific Entities.

  • A sequence of steps or stages that an Instance progresses through, often involving multiple users or systems.

  • Purpose: Manages the flow and approval processes of documents or tasks.

  • Relevance: Instances follow Work Instructions; Work Instructions are defined within Templates.

  • A collection of modifications made to Templates and/or Instances, grouped together for review, to be published.

  • Purpose: Facilitates controlled updates and versioning within the platform.

  • Relevance: Applied to Templates and/or Instances; once approved, changes are Published.

  • The action of publishing and/or making a Template or Instance active, done via change sets.

  • Purpose: Finalises and deploys configurations or updates.

  • Relevance: Follows the approval of a Change Set, all entities in Change Sets are published together

Type
Template
Instance
Work Instructions
Change Set
Publish