Backup Contest before a read is even QC'd???????

Mr. Bunny, you  are  a business person, right?  You like profit, right? You watch the bottom line, right? You work hard to ensure that there are no unnecessary costs in your business, right? You believe that computers and programming can be time and money savers, right?  You task your programming team to find ways to cut costs and increase the bottom line, right?

Well you aren't paying close enough attention to this!

What was a suggestion is now a rant.  This is the second time I have submitted a job before any deadlines and seen a backup contest go out before the QC team has taken a look at it.

This means there is no code written to check on the status of a job other than "Is there audio submitted to the client yet? If there is not audio at XX hours, then auto-generate a backup contest."

What you need is an additional instruction set which goes something like this "Has audio been submitted by the talent yet? If no, then generate a backup contest.  If yes, then notify QC,customer service etc. of the need to QC the audio."

Doesn't that make any sense to anyone there?

Your savings:  

Time: Instead of having additional resources having to take the time to review more audio files and submit them, they only need to do one and they are done

Money: Money is saved 2 ways. First, noone on the staff needs to take the time to QC more files.  This saves labor.  Second, you're not paying out additional fees to more talents and worrying about the cost of the additional record keeping, money transfers etc.

So, in summary, if you are interested in saving time and money, fix this problem.  If it has happened to one of us, it has happened to many and you are bleeding money unnecessarily.

Additional moneys spent on a project for no good reason equates to lower margins, smaller profits, fewer jobs and a host of other bad things.