What should a marketing automation review rule include?
What should a marketing automation review rule include?
A review rule explains which work needs a person’s approval, when that review happens, and what to do if something is uncertain. Before automating a marketing workflow, write down the rule in plain language and test it on a small set of examples.
Which actions should be reviewed?
Consider requiring review for actions that are public, difficult to reverse, or likely to affect customers, spend, or brand trust. Depending on the workflow, that could include publishing a campaign, changing audience criteria, sending a message, or making a budget adjustment. Lower-risk preparation tasks may need a different level of review. Set the boundary based on your organization’s policies and the consequences of an error.
How do I distinguish drafting from publishing?
Name the steps explicitly. For example, “prepare a draft for review” is different from “publish the approved draft.” Specify who may approve the transition and what evidence counts as approval, such as a recorded sign-off in the team’s established process. Don’t treat a draft, preview, or recommendation as authorization to publish.
What is a stopping rule?
A stopping rule says when work must pause rather than continue automatically. Define observable triggers—for example, missing required information, conflicting instructions, an unapproved change, or uncertainty about whether a request falls within scope. State who should be notified and who can decide whether work may resume.
How should I document an exception?
Record what happened, which rule was affected, who reviewed the case, what decision was made, and whether the rule needs updating. Use the documentation method your team already approves, and avoid recording sensitive information unless your policies permit it. An exception should not silently become a new default.
How do I start with one workflow?
Choose a bounded workflow with a clear start and finish. Write down its permitted actions, review points, stopping triggers, and exception process. Test the rule against realistic cases—including an ambiguous case—before expanding its scope. For a related guide to defining a pilot’s scope, see the pilot-scoping article.
Pingback: The one-workflow decision record: a copyable planning template - Foreshadow AI