2025 IEEE International Conference on Acoustics, Speech, and Signal Processing

As an IEEE conference proceedings, all practices are aligned with IEEE Policies as well as the IEEE PSPB Operations Manual.

The IEEE Signal Processing Society holds an open call to the community that is listed on the conference website as well as emails to members and past participants, and posted to Call for Paper Online Message Boards to encourage an open and transparent submission and review process.

The Call for Papers, created by the Technical Program Committee Chairs (Editors), conveys relevant author information and paper requirements, important dates, and a non-exhaustive list of topic areas, called EDICS, which are considered in scope.

Paper submission deadlines are set for Wednesdays, including extensions along with other deadlines as much as possible. Moreover, paper submission deadlines are scheduled to avoid Major World Holidays. This aims to ensure that all members of the community participate by limiting the strain on authors and respecting individual’s personal, family, and home time.

Peer-reviewing is of vital importance to ensure the scientific quality of conference papers, and all papers submitted receive transparent, unprejudiced, efficient, and anonymous peer review, which is carried out by the Technical Program Committee—a well-defined hierarchy structure which includes the Technical Program Committee Chairs and Organizing Committee Members, and the IEEE Signal Processing Society Technical Committee Chairs and Committee Members–which oversees a large group of dedicated reviewers.

The editorial process of a paper consists of two parts: an initial check and then peer review. The paper is sent to a track chair for an initial check. Following this, the paper is assigned to at least three reviewers from the relevant research areas for peer review. These reviewers carefully review the manuscript and provide review comments to the area chair. Authors have an option to submit a rebuttal to the comments. The review comments and authors’ rebuttals, if any, will help the track chair to make the ultimate acceptance or rejection recommendation for the manuscript.

During the editorial process, the conference’s publication provider takes the responsibility of coordination between the publisher and authors, copy editing work, and other necessary publication support.

An Ombud is assigned for each conference and any violations of policies should be reported to the conference ombud, noted on the Organizing Committee page. All reports will be treated confidentially. The Ombud will investigate and prepare a brief statement of facts, a conclusion (proven/not proven) using a preponderance of the evidence standard, and a recommended sanction if a violation is proven. The Conference Organizing Committee will vote to either adopt or not adopt this recommendation and may modify it. The decision of the Committee is final.

General Chairs

• The General Chair is the conference lead overseeing all planning and execution of the conference. They ensure that all IEEE and SPS rules and regulations are followed, represent the conference to the governing bodies such as the SPS Board of Governors and Conferences Board, resolve or escalate issues in a timely fashion, and provide data and best practices information to IEEE and future General Chairs.

Technical Program Committee Chairs

• Technical Program Committee (TPC) Chair(s) are responsible for delivering a well-balanced and high-quality technical program and proceedings. The Technical Program Chair ensures that all persons involved in technical-related tasks, e.g. Area Chairs, session chairs, and reviewers, are experts in their fields and may represent different areas within the domain of the conference. There is also an expectation that all serving would not have a Conflict of Interest (COI) regarding papers under consideration. If a COI exists for any person serving, that paper would be blocked from that individual, and a secondary person on the committee would assume responsibility.
• TPC Chairs, often in coordination with the General Chairs, decide high-level policies, have the general oversight of the process, decide on the final number of accepted papers including the acceptance rate, and provide the final approval for all decisions. TPC Chairs continuously monitor the process to ensure timeliness and fairness. They also handle all appeals, complaints, and misconduct allegations. They are also responsible for applying the no-show policy in preparing the final proceedings.

Track Chairs and Track Co-Chairs

• Track Chairs and Co-Chairs are part of the Technical Program Committee (TPC). They are typically appointed by the corresponding SPS Technical committees.  They handle all the papers in their tracks and )manage the review process for the track. Co-chairs assist in the process and handle papers in which chairs are conflicted. Track chairs may assign reviewers and meta-reviewers directly or, for larger tracks, distribute papers to area chairs for handling. They are ultimately responsible for the decision recommendations on their track.

Area Chairs and Meta-reviewers

• Area Chairs, for the tracks that use them, are part of the TPC. They are responsible for a subset of the papers in a track that is subject to their area. They are responsible for assigning reviewers and meta-reviewers to the papers they are handling. They provide decision recommendations to the track chairs.
• Meta-reviewers, for the tracks that use them, assist Track Chairs and/or area chairs by summarizing the reviews and rebuttals and balancing conflicting viewpoints in them.

Reviewers

