Create a Code of Conduct

The code of conduct is the central evidence for ESRS G1-1. In preeco | nachhaltigkeit you record it in the “New Code of Conduct” slide-over with version status, scope and the ESRS G1-1 disclosures. The application versions codes and distinguishes between the status “Draft” and “Published” – only a published code counts toward the completeness check.

Prerequisites

• At least one active reporting period has been created for the team.
• You have the version, effective date, approval date and the name of the approver at hand – these are mandatory fields.

Step by step

1. Open the “Business Ethics” page via the “Governance → Business Ethics” menu.
2. In the “Code of Conduct” section, click “+ New Code of Conduct”. The “New Code of Conduct” slide-over opens on the right.
3. Complete the “Document” section: enter the “Title” and the “Version” (placeholder e.g. 1.0), choose the “Scope” (Global, Regional, Site-specific or Supplier) and the “Language” – ten languages are available, English is preselected.
4. Enter the “Effective date”, the “Approval date” and “Approved by”. Optionally add the “Document URL”, the “Key topics” (one topic per line) and a “Description”.
5. Complete the “ESRS G1-1 Disclosures” section: check the “Has an anti-corruption policy” toggle, which is enabled by default, describe the roles classified as being at risk of corruption under “Roles at risk of corruption”, and record the “Training strategy” (maximum 500 characters).
6. For the mandatory field “Protection of whistleblowers”, select Yes, No or Subject to statutory provisions. If you select Yes, the “Whistleblower policy URL” field also appears.
7. Click “Create”. Use “Cancel” to discard the entries.

What happens next

• The code appears in the “Code of Conduct” table with the status “Draft”. Refresh the page if the new entry is not yet displayed.
• Then publish the code via its detail page. Only then is it counted as a published code in the business ethics validation.

A tip from practice: create a separate entry with a new “Version” for every revision instead of overwriting an existing code. That keeps it traceable which version was in force in which reporting period – exactly what the evidence trail for ESRS G1-1 expects.