- Using SafetyCulture
- What are actions?
What are actions?
Learn more about actions, helping your team to identify, track, collaborate, and complete tasks together.
What are actions?
The Actions feature allows you to identify, track, and complete tasks as a team. You can create actions to highlight a task that needs completing as you're conducting an inspection, reading a web report, or simply being on the go. Each action includes a built-in chat and activity feed, where your team members can collaborate. All with built-in timestamps in a timeline so you can keep track of everyone's interaction from start to finish.
Actions in SafetyCulture
There will be times when you want to create tasks while conducting inspections or reviewing the inspection's web report. In these scenarios, not only can you create actions for each question, but you can also add logic fields to specific questions to require actions, so that users can't complete an inspection until they've created or linked an action.
If your organization utilizes the Assets feature to track and manage assets, the asset profile page can be your source of truth for everything you need to know about them. From an asset's profile page, you can create and pre-fill actions with the asset, as well as view all completed and open actions relevant to the asset.
There may be times when you want to create tasks that are not linked to any inspections. In these instances, you can create standalone actions from the action list to assign, track, collaborate with your team members, and get things done. Not only that, standalone actions can be repeated to automate and schedule routine tasks.
Each business may have its own language for its task management processes, so rather than using the default "In Progress" or "Complete" as indicators for progress, you can customize the name for each status to something relevant to you and your team.
We understand that you may only want specific users to review actions before marking them as complete. You can manage action status transitions so that only certain users can move actions to certain statuses, giving stakeholders the opportunity to review the work that's been done.
Manage action detail field editing so that only certain users can edit fields such as the due date, giving action creators the confidence that details won't be changed deliberately or accidentally.
We recommend that you familiarize yourself with the fields that can be configured when creating and updating actions, allowing you to provide as much detail as possible for your team.
The action title. Allows up to 255 characters.
The action description. Allows up to 500 characters.
The action site. Keep in mind that if you create an action in an inspection that has the site selected already, the action would be prefilled with that site.
The action assignees. You can assign actions to anyone in your organization, which by default, the assignees would receive email and app push notifications unless configured otherwise. You can also assign actions to people outside your SafetyCulture organization via email. Please note that assigning actions to yourself does not trigger notifications.
The action priority. New actions by default have the "Low" priority selected, which you can update to set a new priority or have no priority at all.
The action due date and time. New actions by default have the due date set to exactly seven days from when the action is created, which you can update to set a new due date, or have no due date at all. If you use the "Priority" field, you can set each action's due date automatically based on the priority that's selected.
The action label. A label can be added to your actions to further organize and classify your actions.
An asset can be added to your actions and these actions will be available in the asset's profile under the "Activity" list.
For each action, you can set one of the three available priorities to help your team members can prioritize tasks that require more attention. You can also automate each action's due date based on the selected priority, further helping you and your team to plan which tasks to complete first when creating actions.
While actions created from an inspection follow the inspection access rules, access to standalone actions can be easily configured so that each action is available to all users in your organization, just site members, or only the creator and assignee.
Despite seeing your team members getting things done by completing actions, you can't help but notice the endlessly growing number of actions. With that in mind, we wanted to help you to organize all of them so you can quickly identify a group of related actions using labels.
Thank you for letting us know.