Digital Lock On

Appearance

Verification Matrix — Worker Sign-on and Lock-on ​

Implements:

  • REQ-WORK-001 Worker Sign-on and Lock-on
  • REQ-WORK-002 Worker Roles (Competencies)
  • REQ-WORK-004 Manual Sign On

Requirement → Scenario Index ​

Requirement RefRequirement (short)Scenario IDs
REQ-WORK-001: QR Lock-on
EDR-1SP initiates lock-on, QR scan availableTC-WORK-SIGNON-001
EDR-2QR scanned, worker details displayedTC-WORK-SIGNON-002
EDR-3Role assigned during lock-onTC-WORK-COMP-001
EDR-4Safety competency check requiredTC-WORK-SIGNON-003
EDR-5Success confirmation displayedTC-WORK-SIGNON-004
EDR-6Worker list and count updatedTC-WORK-SIGNON-005
UBI-1Streamlined consecutive lock-on workflowTC-WORK-CONSEC-001
REQ-WORK-002: Competencies
EDR-1Competency assigned at lock-onTC-WORK-COMP-001
EDR-2Competency update loggedTC-WORK-COMP-003, TC-WORK-COMP-004
SDR-1SP can update worker competency during shiftTC-WORK-COMP-003
UBI-1Competencies persist per worksiteTC-WORK-COMP-006
REQ-WORK-004: Manual Lock-on
EDR-1Manual lock-on availableTC-WORK-MANUAL-001, TC-WORK-MANUAL-002
EDR-2Creates new user record and locks onTC-WORK-MANUAL-004
EDR-3Minimal data required (name, phone, email, company)TC-WORK-MANUAL-004
UBI-1Offline operation supportedTC-WORK-MANUAL-002
Cross-cutting
UNW-1Already locked on blocks lock-onTC-WORK-SIGNON-009
UNW-2Invalid QR rejectedTC-WORK-SIGNON-006
UNW-3Locked on different site blocks lock-onTC-WORK-SIGNON-010
UNW-4Wrong authority blocks accessTC-WORK-SIGNON-011

Scenarios (at a glance) ​

IDTitleType
1.1 QR Lock-on (REQ-WORK-001)
TC-WORK-SIGNON-001 (3.4.1.1)QR scan option available to SP (Own)Positive
TC-WORK-SIGNON-002 (3.4.1.1)Valid QR displays worker detailsPositive
TC-WORK-SIGNON-003 (3.4.1.1)Safety check required before lock-onPositive
TC-WORK-SIGNON-004 (3.4.1.1)Lock-on succeeds with confirmationPositive
TC-WORK-SIGNON-005 (3.4.1.1)Worker list and active count updatedPositive
TC-WORK-SIGNON-006 (3.4.2.1)Invalid QR code rejectedNegative
TC-WORK-SIGNON-009 (3.4.2.2)Already locked on blocks lock-onDefensive
TC-WORK-SIGNON-010 (3.4.2.3)Locked on different site blocks lock-onDefensive
TC-WORK-SIGNON-012Offline QR lock-on succeedsEdge
TC-WORK-SIGNON-013 (3.4.1.3, 3.4.3.3)Returning worker re-locks on successfullyPositive
1.2 Competency Assignment (REQ-WORK-002)
TC-WORK-COMP-001 (3.4.1.1)Default competency 'C' assigned at lock-onPositive
TC-WORK-COMP-002Additional competencies assigned at lock-onPositive
TC-WORK-COMP-003 (5.4.1)Competency updated during shiftPositive
TC-WORK-COMP-004 (5.4.2)Competency removal during shiftPositive
TC-WORK-COMP-005SP (Other) cannot update competenciesNegative
TC-WORK-COMP-006 (3.4.1.3)Returning worker has competencies pre-selectedPositive
TC-WORK-COMP-007Different worksite has no pre-selectionPositive
TC-WORK-COMP-008Competencies visible in worker detailsPositive
1.3 Manual Lock-on (REQ-WORK-004)
TC-WORK-MANUAL-001 (3.5.1.1)Manual lock-on succeeds onlinePositive
TC-WORK-MANUAL-002Manual lock-on succeeds offlineEdge
TC-WORK-MANUAL-004 (3.5.1.1)Enter new worker details and create recordPositive
TC-WORK-MANUAL-005SP (Other) cannot manually lock onNegative
1.4 Consecutive Operations
TC-WORK-CONSEC-001Lock on 10 workers consecutively via QREdge
TC-WORK-CONSEC-002Lock on Worker A then Worker B immediatelyEdge
TC-WORK-CONSEC-003 (3.7)Full lifecycle: lock on, assign, update, lock offIntegration

Scenario details ​

1.1 QR Lock-on (REQ-WORK-001) ​

TC-WORK-SIGNON-001: QR scan option available to SP (Own)
  • Arrange
    • User is logged in as Site Protector assigned to Worksite A
    • Worksite A is Enabled
    • No workers currently locked on
  • Act
    • SP navigates to lock-on workflow
  • Assert
    • QR scan option is visible and available
    • SP can initiate QR scanning

