Skip to main content

SP-T2 Completion Email — EN Master (v1.0)

Trigger: Tier 2 completion event (dataset published, gate met) · Sender: EcoWorld Academy via ZAYAZ platform Variables: [FIRST NAME], [COMPANY NAME], [CLIENT NAME], [TIER3_LINK], [DASHBOARD_LINK] Framing rule applies: no client-motive language; state only what is visible. Localize with the course language batch.

Subject: Your data is live, [FIRST NAME] — Tier 3 is unlocked

Preheader: [COMPANY NAME] is now a Data Gatherer. Here's what changed, and what's next.

Hi [FIRST NAME],

It's official: [COMPANY NAME]'s first ESG dataset is live.

That's not a small thing. Your company just moved from unreported to documented — with real numbers, real sources, and honest flags where estimates bridge a gap. That's more than most companies at this stage can say.

What changed the moment you published:

  • Your ESG score moved — driven by your own data.
  • Your badge now reads Tier 2 — Data Gatherer, visible on the platform.
  • Your data status shows current to [CLIENT NAME] and to any client you share your profile with.

And one thing more: Tier 3 — Target Setter — is unlocked and waiting.

You now have something most companies never build: a documented baseline. Tier 3 is where it starts pointing somewhere. You'll set a target that fits your company — practical, credible, and defensible in front of any client who asks. Registering that target on the platform completes the tier.

Start Tier 3 — Target Setter →

One small favor to yourself first: if you haven't already, put the quarterly "data care" half hour in your calendar. Thirty minutes, four times a year, keeps everything you just built alive.

See you in Tier 3, EcoWorld Academy The ZAYAZ Supplier Programme — brought to you by [CLIENT NAME]

View your dashboard

Copy notes​

  • "Brought to you by [CLIENT NAME]" appears once, in the signature block — co-brand convention, no motive language.
  • The middle block states only platform-visible facts (score, badge, data status) — consistent with m008.
  • The "data care" nudge repeats m009's routine; deliberate, since email outlives video memory.
  • No automation/subscription mention — the fence was shown once in m009 and is not repeated in transactional email.
GitHub RepoRequest for Change (RFC)
Last updated on by ZAYAZ