Short Contributions

Important Dates

All Deadlines 11:59pm AoE

About Short Contributions

The ACM/IEEE International Conference on Human-Robot Interaction is a premier, highly-selective venue presenting the latest advances in Human-Robot Interaction. The conference theme for HRI 2027 is “Innovative HRI”. This year’s HRI conference will feature three types of short contributions (4 pages, excluding references) focused on datasets, code, and replication studies. These short contributions aim to:

1. Advance the sharing and reuse of scientific data and code.
2. Promote wider sharing, reuse, and replication of existing scientific work.
3. Provide additional credit and recognition to authors involved in the production, sharing, and reuse of datasets, code, open science, and replication.

Similar to the HRI Full papers, HRI Short Contributions will be fully and rigorously reviewed, and will be archived in the ACM Digital Library. Accepted submissions are expected to be presented in-person at the conference. All accepted papers will be presented as a poster at minimum, while exceptional or unique papers may be given a short presentation slot.

Submission Categories

To facilitate quality reviewing, and to inform reviewer selection, authors will be required to select a submission category for their short contribution. These categories are:

1. Data
2. Code
3. Replication

Review Process

Submissions should be in a double-blind format. Reviewers will assess submissions based on the criteria associated with each type of submission (accessibility, completeness, utility, and relevance).

When making your submission, please note that all authors will be required to review at least one submission as well as to provide a list of three recommended potential reviewers.

For code and data submissions, please also attach your anonymized code / data as a zip file and submit as supplementary material. The deadlines for the supplementary material is the same as the paper deadlines.

Anonymization Guidelines

When anonymizing your code or data, make sure to carefully check that your licenses, documentation, readme, code / data comments etc. do not contain any identifiable information. Papers will be desk-rejected if anonymization rules are violated. Check the general anonymization guidelines for more in-detail information.

Some codebases may already exist in repositories such as Github etc. For those cases, here are some helpful tools to easily anonymize your existing code or data:

• Anonymous GitHub (view-only link): anonymous.4open.science.
• OSF (view-only link): Create a view-only link for a project.
• Dataverse (private URL): Private URL to review unpublished dataset.
• Zenodo and figshare: disclose-data-dbr-first-then-opendata.

ACM Open Access Publishing

All ACM publications, including those from ACM-sponsored conferences, are now 100% Open Access. Authors have two primary options for publishing Open Access articles with ACM: the ACM Open institutional model or by paying Article Processing Charges (APCs). With ~3,000 institutions already part of ACM Open, the majority of ACM-sponsored conference papers will not require APCs from authors or conferences (currently, around 76% of papers).

Authors from institutions not participating in ACM Open will need to pay an APC to publish their papers, unless they qualify for a financial or discretionary waiver. To find out whether an APC applies to your article, please consult the list of participating institutions in ACM Open and review the APC Waivers and Discounts Policy. Please keep in mind that waivers are rare and are granted based on specific criteria set by ACM.

To support authors and institutions as they continue to adapt to ACM’s Open Access publishing model, the ACM Council has approved subsidized APC rates for calendar year 2027, allowing more time for institutions to join ACM Open. The subsidy will offer:

• $500 APC for ACM/SIG members
• $750 for non-members

This represents a 29% discount off current APC list pricing, funded directly by ACM. Authors are encouraged to help advocate for their institutions to join ACM Open during this transition period. This temporary subsidized pricing will apply to all conferences scheduled for 2027.

SIGCHI is able to provide APC assistance to ACM Members who are not affiliated with Open Access institutions. See this link for information about how to apply for a hardship waiver for APC charges.

New ACM Publication Policies

By submitting your article to an ACM Publication, you are hereby acknowledging that you and your co-authors are subject to all ACM Publications Policies, including ACM’s new Publications Policy on Research Involving Human Participants and Subjects. Alleged violations of this policy or any ACM Publications Policy will be investigated by ACM and may result in a full retraction of your paper, in addition to other potential penalties, as per ACM Publications Policy.

