Why Was My EcoVadis Proof Rejected? 5 Common Reasons & How to Fix Them

Updated: July 26, 2026

If your EcoVadis proof was rejected, the first step is to understand what “rejected” usually means. In many cases, the file was not rejected as a file. It was uploaded, reviewed, and then not credited because the evidence did not clearly support the answer.

This guide explains the main reasons EcoVadis evidence is rejected, not accepted, or not credited: relevance, date, credibility, scope, and clarity. Use it when you already submitted proof and want to understand why the document did not count the way you expected.

What Rejected Proof Usually Means

EcoVadis proof rejected is a broad phrase. It can mean the document was technically rejected, or that the uploaded evidence was reviewed and not credited. This page focuses on the second situation: the document was available to the analyst, yet the evidence did not clearly support the answer.

EcoVadis states that questionnaire responses can only be credited when requested documentation backs them up. That makes the document more than an attachment. It is the evidence trail behind your answer.

My EcoVadis Document Says “Eligible”. Why Was My Answer Still Rejected?

An Eligible document status does not mean that every questionnaire answer linked to that document was accepted. EcoVadis reviews the evidence in relation to each selected answer. A file can meet the document-level requirements and still fail to prove a specific declaration.

After your scorecard is published, check My Performance > Score details > Analysis of your answers. EcoVadis says this section shows how your questionnaire answers and attached documents affected the assessment, including the status of evidence submitted for individual questions and reasons why answers were not accepted.

The step-by-step EcoVadis scorecard guide shows how to move from the theme and indicator view into Analysis of your answers, selected answers, Accepted or Rejected status and document details.

The Analyst Logic Behind Accepted Evidence

EcoVadis evidence is strongest when it shows a working management system. In practical terms, that means your documents should connect commitments, implementation, and performance.

• ✔ Policies: formal commitments, objectives, and expectations.
• ✔ Actions: implementation evidence such as procedures, training, audits, assessments, controls, certificates, and improvement actions.
• ✔ Results: KPI, reporting, performance, monitoring, and trend evidence.

For a broader explanation of how EcoVadis evaluates sustainability management systems, see the EcoVadis methodology explained guide.

Reason 1: Relevance Mismatch

The problem: The document is related to the theme, but it does not answer the specific question. For example, an environmental policy may support a policy question, while a water KPI question needs water performance data.

This is one of the most common reasons EcoVadis evidence is not credited. A general sustainability report, policy, or certificate may be useful in one place and weak in another.

How to fix it

• Read the question type first. Is EcoVadis asking for a Policy, Action, or Result?
• Match the document to the evidence type. Do not use a policy as a substitute for KPI data or implementation proof.
• Use comments and page references. If the answer is on page 42 of a long report, say exactly where the analyst should look.
• Use focused filenames. For example: Environment_Water-KPI-Report_2025.pdf is clearer than report_final_v2.pdf.

For a Result question, an analyst usually needs data. For example, Gerresheimer provides Lost Time Incident Rate performance across multiple years in its Non-financial Report, which makes the performance trend easier to verify.

Reason 2: Outdated Evidence

The problem: The document may be relevant, but the date is outside EcoVadis validity expectations. This is especially common with KPI reports, old policies, old certificates, and historical sustainability reports.

EcoVadis guidance refers to an eight-year validity period for policies and actions and a two-year validity period for KPI reporting documents in several document-preparation contexts.

How to fix it

• Check the document date. Look for issue date, approval date, review date, reporting year, and KPI period.
• Separate policy/action evidence from results evidence. KPI and reporting evidence usually needs to be much more recent.
• Replace old files where possible. If the policy is still active, add evidence of review or reapproval.
• Build a current evidence library. Keep a folder of documents suitable for the current assessment or reassessment.

Reason 3: Credibility Gap

The problem: The evidence may look informal, incomplete, editable, or created only for the assessment. Examples include draft policies, unlabelled spreadsheets, screenshots without context, and internal exports with no clear source, owner, entity, reporting period, or scope.

Credibility does not mean every document must be externally audited. Internal evidence can be useful when it is official, controlled, clearly attributable to your company, appropriately dated or reviewed for the document type, scoped, and clearly part of your management system.

How to fix it

• Use official records. Make the company identity, owner, title, approval or review status, and scope clear. For policies, include an issue, approval or effective date and a clear review mechanism or review date. For KPI and reporting evidence, make the reporting period explicit.
• Turn raw exports into controlled documents. Add reporting period, methodology notes, responsible team, and version control.
• Avoid last-minute evidence created only for the assessment. EcoVadis expects authentic, pre-existing, complete documents.
• Use third-party evidence where appropriate. Certificates, audited reports, verified databases, and assurance statements can strengthen the evidence trail.

For example, Vetter Pharma publishes ISO certificates through its downloads page, and Ansell explains its Zero Waste to Landfill certification from Intertek in its public FAQ. These are examples of evidence that is easier to verify than an unlabelled screenshot.

Reason 4: Scope Mismatch

The problem: The evidence may relate to the wrong legal entity, site, country, business unit, or parent company. This is common for subsidiaries, multi-site companies, and groups with central policies.

A group-level policy can be useful, but the document or questionnaire comment should make clear that it applies to the assessed entity. Site-specific evidence can also be useful, but the coverage needs to be clear.

How to fix it

• Confirm the assessed scope. Check the exact legal entity, address, and assessment scope in the EcoVadis dashboard.
• Match names and entities. The document should name the assessed entity or clearly apply to it.
• Explain group applicability. If using parent-company evidence, explain how it applies to the subsidiary or assessed entity.
• Add local implementation proof. Pair group policies with site records, training logs, certificates, procedures, or KPI evidence from the assessed scope.

For example, Konica Minolta shows group-level environmental management information alongside site certification information on its environmental management system page. That type of structure helps connect central policy to local implementation.

Reason 5: Clarity and Findability Problem

The problem: The right evidence exists inside the file, but it is hard to find. This happens with long sustainability reports, dense policy manuals, scanned PDFs, non-English files, and documents with no page references.

EcoVadis guidance says machine-readable documents help information extraction and translation during the assessment process. If a file is scanned, locked, image-only, or difficult to search, important evidence can be missed or delayed.

How to fix it

• Use machine-readable files. Upload searchable PDFs or text-based documents where possible.
• Point to the exact page. Use the comment box to identify page numbers, sections, tables, and KPI names.
• Do not rely on embedded hyperlinks. Evidence should be contained in the uploaded file or captured document.
• Translate the key section if needed. If the document is not in English, provide the relevant translated excerpt in the comment box.
• Use clear filenames. Include theme, topic, evidence type, entity, and year where useful.

Rejected Proof Repair Checklist

Use this checklist when EcoVadis proof was rejected, not accepted, or not credited.

Frequently Asked Questions

Need an Answer?
Is there a part of the EcoVadis process you're stuck on? Click here to submit your question, and it could be featured in a future edition of The Answer.