While you may only have one version of your standardized operating procedure now, with time you may need to make changes to it. Versions allow you to make a new copy of the procedure and edit it without releasing it for your team to run in operations until your ready to do so.
Gone are the days of waiting for new versions of procedures in Word docs or PDF files to circulate via email or on a shared cloud drive to be reviewed and approved. The platform has flexible workflows from creating procedures to activating them so they can be easily integrated into your operations.
The template for a procedure contains the content of the procedure. Keeni has robust workflows for revisioning procedures to can create additional versions of the template. Once a version of the template for a procedure has been activated, it can be run in your operations.
The template for a procedure starts in the draft status. When in the draft status, you can use our powerful template editor to edit the content and make your procedure actionable.
When you are done editing a template, you can submit the version for review and approval. One or more team members can be specified to review the version of the procedure.
Once a template for a procedure has been approved, it awaits its release. During this status, managers generally make sure their team members are aware of the changes to the procedure and are trained appropriately.
Once a template version is released and activated, it is then the authoritative version for running procedures. Keeni enforces that were can only be one active version of the procedure template.
When a new version or a procedure is activated, the currently active version will become Archived. Archived versions are locked. They can be viewed only.
Once you have at least one version of a procedure template, you can create your first revision. Keeni supports four methods of creating a new version.
Once you have a new version of the procedure template, use our powerful template editor to make the procedure actionable and interactive.
To provide more structure and context into the version control system, template versions can include a description and reason. These can be used to auto-populate the version history in a procedure.