Write the rule in plain language
For example: when a task moves to Review, assign the reviewer. Name the process owner and the exception route.
Check access and availability
Confirm that Automations are enabled and the required trigger, action and any condition are available for the plan and location.
Test isolated examples
Use sample tasks first. Check both the case that should trigger the rule and one that should not.
Check for loops and side effects
Review other rules that change the same fields. Keep approval, payment or external communication steps under suitable human control.
Monitor the rule
Review activity, exceptions and usage. Assign someone to maintain the automation when statuses, owners or integrations change.
References checked 14 November 2026. Features can vary by plan and permissions.