Email checks that people do not learn to ignore

The failure mode for any automated email check is not missing things. It is training the team to click past it. A tool that flags sixty trivial items per draft ends up ignored on the five that carry domain risk. An email pre-check has to earn its place on every run, which means being deliberate about what it blocks on, what it merely warns about, and what it refuses to judge at all. The design constraint is attention, not coverage.

Block on what is certainly wrong

Some constructions are facts, not opinions. A commercial email with no unsubscribe reference and no physical postal address is missing elements the CAN-SPAM implementing rule requires — regardless of the product, the list, or the sender's intentions. A subject line that fakes a reply thread ("Re:", "Fwd:") without an existing conversation is exactly the deception the rule prohibits and exactly the pattern mailbox filters punish hardest. These checks never produce false positives about whether the pattern is present; the only honest uncertainty is how the provider will weigh it. Block here, before the send, because these are the factors that escalate into domain-level consequences.

Warn on what is probably wrong

Patterns that sender guidance agrees on, but that sensible marketers sometimes break on purpose, belong in the middle tier. Spam-trigger phrasing is the classic one: "act now," "free gift," "guaranteed" sit inside the promotional grey zone — the same phrase lands for one sender and buries another, because filters weigh text against reputation context. Formatting pressure behaves the same way: ALL-CAPS, stacked exclamation marks, emoji runs in the subject — placement-limiting signals per Outlook sender practices, not violations. Urgency language: a real deadline stated with a date is fine; manufactured countdown pressure on an evergreen offer is the pattern that trains recipients to mark spam. Warn, show the count, let a human decide — context the machine cannot see often justifies what the pattern alone condemns.

Leave alone what cannot be decided mechanically

Whether your SPF, DKIM and DMARC records are actually live — that lives in DNS, outside the pasted text, and an honest text checker refuses to pretend otherwise. InboxPrecheck never queries DNS; it lists authentication as a checklist advisory and stops there. Whether the list was permission-built — invisible from a draft. Whether engagement history will make this send succeed or slowly poison the domain — invisible from a paste. Whether the claim is substantiated — the evidence lives outside the text. A tool that pretends otherwise produces confident noise, which is worse than silence: it burns the credibility you need for the checks that genuinely know things. This is also why an honest pre-check refuses to output an "inbox probability." Nobody can compute it — providers' internal scoring is private, as the public rules of engines like SpamAssassin and blocklists like Spamhaus only hint at the edges — and pretending otherwise is the check becoming the deceptive pattern it flags.

A workload that stays sane

Teams that keep an email check alive run it on a fixed, boring cadence: one scan per draft, before the first schedule, never after the campaign calendar is committed. The scan is fast precisely because it is mechanical — pattern-match the published factors against the text and it takes seconds and produces the same ranks every time. What the cadence protects is the marketer's attention: if the block tier is already cleared by the time a human reads the draft, the human spends their effort on the judgment calls the tool deliberately refused to make. That division — machine on patterns, human on intent and evidence — is the only arrangement that has held up in practice. Teams that reverse it (humans hunting missing footers, tools pronouncing on list quality) produce exhausted marketers and untrustworthy scores.

What to measure instead of compliance theatre

A single pass/fail verdict is the enemy: it hides the one finding that matters behind fifty that don't, and it invites bargaining ("it sent fine last time"). Named, tiered findings survive disagreement — someone can argue with a rank, but nobody can argue with a quoted sentence and a named factor. If you must report a number, report the count of open HIGH findings, because that is the only figure with an obvious action attached: zero, or the draft does not send. Open-rate attribution dashboards and "deliverability health scores" sound like governance and function as decoration; the fix checklist, closed line by line, is the actual control.

Tiering is the product

What teams actually want from an email check is not more findings; it is a trustworthy ordering of them. Severity tiers — structural and statutory gaps first, claim- and phrasing-sensitivity warnings second, tone noise last — are what keep the check on the desk instead of on the mute list. InboxPrecheck separates these tiers rather than collapsing them into one verdict, because a single undifferentiated signal is what gets muted. And every tier stays reviewable: quoted evidence, named factor, suggested edit — nothing silently rewritten, nothing sent on your behalf.

Decision-support only: findings quote your text and published sender guidance. You make the call before anything sends, and the mailbox providers make the final one.