08.09.2013 Views

Sedex Members Ethical Trade Audit (SMETA) Best Practice Guidance

Sedex Members Ethical Trade Audit (SMETA) Best Practice Guidance

Sedex Members Ethical Trade Audit (SMETA) Best Practice Guidance

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

l <strong>Audit</strong>ors should ensure that problems raised by workers are discussed with management in a nonattributable<br />

way. <strong>Audit</strong>ors must ensure that the comments they report cannot be traced back to an<br />

individual worker.<br />

l When workers raise issues which could be directly attributable to one particular worker and / or could<br />

result in reprisals against workers, these can be reported directly to the appropriate audit reviewers via<br />

a supplementary report, available at GSCP (auditors should check the reviewer’s requirements). The<br />

issue should not be raised at the closing meeting, nor uploaded to <strong>Sedex</strong>.<br />

l <strong>Audit</strong>ors / worker interviewers should leave a contact telephone number, preferably their mobile<br />

number and their local office phone number, with all workers interviewed so that workers can alert the<br />

auditor to volunteer further information or to alert the auditor if there are reprisals or intimidation.<br />

l To protect worker confidentiality, issues which cannot be substantiated (e.g. confirmed by document<br />

review where possible) can be shared with the employment site owner only where there is no risk of<br />

victimisation. An example might be a verbal abuse issue where a large number of interviewees have<br />

raised it – impossible to trace individuals. The auditor must use judgement and above all protect<br />

confidentiality.<br />

7.4 Document Review<br />

7.4.1 Document Availability<br />

The documentation needed for the audit should have been requested during the initial communications with the<br />

employment site.<br />

On the day of the audit, all documentation should be available at the employment site for inspection, including<br />

payroll and working hours records. All documents should be available for a minimum of 12 months prior to the<br />

audit. If records for the previous 12 months are not available, the employment site should explain why this is the<br />

case. Any non-legitimate absence of documentation should be recorded on the audit report as noncompliance.<br />

For a full list of the documents that need to be reviewed See Appendix A3: "Preparation for <strong>Audit</strong> (Site of<br />

Employment”. Also included in “Guide to Pre <strong>Audit</strong> Information”.<br />

7.4.2 Document Sampling for Wages and Hours<br />

<strong>SMETA</strong> <strong>Best</strong> <strong>Practice</strong> <strong>Guidance</strong> (4-Pillar Version 4.0, May 2012)<br />

<strong>Audit</strong>ors should review at least three months’ worth of records from the 12-month set of data (or the available<br />

data for all months of production when the factory is operational less than 12 months) and should include<br />

records for the low season, the peak season, holiday periods and the most recent period available. Particular<br />

emphasis should be placed on how the site manages all aspects of the relevant code.<br />

<strong>Audit</strong>ors should concentrate on operators and wages and hours analysis should cover:<br />

7.4.2.1. Total wages and hours for all workers over the last 12 months should be viewed to establish peak,<br />

low and current production levels.<br />

7.4.2.2. Working hours and wage records are selected to cover both peak and current production levels.<br />

The records for the workers who have taken part in individual interviews should always be<br />

checked. The remainder of records checked should be sampled from the broader pool of<br />

employees.<br />

29<br />

BACK TO CONTENTS

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!