[Mike S.], all of these are buried in the fine print that your organization agrees to every time it accepts a purchase order. It's just that nobody ever reads them in detail to determine what all the organization has actually committed to. They are in the body of the P.O., or in other documents referenced in that P.O., or in boilerplate language on the website of the purchasing organization.
The other side of that coin is that nobody in the purchasing organization is aware that they are asking for all of these things. As near as I can determine, the list of contractual, regulatory and statutory requirements is like a layer of sedimentary stone, topped with perhaps some river bottom mud.
The document(s) were created with good purposes, then as new requirements were identified either by internal or external sources, these were added to the list. Often the organizations have no idea that they are supposed to supply or receive these deliverables. The top layer of mud is revised periodically, and the ones in stone are forgotten but remain in force since nobody ever got around to deleting them.
Sometimes I find contradictions between the terms of the purchase order template and the documents referenced in that template. I will periodically push back on some of the more onerous ones, and the response I usually get is " did we really ask for that? "
And today's winner is:
" Words, as employed in this Agreement, shall have their normally accepted meanings ".
EDIT: Usually buyers profess they are unable to change a P.O. once it's been issued. I did get this response back this week from one of the big aerospace boys:
" Apparently these should have never been called out so I have QA’s approval to remove them from the PO. I will send a revised PO tomorrow."
And I saved the following email exchange yesterday:
Me: Customer has included a new aircraft worthiness requirement in this P.O. that I don't believe is applicable to us, either that or they have some unshared expectations we need to clarify
Sales: But we shipped this to them before !
Me: Yes, and it wasn't in those P.O.s - Please contact the customer
Customer: OMG ! I didn't see that on the purchase requisition - the normal quality guy is on vacation, and the guy covering for him put that in - please disregard.
Me: There is such a thing as a normal quality guy? And they get vacations ?
Our Project Manager: I don't think there is such a thing as a normal quality guy. You can't be normal and do that thankless job. Not possible.
The other side of that coin is that nobody in the purchasing organization is aware that they are asking for all of these things. As near as I can determine, the list of contractual, regulatory and statutory requirements is like a layer of sedimentary stone, topped with perhaps some river bottom mud.
The document(s) were created with good purposes, then as new requirements were identified either by internal or external sources, these were added to the list. Often the organizations have no idea that they are supposed to supply or receive these deliverables. The top layer of mud is revised periodically, and the ones in stone are forgotten but remain in force since nobody ever got around to deleting them.
Sometimes I find contradictions between the terms of the purchase order template and the documents referenced in that template. I will periodically push back on some of the more onerous ones, and the response I usually get is " did we really ask for that? "
And today's winner is:
" Words, as employed in this Agreement, shall have their normally accepted meanings ".
EDIT: Usually buyers profess they are unable to change a P.O. once it's been issued. I did get this response back this week from one of the big aerospace boys:
" Apparently these should have never been called out so I have QA’s approval to remove them from the PO. I will send a revised PO tomorrow."
And I saved the following email exchange yesterday:
Me: Customer has included a new aircraft worthiness requirement in this P.O. that I don't believe is applicable to us, either that or they have some unshared expectations we need to clarify
Sales: But we shipped this to them before !
Me: Yes, and it wasn't in those P.O.s - Please contact the customer
Customer: OMG ! I didn't see that on the purchase requisition - the normal quality guy is on vacation, and the guy covering for him put that in - please disregard.
Me: There is such a thing as a normal quality guy? And they get vacations ?
Our Project Manager: I don't think there is such a thing as a normal quality guy. You can't be normal and do that thankless job. Not possible.
Last edited: