Re: Clause7.5.4 Can I exclude Customer Property?
Jane,
My doubt araise from your first post.
As a manufacturing/ Prop hiring company, we do get the drawings from client and input the information from the drawings and manufacture and deliver to the customer. And do not return the customer property(drawings & specifications)
That's why, I'm confused should I exclude this clause or not.
Divyavb80,
I'm sorry if I confused you - I got interested in the topic 'in general'. Also, 'do we return it?' isn't a failsafe check, as has been agreed in this thread.
First, do not exclude it from your scope.
Second: don't worry. Excluding (or not) this particular clause isn't a big thing; it shouldn't have a big impact at all even if you make the 'wrong call'.
Why? Because if you do exclude it, and later your auditor (who will have the benefit of being there and seeing
your whole system, which I can't) disagreed and said this clause
should be excluded, this will (I assume) be at your pre-audit (before the main audit). No drama: you would just add the exclusion into your manual before The Audit.
Exclusion/inclusion of certain clauses, such as the 7.3 clause on design, would have a huge impact on a system, if the exclusion wasn't a valid one. This one wouldn't (or shouldn't).
Because really, all you need to do is what I hope & expect that you are doing already:
- Checking whatever you receive from your customer (drawings, specs) to use, in order to make sure it/they are accurate & fit for your use; and if not (or if they are damaged - eg, deleted/lost/only some received), telling your customer & rectifying the situation.
- Making sure your customers' property (eg drawings) are identified - eg, by using their filenames & versions, storing them in certain locations, etc
- Protecting & keeping their stuff safe the whole time while it's in your hands. Your customers would (rightly) expect for example, that you don't allow people not on your staff to see their stuff, or don't just toss copies of their confidential drawings out in the paper waste bin, where they might possibly be found & seen by others, but that you dispose of them so as to keep them protected (eg, shred, delete etc)
You would/should build controls to make sure these things happen into your system procedures (you don't need a separate 'customer supplied property procedure!).
OK?