How to Respond to Reviewers Comments for Journal Paper || Response to Reviewers || Revision || Hindi

Journal papers often get stuck at the revision stage not because authors lack effort, but because reviewer comments aren’t addressed in a structured, traceable way. The core takeaway here is that a strong response package links every reviewer point to a specific change in the manuscript—politely, point-by-point, and with clear evidence—so editors can quickly verify that the concerns were actually handled.

The process starts once major revision comments arrive from an international journal. In the example described, an editor flags that the paper isn’t acceptable in its current form and instructs the authors to address the reviewer comments in detail. The comments then come in multiple parts (often from several reviewers), and the guidance is to avoid the “address a bunch and hope” mindset. Instead, each comment must be treated individually: if a reviewer’s request can’t be fully addressed because it points to a different direction or scope, the response should still be courteous and specific—confirm what was done, clarify what wasn’t, and indicate how the issue could be handled in future research.

To make the revision easy to audit, the author prepares a response-to-reviewers document that groups reviewer feedback and corresponding replies. The package includes a cover-letter-like first page with submission ID and the original title, followed by sections such as “Response to Reviewer 1” and “Response to Reviewer 2.” For each comment, the response should be written politely and directly tied to the manuscript modifications. A practical detail emphasized is highlighting: when changes are made in the text, those altered portions should be highlighted in the manuscript and referenced in the response document so the reviewer can see the match between the critique and the fix.

Manuscript changes are handled using two versions of the paper. One file is prepared with Track Changes enabled, and another is a clean version without Track Changes. Track Changes makes edits visible at the line level—new text, deletions, and formatting adjustments—while the clean file leaves only the final revised content (with highlighting limited to the modified sections, depending on how it’s prepared). When submitting, these files are typically combined into a single PDF so editors and reviewers can read the response and verify the edits quickly.

The workflow also includes using Track Changes controls to generate the clean version: after reviewing the edits, authors can accept all changes to remove the markup, leaving a clean manuscript where only the final revised text remains. The same structure is repeated for both major and subsequent revision rounds (with the transcript noting that minor comments may come later and should be addressed similarly).

Finally, the guidance frames this approach as a way to reduce rejection risk: when major revision comments are addressed correctly—often in the majority of cases—acceptance becomes far more likely. The overall message is operational: build a revision package that is organized, polite, and verifiable, with every reviewer concern traceable to a concrete manuscript change.