• Reviewers are selected by the IEEE Signal Processing Society Technical Committees and should consist of senior, mid, and junior professionals in the technical area. Every year, TC members should be asked to suggest new, competent reviewers, notably young reviewers, e.g. post-docs, and very senior or recently graduated Ph.D. students. This is especially important for emerging topics and topics without enough reviewers. In addition, the Conference Organizing Committee should also review the reviewer list and recommend to the Technical Committees additional reviewers to consider.
• New reviewers should be labeled as such if they are not yet in the reviewers list in order the Technical Program Committee Chairs or Area Chairs may more carefully check their credentials while assigning them reviews. It is requested and recommended that authors of all submitted papers participate as reviewers

Initial Triage

Papers undergo compliance checks with the conference submission template guidelines to ensure paper details on submission are consistent with review system data. Checks include the number of papers submitted by one author or co-author (nine or less), paper length, structure, research topics, language, author names, and order.  Papers undergo a first plagiarism and self-plagiarism check using iThenticate. The paper can be sent to peer review only if the paper passes the initial check.

Upon receipt of the paper assignments, Area Chairs review their list of papers for conflicts of interest, report to the Technical Program Chair, and the paper is re-assigned to another Area Chair. Area Chairs will also report to the Technical Program Chair any paper that has been categorized under an incorrect EDICS topic.

Paper Reproducibility and Supporting Content

Authors are encouraged and offered the ability to share datasets, code, and other supporting content associated with accepted papers. The below platforms support reproducibility and publicity for posters and/or presentation files that accompany a conference paper. Free resources are available to upload content.

• IEEE DataPort –  Authors are encouraged to upload up to 2TB of data associated with their conference paper to IEEE DataPort at no cost.  This service is intended to enhance the value of the article, support research reproducibility, and each dataset uploaded to IEEE DataPort is assigned a unique DOI that can be cited and referenced.
• Code Ocean – Authors are encouraged to include associated code, software simulations, algorithms, and more for article readers to understand what produced the results. Articles in the IEEE Xplore® digital library will display the associated and executable code from Code Ocean. Published code is fully citable and receives a DOI for better discoverability.
• IEEE SigPort – Authors are also encouraged to upload their presentations or posters in PDF format to share with other conference attendees.

Editorial Triage 

In this step, Technical Program Committee Chairs scan and place the papers in peer review tracks for Area Chairs to assign reviews.

Review Assignment

• Papers are assigned to a track according to what the authors selected as the first track during submission. If a paper is not a good fit for their track, track chairs have the option to reassign it to a different track, according to their best judgment. The secondary track that the authors choose during submission may serve as a guide for the reassignment but is not binding.
• Papers are assigned to area chairs and/or meta-reviewers (if the track uses them) according to their relevance to their expertise.
• Papers are assigned to reviewers by the track or area chairs, according to relevance to the reviewers’ expertise and the paper’s area either manually or assisted by AI tools, such as the Toronto Paper Matching System.
• Any AI-assisted assignment is manually refined by the track/area chairs as necessary before the final assignment to ensure all papers have sufficient reviewers and reviewers are not overloaded.
• Track chairs have the authority to invite additional emergency reviews as necessary for papers not meeting the minimum numbers or if a specific reviewer is not on the list of available reviewers for that paper, an area chair may contact them directly to recruit them to review the paper. This request must be sent to the Technical Program Chair for review and addition of this new reviewer.
• Each paper is assigned to at least three (3) reviewers. The best effort is made to ensure a good match between the author-declared areas of papers and the reviewers’ areas of expertise and a balanced composition of senior and junior reviewers.

Paper Evaluation (Peer Review)

A set of reviewers selected by the Technical Program Committee will review the submitted documents and rate them according to quality, relevance, and correctness. The conference’s Technical Program Committee will use these reviews to determine which papers will be accepted for presentation at the conference and published in the proceedings. The result of the technical committee’s decision will be communicated to the submitting authors by email, along with any reviewer comments, if any.

Papers undergo single-anonymous review (i.e., reviewers know the names of the authors, but reviewers are anonymous to the authors and other reviewers). At least three reviewers will be assigned to each paper.

Review Criteria

