Infield Checklist : Version management of templates

Related products: InField

Use Case

  • Checklists are part of a formal process / Standard Operating Procedure
  • Checklist Templates are created & formally approved, requiring restriction of access to create & edit checklist templates
  • Checklist Templates are version controlled
  • Approval Status & person responsible are identified;
    • Created by
    • Approved by
  • Status
    • Draft
    • Approved

 

Why is this important?

  • In regulated industries, checklists form part of the Validated records of production
  • Without formal version management Checklists cannot be used as formal records

@Tor Erik Kvisle  this is related to a discussion you had with Gary Goh recently


NewGathering Interest