SoftExpert Action plan tasks

Introduction

Tasks are pending system activities for which a user is responsible. They are divided into two categories: Execution and Tracking.

The tracking option gathers the tasks for which the logged user is responsible, but whose execution is assigned to someone else.

The execution option, in its turn, gathers all the demands the logged user needs to resolve within a defined deadline or period.

See further details on the SoftExpert Action Plan tasks. They will be listed by their names:

Planning approval
Who receives it	Users who compose the route responsible for approving the planning of the action plan or isolated action.
When	The planning of the action plan or of the isolated action is finished.
Purpose	Approve the planning of an action plan or an isolated action.

Request execution
Who receives it	The party responsible for executing the request, defined in the SoftExpert Request component.
When	The issue/approval step (as configured) is finished by the due responsible parties in the SoftExpert Request component.
Purpose	Create action plans to meet the needs of the requesters.

Action rescheduling request execution
Who receives it	User and team members responsible for the action plan to which the action belongs. User and team members responsible for the isolated action.
When	The issue/approval step (as configured) is finished by the due responsible parties in the SoftExpert Request component. Action rescheduling requests can be issued through the Request section on the data screen of the action while it is in the "Execution" step.
Purpose	Reschedule the start and end dates of the action and/or change the party responsible for executing it.

Action execution
Who receives it	SoftExpert Suite user and team members responsible for executing the plan action. SoftExpert Suite user and team members responsible for executing the isolated action.
When	The planning step of an action plan or isolated action that does not have the approval step configured is finished, and the record is sent to the next step. The action plan or the isolated action planning is finished.
Purpose	Allow the responsible parties to start the execution of the planned action, either isolated or action plan actions, enter important information about the execution, and finish it.

Planning
Who receives it	User and team members responsible for the action plan planning. User and team members responsible for the isolated action.
When	The action plan remains in planning, that is, it is not sent to the next step. The isolated action remains in planning, that is, it is not sent to the next step.
Purpose	Allow those responsible to confirm whether the implementation of the isolated action/action plan is in accordance with the pre-established objectives.

Action verification
Who receives it	Users that compose the route responsible for the effectiveness verification of the action plan or isolated action.
When	The execution of a planned action plan action is finished The planning of the plan to which an immediate action belongs is finished or approved, according to the settings performed in its category.
Purpose	Allow those responsible to confirm whether the implementation of the isolated action/action plan is in accordance with the pre-established objectives.

Effectiveness verification
Who receives it	Users that compose the route responsible for the effectiveness verification of the action plan or isolated action.
When	The execution of a planned isolated action is finished. The planning of an immediate isolated action is finished or approved, according to the configurations set in its category. The execution of all the actions that make up a plan is finished or verified, according to the configurations set in its category.
Purpose	Allow those responsible to confirm whether the implementation of the isolated action/action plan is in accordance with the pre-established objectives.

To understand how planning approval works, access the Approving the planning of action plans and isolated actions article.

To understand how action plan execution works, access the Executing an action from a plan article.

To understand how isolated action execution works, access the Executing an isolated action article.

To understand how action plan planning works, access the Planning an action plan article.

To understand how isolated action rescheduling works, access the Planning an isolated action article.

To understand how the verification of the actions of a plan works, access the Executing the verification of action plan actions article.

To understand how effectiveness verification works for an action plan, access the Verifyng the effectiveness of the action plan article.

To understand how effectiveness verification works for an isolated action, access the Verifying the effectiveness of the isolated action article.

Action and action plan tracking
Who receives it	User and team members responsible for the action plan. User and team members responsible for the isolated action.
When	The planning step of the action plan or isolated action is finished and the record is sent to the next step.
Purpose	Track the action plan/isolated action during its execution and perform the necessary adjustments.

As the tasks are executed and closed, they cease to appear on the list of pending records in the Task center.