Comment s'assurer que les exigences de conformité sociale soient des règles applicables?

  • 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.

Qu'en est-il vraiment de tous ces référenties de conformité sociale, de toutes ces propositions d'interventions, de tous ces "experts" en la matière?

La seule recommandation fiable et "viable" pour les organisations françaises se souciant de conformité sociale, est de rester conforme aux textes législatifs Français, et notamment, d'appliquer les textes du Code du Travail. Si l'un de ces textes paraît susceptible d'être remis en cause, une lecture des Conventions de Base de l'OIT apportera, immédiatement, la limite "basse" des exigences sociales concernant le thème concerné.

Que ce soit la conformité sociale à évaluer dans n'importe quel pays membre de l'OIT, là où des opérations de production ont été délocalisées à une époque pas si lointaine, ou si c'est se préparer à aller visiter des organisations locales qui sont déjà partenaires de l'entreprise Française, donneur d'orde, ou qui pourraient le devenir, la démarche est régulièrement la même. trouver sur Internet, en quoi les exigences locales sur les thèmes abordés par les exigences sociétales et les comparer avec la teneur des Conventions de Base de l'OIT. 

Le principe est assez simple à appliquer, cette comparaison entre textes législatifs locaux et les textes de l'OIT est assez rapide à mener : "ce sont les exigences les plus protectrices et favorables aux travailleurs qui seront retenues comme critères de base". 

Ainsi, plus de 90% des exigences sociales contenues dans les référentiels, Codes de conduite ou autre texte, seront facilement évaluées tout en restant en France. A-t-on réellement besoin de tous ces outils référentiels, en plus des textes législatifs légaux?

Cependant, cela ne doit pas exonérer l'entreprise Française d'aller sur site évaluer ou faire évaluer l'Organisation locale sous-traitante/productrice, sur sa performance sociale.

Mais cela est une autre histoire de savoir qui pourra mener ces investigations de façon cohérente, neutre, objective et fiable.