Hello, how can we help you?

Recent Searches: Closing an audit - Accessing a scope or working paper via link - Creating an audit plan - Creating an audit template

SoftExpert Project to-do tasks

 

Prerequisite

  • Access to the My tasks menu.

 

Introduction

To-do tasks are records generated for users to take certain actions. They are divided into two categories: Execution and Tracking.

Despite being under the responsibility of a specific user, tracking tasks do not need to be executed by them.

Execution tasks need to be carried out by the user within a defined period.

See the details of the SoftExpert Project to-do tasks below:

 

Execution tasks

Task execution approval

Who receives it Users who are part of the route responsible for approving the execution, as configured on the task data screen.
When Once the execution of a task with configured approval step is closed.
Purpose To approve or reject the execution of the task, ensuring that the result is in accordance with the established objectives.
 
 

Project and program approval

Who receives it Users who are part of the route responsible for the approval, as configured on the project/program data screen.
When Once the planning, closure, or revisions of the project/program with configured approval step are completed.
Purpose To approve or reject the steps of the project/program, ensuring that the result is in accordance with the established objectives.
 
 

Request execution

Who receives it
  • Creation: party responsible for executing the request; said party is defined in the type or during the issuance of the request. 
  • Revision: responsible users or members of the teams responsible for the project that must be revised.

In order for this task to be generated, the SoftExpert Request component must be part of the solutions acquired by your organization.

When The issue/approval step (as configured) is finished by the due responsible parties in the SoftExpert Request component.
Purpose To plan or revise projects and programs in order to meet the requesters' needs.
 
 

Project evaluation

Who receives it Member of the control matrix associated with the project type under evaluation.
When The planning of the project is finished.
Purpose To help measure and regularly monitor the project in order to identify variations so that corrective actions can be taken when needed.
 
 

Revision acknowledgment

Who receives it Responsible parties defined on the project/program data screen.
When The planning and revisions of the project/program are finished.
Purpose To warn users that a project/program has gone through revision.
 
 

Program closure

Who receives it User and team responsible for the program.
When The execution of the program is finished.
Purpose To allow the responsible parties to finish the execution of the program.
 
 

Project closure

Who receives it User and team responsible for the project.
When The execution of the project is finished.
Purpose To allow the responsible parties to finish the execution of the project.
 
 

Risk action execution

Who receives it User responsible for the action that will treat the risk identified in the project.
When The planning of the project with which the risk is associated is closed.
Purpose To treat the risk identified in the project.
 
 

Task execution

Who receives it Users and teams responsible for the task. 
When Once project planning is finished or approved.
Purpose To execute project tasks.
 
 

Cost payments

Who receives it
  • Users and teams responsible for the task, project, or program.
  • Team responsible for the cost.
When The due date is reached without the cost being marked as paid.
Purpose To enter the actual values of a cost in order to mark it as paid.
 
 

Program planning

Who receives it Responsible user and members of the team responsible for the program.
When While the program is under planning, that is, until it is sent to the next step.
Purpose To finish the planning of a program.
 
 

Project planning

Who receives it Responsible user and members of the team responsible for the project.
When While the project is under planning, that is, until it is sent to the next step.
Purpose To finish the planning of the project.
 
 

Revenue collections

Who receives it
  • Responsible user and members of the team responsible for the task, project, or program.
  • Team responsible for the revenue.
When The due date is reached without the revenue being marked as received.
Purpose To enter the actual values of the revenue to mark it as received.
 
 

Project and program revision

Who receives it Responsible user and members of the team responsible for the projects and programs that will be revised.
When A revision is created for a project or program.
Purpose To execute the revision of projects and programs.
 
 

Task verification

Who receives it
  • If it is a task, the party responsible for the project.
  • If it is a sub-task, the party responsible for the summary task to which it belongs.
When A task with configured verification step is closed.
Purpose To confirm if the execution of a certain task is in accordance with the established objectives.
 
 

 

Tracking tasks

Program tracking

Who receives it User and team responsible for the program.
When Once program planning is finished or approved.
Purpose To track the execution of a program in order to check if it is in accordance with the established objectives.
 
 

Project tracking

Who receives it User and team responsible for the project.
When Once project planning is finished or approved.
Purpose To track the execution of a project in order to check if it is in accordance with the established objectives.
 
 

Risk tracking

Who receives it User responsible for tracking, defined during the association of the risk with the project.
When If the risk has a tracking period defined, the to-do task will be generated on the start date of the period. Otherwise, it will be generated when the status of the project with which the tracking is associated is "Execution".
Purpose To monitor the risks identified in the project.
 
 

Validation control

Who receives it Users who are part of the control matrix associated with the project type under evaluation.
When The planning of the project is finished and until it is closed.
Purpose To manage project evaluation control.
 
 

 

Conclusion

These are the to-do tasks of SoftExpert Project. They disappear from the to-do tasks menu as they are executed or closed.


Was this article helpful?