Accessibility

Make sure to read and follow the accessibility requirements at the HRI 2027 accessibility page. If you have questions or need assistance, please contact the conference accessibility & diversity chairs: diversityaccessibility2027@humanrobotinteraction.org.

Data Submissions

Data submissions are short papers that provide access to and detailed descriptions of research data that is of value to the HRI community. These submissions may include both qualitative and quantitative data collected in HRI settings. Data that has already been published as a part of a previous publication may not be included.

During initial submission, data should be submitted as a supplementary zip file. If the dataset is too large, a representative sample should be submitted.

During final camera-ready submission, regardless of the type of data published, all datasets should be freely and publicly available via a digital repository. Appropriate repositories must be:

• Supported by and recognized within the HRI community.
• Provide permanent identifiers for submitted databases (e.g., accession numbers, DOIs).
• Provide metadata and other documentation to support the use and reuse of data in a given archive.
• Implement or be working toward implementing the FAIR principles of datasets and associated documentation.
• Allow access to data without unnecessary restrictions or, when necessary restrictions are in place, provide clear criteria for access and timely mechanisms of access.

Recommended databases that meet this criteria include: Zenodo (preferred), Dataverse, Dryad, Figshare, Mendeley Data, and Science Data Bank.

Submissions will be assessed by reviewers on the basis of completeness, utility, and relevance.

1. Completeness: Successful submissions should include a clear licensing and maintenance plan. Recommended licenses are visible here. Sufficient detail must be provided on how the data was collected and organized, what kind of information it contains, how it should be used ethically and responsibly, as well as how it will be made available and maintained. Where applicable, established best practices on reproducibility should be cited and conformed to. For cases where questionnaires were used, individual questionnaire items and scoring should be provided.
2. Utility and relevance: Data submissions should highlight how the dataset in question has the potential to influence future work or practice in the HRI domain.

We encourage dataset submissions to outline the steps required to reproduce their data both in the collection, post-processing, and usage stages of the data creation process. This should include reference code where possible.

For eligible data submissions, it is recommended that you provide some form of data visualization illustrating aspects of importance or note related to the submitted dataset.

Given the variety of possible dataset submissions, a single format for submissions that encompasses all possible submissions is not feasible, but authors should use the recommended template for HRI submissions as outlined on the conference website and accessible here (“sigconf”, double column format). The Overleaf template is here.

Recommended structure for data submissions

For authors new to data submissions or seeking additional guidance, the sections and structure below is advised, but not required:

• Title (recommended length 110 characters or fewer).
• Abstract (maximum 170 words).
• Study Overview: This section provides an overview of the study generating the data and its potential use. It should also include a brief summary of previous publications utilizing the data where applicable.
• Methods: The Methods section describes the steps taken to produce the data, including the experimental design used, data acquisition, and computational processing where implemented. It may also cover questionnaire details and their deployment, citing existing works and providing items where applicable.
• Dataset: This section explains the dataset associated with the work, including data maintenance, and a detailed overview of file formats. It includes links to supplemental documentation.
• Usage Notes: This section provides instructions for researchers using the data, addressing ethical considerations and responsible use guidelines where applicable. It highlights the data’s utility and relevance to the HRI community, along with a summary of more detailed documentation.
• References.

In specific cases (e.g. datasets with privacy-sensitive data), a complete dataset might not be directly downloadable. In this case, the authors must outline in their submission reasonable steps for other researchers to access any aspects of the data that cannot be made openly available (e.g. asking for specific ethical approval).

Relation to existing HRI themes

Data submissions can be submitted to the HRI Technical Advances track already. However, this track has a narrower focus, offering an avenue to present and publish datasets that would be useful/important to the community as standalone contributions.

Sample Data Papers

