Prepare the review
Describe what the colleague needs to check, assign the review task to a user or role, and include the relevant task details. Responsibility should be explicit before work changes hands.
WEXCY FOR GROWING BUSINESSES
Give recurring work a named owner, record what was done, and define what must happen before the next step. Keep responsibilities clear as more people take part.

Consider a service business taking on a new client. A coordinator prepares the brief, a colleague reviews it, and the team decides whether it is ready for the next stage.
Describe what the colleague needs to check, assign the review task to a user or role, and include the relevant task details. Responsibility should be explicit before work changes hands.
When the review is completed, record its outcome in the completion details. Finishing the task does not by itself mean the brief is complete or approved.
For example, the client's preferred start date still needs confirmation. Record that finding so the next person knows what remains to be checked.
A configured workflow can use completed tasks and other requirements to control a transition. Review the current stage, owner, and transition options before moving the work forward.
GROWING BUSINESS FAQ
Yes. Tasks can be assigned to a user or role. That assignment is separate from the permissions a person has within the organization.
No. Task completion and the recorded review result are different. Record what the reviewer found, and use the relevant workflow conditions to decide what can happen next.
Transitions can have configured requirements, including completed tasks and other conditions. The conditions must be defined for that workflow; they are not inferred automatically from this example.
Review their task responsibility and organization access separately. Effective access may come from roles and direct grants, so removing one role does not necessarily remove every permission.
Start with one recurring process and make its responsibilities explicit.
Start for free