Reads Approved after 30 days if not rejected
Doesn't it seem unfair that, if every project you accept effects your stats, the ones that are left without Approval don't benefit you, but if one is rejected, you get punished? Especially Speedy projects.
I've been seeing a lot of podcast narration Speedies lately and these never get Approved (but I've had one Rejected because I mis-pronounced the author's name, my bad).
If I am assuming the responsibility of taking on the project, it seems that without Approval ever coming, I'm assuming a risk without chance for being properly recognized by the VB system. What I suggest is that if a read is not rejected by the client, it should be considered Approved after 30 days if the client does not Approve it themselves.
Please sign in to leave a comment.
Thanks Mark! We actually used to do this when VB first started, however, it caused lots of drama with clients who were working with their own picky clients. The issue with the podcast narrations is that they are posted via API and the API does not force the user to accept; they can be left in reviewable status. We are fixing this as we speak!! Very soon, API users will be forced to accept or reject audio the same way the website users are. As always, thanks for your feedback and ideas. Keep 'em coming!
Sounds great. Will there be any way to retroactively allow all those old reads still in reviewable status to be marked as Approved? I have tons of them going back months.
Yep, the fix will be applied retroactively. It's wreaking havoc on our internal stats and measurements as well.
Thank you, Tara!
This is happening to me as well! While it hasn't been 30 days, a narration I did for a website is already live on the client site, but sitting as "reviewable" on my Accepted Projects page.
Are there any updates to this issue? Have things changed since this was posted?