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

  • 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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.

Les informations recueillies lors du tour des installations,ainsi que certaines « explications » fournies par le chef
d'entreprise ou son représentant vont nous permettre de demander à compulser certains documents, archivés ou non, pour apporter les éléments objectifs de conformité (ou non).

La Revue Documentaire :

Exercice pouvant s'avérer difficile car il ne faut pas tomber dans le travers, vus plusieurs fois, ou l'auditeur va se « sécuriser » en se plongeant, la majeure partie de son temps d'audit, dans l'étude documentaire.

L'attitude à adopter n'est pas de demander des documents car il faut les compulser, non, mais systématiquement se poser cette question : « Que rechercher au travers de ce document spécifique ? »

Quelques exemples :

Demander à compulser les bulletins de salaires des mois précédents... pour rechercher quel élément de preuve ? : Déjà que l'entreprise remet bien à ses travailleurs une preuve écrite de rémunération. Pour être efficace, l'analyse des bulletins de salaire doit TOUJOURS être menée conjointement avec celle des enregistrements des heures travaillées.

Que rechercher ?

Si les heures travaillées sont bien comptabilisées et rémunérées correctement et en adéquation avec les règles établies (Droit du Travail, Convention Accords signés, etc.) ; puis s'assurer qu'aucun prélèvement sur le bulletin de salaire ne corresponde à une pratique ou mesure « illégale » (punition, amende, etc.). Une action incontournable pour s'assurer que le site rémunère correctement les heures enregistrées (ex : heures supplémentaires, congés payés, primes, absences...) est de refaire les calculs sur quelques exemples de travailleurs et de s'assurer que tout est correct. Si cela est le cas, pas de souci à se faire quant à sa conformité sur ce sujet.

Rechercher les éléments constitutifs du Système de management, notamment les politiques et les procédures. Deux possibilités au départ : soit le site possède un Système de management écrit, soit le site ne possède pas de système de Management écrit. Mais là encore, se référant à certaines situations rencontrées, On peut découvrir que le site possède bien un Système de Management écrit (politique, procédures, accords, etc.) mais que ses pratiques habituelles au quotidien ne sont pas le reflet de l'application des éléments de son Système de Management. Recherchant les éléments de preuves de conformité, c'est l'étude comparative entre ce qui est écrit et ce qui est réellement mis en œuvre qui apporte la preuve. Les procédures écrites, permettent de savoir comment les actions doivent (et seront) mises en application, de façon régulière afin d'atteindre la conformité recherchée.

Un autre élément d'analyse documentaire est l'aspect formation. Que rechercher ? Est-ce que le site forme, qui et sur quoi de façon cohérente et planifiée ? Les documents à compulser sont les listes d'émargement signées par les participants à la formation, et un rapide coup d'œil sur le contenu de la formation... des entretiens avec les travailleurs concernés pourront apporter la preuve de la réalisation de la formation.

Cette question à se poser systématiquement, « Que rechercher au travers de ce document spécifique ? », permettra un gain de temps et d'efficacité car votre recherche sera ciblée sur la recherche des éléments incontournables de conformité.

Nous verrons, plus tard, que les entretiens sont un exercice incontournable mais très efficace.