Reporting Violations of the Code of Conduct
1. Introduction
All Draka employees are encouraged to report any suspected breach of any law or the Code of Conduct to their own management. As such, Draka has developed a procedure for you to report such activity – this procedure is called “The Whistle Blowing Procedure”. This procedure is not designed to replace honest and open communication between staff and their line managers. However, it may not always be possible to raise certain issues with your direct manager or supervisor. The procedure makes it possible for employees to report their thoughts without fear of reprisal from the company. Draka, on its turn, commits to deal professionally with any genuine concern that may be raised. Draka also welcomes ideas from employees on promoting integrity within our company. If you might have second thoughts about something, don’t hesitate to tell. Your view is very important to us.
2. Draka’s viewpoint on reporting violations
2.1 Introduction
All employees that wish to raise a specific concern about violations of the Code of Conduct are encouraged to first discuss the matter with their direct manager or supervisor. This method is preferred because reporting of concerns to management is the fastest way to clear up any misunderstandings and also the best way to ensure an open working environment throughout the organization.If this option is insufficient, the employee can report a suspected violation of the Code of Conduct to the Compliance Officer:
Ms. Jacoba Bremer
Address: De Boelelaan 7, 1083 HJ Amsterdam, the Netherlands
Email: complianceofficer@draka.com
Alternatively employees could utilize an online reporting option. Please refer to the Draka Intranet site for more information on this option.
A suspected breach refers to a suspicion, based on a reasonable ground, which concerns the organization with:
a) Violation of external rules and regulation
b) Violation of internal rules and regulation
c) Unethical behavior
It will not always be clear whether a particular action falls under one of these categories and you will need to use your own judgment. However, in such cases, Draka would prefer that you report your concerns in good faith, rather than keep them to yourself.
Furthermore, the Whistle Blowing Procedure applies to all Draka companies and all its subsidiary companies worldwide.
2.2 Non-retaliation
Draka wants to ensure that an employee, who reports any breach that he or she reasonably believes to be true, can do so without the risk of retaliation. Employees who report a breach will be given protection and shall not be put at a disadvantage as a result of his or her report. If you have played a role in the irregularities, reporting this is however no guarantee that this will clear your name.2.3 Misuse of Draka's Whistle Blowing Procedure
Draka wants to provide an environment in which employees can express any concerns they may have about wrongdoing at the workplace. We do welcome all reports made in good faith. If it should become clear that the Whistle blowing procedure has not been undertaken in good faith (for example, to pursue a personal grudge against another employee), this will constitute misconduct. Draka cannot permit a situation in which an employee purposely makes a report that he or she knows, or has reason to know, is false. Making a false report will most probably result in consequences for the employee, and he or she may be held accountable for damages suffered by anyone who has been affected by these false reports.3. Reporting procedures
3.1 Internal reporting to the appointed officer
Draka encourages employees to report any misconduct directly and openly to their manager or supervisor. If notifying your manager or supervisor is not possible or inappropriate, or if you are not satisfied with the response you receive, you can notify the Compliance Officer. Draka’s Compliance Officer can be contacted in writing, by telephone, in person or by e- mail. To find out more about who the Compliance Officer is, check the intranet (www.drakaintranet.com) or ask your local manager or supervisor.While reporting please provide as much detailed information as possible. The Compliance Officer will compile a written and dated document of the report when he or she believes it is necessary to investigate upon. The person reporting the incident will then sign the document for approval, and will also receive a copy. If the suspected breach concerns a member of the Board of Management, the Compliance Officer will ensure that the designated member of the Supervisory Board is informed immediately of a reported suspected breach, and of the date that the report was received.
However, if the suspected breach relates to the Compliance Officer, the complaint may be reported to the Staff Director Legal and Taxes of Draka Holding N.V.:
Name: Mr. Ronald Dietz
Address: De Boelelaan 7, 1083 HJ Amsterdam, the Netherlands
Telephone: + 31 (0) 20 5689802
E- mail: Ronald.Dietz@draka.com
Within a period of eight weeks from the date that a report was made, the person involved will be informed by the Compliance Officer of the status with regard to the reported suspected breach. Measures taken in response to the report will be included in the letter.
In the event that information about the status of the situation cannot be given within eight weeks, the Compliance Officer will inform the person involved of this matter. A new date will be set for when the person involved can expect notification of the status.
If the person involved is not satisfied with the outcome of the report or has doubts about whether his/ her concern is being properly dealt with by the Compliance Officer, they have the right to raise it in confidence with the Chairman of the Supervisory Board.
4. Confidentiality
Draka acknowledges that some employees may wish to express their concerns confidentially. Therefore, all reports of a breach will be dealt within a confidential manner. Confidentiality will be maintained to the fullest extent possible, consistent with the need to conduct an adequate investigation of the report.
Last Update
Tuesday, 9 February 2010
(GMT +01:00)