The whole training lifecycle.
Clearly connected.

• Create the employee profile with Employee ID, name, department, designation, qualification and joining date before login creation.
• Assign multiple department induction tasks with individual responsible people and due dates; add or remove tasks with retained history.
• Track pending, completed, overdue and late completion; record supporting evidence, remarks and controlled corrections.
• Generate a numbered, versioned consolidated induction record and retain earlier PDF versions.
• After induction completion, create the login with Mail ID, a controlled Designation and the selected application roles, plus the approved Job Description and Training Need Matrix PDFs.
• Assign QA department induction to an eligible QA Manager or QA Head as well as other permitted department leaders.
• Retain completed induction details and reports when the employee’s new login details are recorded.

Retained evidenceDepartment task history, supporting evidence and a consolidated induction record PDF.

• Use unique normalized Employee IDs, login IDs, department and designation, with controlled Job Description PDFs.
• Manage pending activation, active, locked and disabled accounts, temporary credentials, password reset and mandatory password change.
• Retain append-only versions of personnel documents with checksum-verified authorized viewing and download.
• Revoke sessions when access changes and retain user administration events.
• Require separate Job Description and Training Need Matrix PDFs for new employee accounts through both account-creation paths; each matrix version is one PDF up to 10 MB.
• View Training Need Matrix versions in Manage User and, with the same permitted document access, from the completed induction record. Later uploads require a reason and preserve earlier versions.
• Keep existing accounts usable when no Training Need Matrix is recorded; do not invent or backfill a missing document.
• Keep employee Designation separate from application roles; induction login creation uses the roles selected by the authorized creator.

Retained evidenceAccount history and retained Job Description, Training Need Matrix and Induction Training Record versions.

• Assign configurable permission roles with a controlled reason and enforce authority on the server.
• Maintain Manager scope, including one active Manager per Analyst and controlled relationship changes.
• Review accounts, account status, roles, effective permissions, last login and reporting relationships; export the review.
• Separate Trainee, Manager/HOD, QA leadership, Quality/Auditor and technical System Administrator responsibilities.
• Restrict records and actions to the user’s approved scope; technical administration does not automatically grant business approval.

Retained evidenceReasoned role changes, Manager relationships and an exportable access review.

• Maintain a unique SOP number, title and controlled Function / Subject Area mapping; search the repository and inspect version history.
• Upload validated PDFs with version, effective and review dates; protect the retained artifact with a generated storage key and checksum.
• Activate with an electronic signature, automatically supersede the earlier active version and enforce a single active version.
• Retire with a reason and retain historical versions; inspect linked question sets, assignments, attempts, completions and certificates.
• Control inline viewing and download, and prevent inappropriate completion against obsolete versions under the approved workflow rules.

Retained evidenceImmutable PDF versions, SHA-256 hashes, approval signatures and lifecycle dependencies.

• Maintain TDS number, name and retained PDF versions with activation, retirement and authorized content access.
• Assign department ownership with the receiving department’s business approval.
• Transfer ownership using distinct current and receiving department approvers, approval references and retained history.
• Create traceable TDS assignments and let trainees see their own assigned sheets in My TDS.
• The first successful controlled print freezes and locks that TDS issue. Afterwards, the application offers View only and rejects another controlled print of the same issue.
• A Manager/HOD can authorize a new linked issue through controlled reassignment/reissue, with a mandatory reason and electronic signature. The original stays locked.

Retained evidenceControlled TDS versions, receiving-department approval and ownership transfer history.

• Create SOP-version question sets with multiple choice, true/false and fill-in-the-blank questions; retain accepted answer variants.
• Import a searchable PDF question paper with SOP number/version checks, deterministic parsing and whole-paper rejection when validation fails.
• Review the source paper beside the draft questions; retain its checksum, page references and parser traceability.
• Use manual question entry and editing as an alternative; copy to another version, activate with a signature and retire controlled sets.
• Keep answer keys restricted to authorized reviewers and preserve immutable question snapshots for existing assignments.

Retained evidenceQuestion-set revision, source paper hash, parser/page references and frozen assignment questions.

• Create Departmental, Job Role, Technical and General curricula with controlled numbering, linked versions and SOP/version requirements.
• Target department and designation combinations, preview matching employees and identify existing assignments before creation.
• Set assessment, training due date, enrollment cut-off and Effectiveness Monitoring decisions.
• Create initial assignments, handle later eligible employees and resolve pending enrollments with an approved revised due date.
• Revise with an explicit retraining decision, inspect progress counts and retire curricula while preserving finalized records.

