The scorecard is easy to treat as an ending. The medal is in, the portal is quiet, and the team has other work. The comments on that scorecard are the beginning of the next submission. They describe where evidence was thin, where reporting was incomplete and where a theme did not move.
This article covers how EA keeps that feedback usable: storing the analyst wording against the answer and the file, using version history to see repeats, updating the source so the next Autofill cites the new document, and routing the comment to the people who produce the evidence. That is valuable because EcoVadis submission help can then start from known improvements rather than a blank reconstruction of last year’s comments.
EA drafts from the organisation’s knowledge base and previously approved answers. People still own the source updates and decide what is ready. EA does not award a medal, guarantee a score or submit to EcoVadis.
Keep the comment on the theme and the file
A PDF of analyst comments in someone’s email is difficult to action. The same wording is easier to use when it sits beside the Ethics policy or the Sustainable Procurement answer it refers to.
EA keeps comments on the Autofill answer, next to the citations and supporting documents that answer used. The original analyst wording can be pasted there so it is not summarised into a vague “we need more evidence” task. When the owner next opens that answer, the feedback is on the item, not in a side inbox.
That is the value: the person who can change the file sees the comment in the same place as the draft. Storing comments against answers is how that reading becomes maintenance.
Recurring problems show up in the history, not as a new surprise
Some gaps appear once. Others repeat: missing performance data, undated policies, limited supply-chain coverage. If the team only patches questionnaire wording, the same comment returns.
EA keeps version history and a timeline on each Autofill answer. Edits autosave as versions; the timeline shows what changed and lets the team restore an earlier one. Comparing this cycle’s comments with last year’s versions is how a repeat becomes visible — Sustainable Procurement weak for two cycles is a process and a metric, not a rewritten paragraph.
That is the value: history on the answer is a pattern, not a one-off fix. Without it, each assessment feels new.
Update the source, then let the next draft cite it
Most EcoVadis comments point at documents. The practical response is to replace the weak file in the knowledge base, then confirm that the next questionnaire answer cites the new one.
EA’s EcoVadis questionnaire workflow drafts from approved answers and evidence in the workspace. Once the updated policy or metric is in Storage and approved, the next Autofill run can attach that file instead of the retired one. Citations on the new draft show which source was used.
The loop is: comment on the answer, owner updates the source, Autofill cites the new file, people review. If any of those steps is missing, the next submission can carry the old problem. EA finds and attaches evidence; people still confirm it is current.
Send the comment to the people who create the evidence
Sustainability teams cannot invent an HR policy or an operations metric on their own. Feedback has to reach the people who produce the underlying work.
EA’s approval process lets each Autofill answer have named reviewers and approvers. Assigning the HR or operations owner as reviewer puts the scorecard comment on their queue, with Approve & Next to walk remaining items. A short, specific request on that answer is more useful than a general plea to “engage with EcoVadis”.
The person who owns the document then sees why the theme did not move, in the same record they are asked to accept. The assessment becomes ordinary document hygiene rather than a once-a-year scramble.
What this is worth to the team
Handled this way, EA does four things a filed scorecard PDF will not — and each is already in Autofill, not a side spreadsheet:
- It keeps the analyst wording on the item. Comments sit with citations and supporting documents.
- It makes repeats visible. Version history and the answer timeline show what was used last cycle.
- It makes reuse smarter. Updated, approved evidence in the knowledge base is what the next draft can cite.
- It names who must act. Reviewers and approvers receive the comment on their queue; EA still does not approve or submit.
When you assess whether EcoVadis feedback improves the next submission, those are the tests: are comments stored against answers and files; can the team see issues that recurred; does each comment have an owner and a source update; will the next Autofill cite the new file; and do evidence owners receive the specific feedback that relates to their documents?
Feedback is the start of the next pack, not the end of this one.
Would you like to see how EA supports EcoVadis evidence, review and reuse? Book a demo or try EA for free.
