Computerized System Installation Qualification (IQ)
1. Purpose and Scope
Installation Qualification establishes documented evidence that a computerized system is installed correctly and in accordance with approved specifications, vendor recommendations, and infrastructure requirements.
This phase confirms that the system environment is suitable to support reliable operation before functional testing begins. It applies to all regulated computerized systems, including infrastructure components, commercial off-the-shelf applications, and configured systems subject to GxP requirements.
Installation Qualification does not evaluate system functionality. It verifies that all required components are present, properly installed, and correctly configured at the infrastructure level.
2. Role of IQ within the Validation Lifecycle
Installation Qualification represents the first formal verification step after system procurement and configuration planning. It provides the documented baseline upon which Operational Qualification and Performance Qualification depend.
Within the lifecycle:
- User Requirements define intended use
- Design and configuration define how the system will meet those requirements
- Installation Qualification verifies correct deployment
- Operational Qualification verifies functional behavior
- Performance Qualification confirms performance under routine use
IQ ensures that the system is installed in a controlled and reproducible manner, reducing variability and eliminating environmental or configuration-related risks prior to functional testing.
3. Installation Verification Approach
Installation Qualification is executed through a combination of documented verification steps and objective evidence collection. Activities are typically protocol-driven and may leverage vendor documentation where appropriate. Execution must confirm:
- completeness of system components
- correct installation of hardware and software
- alignment with approved specifications
- suitability of the operating environment
Verification must be traceable, repeatable, and supported by recorded evidence such as screenshots, configuration exports, and installation logs.
4. Infrastructure and Environment Verification
The system environment must be verified to ensure it meets defined requirements and supports system operation. Typical verification elements include:
- server or workstation specifications
- operating system version and patch level
- database installation and configuration
- network configuration and connectivity
- domain and directory services integration
- time synchronization settings
Environmental dependencies must be confirmed to be stable, controlled, and compliant with organizational IT standards.
For cloud or hosted systems, verification focuses on:
- documented infrastructure qualification by the supplier
- service-level agreements and availability commitments
- data center controls and certifications
- logical environment segregation
The diagram below presents the installation architecture of a typical computerized system as it relates to Installation Qualification. It defines the system components, supporting infrastructure, and external dependencies that must be verified during IQ. Each layer and connection shown represents elements that require documented confirmation of correct installation, configuration, and connectivity to establish a controlled and reproducible system baseline.

5. Software Installation and Configuration Verification
Software installation must be verified to confirm that the correct application and associated components are deployed. Verification activities include:
- installation of the correct software version
- verification of installation success without errors
- confirmation of required modules and components
- application of approved configuration settings
- verification of system parameters and baseline configuration
Where configuration replaces custom development, configuration settings become a critical part of the validated state and must be documented and verified.
6. System Components and Interfaces
All system components and interfaces must be identified and verified. This includes:
- application servers and services
- databases and data storage locations
- client installations
- middleware components
- external system interfaces
Interface readiness may include:
- confirmation of connectivity
- verification of data exchange mechanisms
- validation of interface configuration settings
Full interface testing is typically performed during Operational Qualification, but installation readiness must be confirmed during IQ.
7. Security and Access Control Setup
Initial security configuration must be verified to ensure controlled system access. Typical checks include:
- user account management mechanism
- role-based access structure availability
- password policy configuration
- account lockout and session timeout settings
- system administrator access control
IQ confirms that the system supports defined security controls. Detailed access control testing is performed during Operational Qualification.
8. Data Integrity Foundations
Installation Qualification must confirm that core data integrity controls are present and enabled at the system level. Verification includes:
- audit trail functionality enabled
- secure data storage locations defined
- protection against unauthorized data modification
- system time synchronization to ensure timestamp integrity
- backup configuration and scheduling
These controls form the baseline for compliance with 21 CFR Part 11 and ALCOA+ principles.
9. Backup and Recovery Configuration
Backup and recovery mechanisms must be verified to ensure data protection. Typical verification elements:
- backup schedule configuration
- backup location and media
- confirmation of successful backup execution
- restore capability verification at a basic level
Full disaster recovery and restore testing may be performed separately but must be supported by IQ configuration verification.
10. Documentation Verification
All required documentation must be available and aligned with the installed system. This includes:
- vendor installation documentation
- system architecture documentation
- configuration specifications
- licensing information
- operating procedures
Documentation must be reviewed for completeness and consistency with the installed system.
11. IQ Protocol Structure and Execution
Installation Qualification is executed using a pre-approved protocol that defines:
- scope of installation verification
- required test steps and checks
- acceptance criteria
- required evidence
- deviation handling process
Execution must be controlled and documented. Each step must include:
- clear instructions
- expected result
- actual result
- objective evidence reference
Deviations must be documented, assessed for impact, and resolved prior to progression to Operational Qualification.
12. Acceptance Criteria
Acceptance criteria for Installation Qualification are objective and evidence-based. Typical criteria include:
- all system components installed as specified
- infrastructure meets defined requirements
- software installed without errors
- required configuration settings applied correctly
- security baseline established
- backup mechanisms configured
- required documentation available and accurate
All discrepancies must be resolved or justified prior to approval.
13. Deliverables and Approval
Installation Qualification results in formal documentation confirming that installation requirements have been met. Typical deliverables include:
- executed IQ protocol
- installation checklists
- configuration records and screenshots
- deviation records and resolutions
- summary report
Final approval confirms that the system is correctly installed and ready for Operational Qualification.
14. Link to Ongoing Lifecycle Control
Installation Qualification establishes the initial baseline configuration of the system. This baseline must be maintained under change control.
Any changes to:
- infrastructure
- software version
- configuration settings
- interfaces
must be evaluated for impact and may require partial or full requalification.
IQ therefore serves as the reference point for maintaining the validated state throughout the system lifecycle.

