---
title: Creating an Action
description: "# **Creating an Action** Creating an action in uAuditor allows users to assign corrective tasks to team members and track their progress until completion. Actions help ensure issues identified during inspections or daily operations are addressed quickly and consistently. Actions…"
url: "https://uauditor.com/ar/help-center/actions/managing-actions/creating-an-action/"
updated: "2026-05-03"
category: Actions / Managing Actions
---

# Creating an Action

# **Creating an Action**

Creating an action in uAuditor allows users to assign corrective tasks to team members and track their progress until completion. Actions help ensure issues identified during inspections or daily operations are addressed quickly and consistently.

Actions can be created manually from the Actions module or automatically from failed inspection items (if auto-assignment is enabled).

## **When to Create an Action**

You should create an action when:

- an inspection item fails
- a safety issue is identified
- equipment requires maintenance
- a compliance gap is detected
- a follow-up task must be assigned
- an operational improvement is required

Creating actions ensures issues are documented and resolved in a structured workflow.

## **How to Create an Action**

To create a new action:

1. Open the Actions module
2. Click Create Action
3. Enter the action title
4. Add a description (optional but recommended)
5. Select priority level
6. Assign the action to a user
7. Select location or equipment if applicable
8. Set a due date
9. Add watchers if needed
10. Click Save

The action becomes immediately visible to the assigned user.

## **Required Information When Creating an Action**

Depending on system configuration, some fields may be required before saving the action.

Typical required fields include:

- action title
- assignee
- due date
- location (if location-based permissions apply)

Optional requirements such as media attachments or descriptions may also be enforced by administrators.

## **Setting Action Priority**

Priority helps teams understand how urgent the action is.

Common priority examples include:

- High — requires immediate resolution
- Medium — should be completed soon
- Low — routine follow-up task

Using priorities improves workload planning across teams.

## **Assigning the Responsible User**

Each action must have a responsible assignee who is expected to resolve the issue.

You can assign actions to:

- specific users
- location administrators
- predefined responsible roles (depending on configuration)

Clear assignment ensures accountability.

## **Linking Actions to Locations or Equipment**

Actions can be linked to:

- branches or locations
- assets or equipment
- inspection items (when created from inspections)

Linking actions improves traceability and reporting accuracy.

## **Adding Watchers to an Action**

Watchers are users who receive visibility into the action without being responsible for completing it.

Watchers can:

- monitor progress
- receive updates
- review supporting evidence
- participate in discussions

This helps supervisors stay informed without managing the task directly.

## **What Happens After Creating an Action**

Once created:

- the assignee receives visibility of the action
- the action appears in the Actions module
- the due date countdown begins
- status tracking starts automatically
- watchers receive updates if configured

The action remains active until completed or updated.

## **Best Practices for Creating Actions**

To create effective actions:

- use clear and descriptive titles
- assign actions to the correct responsible user
- set realistic due dates
- include supporting context in descriptions
- attach evidence when available

Creating well-defined actions helps ensure faster resolution and stronger operational follow-up across locations.