A QA Rubric for Every Cold Email Before It Ships

Cold email QA should not start with grammar.

Grammar matters. Tone matters. Length matters.

But the first question is simpler: should this message be sent at all?

If the source is weak, the claim is stretched, or the persona does not match the reason, a clean sentence only makes the problem harder to spot.

The QA rubric should catch that before the campaign owner is debating commas.

The mistake most teams make

Teams review copy after the campaign has already made the important decisions.

The target is selected. The angle is chosen. The draft is written. The sequence is nearly loaded. At that point, QA becomes a cleanup pass.

That is too late.

QA should review the campaign row before the row becomes a send. The reviewer needs to see the source, signal, angle, confidence, claim boundary, and block reason.

Without that context, they are judging vibes.

What the research actually says

Litmus warns that stale data can lower engagement, hurt deliverability, and reduce ROI. It also says personalization data should be accurate, current, trustworthy, and useful. Litmus

Google's sender guidelines say message headers and content should be accurate, not misleading or deceptive. Google

Those sources support a practical QA standard: review the evidence and claim boundary before the email ships.

What this means for outbound teams

A useful QA rubric should evaluate the row, not just the prose.

That means checking:

• source quality
• source freshness
• account specificity
• seller fit
• persona fit
• claim safety
• message clarity
• send/no-send decision

This kind of rubric makes review slower at first and faster later. The team stops arguing about taste and starts reviewing against the same quality bar.

It also makes client review easier. Instead of sending a pile of drafts, the agency can show why each row was approved, revised, or blocked.

The Ailyus angle

Ailyus helps teams create review-ready campaign rows.

Each row can include source URLs, evidence summaries, ranked angles, confidence scores, claims-controlled message plans, draft evaluations, review states, and block reasons.

That gives QA something concrete to inspect.

The draft is not floating alone. It sits inside an evidence record.

Practical framework: cold email QA rubric

Score each item 0, 1, or 2:

1. Source: no source, weak source, strong source.
2. Freshness: stale, unclear, current enough.
3. Relevance: generic, plausible, seller-specific.
4. Persona fit: wrong, uncertain, clear.
5. Claim boundary: overstated, needs review, supported.
6. Message quality: awkward, acceptable, clear.

Use the total:

• 10 to 12: approve.
• 7 to 9: human review.
• 0 to 6: block or rewrite.

Key takeaways

• Cold email QA should start before copy review.
• Source quality and claim safety belong in the rubric.
• The rubric should produce approve, review, rewrite, or block decisions.
• Ailyus helps teams make QA row-based and evidence-backed.

CTA

Want the pre-send QA rubric? Download the rubric.

Sources

1. Litmus - Email Marketing Personalization Using Data
2. Google - Email sender guidelines