S
SteelWoman
You might try defining for your organization the "basics" for taking an order. We actually just discussed this very issue with our registrar yesterday (here for our last, hopefully, QS audit before "transitioning"). In our world, for instance, if you want steel there are BASIC things we need to know, like what thickness, what width, what alloy, what tensile strength, etc. We OFTEN have customers who call and give us width, thickness, and what the part is they'll be making, but nothing else. It is then up to us to DISCERN what rockwell strength, tensile strength etc. will be required for the customer to make that part successfully. And in such cases we will document the addition of those specs to the customer order as an "internal spec" - not something the customer asked for, but something we KNOW THEY NEED (that's the mind-reading part) to make the part successfully.
So, for your process you might look at defining what those basics are, and then establishing some sort of method for asking the question when the customer fails to give you any of those basics. And if they really don't have that info to give you, figuring out a way to document that basic requirement ANYWAY.
So, for your process you might look at defining what those basics are, and then establishing some sort of method for asking the question when the customer fails to give you any of those basics. And if they really don't have that info to give you, figuring out a way to document that basic requirement ANYWAY.