When we work one of these Typeset/HTML jobs, our best practice model is to have the HTML read on the first proof cycle even if the HTML output isn't being requested. What that allows us to do is produce the HTML output for client review at the drop of a hat. So when the client calls up after proof cycle eight, say, and says OK, send me the HTML in an hour, we can do that. We don't have to worry about there being an HTML error that's crept in somewhere and hasn't been checked.
In order to produce an HTML proof (which we print out so our proofreaders can read it against the typeset proof), the EFW Notes have to have been input by the customer service rep (or, according to the TLA doctrine, CSR). Without those Notes in the database, we simply cannot produce the proof from our system.
So we are constantly calling up the Operations Centers (or, in flagrant diregard for the TLA doctrine, OPCOs) to have them create or update these EFW Notes. The most frequent OPCO we have to call is the NYC OPCO. The CSR they have on third shift has told more than one person on more than one occasion that he can not create EFW Notes for a job before receiving the typeset output.
This is utter bullshit, the Notes can be created at any point and, as a matter of fact, the CSR best practice procedures require him to create these notes before sending the work to us or within 15 minutes of doing so. His excuse is that he needs to put the file names of the typeset job into the notes and he can't know those file name until his has the output. He is correct in that he should include that information in the notes. What he is forgetting is that this is a later part of the process.
Or, more accurately, he's a lazy fuckwad (LFW) who is preventing me from doing my god damn job (GDJ) because entering information and then editing later is too much for his miniscule brain (MRN)!