Podcast analytics are unusually blunt: a drop-off curve and nothing about cause. The curve tells you when, and the entire useful question is why.
What to put in the public brief
- Episode length, honestly
- The topic in general terms
- That they will listen and then write
- Whether headphones or a specific listening context matters
- Roughly how long in total
Keep the show identity private where you can, so responses are about the episode rather than the brand.
What to put in the private instructions
Ask where they would have stopped if not being paid
The single most useful question, and it needs permission to be answered honestly. Say plainly that "after four minutes" is a valid and well-paid answer.
Ask for three timestamps in their own words
One moment that held them, one that lost them, one they would quote. Chosen by them, not prompted by you.
Ask what they would tell a friend it was about
If that does not match your intent, the episode has a framing problem no amount of editing the middle will fix.
Ask about the first ninety seconds separately
It is where most of the loss happens and it is usually the part that was recorded last and edited least.
Proof worth requiring
Ask for
Three timestamps with a sentence each, the stopping point, the one-line description, and how they listened — headphones, car, speaker.
Do not ask for
A rating or a score. It compresses a drift into a number, and you will average the numbers across people who drifted at completely different places.
When this task type is the wrong tool
If you want to know whether people find the show at all, that is a discovery question and this measures the wrong thing entirely.
If the issue is audio quality rather than content, name that as the task instead — a listener asked about content will politely absorb a hum they would never tolerate unpaid.