Retained evidenceCurriculum versions, target population preview, enrollment decisions and linked assignment progress.

• Assign to one or many authorized recipients with assessment required or not required, instructions and a due date.
• Prevent duplicate open assignments and explain trainee-specific rejections when a bulk request cannot include everyone.
• Retain the SOP version, trainee/profile information, approved question snapshot, assignment source and business reason.
• Trace manual, curriculum, SOP revision, periodic, role change, deviation, CAPA, audit finding, incident, equipment change, return from absence, qualification expiry, planned schedule, session and TDS assignment sources.
• Cancel unfinished work with a reason and retain linked replacement assignments rather than overwriting earlier cycles.
• Use a permanent, readable ASM assignment number across training sources and linked TDS reissues. A genuinely new assignment receives a new number; reusing an obligation retains its number.
• Show Function / Subject Area from the controlled source rather than asking the user to re-enter it.
• Capture known trainee name, Designation and applicable application roles when a new assignment or replacement is created; keep earlier records unchanged.

Retained evidenceAssignment source, reason, reference, exact SOP/question snapshots and reassignment links.

• Plan SOP/version training for selected trainees with a release date, training due date, assessment and EM decisions.
• Track the schedule lifecycle separately from the progress of assignments that it releases.
• Amend before release, correct or exclude individual trainees and cancel remaining planned work.
• Automatically release against the configured business date; retain failed release reasons and controlled retries.
• Show the planned register and released assignment progress together, including individual exclusions and failed release follow-up.
• Derive applicable EM responsibility from the trainee’s approved relationship rather than an unrelated default person.

Retained evidenceSchedule number, release attempts, failure reasons and resulting assignment links.

• Extend training due dates through a permission-controlled, signed action with a business reason.
• Retain original and revised deadlines and the approval evidence alongside the assignment.
• Apply the associated EM due-date adjustment where the approved workflow requires it, while retaining the change history.

Retained evidenceOriginal and revised dates, approval signature, reason and extension history.

• Show the learner’s own assignments, deadlines, work status, training history and clear next actions.
• Open the exact assigned controlled PDF and record signed initial reading and rereading acknowledgements.
• Save and recover assessment drafts, explicitly confirm final submission and lock submitted answers.
• Show the trainee’s individual session records and required acknowledgements, while protecting answer keys and unapproved results.

Retained evidenceContent access, signed reading/rereading, saved responses and own training history.

• Record instructor-led, OJT, practical demonstration, external, workshop, self-study and blended delivery.
• Use a controlled SOP or Other / Non-Master Document reference with subject area, time, venue, participants and supporting documents.
• Select internal or external trainers whose authorization covers the subject area and training date.
• Schedule sessions, change the trainer, amend details or cancel with retained evidence.
• Close the session with an electronic signature and record the actual attendance and absence reasons for each planned trainee.
• Apply individual acknowledgement and assessment criteria before individual completion; connect the correct EM obligation and avoid duplicate assignment/session obligations.
• Retain completed-record corrections and produce a completed-session report/PDF with attendance, individual completion, assessment and EM summaries.
• Keep the selected trainer out of the trainee list, including an external trainer linked to a system account.
• For SOP training, link the exact-version SOP assignment to each attendee even when assessment and EM are both not required; individual work follows signed attendance and completion rules.
• Record New Training, Retraining, Refresher Training or Revision / Change Training as a separate Training Requirement for SOP and Other-document sessions.
• Keep make-up delivery linked to the specific earlier obligation when appropriate; independent repeat training remains separate.

Retained evidenceSigned session closure, attendance, individual records, assessment/EM links and completed-session report.

• Score equal-weight questions using binary marks with no partial credit and the reviewed 80% pass rule.
• Allow one active attempt and a maximum of two attempts in an assignment cycle, with safe draft recovery and idempotent submission.
• Review questions, learner responses, approved answers, automatic results and overall score together.
• Confirm with an electronic signature; apply authorized per-response overrides with reasons and retain controlled signed corrections.
• Release the approved result to the trainee and represent confirmed completion through the retained evaluation and assignment record.

Retained evidenceLocked responses, automatic marks, signed Manager evaluation and correction history.

