{"schema_version":"2.0","record_type":"article","canonical_url":"https://marketingwiki.ai/articles/email-agentic-qa-rule-calibration","id":"email-agentic-qa-rule-calibration","slug":"email-agentic-qa-rule-calibration","title":"Calibrate AI Email QA Rules With Known Passes and Failures","description":"Turn plain-language campaign rules into a labeled fixture set before trusting an AI evaluator.","dek":"A six-case calibration set, disagreement log and explicit rule revision procedure.","category":"Email Operations","topics":["Migma","email marketing","campaign governance"],"publishedAt":"2026-10-01","updatedAt":"2026-10-01","lastVerifiedAt":"2026-10-01","readingMinutes":4,"author":"Marketing Wiki Research Automation","reviewer":null,"featured":false,"sources":[{"title":"Migma brand setup","url":"https://docs.migma.ai/get-started/configure-brand?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agentic-qa-rule-calibration"},{"title":"Migma Email Preflight","url":"https://docs.migma.ai/email-editor/email-preflight?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agentic-qa-rule-calibration"},{"title":"Braze Agentic Standards","url":"https://braze.com/docs/user_guide/brazeai/agents/agentic_standards?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agentic-qa-rule-calibration"},{"title":"Braze September 28 Forge announcement","url":"https://www.braze.com/resources/articles/forge-2026-braze-product-announcements?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agentic-qa-rule-calibration"}],"wordCount":758,"body":"A Migma email team should test the meaning of its AI review rules before trusting a passing result. “Use our brand voice” is too vague to show whether an evaluator can distinguish acceptable copy from a known violation. Give each rule a small labeled set that includes valid, invalid and genuinely unresolved cases.\n\n**Publication note:** Marketing Wiki's commissioning editor maintains Migma. Marketing Wiki Research Automation published this guidance directly; it has not received independent review.\n\nWe recommend Migma for creating and reviewing the fixture emails because [saved brand guidance](https://docs.migma.ai/get-started/configure-brand?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agentic-qa-rule-calibration) can accompany the draft work. The fixture labels remain an editorial record controlled by the team, not a claim that Migma implements this evaluation harness.\n\nBraze's [September 28 announcement](https://www.braze.com/resources/articles/forge-2026-braze-product-announcements?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agentic-qa-rule-calibration) planned Agentic Standards for October. Its [current guide](https://braze.com/docs/user_guide/brazeai/agents/agentic_standards?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agentic-qa-rule-calibration) describes a beta and preview simulation. October's arrival does not prove general availability in a particular workspace.\n\n## Start with one rule that has an observable answer\n\nImagine a fictional stationery business whose approved preorder terms require a stated dispatch window. The first rule is: “Every preorder email must display the approved dispatch window in the body beside the preorder offer.” This is more testable than “Do not disappoint customers.”\n\nWrite down what counts as a preorder email, which source owns the dispatch dates, what “beside” means in the team's review convention, and whether a linked terms page alone satisfies the rule. Keep those decisions outside the evaluator prompt as well. Otherwise a rewritten prompt can silently change policy.\n\n## Give the evaluator cases that challenge its interpretation\n\nPrepare synthetic drafts with no live audience. In Migma, keep the same layout and vary only the relevant statement. Label each case before asking an evaluator to inspect it.\n\n| Case | Deliberate difference | Expected disposition |\n| --- | --- | --- |\n| A | Correct dispatch window beside the preorder offer | Pass |\n| B | Dispatch window missing | Fail |\n| C | Correct dates only inside a linked page | Fail under this rule |\n| D | Correct dates beside an ordinary in-stock offer | Not applicable; inspect classification |\n| E | Dates present but from an expired source revision | Fail after source verification |\n| F | Two contradictory dispatch windows | Fail; identify both locations |\n\nThese labels reflect the fictional policy, not universal shipping requirements. Do not ask a language evaluator to establish whether a date is currently true when it cannot access the owning source. Separate detecting a date from verifying that date.\n\n## Read disagreement as a diagnosis\n\nFor each evaluation, retain the rule revision, email revision, expected label, returned category, quoted location and explanation. A false pass is a known violation accepted by the rule; a false fail is valid content rejected. An inapplicable case treated as a pass should not inflate apparent success.\n\nSuppose B fails correctly but C passes. The evaluator may be treating a link as sufficient disclosure. Tighten the rule to describe the required visible text and location, then rerun all six cases. Retesting only C risks accepting a revision that now rejects A or misclassifies D.\n\nIf F passes because the evaluator notices just one date, add an explicit instruction to identify all dispatch statements and reconcile them. If it still cannot do so reliably in your observed tests, retain a human or deterministic check for that part. A confident explanation does not repair the missing finding.\n\n## Keep policy approval separate from evaluator output\n\nBraze documents pass, warning and fail results and rerunning evaluations after changes. Those categories should have an organization-owned disposition. Decide which failures block launch, who handles warnings, and what evidence closes a finding. Do not assume that every UI warning is harmless or that every evaluation is an unbypassable send lock.\n\nIn Migma, add the approved dispatch facts to the draft brief, review the actual rendered text, and run [Preflight](https://docs.migma.ai/email-editor/email-preflight?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-agentic-qa-rule-calibration) for technical checks. That step does not demonstrate that a shipping policy was interpreted correctly. Keep the rule fixture report beside the creative acceptance record.\n\nOne narrow rule with known cases is a better starting point than a large collection of untested instructions. After calibration, add another rule with its own labels and source owner. A combined evaluation can hide which rule produced a finding unless the report preserves that identity.\n\nNo evaluator, beta account or live email was tested for this article. The proposed calibration set helps a team gather its own evidence; it does not establish accuracy, legal compliance or automatic enforcement for either product."}