quelles actions pour mener un audit efficace sur site? (2)

  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 23.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 24.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 25.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 26.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 27.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 28.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 29.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 30.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 31.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 32.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 33.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 34.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 39.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 40.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 41.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 42.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 43.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 44.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 45.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 46.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 47.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 48.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 49.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/13/d149292364/htdocs/ifme.org/modules/token/token_node.inc on line 50.
  • warning: Creating default object from empty value in /homepages/13/d149292364/htdocs/ifme.org/modules/pathauto/pathauto.module on line 112.

Nous avions vu, précédemment, qu’un audit social mené sur site devait, avant tout, permettre de découvrir les preuves de conformité du site aux exigences sociales/sociétales du référentiel choisi (ou imposé par son donneur d'ordres principal, souvent).

Le Tour des installations :

Activité souvent « bâclée » car « mangeuse de temps ».

Quand doit-il être mené ? En début de journée et toujours accompagné par le chef d’entreprise ou d’établissement ou de son représentant «officiel».

Pourquoi ? : Pour permettre de détecter les situations que le site rencontre souvent en « activité » normale… Egalement pour « faire participer » la Direction du site aux éventuelles découvertes de situations qu’il ne voit plus, et qui parfois, sont conformes, ou parfois non-conformes. C’est l’occasion de lui poser la question de savoir " s’il est capable d’expliquer la situation rencontrée", et nécessairement, "s’il envisage d’y apporter une correction", ou le féliciter directement face à une situation conforme.

Comment ? : Toujours demander à ce que le site vous fournisse un plan au sol des installations visitées. Durant la visite, pour pourrez inscrire vos premières remarques et annotations pour vos actions de la suite de la journée (ex : noter les endroits où il faudra s’entretenir avec les travailleurs y travaillant, documents à rechercher pour vous apporter la preuve de la maîtrise de la situation rencontrée, etc.)

Quoi vérifier ? : Lors d’un tour des installations, le système de sécurité (prévention, lutte) incendie du site sont spontanément des éléments s’offrant aux contrôle de l’auditeur : Extincteurs présents, valides, en marche ou hors de service, RIA, en nombre et opérationnels, évacuation des fumées, voies de circulation pour les évacuations, issues de secours (accès libres ou encombrés ou cadenassés …), les éventuelles situations ou installations pouvant présenter un risque d’incendie (armoire électriques, contenant inadaptés pour produits inflammables, etc.), les postes de travail sécures ou dangereux, etc. L’aspect Hygiène, est également vérifié lors de cette visite des installations… (armoires de secours – contenu et validité des produits, WC – propreté et opérationnels, les vestiaires, les salles de repos, les installations de préservations des repas ou de leur cuisson, L’air ambiant (température, particules en suspension…), l’environnement sonore, la présence d’Equipements de Protection Individuels (EPI) adaptés aux risques et portés, l’accès libre à l’eau potable, etc.

A l’issue de ce tour des installations, l’auditeur aura collecté tellement d’éléments qu’il aura à vérifier au travers de la revue documentaire et/ou des entretiens, que le temps passé à découvrir les installations lui sera profitable pour optimiser le reste de ses investigations documentaires ou d’entretiens…

La prochaine fois nous aborderons l’aspect contrôle des documents, Système de Management et Procédures du site prouvant la maîtrise de la conformité du site par rapport aux exigences sociales du référentiel choisi.