ComplyBar logoComplyBar

How do I send a task back for rework?

When you review a task and it isn't right yet, you send it back instead of approving it. ComplyBar calls this Request Changes. Open the task, click its status pill, and pick it from the dropdown.

Where the task goes, and who gets it.

  • From Pending Review, the reviewer (or any admin) sends it back to Prep Pending. It lands with the assignee.
  • From Pending Approval, the approver (or any admin) sends it back to Pending Review. It lands with the reviewer — not the assignee — because the reviewer is who passed it along.
  • From Complete, an admin can reopen the task with "Revert to Prep Pending".

You have to say why. Every send-back requires a written reason. This isn't just a form check — the database refuses the change without one, so there's no way to send work back silently.

The reason shows up in three places: inline under the status change in the task's activity log, in the notification and email to whoever now owns the task, and in the audit trail behind your Performance Report.

What the other person sees. They get an in-app notification and an email with your reason, unless they've turned "Changes requested on task" off in their notification settings. If you send back a task that was assigned to you, nobody is emailed — you already know.

How this shows up in reporting. The Performance Report tracks a rework rate: the share of a person's assigned tasks that got sent back at least once during the period. It counts tasks, not send-backs, so a task bounced three times still counts once, and it's attributed to the assignee. Because every send-back carries a reason, you can always open a task and see what actually happened rather than guessing at the number.

Unskipping a task, or a blocked task becoming workable when its dependencies clear, is not rework and never affects the rate.

When not to use it. Request Changes moves the task backward and counts against rework. If you only want to ask a question or leave context, use the task's comment thread instead — that leaves the status alone.

From the blog