• Parag Khanna, Andreas Naoum, Elmira Yadollahi, Mårten Björkman, and Christian Smith. 2025. REFLEX Dataset: A Multimodal Dataset of Human Reactions to Robot Failures and Explanations. In Proceedings of the 2025 ACM/IEEE International Conference on Human-Robot Interaction (HRI ’25). IEEE Press, 1032–1036.
• Matthias Rehm, Kasper Hald, and Ioannis Pontikis. 2024. Benchmark Movement Data Set for Trust Assessment in Human Robot Collaboration. In Proceedings of the 2024 ACM/IEEE International Conference on Human-Robot Interaction (HRI ’24). Association for Computing Machinery, New York, NY, USA, 934–938. https://doi.org/10.1145/3610977.3637472

Code Submissions

Code submissions are short papers that provide access to and detailed descriptions of different code, tools, and software that is of value to the HRI community. These submissions may include software, analysis code, and other digital tools of use to the HRI community. Code that has already been published as a part of a previous publication may not be included.

During initial submission, code should be submitted as a supplementary zip file.

During final camera-ready submission, regardless of the type of code published, all code submissions should be made freely and publicly available via a digital repository at the time of submission. Appropriate repositories must be:

• Supported by and recognized within the HRI community.
• Provide metadata and other documentation to support the use, reuse, and potential modification of code in a given repository.
• Ensure long term preservation of code and associated documentation.
• Allow access to the code without unnecessary restrictions or, when necessary restrictions are in place, provide clear criteria for access and timely mechanisms of access.

Recommended databases that meet this criteria include: Github (preferred), Zenodo (preferred), Dataverse, Dryad, Figshare, Mendeley Data, and Science Data Bank.

Within these repositories the following must be present:

• Compiled standalone software and/or source code.
• A clear open-source license for the code or software submitted.
• A small – simulated or real – dataset to demo the software/code (where applicable).
• A readme file that contains:
  1. System requirements: all software dependencies and operating systems (including version numbers); versions the software has been tested on; any required non-standard hardware (including specific makes and models for robotic platforms).
  2. Installation guide: instructions on how to install the software or run the code.
  3. Demo: instructions for the demo or demo video of the code; expected output (where appropriate).
  4. Instructions for use: how to run the software or code.

We strongly recommend that you ask colleagues that are not familiar with the code or software to test it prior to submission.

Compatibility with at least one common and accessible hardware-software platform is required. The platform must be in common use by the HRI community (e.g., software platforms such as Ubuntu and ROS versions, Windows 10/11, macOS versions, etc., languages such as Python, C++, MATLAB, R etc.). If reviewers cannot run your software/code (either due to lack of clear instructions or using outdated software) then it cannot be assessed along the required criteria and may be rejected.

Software manuscripts will not be considered under the following circumstances:

• They require access to databases or other resources whose persistence is not guaranteed (e.g., individual laboratory databases without funding support).
• Running the software depends on proprietary or otherwise unobtainable ancillary software or hardware.

Submissions will be assessed by reviewers on the basis of completeness, utility, and relevance.

1. Completeness: Successful submissions should include a clear licensing and maintenance plan. Recommended licenses are visible here. Sufficient detail must be provided on how the submitted code can be used both ethically and responsibly to further HRI research. Furthermore, submissions should also highlight how the submitted code will be made available and maintained. Where applicable, established best practices regarding documentation and origination of the code and repositories should be cited and conformed to.
2. Utility and relevance: Code submissions should highlight how the code in question has the potential to influence future work or practice in the HRI domain.

Given the variety of possible code submissions, a single format for submissions that encompasses all possible submissions is not feasible, but authors should use the recommended template for HRI submissions as outlined on the conference website and accessible here (“sigconf”, double column format). The Overleaf template is here.

Recommended structure for code submissions

For authors new to code submissions or seeking additional guidance, the sections and structure below is advised but not required:

• Title (recommended length 110 characters or fewer).
• Abstract (maximum 170 words).
• Background & Summary: This section provides an overview of the code or software and its potential use in the HRI community. It cites previous publications that utilized the code or software where applicable and summarizes this use where applicable.
• Purpose: This section describes the key operations performed by the software or code. It explains the fundamental task(s) it accomplishes and the general approach used to address a given problem or objective.
• Characteristics: This section describes the key characteristics of the software or code, including details of algorithms used, installation and usage instructions, and software dependencies where applicable. It also comments on whether the source code has been submitted for community input and provides links to the commenting site if so.
• Code/Software: This section explains the code or software associated with the work, including the code maintenance, and a detailed overview of files and formats. It includes links to supplemental documentation.
• Usage Notes: This section provides instructions and guidance for researchers using or modifying the software/code. It addresses ethical considerations and responsible use guidelines. It includes a summary of more detailed documentation associated with the code/software and highlights its utility and relevance to the HRI community.
• References.

Relation to existing HRI themes

Code submissions can be submitted to the HRI Technical Advances or Systems tracks as supplementary material to an existing paper. However, this track has a narrower focus, offering an avenue to present and publish code repositories that would be useful/important to the community as standalone contributions.

Sample Code Papers

• Jialong Li, Zhenguo Wang, Tianci Wang, Maj Stenmark, and Volker Krueger. 2026. Quest2ROS2: A ROS 2 Framework for Bi-manual VR Teleoperation. In Proceedings of the 21st ACM/IEEE International Conference on Human-Robot Interaction (HRI ’26). Association for Computing Machinery, New York, NY, USA, 1288–1292. https://doi.org/10.1145/3757279.3788806
• David Porfirio, Mark Roberts, and Laura M. Hiatt. 2025. An Interaction Specification Language for Robot Application Development. In Proceedings of the 2025 ACM/IEEE International Conference on Human-Robot Interaction (HRI’25). IEEE Press, 1062–1066. dl.acm.org/doi/10.5555/3721488.3721622
• Varad Dhat, Nick Walker, and Maya Cakmak. 2024. Using 3D Mice to Control Robot Manipulators. In Proceedings of the 2024 ACM/IEEE International Conference on Human-Robot Interaction (HRI ’24). Association for Computing Machinery, New York, NY, USA, 896–900. https://doi.org/10.1145/3610977.3637486

Replication Studies

Replication studies report on reproducing previous published results, positive or negative. The authors should provide a clear and detailed description of the methods for another researcher to closely replicate the experimental procedures and results. The authors should use the HRI paper template but adapt the sections to clearly outline the following:

• What is the scope of reproducibility of the paper?
• What were the methods?
• What were the results?
• Were you successful in reproducing the results? If not, what could be the plausible reasons?
• What was easy to replicate?
• What was difficult / unclear where the authors may have made some assumptions?
• Was there any attempt to contact the authors of the original submission that is being replicated?

Reviewers of these submissions will be asked to focus on the level of clarity and details on the above mentioned criteria and prioritize scientific rigor and importance of the replicated study/results to HRI as a field.

Authors should use the recommended template for HRI submissions as outlined on the conference website and accessible here (“sigconf”, double column format). An Overleaf link is here.

Relation to Full Paper HRI themes

Replication studies which significantly expand on the original research (e.g., add a new condition) and warrant a full-length paper should instead be submitted as a regular full paper.

Sample Replication Papers

• Antara Shah and Naomi T. Fitter. 2026. Seeing Eye to Eye Again: In-the-Wild Replication Study with an Expressive Eye Display for the Stretch Mobile Manipulator. In Proceedings of the 21st ACM/IEEE International Conference on Human-Robot Interaction (HRI ’26). Association for Computing Machinery, New York, NY, USA, 1273–1277. https://doi.org/10.1145/3757279.3788803
• Strait et al., A Three-Site Reproduction of the Joint Simon Effect with the NAO Robot, HRI 2020
• Pereira et al., Effects of Different Interaction Contexts when Evaluating Gaze Models in HRI, HRI 2020