TC-WORK-SIGNON-002: Valid QR displays worker details
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worker has valid QR code
    • Worker state: Not on Site
  • Act
    • SP scans worker's QR code
  • Assert
    • System displays worker details (name, ID)
    • System prompts for competency assignment
    • System prompts for safety competency check

TC-WORK-SIGNON-003: Safety check required before lock-on
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worker QR code scanned successfully
    • Worker state: Not on Site
  • Act
    • SP attempts to complete lock-on
  • Assert
    • System requires confirmation that worker is "competent and current/prepared for work"
    • Lock-on button remains disabled until safety check confirmed

TC-WORK-SIGNON-004: Lock-on succeeds with confirmation
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worker QR scanned, details displayed
    • Competency assigned (defaults to 'C')
    • Safety check completed
    • Device is online
  • Act
    • SP confirms lock-on
  • Assert
    • System displays success confirmation
    • Worker state changes to Locked On (Active)
    • Shift tracking begins

TC-WORK-SIGNON-005: Worker list and active count updated
  • Arrange
    • User is logged in as Site Protector (Own)
    • Active count shows 0 workers
    • Worker successfully locked on
  • Act
    • SP views worksite overview
  • Assert
    • Worker appears in active workers list
    • Active count incremented to 1
    • Worker competency and details visible

TC-WORK-SIGNON-006: Invalid QR code rejected
  • Arrange
    • User is logged in as Site Protector (Own)
    • QR code is invalid/expired/corrupted
  • Act
    • SP scans invalid QR code
  • Assert
    • System displays error message
    • QR validation fails
    • No worker details displayed
    • Lock-on does not proceed

TC-WORK-SIGNON-009: Already locked on blocks lock-on
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worker is currently Locked On (Active) to this worksite
  • Act
    • SP scans worker's QR code
  • Assert
    • System displays error: "Worker already locked on"
    • Lock-on does not proceed

TC-WORK-SIGNON-010: Locked on different site blocks lock-on
  • Arrange
    • User is logged in as Site Protector for Worksite A
    • Worker is currently Locked On (Active) to Worksite B
    • Both worksites in same PWA
  • Act
    • SP scans worker's QR code
  • Assert
    • System displays error: "Worker locked on different site, must lock off first"
    • Lock-on blocked
TC-WORK-SIGNON-012: Offline QR lock-on succeeds
  • Arrange
    • Device is offline
    • User is logged in as Site Protector (Own)
    • Worker has valid QR code
    • Worker state: Not on Site
  • Act
    • SP scans QR, assigns competency, confirms safety check
    • SP completes lock-on
  • Assert
    • Lock-on succeeds locally
    • Worker state changes to Locked On (Active)
    • Shift tracking begins
    • Event queued for sync when online

TC-WORK-SIGNON-013: Returning worker re-locks on successfully
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worker state: Locked On (Returning) - previously locked off with "returning to site later"
    • Worker has valid QR code
  • Act
    • SP scans worker's QR code
    • SP confirms safety check
  • Assert
    • Re-lock-on succeeds
    • Worker state changes to Locked On (Active)
    • Same shift continues (shift tracking maintained)
    • Active count incremented

1.2 Competency Assignment and Updates (REQ-WORK-002) ​

TC-WORK-COMP-001: Default competency 'C' assigned at lock-on
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worker QR scanned successfully
    • No additional competencies selected
  • Act
    • SP completes lock-on without explicitly selecting competency
  • Assert
    • System assigns default competency 'C' (Competent and Current)
    • Worker locked on successfully with 'C' competency
    • Competency visible in worker details

TC-WORK-COMP-002: Additional competencies assigned at lock-on
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worker QR scanned successfully
  • Act
    • SP selects additional competencies: FA, ESO
    • SP completes lock-on
  • Assert
    • Worker locked on with competencies: C, FA, ESO
    • All competencies visible in worker list
    • Competencies logged in audit trail

TC-WORK-COMP-003: Competency updated during shift
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worker is Locked On (Active) with competency 'C'
  • Act
    • SP selects worker
    • SP selects "Change competencies"
    • SP adds competency 'GMO'
    • SP saves
  • Assert
    • Worker competencies updated to: C, GMO
    • Update logged with timestamp
    • Updated competencies visible immediately

TC-WORK-COMP-004: Competency removal during shift
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worker is Locked On (Active) with competencies: C, FA, ESO
  • Act
    • SP selects worker
    • SP selects "Change competencies"
    • SP deselects 'ESO'
    • SP saves
  • Assert
    • Worker competencies updated to: C, FA
    • Removal logged with timestamp
    • Updated competencies reflected in worker list

TC-WORK-COMP-005: SP (Other) cannot update competencies
  • Arrange
    • User is logged in as Site Protector assigned to Worksite B
    • Worker is Locked On (Active) to Worksite A
  • Act
    • SP (Other) attempts to update worker competencies
  • Assert
    • Access denied
    • Competency update action not available or blocked

