When a secret project is rejected/reposted, how do we hear the previous read?
This is a matter I have been bringing up for over a year now.
When a secret project is reposted, it quite often includes a link to the previous read. The problem is that since it is a secret project, we cannot access it and have a listen to the previous read.
That leaves us two choices, skip it or take a chance that our read is similar to the rejected read.
Sometimes we get lucky and deliver a read acceptable to the client. Sometimes we don't.
It would be wonderful to be able to hear to previous reads to ensure that we don't duplicate what has been done before.
And again, it has been over a year now. Why?
Please sign in to leave a comment.
Hey Mark,
I've been pushing for an update here, but this request is considered low priority for now. It sounds like an easy fix, but apparently, it will take significant changes to the code. Thinking out loud here with no feedback from engineering, perhaps we could at least supply the client's comments as to WHY they rejected the read, even if we can't display the audio? I will brainstorm with the engineering team to see if that's even possible and let you know what they say. Thanks for the reminder!
Thanks Tara, any info is helpful. Had a feeling it was a problem as I have mentioned it off and on for the last year and... bupkis! The reason for rejection would be a good start, but you know how important it is to hear things to know for sure.
I'm interested in this answer too. Given the potential impact of a rejection on our stats and how hard it is to correct stats that have gone south, I find myself reluctant to attempt a previously rejected read without insight from the client.