ICASSP Author Response
Use this after ICASSP reviews are released. First confirm whether the current cycle even runs a
rebuttal: ICASSP historically had no author-response stage, and a short window is a
comparatively recent addition (in the 2026 cycle authors could reply until ~22 December
2025). Reopen the current call before promising reviewers anything.
What the rebuttal is and is not
- It is a short, text-based reply to the reviews, not a chance to upload a revised PDF or new
experiments. Argue from what you already submitted.
- ICASSP is single-blind, so the reviewers know your identity; write professionally and do
not attempt to re-establish anonymity or drop identifying hints to sway a reviewer.
- The audience is the area/technical-committee decision: give whoever aggregates the reviews
a clean reason to accept, not a point-by-point defense that wins arguments but not the paper.
Triage before drafting
- Separate factual errors in the review (a metric misread, a missed baseline that is in the
paper) from legitimate gaps (a missing comparison, an unreported condition).
- Fix the factual errors first with an exact pointer: "Table 2, row 3 already reports this."
- For real gaps, concede cleanly and scope a camera-ready clarification that adds no
unsupported new claim — the four pages you submitted are the evidence of record.
- Rank concerns by decision weight; one resolved correctness objection outranks five answered
style notes.
Signal-processing reviewer pushback patterns
| Pushback |
What it signals |
ICASSP-ready fix |
| "The baseline is not the current strong method" |
Reviewer knows the task's state of the art |
Name the specific stronger baseline you did compare, or concede and scope it for camera-ready |
| "Which SNR / condition does this hold at?" |
The reported number hides its operating point |
Point to the sweep or table cell; if only one condition was tested, say so plainly |
| "Metric is not the one this task uses" |
Measurement mismatch (e.g., accuracy where SI-SDR belongs) |
Report the field-standard metric if you have it, or explain why yours is defensible |
| "No significance / spread over runs" |
One-seed result |
Cite the multi-run spread if present; otherwise concede it as a limitation |
| "This is a known result / prior art" |
Novelty challenge |
Cite the exact delta versus the named prior work in one sentence |
Drafting pattern
- Open with the single most decision-critical correction or concession.
- Anchor each point to an exact location in the submitted paper (table, figure, equation, line).
- State the signal-processing consequence, not just the fact.
- Promise only camera-ready wording or clarification fixes that stay within the accepted claim.
Micro-example
Reviewer objection: the enhancement gain is reported only at one SNR, so the improvement may not
generalize. Reply skeleton:
- Concede the main table fixes SNR at one value for space.
- Point to Fig. 3, which already sweeps 0-15 dB and shows the gain persists.
- Note the trend is monotone, so the single-SNR table is representative, not cherry-picked.
- Offer one camera-ready sentence stating the operating range explicitly.
Calibration for a short window
- Reply early; ICASSP rebuttal windows are brief and a late, exhaustive reply is worth less
than a prompt, precise one.
- Do not paste new derivations or fresh result tables the reviewers cannot verify against the
submitted PDF.
- Keep within any stated length/format cap; if none is stated, be concise anyway — committee
members read many rebuttals in one sitting.
Output format
[Rebuttal exists?] yes (dates) / no this cycle / unverified
[Priority issue] <reviewer concern>
[Decision dimension] correctness / novelty / evidence / clarity / metric-fit
[Draft response] <ICASSP-ready text, anchored to submitted paper>
[Evidence anchor] <table/figure/equation/line>
[Camera-ready promise] <scoped fix that adds no new claim>
Currency note
The 2026 rebuttal window (reported open to ~22 December 2025) was checked 2026-07-09 via
official-page renderings (see ../../resources/official-source-map.md). Whether a rebuttal
recurs, and its dates and length, are cycle-specific — verify on the current call before drafting.
Source: brycewang-stanford/Awesome-Journal-Skills → ICASSP-Skills/skills/icassp-author-response/SKILL.md
1---2name: icassp-author-response3description: Use when drafting an ICASSP rebuttal or author response to reviews, covering the recently added and short author-response window, the single-blind setting where reviewers already know you, answering signal-processing reviewers from the four-page record without a revised PDF, and writing for the technical-committee decision rather than for tone.4---567# ICASSP Author Response89Use this after ICASSP reviews are released. First confirm whether the current cycle even runs a10rebuttal: ICASSP historically had **no** author-response stage, and a short window is a11comparatively **recent addition** (in the 2026 cycle authors could reply until ~22 December122025). Reopen the current call before promising reviewers anything.1314## What the rebuttal is and is not1516- It is a **short, text-based reply** to the reviews, not a chance to upload a revised PDF or new17 experiments. Argue from what you already submitted.18- ICASSP is **single-blind**, so the reviewers know your identity; write professionally and do19 not attempt to re-establish anonymity or drop identifying hints to sway a reviewer.20- The audience is the **area/technical-committee decision**: give whoever aggregates the reviews21 a clean reason to accept, not a point-by-point defense that wins arguments but not the paper.2223## Triage before drafting24251. Separate **factual errors in the review** (a metric misread, a missed baseline that is in the26 paper) from **legitimate gaps** (a missing comparison, an unreported condition).272. Fix the factual errors first with an exact pointer: "Table 2, row 3 already reports this."283. For real gaps, concede cleanly and scope a **camera-ready** clarification that adds no29 unsupported new claim — the four pages you submitted are the evidence of record.304. Rank concerns by decision weight; one resolved correctness objection outranks five answered31 style notes.3233## Signal-processing reviewer pushback patterns3435| Pushback | What it signals | ICASSP-ready fix |36|---|---|---|37| "The baseline is not the current strong method" | Reviewer knows the task's state of the art | Name the specific stronger baseline you did compare, or concede and scope it for camera-ready |38| "Which SNR / condition does this hold at?" | The reported number hides its operating point | Point to the sweep or table cell; if only one condition was tested, say so plainly |39| "Metric is not the one this task uses" | Measurement mismatch (e.g., accuracy where SI-SDR belongs) | Report the field-standard metric if you have it, or explain why yours is defensible |40| "No significance / spread over runs" | One-seed result | Cite the multi-run spread if present; otherwise concede it as a limitation |41| "This is a known result / prior art" | Novelty challenge | Cite the exact delta versus the named prior work in one sentence |4243## Drafting pattern44451. Open with the single most decision-critical correction or concession.462. Anchor each point to an exact location in the submitted paper (table, figure, equation, line).473. State the signal-processing consequence, not just the fact.484. Promise only camera-ready wording or clarification fixes that stay within the accepted claim.4950## Micro-example5152Reviewer objection: the enhancement gain is reported only at one SNR, so the improvement may not53generalize. Reply skeleton:54551. Concede the main table fixes SNR at one value for space.562. Point to Fig. 3, which already sweeps 0-15 dB and shows the gain persists.573. Note the trend is monotone, so the single-SNR table is representative, not cherry-picked.584. Offer one camera-ready sentence stating the operating range explicitly.5960## Calibration for a short window6162- Reply **early**; ICASSP rebuttal windows are brief and a late, exhaustive reply is worth less63 than a prompt, precise one.64- Do not paste new derivations or fresh result tables the reviewers cannot verify against the65 submitted PDF.66- Keep within any stated length/format cap; if none is stated, be concise anyway — committee67 members read many rebuttals in one sitting.6869## Output format7071```text72[Rebuttal exists?] yes (dates) / no this cycle / unverified73[Priority issue] <reviewer concern>74[Decision dimension] correctness / novelty / evidence / clarity / metric-fit75[Draft response] <ICASSP-ready text, anchored to submitted paper>76[Evidence anchor] <table/figure/equation/line>77[Camera-ready promise] <scoped fix that adds no new claim>78```7980## Currency note8182The 2026 rebuttal window (reported open to ~22 December 2025) was checked 2026-07-09 via83official-page renderings (see `../../resources/official-source-map.md`). Whether a rebuttal84recurs, and its dates and length, are cycle-specific — verify on the current call before drafting.8586---8788**Source:** [`brycewang-stanford/Awesome-Journal-Skills`](https://github.com/brycewang-stanford/Awesome-Journal-Skills) → `ICASSP-Skills/skills/icassp-author-response/SKILL.md`
thedixitjain