Table of contents
At a glance
How do you validate Cornerstone Learning for GMP training?
Demonstrate a defined Cornerstone Learning workflow covering the correct learners, approved content version, suitable completion criteria and records that remain understandable. Map IV&V evidence to functions in use and test gaps. Decide how to handle version equivalence, dynamic assignment and signatures. A supplier package or Completed status does not demonstrate these controls or practical training effectiveness.
- Learning processes, configuration, and allocated validation support are separately defined for your specific application.
- Requires retraining and completed equivalent assignments to establish different professional judgments.
- A signature requirement may depend jointly on the organizational unit and the learning object.
- Dynamic reassignment does not automatically restore manually removed training.
Define the boundaries of Cornerstone Learning within the GMP training process
Cornerstone Learning can manage development offerings, voluntary courses and binding training. Validation counts which of these functions support your GMP processes. If you have the relevant proof of a manufacturing instruction there, a false version or completion status has different consequences than a voluntary language training.
This guide concerns GMP for human medicines. The EudraLex index identifies Chapter 2 for training, Chapter 4 for documentation and Annex 11 for computerised systems. Assess clinical trials, medical devices, veterinary medicines and any US requirements separately. The supplier's international presence does not make every framework applicable.
Consult which Cornerstone Learning Modules and what services of the IV&V Maintenance Service your offer includes. Determine the actually ordered offer, the modules used, interfaces and responsibilities. The designation of the IV&V offer does not yet describe the suitability of your configuration. Likewise, the practical effectiveness of a training remains to be evaluated professionally: a stored completion does not answer this question alone.
IV&V materials specifically tailored to your usage needs
The 2026 Cornerstones Data Sheet outlines impact assessments, formal validation documentation, and executed test scripts for each respective release element. The basis is so-called Critical-to-Customer Requirements. Additionally referenced are plans, change logs, traceability matrices, and reports. This provides more specific support than a general statement on industry suitability.
The key consideration remains coverage: Which function was tested, with which configuration, and what was the outcome? Does this align with your training process? Can open findings and excluded functions be evaluated? The public specification sheet is not a substitute for the actually delivered package. The referenced Regulatory Position Paper must also be available for project-specific assessment.
The following work aid combines supplier evidence with internal decisions. Use appropriate documentation based on documented evaluation. If a link to internal usage is missing, supplement with targeted assessments. A comprehensive end-to-end test of all supplier functions is neither required nor justified, nor is an automatic adoption of the supplier's conclusion.
| Area to assess | Available supplier certificate | Own reconciliation |
|---|---|---|
| Scope of release | Impact Assessment and documented Release Elements | The affected own training programs, configurations, and data pathways are determined. |
| Functional test | Executed scripts with results and findings | Identify appropriate prerequisites and remaining defect cases. |
| Retraining | Versioning requirements and testing linkage | Record why the team requires new training or accepts an equivalent qualification. |
| Signature | Documented technical control function | Actually effective OU-object settings and identity verification are checked. |
| Operation | Maintenance documentation and agreed services | Responsibility for changes, validation evidence, retention, and equipment malfunctions to be documented. |
Prior to configuration, define the required training scope.
Start with a specific instruction and the relevant personnel group. Which released content is being trained on? What activity does this training presuppose? How does the department determine that the training was successful? Additionally, describe who authorizes exceptions and how a required hands-on orientation is supplemented.
An appropriate requirement might be: Following a materially significant change, the relevant QA personnel shall review and edit the updated course version and confirm the intended completion. Prior participation shall only satisfy the new requirement if the responsible party has provided a rationale for equivalence. This represents an example of a professional standard, not a blanket rule applicable to every editorial correction.
Assign the following data to this required action: unique user identifier, organizational assignment, course version, expiry date, completion conditions, and optionally, digital signature. These elements give rise to relevant error scenarios. The absence of a user within the target group, completion of the wrong content, and excessive administrative privileges require distinct control measures. The simple count of completed courses may obscure these differences.
New course version: Retraining or recognized equivalence?
The Cornerstone assistance distinguishes between Append and Replace in online courses. Append enables parallel versions; Replace replaces the previous version as of the effective date. The selection made during the first versioning determines subsequent versions. Therefore, verify the existing versioning prior to distributing a new SOP version.
The decision regarding version equivalency is independent. A requirement for retraining implies a new training session; a completed equivalent may recognize a prior completion. This setting must align with a technical assessment of changes. The title "Version 2" alone neither indicates that retraining is required nor that retraining has actually been triggered.
User filters take into account, among other things, course version, current status and type of assignment. At a future effectiveness date, the system calculates the affected user quantity again. Therefore, check intermittent organizational changes. For a reliable acceptance, compare identifiers and versions with an independently created set of targets. The documented rules concern this online course run; do not transfer them unchecked to materials, curricula or other assignment models.
Verify separation of approval signature and publication rights
At the learning object level, Cornerstone requires two appropriate configurations: an Electronic Signature for the organizational unit and a Required Electronic Signature at the learning object level. Once the prerequisites are met, the course remains in a pending completion status until signature confirmation, at which point the status is updated to Completed.
User name and password re-entry is separately configurable. Therefore, a displayed name or decorative signature does not substitute for verification of the actual process. Define the meaning of confirmation: participation, awareness, or another predefined statement. Verify identity, time relevance, and connection to the relevant documentation.
Cornerstone also notes that a later-activated signature requirement does not generate a retroactive signing step for previously completed learning objects. Historical evidence must be evaluated according to the conditions prevailing at the time. For administrator rights, the help documentation distinguishes between upload and publication. Test with realistic roles to determine who is authorized to prepare content and who is authorized to effectively publish it. Technical course administration and subject-matter approval authority must not be implicitly equated.
Test example: A new SOP for three target groups
The following scenario is a standalone reference document and does not represent a completed Cornerstone test. Individuals A, B, and C are part of the QA target group; D is outside this group. In Version 1, A is completed, B is under review, and C has not yet begun. The professionally revised Version 2 requires retraining and a final signature for all three target personnel.
For this example, appropriate filters and retraining requirements are selected. The required signature conditions are activated for the organizational unit and learning object. Versioning procedures, effective date, and test environment are documented. An independent list of the three target identifiers is retained for comparison and is not derived from the subsequent final audit report. For the negative role test, a test account with upload rights but without the required publication rights is established.
| Test step | Expected result | Sample inspection batch to be retained |
|---|---|---|
| Version 2 for A distribution | Despite the previous closure, the new training requirement remains in effect. | Version, Filter, Equivalence setting and Transcript before/after. |
| Distribute version 2 to B and C. | Both target individuals receive the new version in accordance with the established procedure. | Separate identification and version comparison for B and C. |
| Check the D as a control sample. | This version cycle has no training documented for D. | Target group rules and verified non-assignment. |
| Edited content, signed but not approved | Pending Completion Signature; the defined requirement has not yet been fulfilled. | Status update and pending step. |
| A confirmed compliant and properly maintained | Version 2 is complete for A; B and C remain open. | Identity, version, completion and signature context. |
| Unauthorized role attempting publication | The unauthorised action is still blocked. | The role assigned at the time, the action attempted and the actual system response. |
Account for personnel transfers and remote training activities
The Learning Assignment Tool supports one-time and dynamic assignments; repetition and dynamic removal have separate settings and permissions. Document which procedure generated the evidence. A directly assigned course and a dynamically distributed course may not produce the same effect upon role change.
At Dynamic Reassignment, Cornerstone identifies a key boundary: reassignment requires that a prior dynamic removal has occurred. A manual deletion from the transcript or a removal using the Training Removal Tool does not trigger this mechanism. The expectation "the person returns, so everything is automatically restored" is insufficient as a validation assumption.
Therefore, track an entry, a transfer out of the target area, and a return. After each step, verify the version and deadline. For reassignment, the relevant assignment determines the deadline; for curriculum sub-objects, the help text outlines specific considerations. Do not treat example durations as mandatory operational deadlines. The department and training responsibility must predefine which training is required upon return.
History, interfaces, and readable training records are linked
The change history of an online course, as shown in Cornerstone, includes among other details the change date, user, and modified files. This view assists in tracing content modifications. However, it does not automatically capture all changes to assignments, signature rules, user master data, or reports. Individual object-specific evidence must be reviewed and verified.
For a historical training decision, the relevant person, the content trained at that time and the meaning of the degree should remain understandable together. Define where this information is located and how it remains accessible to retired employees or discontinued courses. A current link to the latest SOP does not explain an earlier training degree easily.
For connected HR or document management systems, the transition to review must include correct identification, authorized organizational assignment, unambiguous version reference, and detection of incomplete or duplicate transfers. These are independent review considerations, not assertions regarding specific Cornerstone APIs. For exports, define the required context and verify readability and completeness. A screen capture or CSV file alone is not sufficient as evidence of long-term compliance due to format alone.
Link batch release to the own configuration status
A logically scoped initial validation establishes a solid foundation: approved usage, configuration, roles, interfaces, documented requirements, and definitive findings. During an update, compare this baseline against relevant manufacturer changes and your IV&V package. Then assess whether previous validation evidence remains valid and identify any additional testing requirements.
The September 2026 public help also contains references to early adopter functions and postponed deployments. A help page therefore does not prove that a function is active in your tentant. Keep track of product status, activated options and the maintenance planning that applies to you.
Changes may also arise outside of a manufacturer's release: new organizational rules, different signature requirements, or a revised equivalence decision can affect the supporting evidence. Evaluate the impact of such changes systematically. In the case of an unexpected closing wave, identify and clarify affected personnel and content, retain original records, and determine any necessary actions. A renewed individual green test does not replace this evaluation; likewise, no change automatically requires the repetition of all tests.
What a SME should prepare: Responsibilities, Efforts, and Checklist
The primary driver of effort is often the diversity of actual rules: multiple locations, different customer segments, existing agreements, curricula, and external data pathways. Start with a clearly defined and representative training process and representative deviations. A mere number of courses only inadequately describes the audit requirements.
The department defines training requirements and success criteria. QA integrates the evidence into the quality system. The system owner is responsible for configuration and operation; IT manages identities and interfaces. A qualified course administrator provides the specific settings. Although multiple responsibilities may be held by the same individual, decision-making and technical execution should remain distinguishable.
Before the test starts, the following points should be answered. Lack of information is treated as open tasks with the person responsible instead of replacing them with general manufacturer commitments.
- Usage and relevant training decisions in the human medicinal product GMP process described.
- Actually ordered modules, IV&V documentation, and relevant release elements assigned.
- Target personnel, course completion status, and justified training/qualification equivalence decisions defined.
- Versioning filter, effective date, and signature conditions documented.
- Positive and negative assignment, allocation, and version scenarios prepared.
- Historical records, data pathways, and required export context described.
- Investigations, release decisions, and actions regarding changes to be agreed upon with responsible parties.
Project experience and collaboration
Preserve training content and completion records across version changes
With training owners, we link an employee's task to the required content and evidence of completion. An SOP revision lets us test retraining and recognition of existing completions in Cornerstone. We can add missing rules to an established workflow. A new qualification process also needs assigned responsibility for course versions and exceptions. We then check whether a historical completion identifies what was taught at the time and whether new training needs remain visible.
Frequently asked questions about Cornerstone Learning
Has Cornerstone Learning been validated by the supplier?
Cornerstone provides defined supplier documentation under IV&V Maintenance. The scope of the reviewed documentation must align with your specific usage requirements. Request the actually agreed documentation and compare requirements, prerequisites, results, and open findings. The designation of the offering or a datasheet alone does not validate your configured training processes. Supplementary internal audits shall be tailored to remaining risks and evidence gaps.
How do we scope a Cornerstone offering with validation support?
List the modules in use, configuration, data pathways, and assigned validation evidence in the proposal. Assign a designation such as "Validated Cloud" to the actual service capabilities. Cornerstone provides, among other things, an IV&V Maintenance Service for the Life Sciences sector. The specific services covered under the contract and those that remain under the client’s own responsibility must be clarified based on the specific offering.
Does every SOP amendment require a new training?
A new SOP version number alone does not determine the need for retraining. Assess whether the required knowledge or tasks have changed. A professionally relevant change may necessitate retraining; a justified editorial correction may be handled differently. Only after this professional evaluation should you select the appropriate implementation in Cornerstone. The "Requires retraining" and "Completed Equivalent" flags must align with this professional assessment.
How can I check that a new course version reaches everyone who needs it?
Compare an independently defined target list of personnel with the actual assignment outcome. Consider course version, previous status, organizational unit, and assignment type. If later effectiveness is achieved, the affected personnel may have changed during that period. Therefore, also verify personnel additions and departures, as well as individuals outside the target group. A matching total count is insufficient without a unique identifier comparison.
Why does a course remain in Pending Completion Signature status?
This status may indicate that the content components are complete, but the configured completion signature is still missing. Verify the active settings of the organizational unit and the learning object, as well as the intended signature workflow. Removing the signature requirement alone is not sufficient to close an open entry. First, it must be clarified which professional validation is required for this course.
Are previous closures re-signed after activation of the signature requirement?
According to Cornerstone, a later-activated signature requirement does not impose retroactive signing obligations for previously completed learning objects. Evaluate these evidences based on their original conditions. If additional professional verification is required, plan a controlled catch-up process. Do not retrospectively treat a historical closure as having been signed at the time.
Why is there no training provided upon return to a department?
First, verify the original distance path. Dynamic reassignment assumes dynamic distance; manual distance or use of the Training Removal Tool does not automatically result in the same reassignment. Additionally, check the criteria, status, and activated settings. Then, based on the training requirement, determine whether a reassignment is necessary, and ensure that any correction is clearly documented.
Does the transaction history suffice as an audit trail?
It addresses certain questions regarding changes to the online course, such as date, user, and file modifications. Whether it suffices for your entire documentation process depends on the relevant data and changes. Additionally, investigate assignments, closures, signature configurations, and permissions. Assess coverage, access, and readability; do not automatically assume that any single view provides a complete history of all activities.
Must every Cornerstone release be completely retested?
A blanket full revalidation is not an appropriate planning criterion. Compare the change against its actual implementation and existing documentation. Leverage relevant IV&V results and justify additional testing for affected functions or data paths. The decision to retain certain validations also requires a clear rationale linked to the current state. Configuration changes between releases fall under the same evaluation.
Which documents reduce coordination effort prior to project initiation?
Prepare a real-world training instruction with version history, list of affected personnel, assignment rules, roles, and typical closing documentation. Supplement existing supplier documentation and a overview of data pathways. This enables QA, IT, and functional areas to clearly resolve outstanding decisions. Fixed effort estimates without these details mask differences between a simple course flow and multiple integrated locations.
Sources and review date
As of October 6, 2026. Supplier reference: Cornerstone-IV&V Data Sheet 2026 and public online help, published on September 18, 2026. Specific customer packages, configuration, and release planning are individually confirmed. Regulatory reference: Human Medicinal Product-GMP. Examples and tables are internal work aids, not completed product tests.
- Cornerstone – Life Sciences
- Cornerstone Independent Verification & Validation Maintenance Service
- Training Completion Electronic Signature Preferences
- Online Course – Create Version – Versioning Options (Step 2)
- Online Course – Modification History
- Learning Assignment Tool – Overview
- Dynamic Reassignment Overview
- Cornerstone Online Help – Change Log 262
- European Commission: EudraLex Volume 4 – Human Medicinal Products-GMP
- EU-GMP Chapter 2: Personnel and Training, in particular Sections 2.10–2.11
- EU GMP Chapter 4: Documentation
- EU GMP Annex 11: Computerised Systems, January 2011 revision
Sources checked: .
Assess the Cornerstone training process purposefully
We support you in capturing the actual assignment and closure criteria, evaluating supplier documentation, and implementing the remaining checks in coordination with QA and IT.
- Cloud and SaaS validation →
Maintain the validated state of cloud and SaaS systems as suppliers issue new versions. We define the boundary between your responsibilities and the supplier’s and agree how each release will be assessed.