1. Language and Clarity of Presentation – The manuscripts submitted to the conference should be written in English, which is required to be inclusive, appropriate, and understandable for editors, reviewers, and future readers. Please use proper grammar, and fluent sentences, choose good words, and avoid syntax errors in your paper. Authors should be aware that comprehension difficulties may lead to rejection of the paper.
2. Importance/Relevance – Every researcher working in the general technical area should find interest in works “Of broad interest” such as, for example, a contribution that has broad impact, or a surprising result. Works “Of sufficient interest” do not have to address everyone in the audience, but should have an impact in a certain area. Works “Of limited interest” should be considered only if their novelty, clarity, and correctness is excellent. “Irrelevant” implies rejection, and must be justified thoroughly.
3. Novelty/Originality – “Very original” papers open new directions and often become seminal papers. “Has been done before” implies reject, in which case the reviewer’s comments must include appropriate justifications and relevant references.
4. Technical Correctness – “Technically correct” means that the work conclusions are supported by flawless arguments. Proofs are correct, formulas are correct, there are no hidden assumptions, and experiments are well-designed and properly evaluated. However, “Has major problems” implies rejection and must be justified thoroughly. For “minor errors”, the reviewer should list the errors that need to be corrected by the authors.
5. Experimental Validation – Different papers need different levels of experimental validation. A theoretical paper may need no experiments. A paper presenting a new idea might just need an experiment illustrating that there exists a situation where the idea applies. A paper presenting a new phenomenon or a performance evaluation paper may need thorough experiments and evaluation. “Insufficient validation” implies rejection and must be justified thoroughly.
6. Reference to Prior Work – “Does not cite relevant work” implies rejection. This option should be selected only if the missing work is well-known in the community and commonly cited, else we suggest selecting “References missing”. List the missing references. Reviewers are asked to review the citations for relevance and conflict of interest.

Immediate Rejects/Desk Rejects

For submissions that do not have a minimum quality or do not include adequate technical content as checked by two senior experts, e.g. Area Chairs or Technical Committee Chairs,  may be desk rejected and not subject to a full reviewing process. The immediate rejection must be supported by a clear motivation provided to the authors. This does not prevent authors from appealing later to the Technical Program Committee Chairs.

This option is used at the discretion of the event Organizing Committee; however, to be used, it has to be clearly announced well before the submission deadline on the event Web page and Call for Papers.

For scenarios where over nine (9) papers have been submitted listing the same author or co-author, the author will be contacted and asked to reduce the submitted papers to nine (9) or less.

Rebuttal Process

After reviews are returned to the authors, they are given at least one week to submit an optional rebuttal that is sent to the Technical Committee (TC) Chairs and their Area Chairs for use in helping make a final decision on papers. It is up to the Area Chairs to use a rebuttal response in making their decisions and it is noted that these Rebuttals are not shared with the original reviewers.

Notification of Acceptance or Rejection

Authors will be notified of paper acceptance or non-acceptance by email as close as possible to the published author notification date.

If accepted, the email notification may also include the presentation format chosen for your paper (lecture or poster) and the presentation date and time, if available. If this information is not available at the notification stage, a separate email notification will be sent soon after the acceptance notification date. The assignment of papers to oral or poster sessions is a purely scheduling decision from the TPC and does not reflect a quality judgment on the papers.

For both Acceptances and Rejections, the notification email will include comments from the reviewers. The conference cannot guarantee that all of the reviewers will provide the level of comment desired by each author. However, reviewers are encouraged to submit as detailed comments as possible.

An Ombud is assigned for each conference and any violations of policies should be reported to the conference ombud, noted on the Organizing Committee page. All reports will be treated confidentially. The Ombud will investigate and prepare a brief statement of facts, a conclusion (proven/not proven) using a preponderance of the evidence standard, and a recommended sanction if a violation is proven. The Conference Organizing Committee will vote to either adopt or not adopt this recommendation and may modify it. The decision of the Committee is final.

• The author must register at the full conference rate and for a maximum of four papers per author registration.
• One author may not be listed on more than nine (9) submitted papers.
• The paper must be presented at the conference live by one of the authors. (See No-Show Policy)
• All accepted papers must have an IEEE Electronic Copyright form submitted before the manuscript can be included in the conference proceedings. You will be required to submit the form during the submission of the final version of the paper.

Special session paper reviews are managed by the special session organizers, who report to the Technical Program Committee Chairs. Such papers also undergo review by at least three reviewers. At least one reviewer should be assigned externally by the TPC Chairs.

Proposals to hold a satellite workshop are reviewed and accepted or rejected by the Organizing Committee including the TPC Chairs.  Each Satellite Worksop Organizing Committee has its independent peer review process. Submitted workshop papers should abide by the conference’s paper style, format, and length, while their peer-reviewing process should follow all IEEE Policies and the main conference reviewing guidelines if the workshop organizers desire that the workshop papers be published at the IEEE Xplore Digital Library.

The goal of the review process is to accept papers that are technically sound and make an original and substantial contribution to the field. Your review plays a pivotal role in helping the Program Committee make this determination. Therefore, please budget sufficient time to read the paper and complete your review by the deadline. If due to unanticipated events you are not able to allocate enough time to review the paper, please inform the Program Committee as soon as possible so that they can make appropriate adjustments.

You will be asked to provide an evaluation of the paper assigned to you according to the following criteria:

