Email writing · Practical guide
Cold email relevance evidence worksheet: connect each sentence to its purpose
Keep a short ledger showing why each personalized claim belongs in the message. Evidence of a fact and evidence of its relevance are separate checks.
Reviewed · Examples are illustrative
Who this helps: Writers reviewing specific claims, stakeholder messages and recipient requests.
Define the decision
A researcher may correctly identify a launch or a role change that has no meaningful connection to the offer. The worksheet asks both whether the fact is supported and whether it changes the message. It also records the boundary between an observation and an internal need that remains unknown.
Work through the procedure
- List the factual claims in the draft and their sources.
- Write the narrow wording each source actually supports.
- Explain how the fact affects recipient selection, the offer or a routing question.
- Remove unsupported or irrelevant claims and preserve unresolved questions for review.
Worked example
The following is a synthetic example for this procedure, not a customer result or performance benchmark.
Claim: a public role includes supplier onboarding
Source: current role page, observation date recorded
Permitted wording: mention that listed responsibility
Business connection: offer an onboarding ownership worksheet
Unknown: whether the current process needs improvement
Draft action: ask about usefulness without asserting a process failure.Read the result
The worksheet can reject a true but irrelevant fact and a relevant but unsupported claim for different reasons. That makes revision more precise than a general request to personalize better. A reviewer should be able to reconstruct the approved wording without reopening every discarded research detail.
Check before moving on
- Preserve source dates for temporary facts.
- Avoid storing unnecessary personal details in the ledger.
- Recheck claims after a substantial copy change.
Limits and next action
This is an editorial artifact, not automatic source verification in Zintara. A URL in a research result is not proof that every generated sentence is supported by it. Human review must inspect the actual claim and context.
Source: Zintara product context; procedures and examples are editorial guidance
Source references
Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.
Related guides
- Cold email copy review checklist: approve facts, meaning and the next action →
- One-question cold email CTA: remove competing decisions from the close →