Email sequences are written as a set and received as a series. The gap between those two is where sequences go wrong, and it only appears when someone lives through the week.
What to put in the public brief
- That the task runs across a week or more
- That they must stay reachable and check regularly
- That they will create a real account with an email they control
- Roughly how many check-ins
- What you will do with their address afterwards
Keep the product and signup link private until a spot is reserved.
What to put in the private instructions
Say whether to use the product or not
And say it firmly. A tester who half-uses it produces a branch you cannot interpret.
Ask them to log each email as it arrives
Subject, time, and one line on whether it felt relevant right then. Retrospective recall at the end of the week loses the timing, which is the whole point.
Ask for the moment they would have unsubscribed
If any. Name it as a legitimate answer so nobody softens it out of politeness.
Ask them not to unsubscribe until the end
Otherwise the test stops at the finding rather than continuing past it.
Proof worth requiring
Ask for
A log of every email with timestamps, screenshots of any that looked wrong, and the unsubscribe moment if there was one.
Do not ask for
Their inbox credentials or a forward of every message. Screenshots and a log are sufficient, and anything more creates an obligation over their mailbox you do not want.
When this task type is the wrong tool
If the emails are not arriving reliably, fix deliverability first. An email rendering check covers placement and display for a fraction of this cost.
If you want to know whether one message persuades rather than whether the sequence fits together, test that message on its own.