• How confident are you in your evaluation of this paper
• Importance/Relevance
• Classify the type of paper
• Originality/Novelty
• Theoretical development
• Experimental validation
• Clarity of presentation
• Reference to prior work
• Overall evaluation of this paper
• Award quality

Each of these criteria has multiple options, one of which must be chosen. The rationale given in the review form for these criteria in the review form are self-explanatory and are not repeated here.

Your score and your comments will be shared with the authors. The only exception is “Confidential Comments to technical Program Committee.” Please use this field to convey to the Program Committee only something confidential that you believe should not be disclosed to the authors.

General Comments:

When deciding your recommendation for a paper, do not be shy. Use the whole spectrum of evaluation scores: if you think a paper is outstanding in any of the criteria, give it the highest score for that criterion. Similarly, if you think a paper is really bad (and can convincingly support your opinion), then give it the lowest score. Please give intermediate scores only when you think the paper lies in the middle and not because you did not have time to read the papers thoroughly or are not confident. This will greatly help the Program Committee accept the good papers and reject the bad ones.

Reviews that are too sketchy, short, or superficial do not help the authors, the Program Committee, and the ICASSP community. Therefore, please devote enough time to write a thoughtful and detailed review. Please be as specific and detailed as you can. Please be thoughtful and fair; do not let personal feelings affect your review.

Please ensure that your scores are consistent with your comments. If you have a negative assessment of an aspect of a paper that has led you to give a low score, please articulate it in your review. A negative review comment such as “has been done before” or “this is well known” must, in all fairness to the authors, include appropriate justifications and relevant references. The authors, even if they are disappointed, would greatly appreciate your comments.

Minor flaws or presentation issues or deviations from the paper submission guidelines can be addressed by the authors based on the review comments and should not be a reason to reject the paper. This year, ICASSP adopted the IEEE Conferences Template and, because of the change from past years, a number of authors encountered problems in strictly complying with the formatting requirements. So please disregard minor formatting issues during the review process and  focus your review comments and assessment on the technical content of the paper. Authors will be asked to format their final submitted camera-ready versions consistently.

When you suggest improvements in the writing, please be specific. If a particular passage in the text is unclear, please point it out and suggest improvements. However, if the whole paper or a major portion of it is poorly written, then say so; you are not expected to rewrite it for the authors.

If you think that the paper has merits but does not exactly match the topics of the TC, please do not simply reject the paper but articulate why in your review.

Please avoid referring to the authors by using the phrases “you” or “the authors”; instead use the phrase “the paper”.  Please do not belittle the paper or the authors, and avoid sarcastic comments. Even if you think that a paper is very weak, please still provide constructive feedback to the authors. The paper may have been written by a student or researcher who is submitting a paper for the first time. You do not want to crush their spirits.

If you notice unethical or suspect behavior, please notify the Program Committee as soon as possible.

Conflict of Interest

Please make sure that there is no obvious conflict of interest. Examples of potential conflicts of interest are the following:

• You work in the same research group as one of the authors.
• You have been involved in the work and will be credited in some way (e.g., you have hosted one of the authors in your lab, to carry out work related to the paper).
• You have formally collaborated (e.g., written a paper together, or been awarded a joint grant) with one of the authors in the past three years.
• You were the M.Sc./Ph.D. advisor (or advisee) of one of the authors, regardless of how many years ago this happened.
• You have reasons to believe that others might see a conflict of interest, even though there is none (e.g., you and one of the authors work for the same multinational corporation, although you work in different departments on different continents and have never met before).

In case you have any doubt about a potential conflict of interest, then please contact the Program Committee to determine how to proceed.

Confidentiality and Anonymity

As a reviewer, it is your responsibility to zealously protect the confidentiality of the ideas represented in the paper you review.

• Please keep all copies of the paper strictly confidential. Please do not show your assigned papers to anyone else, including colleagues or students, unless you have asked them to help with your review, in which case also make them clearly aware of the confidentiality requirements.

• Please do not use ideas from the paper to develop new ones until the paper has been made public.
• Please do not disclose your identity to the authors.
• Please do not ask the authors to cite your past work unless your work is directly relevant. Otherwise, this request is unethical.

The Program Committee thanks you for your time and efforts in upholding the scientific quality of the papers presented in ICASSP. The committee looks forward to seeing you in Hyderabad!

Sources: In drafting these guidelines, we borrowed many ideas and wordings from the following sources:

• ISMIR review guidelines (https://ismir.net/reviewer-guidelines/)
• ICASSP editorial policies (https://2024.ieeeicassp.org/editorial-policies/)
• NeurIPS reviewer guidelines (https://neurips.cc/Conferences/2023/ReviewerGuidelines