Using the EU Voluntary Standard in Tenders, Supplier Onboarding and Customer Due Diligence

Tenders and onboarding portals combine different information purposes. A customer may request sustainability-reporting data for its own mandatory report, evidence of a policy, proof of a certification, product-level environmental information, sanctions or modern-slavery declarations, incident history and commercial commitments. The EU Voluntary Standard can organise much of the sustainability layer, but a controlled response process must classify what sits inside the report, what needs separate evidence and what should not be released without further approval.

LRA tender response workflow: classify the request, reuse the approved core, add scoped evidence, approve release and archive the exact version sent.

B1 requires a brief description of sustainability-related certifications or labels obtained by the undertaking, including the issuer and, where relevant, date and rating score. This makes certifications easy to reuse in a tender, but their scope must remain visible. An ISO 14001 certificate for one site does not certify the sustainability report, the full group, a product footprint or every environmental disclosure.

Where the value chain cap applies, information outside Annex II for the protected undertaking’s employee band can be declined for the customer’s mandatory-reporting purpose. The cap does not prohibit voluntary sharing. An SME may choose to provide an above-cap target, Scope 3 estimate, product initiative or policy because it strengthens a tender or reflects common sector practice. The decision should be explicit and should not convert a voluntary answer into a permanent, unrestricted commitment.

1. Register the request. Capture customer, portal, deadline, purpose, contract/tender reference, intended users and required declarations.

2. Split the questionnaire into lines. Do not classify a mixed questionnaire as a single legal purpose.

3. Map each line. Link to the approved EU disclosure, evidence record, other legal source or “new information required”.

4. Test the value chain cap where relevant. Confirm ultimate requester, mandatory-reporting purpose, protected status and exact Annex II coverage.

5. Verify evidence and date. Check entity/site scope, reporting period, method, expiry, assurance scope and unresolved gaps.

6. Choose response type. Report cross-reference, concise answer, document upload, voluntary above-cap answer, clarification request or decline.

7. Apply legal, privacy and confidentiality review. Particular care is needed for incidents, personal data, trade secrets, contracts and product claims.

8. Approve the release. Data owner approves facts; reporting owner approves consistency; commercial/legal owner approves the representation; final approver authorises release.

9. Archive the exact submission. Save portal exports, attachments, screenshots, confirmations and change log — not only the working spreadsheet.

10. Monitor triggers. Correct or update the customer if a material error, incident or certificate change affects the response.

Uploading the same pack everywhere. Different recipients and purposes require different access, wording and evidence.

Letting the portal define the reporting claim. A checkbox such as “ESG report audited” must be reconciled to the actual basis and assurance scope.

Using homepage links. Cross-references should lead directly to the current disclosure or document version.

Treating commercial sensitivity as automatic confidentiality. Apply the Standard’s omission conditions and separate tender-release judgement.

Turning a voluntary answer into a standing warranty. Review tender declarations and contract incorporation.

No record of what was sent. Portal entries can change; archive the exact submission and confirmation.

Marketing edits after approval. Any change to a quantitative or technical claim should return to the owner and reviewer.