TC-WORK-COMP-006: Returning worker has competencies pre-selected
  • Arrange
    • Worker previously locked on to Worksite A with competencies: C, FA, STMS
    • Worker shift ended
    • Worker returns to Worksite A on new shift
  • Act
    • SP scans worker QR for lock-on
  • Assert
    • System pre-selects previous competencies: C, FA, STMS
    • SP can modify if needed
    • Worksite-specific memory working correctly

TC-WORK-COMP-007: Different worksite has no pre-selection
  • Arrange
    • Worker previously locked on to Worksite A with competencies: C, FA
    • Worker now locking on to Worksite B for first time
  • Act
    • SP scans worker QR for lock-on to Worksite B
  • Assert
    • System shows only default 'C' (no pre-selection)
    • Competency memory is worksite-specific
    • SP must select additional competencies if needed

TC-WORK-COMP-008: Competencies visible in worker details
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worker is Locked On (Active) with competencies: C, FA, ESO, GMO
  • Act
    • SP views worker details in active workers list
  • Assert
    • All assigned competencies visible: C, FA, ESO, GMO
    • Competencies clearly labelled
    • Easy to identify worker capabilities

1.3 Manual Lock-on (REQ-WORK-004) ​

TC-WORK-MANUAL-001: Manual lock-on succeeds online
  • Arrange
    • User is logged in as Site Protector (Own)
    • Device is online
    • Worker exists in system but QR code unavailable
    • Worker state: Not on Site
  • Act
    • SP initiates manual lock-on
    • SP selects worker from list
    • SP assigns competency, confirms safety check
    • SP completes lock-on
  • Assert
    • Lock-on succeeds
    • Worker state changes to Locked On (Active)
    • Active count incremented
    • Audit trail records manual lock-on method

TC-WORK-MANUAL-002: Manual lock-on succeeds offline
  • Arrange
    • Device is offline
    • User is logged in as Site Protector (Own)
    • Worker exists in cached data
    • Worker state: Not on Site
  • Act
    • SP initiates manual lock-on offline
    • SP selects worker, assigns competency, confirms safety check
    • SP completes lock-on
  • Assert
    • Lock-on succeeds locally
    • Worker state changes to Locked On (Active)
    • Event queued for sync

TC-WORK-MANUAL-004: Enter new worker details and create record
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worker needs to be locked on but has no QR code (temporary worker, visitor, or QR unavailable)
    • Worker state: Not on Site
  • Act
    • SP initiates manual lock-on
    • SP enters worker details:
      • Name (required)
      • Phone (required)
      • Email (required)
      • Company (required)
    • SP assigns competency, confirms safety check
    • SP completes lock-on
  • Assert
    • New user record created in Admin database
    • Worker immediately locked on to worksite
    • Worker state: Locked On (Active)
    • Active count incremented
    • All required fields captured
    • Note: Duplicate records acceptable if worker entered multiple times

TC-WORK-MANUAL-005: SP (Other) cannot manually lock on
  • Arrange
    • User is logged in as Site Protector assigned to Worksite B
    • Attempting to manually lock on worker to Worksite A
  • Act
    • SP (Other) attempts manual lock-on
  • Assert
    • Access denied
    • Manual lock-on not available for other worksites

1.4 Consecutive Operations ​

TC-WORK-CONSEC-001: Lock on 10 workers consecutively via QR
  • Arrange
    • User is logged in as Site Protector (Own)
    • 10 workers with valid QR codes ready
    • All workers state: Not on Site
    • Device online
  • Act
    • SP scans Worker 1 QR, assigns competency, confirms safety, locks on
    • SP immediately scans Worker 2 QR, repeats process
    • SP continues for all 10 workers in rapid succession
  • Assert
    • All 10 workers locked on successfully
    • Streamlined workflow maintained throughout
    • Active count shows 10
    • No performance degradation
    • All workers visible in active list

TC-WORK-CONSEC-002: Lock on Worker A then Worker B immediately
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worker A and Worker B both state: Not on Site
  • Act
    • SP locks on Worker A
    • SP immediately initiates lock-on for Worker B (no delay)
  • Assert
    • Both workers locked on successfully
    • No interference between operations
    • Both workers shown in active list
    • Active count: 2

TC-WORK-CONSEC-003: Full lifecycle: lock on, assign, update, lock off
  • Arrange
    • User is logged in as Site Protector (Own)
    • Worker state: Not on Site
    • Device online
  • Act
    • SP locks on worker via manual lock-on (creates new user record)
    • SP assigns default competency 'C'
    • SP assigns additional competency 'FA'
    • SP updates competency to add 'ESO'
    • SP locks off worker (covered in lock-off tests)
  • Assert
    • All operations succeed in sequence
    • New user record created successfully
    • Each step properly recorded
    • Audit trail complete
    • Worker state transitions correct throughout

Internal use only