E-signature version history

WHAT THIS IS

• E-signature version history is the system-wide tracking of all changes related to signed activities, activity templates, and operator e-signature identities. Every change creates a new version that is preserved and accessible for auditing.

WHY IT MATTERS

• This ensures full traceability across the system. It allows you to see what changed, when it changed, and who made the change—supporting compliance, accountability, and investigations.

WHEN YOU WOULD USE THIS

• Use this when:
  • You need to audit changes to a specific activity record
  • You want to review how an activity template has evolved
  • You need to track lifecycle events for an operator’s e-signature

HOW IT WORKS

• Factbird automatically creates a new version whenever a change occurs in the e-signature system. These versions are preserved and grouped based on where the change happened.
   
• At the activity level, each submission maintains its own version history. Every correction or update creates a new version while keeping previous ones intact. This provides a tamper-evident audit trail for that specific record.
   
• At the template level, configuration changes—such as enabling or disabling e-signature—are tracked over time. Each update to the template is recorded as a new version.
   
• At the operator level, the system logs all lifecycle events related to an e-signature identity. This includes creation, activation, deactivation, PIN resets, and lockouts. Each event is versioned and includes details about who performed the action and when.
   

• Together, these version histories provide a complete picture of changes across the system, allowing users to trace actions at the record, configuration, and identity levels.
  
  
  
  

  
  
  
  
  

   

   

KEY TERMS / COMPONENTS

• Version:
  • A snapshot of a record, template, or e-signature at a specific point in time
     
• Activity version history:
  • The list of all changes made to a specific activity submission
     
• Template version history:
  • The record of all configuration changes to an activity template
     
• E-signature audit log:
  • The lifecycle record of an operator’s e-signature identity, including all status and PIN-related events

COMMON MISUNDERSTANDINGS

• New versions replace old data:
  • Previous versions are never overwritten; all versions are preserved
     
• Version history is only for activities:
  • Version tracking exists across activities, templates, and operator e-signatures