• Require rereading after the first confirmed failure before the second assessment attempt.
• Close the cycle after the second confirmed failure and surface it in a dedicated Manager reassignment queue.
• Create a fresh linked assignment with its own attempt cycle while preserving the original failure and evaluation records.
• Follow replacement outcomes in the chronological failure and reassignment report.

Retained evidenceFailure/rereading history, closed second failure and linked replacement cycle.

• Prepare requests for internal or external trainers, optionally linked to a system user, with Function / Subject Area scope.
• Record qualification basis, SOP training evidence, supporting attachments, effective dates and restrictions.
• Draft, edit, submit or withdraw requests; QA can approve, return or reject through a signed decision.
• Correct and resubmit returned requests with retained decision history.
• Inspect authorization status and expiry; suspend or revoke with controlled evidence, and validate the authorization when scheduling delivery.
• Show Authorized trainers first, followed by Authorization requests and Signed authorization history.
• Let the permitted Manager/HOD assign SOP training evidence for a trainer request; retain controlled assignment references and approval history.

Retained evidenceRequest, qualification basis, attachments, QA decision and authorization lifecycle.

• Plan EM required or not required, method and due date; create tasks after the applicable individual training completion criteria.
• Resolve responsibility from approved relationships and show Pending Owner Resolution when an authorized owner cannot be resolved.
• Show only the logged-in responsible person’s own EM tasks in My EM Tasks, including pending, overdue and completed work. Broader reporting permission does not add other evaluators’ tasks to this personal queue.
• Reassign open tasks with a reason or sign a controlled method change; preserve the task history.
• Record conducted date, criteria, Effective / Not Effective outcome, remarks and optional supporting files through an electronic signature.
• Require action details for Not Effective outcomes and allow controlled follow-up retraining through a linked assignment or session.
• Completed EM is read-only for every role, for Effective and Not Effective outcomes alike. Keep the signed result and existing evidence without reopening it for correction.
• Track each EM obligation with a permanent EM reference; keep owner changes and open-task method changes in its retained history.

Retained evidenceEM plan, obligation, responsible evaluator, signed outcome/evidence and linked follow-up.

• Filter by period, department, Function / Subject Area, SOP / Training Item and EM method.
• Review EM required, completed, pending, overdue, Effective and Not Effective counts with monthly coverage and effectiveness rates.
• Calculate coverage as EM Completed ÷ EM Required Trainings × 100; exclude trainings where EM was not required.
• Calculate effectiveness as Effective ÷ (Effective + Not Effective) × 100; exclude pending, overdue and cancelled outcomes.
• Group by Training Completion Date: a March EM review of January training updates January’s cohort and counts the obligation once.
• Inspect Not Effective cases by department; overall percentages use underlying counts, with a dash when the denominator is empty.

Retained evidenceScoped monthly counts, underlying percentage denominators and Not Effective department breakdown.

• Prepare Instrumental / Chemical Analysis eligibility with the required Analyst Training Matrix attachment and the trainee’s historical identity.
• Submit the request to QA; review, return for correction, approve or reject under the permitted authority and scope.
• Retain the decision, required remarks, signed approval and earlier eligibility history; training completion alone is not an eligibility approval.
• New analyst qualification recording has been removed. Existing qualification records remain available as retained history where authorized.

Retained evidenceEligibility requests, Analyst Training Matrix evidence, signed QA decisions and retained history.

• Issue a durable numbered PDF linked to confirmed training completion, trainee/SOP context, score, template version and approver.
• Show the learner’s own certificates and an authorized searchable certificate register.
• Verify the retained PDF checksum when delivered.
• Reissue or revoke through a signed reasoned action and retain the earlier certificate artifacts.
• Use controlled certificate numbering and the approved trainee identity, Designation, training reason and assessment wording. Preserve signed PDFs when profiles later change.

Retained evidenceNumbered PDF, template version, signature manifestation and prior artifact history.

• Include required EM obligations from completed assignment and session training, including Other / Non-Master Documents. Explicitly linked delivery is counted once.
• Filter by department, EM status and EM due-date range, with optional trainee, training item, method and training-source filters.
• See Pending, Overdue, Completed, unresolved-owner and EM Task Missing exceptions. Due today remains pending; cancelled tasks are excluded unless selected.
• Show historical trainee and evaluator details, training completion, method, due/conducted dates, signed outcome and remarks. Missing or conflicting evidence remains Not recorded.
• Use the same scoped data in the preview, printable A3 landscape PDF and inspection-package CSV; long remarks and supported Unicode names remain readable.

