How to Collect Feedback on Files and Link Each Comment to the Right Version

Why a comment needs a reference

“Change the ending” seems clear until someone asks: the ending of which file and which version? When several copies of a document, image, or video are circulating, a comment without a reference can be applied to the wrong material or describe a part that has already changed. To avoid this, link each comment to the file and the state the person reviewed.

A form can help collect structured information, but that does not mean the response is noted directly on the file. Record separately what material was reviewed, where the issue is, and what change is proposed. That way, the team can check each comment before deciding what to do.

• Weak reference: “The page is wrong.”
• Useful reference: “Website_proposal_v02, page 3, second block: the button doesn’t stand out; I suggest using the text ‘Request an appointment.’”

Before sharing: identify the file and version

Prepare a clear reference before inviting people to review. Include a recognizable project name, the type of material, and a version identifier, such as “Product_catalog_v03.” If helpful, add a review date or a label such as “for comments.” Avoid ambiguous names like “final,” “final2,” or “latest”: they don’t clearly indicate which file is being reviewed.

Decide which reference will be used for the review round and share that resource, rather than a mixture of copies sent by email and old links. Check that the link opens the intended material, and note the version identifier you’ll include in the instructions and form. These are organizational guidelines for the review process, not a description of specific platform features.

• Check the file name and open the link as the reviewer will.
• Note the version identifier that will appear in the form.
• If you share several items, give each one a different name or code.

Design a short, actionable form

Ask for the minimum information needed to interpret each comment. A practical outline includes the material reviewed, version, location, observed issue, and proposed change. The location depends on the format: page and paragraph in a document; area of the image; or timestamp and segment in a video or audio file. If a precise coordinate isn’t possible, ask for a description that lets you find the point without guessing.

To organize responses, ask for one comment per entry or have each issue entered in its own section. Separate “what’s happening” from “what you suggest changing”: the proposed change won’t always be the only possible solution. Make only the necessary fields required, and explain how to respond.

• Material and version reviewed.
• Specific location: page, visual element, or timestamp.
• Observed issue and proposed change.
• Name or contact details only if you need to clarify or confirm the response.

Share the file and form with clear instructions

Send the file link and the form link together, identifying them as separate resources. Explain which one to open for the review and which one to complete to submit comments. Include the exact name of the material, its version, the review deadline, and instructions on whom to contact if the file won’t open or looks different than expected.

Adapt the instructions to the type of material. For a document, say whether you want feedback on the content, structure, or both; for an image, specify what aspect to evaluate; for a video, say whether you’re looking for comments on the edit, text, or specific moments. If you need to resolve questions about a response, request contact details; if you’re looking for general opinions, you can allow anonymous responses, bearing in mind that you won’t be able to ask respondents for clarification.

• Include the file name and version in your message.
• Ask reviewers to note one location per comment.
• Explain how to report an access problem without sending another copy through a different channel.

Organize responses before editing

When you close or pause the response period, gather the entries for the round alongside the reference for the material reviewed. Before changing anything, sort them by file and version. Check whether each response includes enough detail about the location and issue. If information is missing, mark it as awaiting clarification rather than filling in the gaps by intuition.

Turn the responses into a change list with simple statuses, for example: pending, clarification requested, accepted, rejected with a reason, and applied. Keep each task linked to the original comment. Group duplicates only after confirming that they refer to the same point and request. This reconciliation is an editorial task for the team, not an automatic conclusion generated by the form.

• Verify the version and location before accepting a comment.
• Don’t assume that several people pointing out the same symptom are proposing identical instructions.
• Record what was changed and what remains unapplied, with a clear reason.

If the file changes during the review

If the file changes while the review round is still open, pause applying comments and confirm which version each person received. Compare that reference with the current state: a comment about a deleted sentence may no longer be relevant, while a request about a replaced design may require a new decision. Don’t assume a response is still valid just because the file name hasn’t changed.

If the change doesn’t affect the points under review, tell the group what changed and indicate which reference applies to new responses. If it affects relevant content, structure, or decisions, identify a new version and open another round for the affected parts. Keep comments from each round separate so references don’t get mixed up.

• Pause and determine which version each person saw.
• Assess whether the change affects comments already received.
• Open another round when the material being reviewed changes substantially.

Close the round and keep only what’s needed

Before closing, check that every relevant comment has a decision and that accepted changes have been applied to the intended file. Review the complete result, not just the marked points: one change may affect other parts. If there were several rounds, identify the resulting version and avoid presenting an older file as current.

Limit access to responses and contact details to the people who need them to review or resolve comments. Collect only the data you need; decide how long you’ll keep the responses, and delete contact details and working copies when they’re no longer needed for the process. If you need to retain the decision history, keep the minimum useful context and avoid keeping duplicates without a purpose.

• Is the reviewed version identified, along with the version being delivered?
• Can each applied change be linked to a specific comment?
• Were unapplied suggestions clarified or documented?
• Are access to responses and their retention period defined?

Sources and scope of this guide

CATEDU presents digital tools for collecting and giving feedback as a way to facilitate an exchange of information: https://libros.catedu.es/books/b2-idiomas-area-3-ensenanza-y-aprendizaje/page/5-herramientas-para-recoger-y-dar-feedback-digital. AulaTIC / TotemGuard describes using an anonymous form to collect student opinions: https://www.totemguard.com/aulatotem/2017/04/como-recoger-feedback-alumnos-para-mejorar-como-profesor/.

These sources address feedback and forms; they don’t document how to link comments to file versions or reconcile responses when a file changes. The identification, tracking, and closing steps described here are process recommendations, not features attributed to those sources or to any specific platform.

Frequently asked questions