Task validation

Validation flow

The process always follows the same order:

1. The employee carries out the task and marks it as completed from the app.
2. The system alerts the manager that there is work pending review.
3. The manager goes to the back office, reviews the work and decides whether to accept or reject it.
4. If they accept, the task moves to validated and is closed.
5. If they reject, the task moves to rejected, with the reason visible to the employee.

Accepting a completed task

To validate a task, the manager has to:

1. Sign in to the back office and open the Tasks section.
2. Filter by Completed status to see those awaiting review.
3. Open the task detail.
4. Read the employee's notes and review the evidence provided.
5. Validate the task.

Once validated, the task is closed: the *validated* status is neither assigned nor reverted by hand from the edit form. If rating is enabled, you can then score the employee's work.

Rejecting a completed task

If the manager considers that the work is not correct, they can reject it.

Steps to reject a task

1. From the task detail in the back office, press Reject.
2. Write the reason for the rejection. It is mandatory: without text, the action cannot be confirmed.
3. Confirm the rejection.

The task moves to rejected status and the reason is visible to the employee alongside the task's complete history.

Consequences of rejection

When a task is rejected:

• It stays in rejected status, which is a closure with a reason: the task does not return to the employee's work list on its own.
• The time-compliance indicator changes to show *Rejected*, because meeting the deadline stops being what matters.
• The history records the rejection, the reason, the author and the date, so that there is evidence of the complete cycle.

If the work has to be redone, the manager edits the task and returns it to assigned status, adjusting the deadline where appropriate. The employee gets it back in their list and the cycle starts again.

Who can validate

By default, managers and owners validate. Each task also includes the Allow validation by supervisor option, enabled by default, which lets the branch supervisors validate or reject that task.

It is a decision made per task, not a permission on the employee's profile: it is ticked when creating the task or when editing it, alongside the rating and mandatory evidence options. This makes it possible to decentralise day-to-day operations and reserve the validation of sensitive tasks for the manager.