Retained evidenceConsistent preview, A3 landscape PDF and inspection-package CSV with permanent EM references.

• Review scoped workload, completion and department counts for the selected assigned period and reporting cut-off.
• Review assessment and EM against their training-completion cohorts; later EM results update the original training cohort.
• See current overdue training by due month and current open exceptions, with reasons and links to the relevant permitted register.
• Keep training, failed/retraining work and EM outcomes distinct so totals can be understood without double counting.
• Use the dedicated management-summary permission; technical administration alone does not grant this business review access.

Retained evidenceRead-only workload cards, monthly charts, accessible count tables and links to permitted underlying registers.

• Use trainee and Manager work summaries to identify due work and pending evaluation; an Auditor’s access follows review permissions.
• Review the training matrix with assignment-owned Completed On dates, trainee history and SOP history.
• Inspect failure/reassignment chains, certificate records, completed-session reports and the EM Trend view.
• Generate the supported filtered readable PDF/CSV outputs and asynchronous owner-scoped export jobs.
• Build inspection ZIP packages containing readable exports, stable identifiers, applied criteria and a file-size/checksum manifest.
• Retain generated, failed, downloaded and expired export events and apply controlled artifact expiry.
• Keep Training Source visible in the Training Matrix: distinguish manual SOP assignments, curriculum, planned schedule and session delivery while retaining the actual originating obligation.
• Use a consistent Matrix layout for name, Designation, Employee ID, SOP/version, source, readable training reference, dates, trainer, assessment, reason and status.
• Use recorded historical identity and explicitly linked trainer evidence. For manual SOP reading supported by a valid signed acknowledgement, display Self Study / N.A. regardless of assessment outcome; do not assume the assigner was the trainer.
• Show Designation in Trainee History and Failures and Reassignments; remove Role from the SOP History display while retaining technical roles for traceability.

Retained evidenceFiltered reports, readable exports, stable record IDs and SHA-256 inspection manifests.

• Find submitted papers by trainee, SOP, submission period and result.
• Review the locked submitted responses and associated evaluation evidence.
• Download the authorized answer-paper PDF while keeping trainee answer-key access restricted.

Retained evidenceReadable submitted-response and evaluation evidence, with authorized PDF download.

• Show permission-based in-app notifications and let recipients mark them as read.
• Notify Managers of overdue SOP review dates and training assignments.
• Configure scheduled SMTP reminders with delivery deduplication and repeat intervals; email requires an operational mail configuration.

Retained evidenceNotification read state and deduplicated reminder delivery records.

• Review unified Platform and Training activity with friendly labels, resolved user names, global sorting, filters and cursor pagination.
• Expand original technical evidence and produce human-readable filtered audit exports.
• Reauthenticate for electronic signatures and bind signer identity, time, meaning, statement and record hash to the action.
• Retain append-only audit and signature records, including failed reauthentication security events.
• Record audit-trail reviews with period, scope, conclusion, exceptions and corrective-action references.

Retained evidenceActor, time, action, record, outcome, reason, signature meaning and record hash.

• Control nine categories: Department, Designation, Training Type, Training Rule, Signature Meaning, Report Definition, Qualification, Function / Subject Area and Training Venue.
• Prevent normalized duplicates and require reasons for controlled creation and retirement.
• Preserve historical values and apply dependency restrictions; rename or reactivate supported subject areas and venues.
• Connect subject areas to SOPs, trainer authorization and trainer-led session scheduling.

Retained evidenceApproved values, normalized uniqueness, controlled changes and historical use.

• Enforce password history, age and warnings, lockout, inactivity and absolute session expiry, logout and revocation.
• Use anti-forgery protection, secure-cookie settings, rate limits, security headers, safe errors and request correlation identifiers.
• Retain artifacts privately and verify integrity; inspect health/readiness, storage, runtime, host clock, export jobs and certificate errors.
• Review a non-secret effective configuration version/fingerprint and backup/restore status.
• Sign maintenance mode to block business activity during controlled upgrades or recovery.
• Use the included encrypted complete-backup, checksum verification and restore scripts, HTTPS pilot ingress and controlled migration runbooks.
• Support desktop and mobile browser layouts, keyboard focus and readable workflow feedback.

Retained evidenceOperational status, configuration fingerprints, signed maintenance and recovery runbooks.