Call for Papers
Menu
Call for Papers

Paper Submission Instructions

Formatting, length, anonymity and policy requirements for submitting a paper to ISPASS 2027.

Requirements

Please make sure that your submission satisfies all of the following.

  • An abstract is required. You will not be able to submit a full paper without first registering an abstract by the abstract deadline.
  • The paper must be original material that has not been previously published in another conference or journal, and is not currently under review elsewhere. Material presented previously at a workshop without copyrighted proceedings may be submitted.
  • The content of the submission is limited to nine (9) single-spaced, double-column pages using 10-point type on 8.5×11 inch pages (IEEE conference style), with an unlimited number of additional pages for references. All content other than references — figures, appendices and so on — must fit within the first nine pages. Papers that exceed the length limit or deviate from the formatting requirements may be rejected without review.
  • References must list all authors.
  • Papers are reviewed double-blind. Author names and other hints of identity must be removed from the submitted paper.
  • Do not omit references in order to preserve anonymity — that leaves reviewers unable to grasp the context. Cite your own work in the third person, as you would cite anyone else’s.
  • Please number the pages of the submission.
  • The paper must be submitted as a PDF. No other format can be accepted, and the document must print exactly as received.

For tool and benchmark papers, tick the tool/benchmark box in the paper topics. Do not include a URL to the tool or benchmark if it would reveal your identity; state instead that you intend to open-source it on acceptance.

Templates

Use the IEEE conference style templates for Word and LaTeX provided by IEEE eXpress Conference Publishing:

IEEE conference templates

Policy on arXiv posting

You may submit a paper already posted to arXiv, or post your paper to arXiv after submitting it. The submission system allows you to record the arXiv link.

  • If you post to arXiv after submitting, notify the Program Chair.
  • We recommend using different titles for the different versions of the paper.
  • We expect authors to refrain from advertising the work on social media during the evaluation period.

Policy on the use of generative AI

Generative AI tools may assist with editing and language polishing without disclosure. Any substantial use, for example to generate text, code, data, figures or citations, must be disclosed in the paper’s acknowledgments.

Generative AI tools may not be listed as an author of an ISPASS submission. Authors remain fully responsible for the accuracy and originality of all content, including verifying that AI-assisted text does not fabricate or misrepresent results, data or citations.

Conflicts of interest

A conflict of interest exists with:

  • Your PhD advisor(s), postdoctoral advisor(s), PhD students and postdoctoral advisees, in perpetuity.
  • Family relations by blood or marriage, in perpetuity.
  • People with whom you have collaborated in the past four years: co-authors on accepted, rejected or pending papers, co-PIs on accepted, rejected or pending grants, those who fund your research, and researchers whom you fund.
  • People at your current institution, at an institution where you were in the past four years, or at an institution with which you are actively discussing employment.
  • Co-PIs within the same umbrella-funded research structure who participate regularly in non-public meetings where unpublished work is discussed.
  • Anyone else with whom you believe a conflict exists. If the reason is not listed above, please contact the Program Chair.

The following are not, by themselves, conflicts of interest:

  • Service collaborations, such as writing a report, serving together on a program committee, or co-presenting a tutorial.
  • Co-authorship of a survey, compendium, tool or artifact to which multiple authors contributed without an actual project collaboration. For example, authors who each contributed different modules to an open-source framework are not in conflict with one another.

Undeclared conflicts, or conflicts falsely declared to influence reviewer assignment, may result in rejection of the paper.