Table of contents
At a glance
How do you validate ConSense GxP for your intended use?
Identify the deployed ConSense platform, GxP module, additional functions and deployment model. Derive requirements from the document and evidence process. Who may edit, review, approve and use each document? Which instruction version applies to each record? Assess relevant supplier evidence and test remaining handovers in the configuration. A supplier’s description of a product as prevalidated does not release the customer system for general use.
- GxP is currently a module within the manufacturing release; additional functions are included only in the actual system scope.
- Release, entry into force and use of a requirement shall be technically clear.
- A current document link does not automatically retain the historical reference of a form submission.
- Supplier documentation, roles, and change tests are evaluated at the specific process level.
Define the actual document and record verification process
Start with a work instruction and provide evidence of its application. Who prepares the instruction, who evaluates it, and who implements it? Where is the execution documented? Once errors in this chain could influence a quality-related decision, the assessment must extend beyond simple document archiving.
This article addresses human medicinal product GMP. The current EudraLex index covers Chapter 4 and Annex 11 in the January 2011 revision. Annex 11 is a GMP guideline for computerised systems. Medical devices, clinical research, and other GxP areas require a separate classification; the product name ConSense GxP does not define the applicable scope.
Describe the intended use, including expression, export, or associated form. A correctly released instruction within the system may be misapplied outside the system. Critical considerations are the specific transition points and resulting errors. From these, derive requirements and validation depth, rather than assigning a software category to the product on a general basis.
GxP Module, Forms, and Scope of Operation Differ
ConSense presents a modular platform. The module overview explicitly references GxP requirements and includes, among other features, electronic signatures, roles, audit trail, release, and activation. FORMS, corrective and preventive actions, training, and qualification are described as separate functional areas. This does not imply that every customer installation includes all of these functions.
The public FAQ describes server operation and a hosting service; ConSense PORTAL is referenced there as a web-based, hosted version. Therefore, clearly define product name, modules, license scope, software version, and operator responsibilities. From the publicly available pages, no current overall build number or complete edition matrix can be derived.
The following matrix assigns the components to a purpose. It is not a claimed package configuration. Just complete the functions actually used and clarify who is responsible for their operation, adaptation and use in the process.
| Component | Technical Reference | Clarify prior to project start |
|---|---|---|
| Platform and GxP module | Roles, Release Approvals, and Change Documentation | Specific version, license, and configuration |
| Document management | Valid instruction and prior revision | Reader view, release and archive access |
| FORMS | Form template and completed process | Link to the version of the instruction used |
| Actions | Assigned tasks and decisions | Transfer, Responsibility, and Closure |
| Training / Qualification | Required knowledge or qualification | Actual functional scope and intended use |
| Server / Hosting | Availability, Security, and Modifications | Operator responsibilities and corresponding contractual documentation |
Approval does not automatically mean immediate implementation.
Define the significance of document statuses within your process. A draft is under review; a technical approval confirms the reviewed content; implementation signifies the intended start date of its application. This distinction is particularly important when prior training, organizational preparations, or template exchanges are required.
The ConSense module overview specifies release and implementation with a 4- to 8-eye principle. This represents a described product feature and is not a general obligation requiring a specific number of participants. Define the appropriate roles for your process and assess their concrete implementation. Time-based activation or specific locking logic is not assumed to be already validated or implemented.
Consider user access from the actual work environment. A search result, a saved link, and a terminal can represent different pathways to instruction. Verify that the intended work state is clearly evident and that a draft is not mistaken for an approved version. Old paper copies require additional controlled handling.
Maintain the specification document and completed form together
ConSense FORMS describes configurable forms and workflows, as well as connections between instructions, execution, and documentation. For validation, it is essential to determine what such a connection means in a specific process. Does it reference the current content available today, or is it traceable to the specific revision applied during execution?
Therefore, do not evaluate only a new empty template. Investigate a completed legacy process, an open process during change, and a newly restarted process. These states may require different technical and operational decisions. A subsequent reference to the most recent document must not inadvertently imply a previously applied version without proper review.
For open transactions, the process owner decides whether to continue under the former instruction, move to the new version under control or pause the work. Public product descriptions do not specify a general migration rule for such instances. Define the expected outcome and test the configured workflow.
Verify rights and approvals at the specific process step
A role should represent a clear, professional responsibility. Who is authorized to modify a template, who reviews its content, who grants it authority, and who is permitted to read it only? Please include provisions for delegation and revocation of permissions. The mere presence of a technically accessible button does not constitute professional authorization.
The manufacturer describes electronic signatures with user binding and timestamping, along with an audit trail. The specific signature requirements applicable to a given process and the evidence provided by the setup to support those requirements must be evaluated independently. A general functional description does not imply a universal requirement for electronic signatures nor guarantees the legal validity of any confirmation.
An appropriate internal negative test attempts a release using an identity that is not permitted according to your role-based rule. Additionally, verify how an authorized correction is made visible: what was changed, how the original state remains identifiable, and how the decision can be traced back later. Manufacturer terminology such as "complete" does not substitute for this specific verification.
Example: a SOP and three form process workflows
This example does not represent a completed ConSense test. SOP-07 Revision 1 is currently effective. Author A will prepare Revision 2; for this case, a review by B and a release by C are required. Implementation occurs only after the predetermined decision has been made. This role sequence constitutes a standalone example specification.
F1 was fully completed under Revision 1 prior to the transition. F3 was also initiated under Revision 1 but remains open at the time of transition. F2 will be started only after the implementation of Revision 2. The independent target thus identifies three distinct processes: two have a historical start reference to Revision 1, while one begins under Revision 2. Decisions on the further handling of F3 must be explicitly made.
Run each failure scenario in an appropriate test configuration starting from a defined initial state. An existing legacy configuration must not subsequently be regarded as having been executed under Revision 2. The table outlines expected operational behaviors; whether and how your installation meets these expectations through configuration, technical controls, and additional procedures is the subject of evaluation.
| Status / Incident | Action | Predetermined expected result | Reference to be verified |
|---|---|---|---|
| Revision 2 in draft | Reader opens search or direct link | Revision 1 remains clearly identifiable as the valid reference; the draft is not to be considered an operational instruction. | Display, Status, and Document Condition |
| Unauthorized Release | Author A attempts the decision intended for C | Own role rules are not being circumvented without notice | Identity, Authorization, and Protocol |
| Revision 2 becomes effective | Execute the proposed decision | New work status clearly defined; Revision 1 historically available | Release and Implementation |
| F1 completed | Open the historical record after the change | Execution remains assigned to Revision 1 | Stored historical relationship |
| F2 restarted | Formulation after switch begins | Reference to the effective revision 2 | Template and applicable instruction version |
| F3 still open | Retrying after switch change attempt | No silent reinterpretation; predefined continuation/transition decision clearly justified | Original starting reference and controlled decision |
Do not mix information, training and competence
ConSense describes notifications for new content and integration with training and qualification management. For your process, several distinct pieces of evidence may be required: content has been provided, an employee has acknowledged it, a training session has been conducted, or a required qualification has been assessed.
Which of these statements is required follows from the activities and the specific change. A new document version may include only a minor editorial correction or a revised work procedure. Validation assesses the suitability of the established documentation pathway; it does not replace the professional judgment regarding training needs.
For example, verify a newly assigned user and a user whose role has changed. Are relevant tasks directed to the correct target group? Are previous authorizations still valid in content and scope? An automatic lockout of a machine or activity is not derived from a module linkage. If your process requires such a linkage, it must be explicitly described and supported with validation evidence.
Intentionally adopt supplier documentation and identify gaps
ConSense provides IQ/OQ support, templates, checklists, and, upon request, extended validation guidance. The actual package contents and test results for your specific configuration have not yet been described. Please request the appropriate delivery scope with version reference, prerequisites, and known deviations.
Align existing documentation to your requirements. An appropriate justification may be directly usable; another may require additional review, for example, due to missing own workflow sequence or form transition. Do not assume complete coverage nor that supplier documentation exclusively pertains to unaltered standard functions.
With an existing system, begin with actual evidence: Which templates are used, which processes remain open, and which historical records must remain understandable? The current configuration and the original implementation documentation may differ. Prioritize traceable gaps based on their significance and avoid simply recreating already viable documentation.
Assess the impact of configuration changes and updates
A form field, a responsibility, or a release step may change quickly. This does not automatically diminish its impact on the process. Identify which new and ongoing processes are affected and whether previous evidence has been presented or evaluated differently.
Plan targeted repeat validations based on these impacts. During a role change, different cases are prioritized compared to a new form version. A version change may introduce additional requirements for operations or restoration. This does not imply a general obligation for full revalidation nor a blanket exemption for minor configuration changes.
Discuss with IT or hosting partner who will notify of changes, provide test opportunities, and enable data restoration. Also verify the readability and assignment of older records. A described hosting arrangement or automated backup alone does not confirm that the required technical interdependencies are preserved after restoration.
Preparation for introduction, inventory and next change
Start with one relevant requirement and the evidence for it. QA and process owners clarify its meaning and acceptance criteria. Key users explain the configuration and IT explains operation. Small teams may combine tasks. Responsibilities and decisions must still be traceable.
The effort is primarily driven by unknown module stations, numerous document types, complex roles, ongoing legacy processes, and unclear historical linkages. For a new implementation, a defined target workflow is required; for existing systems, a reliable as-is state must be established, and for changes, a thorough impact assessment is necessary. Only from this foundation can the scope, level of involvement, and timelines be meaningfully derived.
- Aggregate product, module, version, and operational scope.
- Describe document statuses and release rules for approval and implementation.
- Assign roles including delegation and revocation of authorisations.
- Prepare closed, open, and new formular processes as test cases.
- Compare available supplier documentation with actual system configuration.
- Define storage, restoration, and responsibility for changes.
Project experience and collaboration
Link the document revision to the completed record
In ConSense, we connect the instruction effective at the time with the forms people actually completed. Your process owners choose a typical transaction. Together with QA and IT, we trace its revision, confirmation and subsequent retrieval. We assess whether the supplier package covers your configuration and where handover tests are needed. If historical records cannot be tied to the applicable version, we clarify that rule before testing further forms or approval steps.
Frequent Questions about ConSense Documents and Forms
Is ConSense GxP a standalone software edition?
The current public manufacturer's presence leads GxP as a module of the ConSense platform. Further functions such as FORMS, measures or qualifications are described separately. Therefore, the concrete ordered and configured combination counts for your proof. Older product names in references do not provide a reliable current license matrix.
What does the manufacturer's statement "pre-validated" mean for our project?
This is a reason to request the associated documentation. Only by assessing the actual scope can the required specifications, versions, and usage conditions be fully understood. Suitable conclusions may be justified and adopted. However, the assigned roles, data flows, and usage must align with the established requirements. Neither general trust nor routine re-execution of all tests constitutes an appropriate alternative decision.
Must release and approval be two separate documents?
Crucially, the clear indication of the validity and timing of decisions is essential, not a prescribed number of files. The procedure must demonstrate whether a content has been reviewed and when it is intended for application. This can be established through a continuous and coherent traceability record. Assess how your configuration reflects this distinction; a time-based product function is not required.
Is a link to the current SOP available on the form?
For access to a current specification, such a link can be helpful. For historical traceability, it must remain clearly demonstrable which specific content was actually applied. If the link later only displays the new revision, the question of which version was in effect remains unanswered. Purposefully evaluate both legacy and current processes and define which version reference must be retained.
What happens to open formular workflows upon the implementation of a new SOP?
Determine whether an open process should be continued, changed or stopped under the previous revision. The decision follows the change and your process; the public manufacturer's pages do not call this a universal technical rule. Check the selected configuration at a representative open process, including historical start-up and documented decision.
Does an electronic signature automatically ensure the correct release?
It may provide part of the evidence. Additionally, the person, authorization, confirmed content, and significance of the decision must be consistent. The applicable signature requirements depend on the actual process and regulatory domain. A general product statement does not validate any specific configuration nor the technical accuracy of the released content. Therefore, review inappropriate roles and controlled corrections.
How do we handle printed work instructions?
Incorporate printouts into the intended distribution process. ConSense includes, among other things, document or QR references and terminal identifiers. Such references can assist in identifying the current status, but do not automatically retrieve paper copies. Define how issuance, validation check, and replacement function within your work environment and specify the evidence required to support these processes.
Is acknowledgment of knowledge concurrently equivalent to training or task authorization?
These statements should be distinguished professionally. A formally acknowledged competence assessment conveys a different meaning than a completed training or a formally assessed qualification. The required statement depends on the specific activity and the change. Review the established evidence pathway and its target group; an automatic linkage to machine access or task authorization does not automatically follow from the available modules.
What must a small company be prepared to provide at the outset?
A clear specification and documentation process, the actual module/version list, existing supplier documentation, and named subject-matter and technical contacts are helpful. Prepare one new, one completed, and one open process. This selection makes many relevant transition points visible. Missing information will be retained as tasks, rather than being replaced with general product brochures.
What factors influence effort and duration?
Key factors include configuration diversity, the number of relevant document types, role complexity, interfaces, and the quality of existing evidence. A clear standardized workflow should be treated differently from historically evolved forms with open legacy processes. Begin with a focused inventory assessment and prioritized failure scenarios. This leads to specific action packages and required stakeholder involvement; a general duration cannot be inferred from the product name alone.
Sources and review date
As of 6 October 2026. Basis is the public ConSense product and module descriptions. This does not confirm the current overall build number, complete license matrix, or verified customer configuration. Actual validation packages have not been reviewed. Regulatory example scope: Human medicinal product-GMP. Tables and expected deviations are standalone work aids and do not represent completed product testing.
- ConSense Platform Overview
- ConSense Module Overview
- ConSense GxP Validation Management
- ConSense Document and Knowledge Management
- ConSense Formularmanagement FORMS
- ConSense FAQ
- European Commission: EudraLex Volume 4, Human Medicinal Products - GMP
- EU GMP Annex 11: Computerised Systems, January 2011 revision
- EU GMP Chapter 4: Documentation, January 2011 revision
Sources checked: .
Clarify the validation pathway for your ConSense configuration
We support you in defining modules and process boundaries, evaluating existing evidence, and developing appropriate checks for document transfers and form-based documentation.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

