Jump to content

  • Quick Navigation
Photo

BRC Rules regarding Creating documents and approving them and auditing

Share this

  • You cannot start a new topic
  • Please log in to reply
5 replies to this topic

Bre

    Grade - Active

  • Newbie
  • 18 posts
  • 8 thanks
0
Neutral

  • United States
    United States
  • Gender:Female

Posted 28 January 2014 - 09:27 PM

Hi All,

 

 

I was wondering what everyone's thoughts are on creating documents and approving them. Can the same person that created the document theoretically approve their document? Also, as the food safety manager, I would prefer auditing my program, because I am much harder on it than others are, so I would like to take my name off the created by and put my plants managers name on this? Any controversy with this? I know you should have your whole staff involved, but for us, its easier to have one or two main people auditing the plant as opposed to a big group of people... Let me know your thoughts.

 

Thanks,

Bre



Charles.C

    Grade - FIFSQN

  • IFSQN Moderator
  • 20,542 posts
  • 5662 thanks
1,544
Excellent

  • Earth
    Earth
  • Gender:Male
  • Interests:SF
    TV
    Movies

Posted 29 January 2014 - 12:01 AM

Hi All,

 

 

I was wondering what everyone's thoughts are on creating documents and approving them.

 

Can the same person that created the document theoretically approve their document?

IMO It depends on the document and the relation to the issuer/user. From memory not mentioned in BRC ? Specific example ?

 

Also, as the food safety manager, I would prefer auditing my program, because I am much harder on it than others are, so I would like to take my name off the created by and put my plants managers name on this? Any controversy with this?

Again IMO it perhaps depends on the document but why not have the Plant Manager finalize/issue it if it relates directly to his/her function. ? Specific example ?

 

I know you should have your whole staff involved, but for us, its easier to have one or two main people auditing the plant as opposed to a big group of people... Let me know your thoughts.

The limitations / options are discussed in detail in several recent threads. Try searching a little?. BRC requires "independence" from memory.

added later - here are a couple, sort of mixed standards discussions, but basic idea is pretty uniform I think -

 

http://www.ifsqn.com/forum/index.php/topic/21702-internal-audit-help/#entry67152

 

http://www.ifsqn.com/forum/index.php/topic/21744-so-basically-we-need-to-do-the-entire-brc-audit-internally/

 

Thanks,

Bre

Dear Bre,

 

A few comments above.

 

Rgds / Charles.C


Kind Regards,

 

Charles.C


zee

    Grade - Active

  • IFSQN Active
  • 5 posts
  • 0 thanks
0
Neutral

  • United States
    United States

Posted 30 January 2014 - 04:37 PM

Hi All,

 

 

I was wondering what everyone's thoughts are on creating documents and approving them. Can the same person that created the document theoretically approve their document? Also, as the food safety manager, I would prefer auditing my program, because I am much harder on it than others are, so I would like to take my name off the created by and put my plants managers name on this? Any controversy with this? I know you should have your whole staff involved, but for us, its easier to have one or two main people auditing the plant as opposed to a big group of people... Let me know your thoughts.

 

Thanks,

Bre

Hi Bre,

  To my knowledge there is nothing stating you can't create your own documents....  if you created it I would say that you did and you are the one authorized to make changes, revisions etc.  As for auditing goes, we have a food safety team that audits the physical plant monthly ie. equipment, walls, ceilings and grounds etc.  But our actual internal audit is done by a sister plant which is nice because it's someone with fresh eyes that knows the standards.  (keep in mind they should have a internal auditing certificate)  If you do not have a sister plant I would recommend people educated on the standard and departments do cross auditing. ie Production audits QA, Maintenance audit HR and training etc.



balakrishnan_dl

    Grade - Active

  • IFSQN Associate
  • 15 posts
  • 2 thanks
1
Neutral

Posted 31 January 2014 - 04:38 AM

Hi,

 

Can't this job not get done by qualified and independent third party consultants?

 

Balakrishnan Ramanathan,Chennai,India.

 



trubertq

    Grade - PIFSQN

  • IFSQN Principal
  • 658 posts
  • 281 thanks
137
Excellent

  • Ireland
    Ireland
  • Gender:Female
  • Location:Donegal

Posted 01 February 2014 - 08:21 PM

Of course you can...that's what I do for my clients.

 

I create the documents, The Quality manager approves them and I do all the Internal Audits as I am independent of ALL areas.

 

Bre in your case I'd say you should create the documents relating to your own area, and push the responsibility for other areas onto the managers of those areas. Technically you should have independence from the areas you are auditing, therefore you can't audit your own area. So you need at least one other person trained in auditing so they can audit the areas where you are  the auditee.

 

Someone who is totally unrelated comes in with a fresh pair of eyes and sees things you don't. However hard you feel you are on an area, your audit will always be coloured by your knowledge of what is behind the scenes ( if you know what I mean). The checklists can be created by you of course ( as the likelihood of anyone else creating them is probably slim) so you will have a hand in 'directing' the audit that way.


I'm entitled to my opinion, even a stopped clock is right twice a day

Azhar Sayyed

    Grade - Active

  • IFSQN Associate
  • 15 posts
  • 3 thanks
0
Neutral

  • India
    India
  • Gender:Male

Posted 08 February 2014 - 11:54 AM

Documents can be prepared by the FSTL or department head but it shall be approved by senior management. While regarding Internal Audit- An auditor cannot audit his own work.





Share this


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users