You can add checklist items to any step in Runway to cover any unique parts of your team's release process.
A step won't be marked as complete (green) in Runway until all checklist items have been completed -- in addition to the normal criteria that would mark a step as completed.
When a checklist item is marked as completed, Runway will keep track of when the status changed, and who updated it.
An example Kickoff checklist
Each step has a Checklist tab, from which you can view the list of all checklist items, or Add items to the list or Edit the existing list.
If you click the Edit button, you'll see additional controls to Delete an item, Edit an item's details, or re-order the list. Hit Done when you're finished making changes.
Click the Add button to create a new checklist item.
Create checklist item dialog
Specify which step of the release process this checklist item applies to.
Specify which types of releases (major, minor, point, hotfix) require this checklist item.
A name for this task. This appears on the checklist itself, as well as notifications related to updates on this item.
Keep this option selected if you want your team to be notified about updates to this item during a release cycle. Runway will post in Slack when a task is completed, or was formerly completed but reverted, as well as who performed the change and when.
Optional - You can add information here that can easily be surfaced in Runway for team members working on this task. These notes serve as documentation available on every release cycle. Markdown is supported, and there's a built-in viewer.
Optional - Specify a role here if a task is intended to be completed by a team member from a specific group. This may affect which team members signed into Runway have permissions to mark this task as 'completed' or revert a completed status.