Sedric's analysis is a starting point, not the last word. When you change a result, you're not just fixing one item — you're telling Sedric something about how your policy should be applied, and that shapes how future content is analyzed.
That's the feedback loop, and it's the single most valuable thing your team does in the platform. This article covers where you can give feedback, what happens when you do, and how to make it count.
Where you can give feedback
Feedback isn't limited to flipping a pass to a fail. You can correct the analysis at every layer, which means you can fix the actual cause rather than the symptom.
Layer | What you're correcting | When to use it |
Context | What Sedric understood about the content — its channel, the regulation, what happened inside it. | The result is wrong because Sedric misread the content itself. |
Applicability | Whether a rule should have been evaluated here at all. | The rule doesn't belong on this kind of content, or it was skipped when it should have applied. |
Adherence | Whether a finding passed or failed. | The rule applied correctly, but Sedric reached the wrong conclusion about it. |
Work from the bottom up. If a rule fired on content it should never have touched, correcting applicability is the real fix; flipping the finding to Pass only hides it on this one item.
What happens when you make a change
Two things, immediately and over time.
On this item, the change takes effect straight away. Changing a result recalculates the rule's outcome and the item's score. Marking a rule as not applicable excludes it from the score entirely, because a rule that shouldn't have been evaluated shouldn't count against the content.
On future content, your reasoning is what carries. The explanation you give refines when a rule applies and how it's enforced next time — so the same misunderstanding is less likely to repeat.
Everything you change is recorded in the item's activity log, alongside who changed it and when, so the trail behind any result stays complete.
Always give the reason
Wherever you change something, you'll be asked why. This isn't a formality — the reason is the part Sedric learns from. A corrected result with no explanation fixes one item; a corrected result with a clear explanation improves every item like it.
Good feedback:
Describes the rule, not just this instance. "This rule only applies to content aimed at retail clients" teaches far more than "wrong."
Points at what was missed. If the disclaimer was there and Sedric didn't see it, say where it was.
Uses your own compliance language. Write it the way you'd explain it to a new colleague on your team.
Stays short. One or two clear sentences beat a paragraph.
If you find yourself writing the same correction repeatedly across many items, that's a signal the rule itself needs adjusting rather than the results. Raise it with whoever owns your policy, or with your customer success representative.
Who should give feedback
Anyone reviewing content. Reviewers see the cases that matter most, because they're closest to the content, and the analysis improves fastest when corrections come in as part of normal review rather than being saved up for a periodic clean-up.
Corrections apply going forward. Content that has already been analyzed keeps its original analysis and results.
For any questions, feel free to contact your customer success representative or reach out via the in-app support.