SoftExpert Competency Tasks
This content was generated by artificial intelligence. To request a review, please email documentacao_se@softexpert.com
Prerequisite
- Access the My Tasks menu.
Presentation
In SoftExpert Competência, tasks gather the pending items that are the user's responsibility and need to be completed within defined deadlines, avoiding delays that could compromise stages of the system's workflow.
In general, these tasks can also generate email notifications , provided the email server is configured in the SoftExpert Configuration component.
The tasks generated in the system are divided into two types:
- Execution: tasks that require some action to advance the process (planning, preparing, executing, finalizing, etc.).
- Follow-up: tasks focused on consulting/monitoring information (e.g., tracking inherited goals).
The My Tasks menu centralizes all the pending tasks of the logged-in user, that is, the tasks that they actually need to perform.
Execution tasks
Below are the main execution tasks that can be generated in SoftExpert Competência.
| Who receives | Members of the team responsible for the evaluation plan. |
| When | When an evaluation plan is registered or when a cycle is completed and the frequency is Execution Date , provided that the anticipation is less than or equal to the current date. |
| Purpose | To plan or execute a new cycle of the evaluation plan. |
Configuration note (Frequency) : If the plan is set to Uncontrolled Frequency , the task will not be generated.
How to run :
1. In My Tasks , select the pending assessment plan.
2. Click the button
and choose an option:
- Evaluation planning : creates the cycle in the planning stage (inform planned dates and responsible team, etc.).
- Evaluation plan execution : creates the cycle directly during execution (specify start date and responsible team, etc.).
| Who receives | Team members responsible as defined in the Initial Assessment (General Parameters) section. |
| When | When registering a new user in SoftExpert Administration, provided that they have mapped competencies and have not yet been evaluated and/or are not associated with an evaluation plan, the current date is less than or equal to the configured grace period, and the option "Enable task for initial evaluation of new employees" is checked. |
| Purpose | Record an initial employee assessment or associate it with an evaluation plan so that the employee goes through the evaluation workflow. |
How to run :
1. Select one or more pending collaborators.
2. Select an action:
- Include an evaluation plan (create a plan that generates evaluations for the selected employees);
- Record initial assessment (express assessment; available only under specific conditions);
- Associate with evaluation plan (links to an existing plan that is eligible for selection).
3. Save: the collaborator will no longer appear as pending.
Note : There is a parameter to consider an express evaluation as an initial evaluation, preventing the task from being generated in certain scenarios.
| Who receives | Team responsible for planning the evaluation plan. |
| When | When the cycle is saved but not sent to the next stage. |
| Purpose | Complete the cycle planning before sending it for execution. |
How to run :
1. Select the pending evaluation plan.
2. Review the cycle data and make adjustments on the data screen (edit button).
3. Click Save and next step and choose:
- Save only : keeps it pending; it can be sent later from the main screen or the planning menu.
- Confirm : This concludes the planning process and generates the " Execute evaluation plan" task for those responsible to begin implementation.
| Who receives | The supervisor of the evaluated employee and/or members of the control team, according to the cycle. |
| When | When a cycle is initiated (or evaluations are generated) and a preparation stage is configured. |
| Purpose | Adapt the assessment to the employee's reality before implementation. |
This task exists when the cycle requires a preparation step before execution (cycle setup).
During preparation, it is possible to:
- Prepare multiple assessments simultaneously, completing the preparation and releasing the assessments for execution;
- Prepare only one assessment by accessing the preparation data screen for the selected employee.
| Who receives | Evaluators for the cycle (self-evaluation, leader, team members, peers and/or consensus, depending on the configuration). |
| When | When starting the cycle or when finishing the preparation. |
| Purpose | Assess the employee's skills and career and succession planning. |
How to run (overview)
1. Select the assessment plan grouping and evaluator type .
2. Select the collaborator.
3. Open the evaluation and adjust the Period (start/end).
4. To evaluate:
- Select the proficiency level for the skill; or
- When there are assessment items, evaluate the items (the items make up the competency score according to their value/weight).
5. Save/advance according to the cycle steps.
Important note : If configured, the plan can be automatically terminated when all assessments are completed; otherwise, termination may require manual action (task).
| Who receives | Team responsible for implementing the evaluation plan. |
| When | After completing the cycle planning or when a cycle is directly included in the execution. |
| Purpose | Initialize, adjust collaborators/evaluators, and close the execution of the plan cycle. |
How to run :
1. Select the evaluator/grouper for the consensus evaluation.
2. Use the action to view the result.
3. Confirm your knowledge (you can select multiple evaluations).
4. After confirming, the record will no longer appear as pending.
| Who receives | Person responsible for feedback (usually the leader; or a user defined in the cycle). |
| When | According to the cycle rules (feedback enabled, manual/automatic consensus, feedback rejection, etc.). |
| Purpose | Allow the supervisor to send feedback to the employee being evaluated. |
How to run :
1. Select the pending employee.
2. Access the evaluation screen in the Feedback section and record the comment on the timeline.
3. Execute the feedback and confirm:
If "Requires feedback confirmation" is enabled in the evaluation plan settings, the system generates the "Employee feedback confirmation" task for the employee.
Note : If the collaborator rejects the task, it can be returned to the evaluator (there is a configurable limit on the number of steps).
| Who receives | A collaborator who received feedback, when the cycle requires confirmation. |
| When | After feedback has been provided and processed, in accordance with the rules of the cycle. |
| Purpose | Allow the employee to accept or reject the feedback received. |
How to run
1. Select the pending reviewer/record and open the review in the Feedback section .
2. Comment in the feedback, if necessary.
3. Choose:
- Accept : confirms and closes the pending issue.
- Reject : confirms the rejection and the system generates a new task. Feedback from the employee to the responsible party.
| Who receives | User who completed the consensus evaluation. |
| When |
|
| Purpose | To allow the creation of a development plan for the evaluated employee. |
| Who receives | Evaluated employee (and leader, depending on the configuration). |
| When |
The employee feedback process will be completed if the option "Release results only after feedback" is enabled in the performance review cycle data.
|
| Purpose | Allow collaborator and leader to view/confirm the result (consensus). Generation depends on cycle configuration. |
Conclusion
These are the tasks from SoftExpert Competência, which disappear from the tasks menu as they are completed or finished.