Use this after IROS reviews arrive — and, crucially, before submission too, because IROS traditionally offers no rebuttal. The reviews come with the decision, so the "response" is spread across three real channels: pre-answering in the paper, editing the camera-ready, and, if rejected or on the journal route, a response letter or resubmission memo. Confirm the current cycle's policy before assuming a rebuttal window does or does not exist.
The most effective IROS author response is written before anyone reviews the paper. Anticipate the standard objections and disarm them in the body and the video:
When the decision is accept (often with requested changes), the meta-review is your instruction set. Integrate its asks without inflating the contribution beyond what was reviewed.
| Meta-review ask | Camera-ready move | Trap to avoid |
|---|---|---|
| "Report failure cases" | Add the failure taxonomy table you logged | Do not add new claims the reviewers never saw |
| "Clarify the compute budget" | State measured rate and power on the robot | Do not quietly change the reported system |
| "Compare to system X" | Add the same-platform comparison if you have it | Do not fabricate a comparison you did not run |
| "Fix anonymized links" | Replace with the public, licensed release | Do not leave "code coming soon" |
Reviewers rejected a manipulation paper for "insufficient real-robot evidence." The memo:
Response draft skeleton (camera-ready or RA-L letter):
[Point] <reviewer/meta-review concern>
[Change] <exact edit or added table/figure>
[Location] <section / table / line in the revised paper>
[Not added] <new claims deliberately withheld to stay within review scope>
[Channel] pre-submission / camera-ready / RA-L letter / resubmission memo
[Priority concern] <the objection that most threatens acceptance>
[Response] <IROS-appropriate, scoped, anonymity-safe>
[Evidence anchor] <paper/video/log item>
[Forbidden] <new unsupported claims / identity leaks / fabricated comparison>