Zeal’s enforcement workflow is designed to guide each post in a structured and transparent way. Below is a step-by-step overview of how enforcement actions are executed in Zeal 2.0.
The process begins with Quality Analysts (QAs) reviewing flagged posts. Once verified as actionable, QAs click the “Check and Enforce” or “Enforce” button to signal that the posts are ready for enforcement.
This can be done individually or in bulk for efficiency.
If auto-takedown rules are configured, Zeal 2.0 will automatically trigger the ‘Enforce’ action once the posts meet the predefined criteria, eliminating the need for manual input at this stage.
This step ensures that only qualified and reviewed posts are passed to Enforcers, maintaining both accuracy and speed.
Once posts have been checked and enforced by QAs, Enforcers must confirm that the correct IP Asset, IP Certificate, and Site Code are pre-selected before proceeding.
To identify any issues, Enforcers can use the Validation Errors filter:
This highlights posts missing key enforcement elements or with incorrectly populated fields.
A warning icon appears next to the label on the right-hand side for any post with validation errors:
Enforcers can resolve validation errors directly on the listing or in bulk, ensuring that every notice is legally complete and accurate.
Note: Once validation errors are resolved, notices are automatically visible in the Notice View (Queued) for the next stage of processing.
After correcting validation issues (if present) notices enter the Notice View and are automatically visible in the Queue stage. Notices can be enforced individually or in bulk by clicking “Send Now”
Clicking Send Now will send the notices to the platforms and trigger the notices to move from Queue into In Progress.
Enforcers can click on the Notice ID to open the detailed view, which includes:
Enforcement summary: Number of posts removed (top left) and items still awaiting takedown (top right, “Pending Takedown”).
Items in Notice section: Each post’s current status is displayed as Active or Down, with three dots indicating system checks confirming full and persistent removal.
Related accounts and items are also visible, providing context for broader enforcement actions.
Within the Notice View, users can access key enforcement details through clear, structured columns:
Method – Indicates the auto-enforcement method used to issue the notice. Possible methods include Email, API, IP Portal, or Webform, depending on the platform’s integration.
System – Specifies whether the enforcement process for the domain or platform is automated.
If automated, this column displays “Automatic.”
If manual action is required, it displays “Manual.”
Once all posts in a notice are confirmed as down, the notice automatically moves from In Progress to Processed. This stage displays the batch size, number of offline posts, and the notice sent date, providing a clear audit trail for every action.
The enforcement process blends automated efficiency with human oversight, ensuring that takedowns are both fast and accurate.
QAs focus on qualification and review.
Enforcers ensure legal and procedural accuracy.
The system automates transitions, validations, and status updates.
The result is a streamlined end-to-end enforcement pipeline that minimizes errors, accelerates removals, and gives brands full visibility into every stage of the takedown process.
