> For the complete documentation index, see [llms.txt](https://2026.istvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://2026.istvs.org/conference/call-for-papers.md).

# Call for Papers

ISTVS 2026 | October 11-15, 2026  | Pretoria, South Africa

{% hint style="danger" %}
Paper submissions are closed for the 2026 Conference!
{% endhint %}

<figure><img src="https://3752480070-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtANpeUQMKculoemLt49T%2Fuploads%2FaNyWbrL7Hhkx3RcUlHQ1%2FISTVS2026-CFP.jpg?alt=media&amp;token=c484ea1e-45e7-4035-8a54-441102b08a9e" alt=""><figcaption></figcaption></figure>

*ISTVS 2026*, the *56th Conference of the International Society for Terrain-Vehicle Systems* welcomes original and previously unpublished research and review papers describing results of research which are relevant to the conference topics and to terrain-vehicle systems.

* Interested authors are invited to submit an abstract between **16 February and 3 April, 2026 (extended deadline)**.
* Abstracts must be **under 1800 characters** and must emphasize the objectives and results.
* Authors may choose between the following two types of submissions: **full paper** or **abstract-only**.
* For either type of submission, authors can choose to do an **oral presentation** at the conference or submit a **poster** for the conference poster session. At least one of the authors must attend the conference for either.

### **Abstract review**

All abstracts will be reviewed by the conference Editorial Committee. The corresponding author will be notified of abstract acceptance by **13 April, 2026**.

### **Full paper submissions**&#x20;

{% hint style="danger" %}
Paper submissions are closed for the 2026 Conference!
{% endhint %}

After abstract acceptance, authors submitting a full paper must make their submission by **15 May, 2026**. Each full paper will be subject to peer review by the conference Scientific Committee. Each paper will be either accepted, accepted with revisions or rejected; authors will be notified by **1 July, 2026**. If a revision is requested, the revised paper must be submitted by **2 August, 2026**.

All accepted submissions of either abstract-only or full-paper type will be included in the conference program and will be published in the conference proceedings, on the condition that **at least one author attend the conference** to present the work. **Only full papers** will be assigned a **DOI** and will have a permanent individual page on the conference website.

### Key dates

Key dates are listed [here](/schedule.md#key-dates).

### Technical tracks

The conference includes the following thematic tracks:

* Innovative concepts in tires, wheels, tracks, and other ground contact elements
* Propulsion systems and vehicle electrification
* Creative terrain mechanical characterization and deformation modeling
* Advances in off-road mobility modeling
* Off-road autonomy, robotics and navigation
* Planetary terramechanics
* New instrumentation and analysis methods in terramechanics testing
* Climate impacts on terrain, terramechanics, and off-road vehicles
* Off-road vehicle dynamics and control, including advanced driver assist and collision prevention systems
* International collaborations

### Submission platform

As in previous years, the conference submission platform is **EasyChair**. If you’ve participated in a recent ISTVS conference or have used EasyChair in the past, you will be able to log in with your existing account. If you’re new to ISTVS conferences, use the *Create an account* link on the login page below to get started.

Access the ISTVS 2026 EasyChair site here: <https://easychair.org/my/conference?conf=istvs2026>

### Submission guidelines

* Make sure that the authors you list in the **EasyChair** form are **the same** as in your full paper and/or poster, and in the **same order**.
* Ensure the authors’ affiliations match across **all** submissions and forms.
* If at any time you need to make changes to the list of authors, please **promptly notify the conference organizers**.
* If the same authors appear in **multiple submissions**, please write the authors' **names** and **affiliations** in the **same way**, for **all submissions** (both in EasyChair and in the papers/posters).
* If the Latin alphabet is not your native alphabet, please make sure that you use the **same transliteration** for your name across all submissions.
* If at any time you wish to **change your submission type** (abstract-only vs full paper) or **change your presentation type** (oral presentation vs poster session), please **promptly notify the conference organizers**.

### Templates for submissions

#### Abstract

**No template** is required to submit your abstract. Submission is done directly on the [EasyChair submission platform](https://easychair.org/my/conference?conf=istvs2026).

#### Full paper <a href="#full-paper" id="full-paper"></a>

Papers must be submitted in *Microsoft Word* format and must **comply with the conference template**.

{% file src="/files/N89YgQCKmOLGWHQ2QcoS" %}

The zip archive provided includes a **reference PDF**, in case the *Word* document breaks when opened locally.

#### Presentation <a href="#presentation" id="presentation"></a>

**Presentation time: 20 minutes total**

* **15 minutes** for the presentation
* **5 minutes** for questions

You may use your own presentation template. Please follow these formatting guidelines:

* Use a **widescreen layout**.
* Include **slide numbers**.
* Use a **clean, clear layout** that will be easy to read in a large auditorium.
* Ensure that text, figures and other content are **large enough to be clearly visible from a distance**.
* Where possible, maintain **visual consistency** throughout the presentation.

#### Poster <a href="#poster" id="poster"></a>

You may use your own poster template. Please follow these requirements:

* **Maximum size:** A1, **594 × 841 mm** (23.4 × 33.1 inches)
* **Orientation:** Portrait or landscape
* Use a **clean, clear layout** that is easy to read.

The poster **shall not exceed A1 size**.

#### Final Paper Submission Requirements

For your paper to be included in the **Conference Proceedings**, please complete the following requirements.

**1. Submit the copyright form**

ISTVS must receive a **completed and signed copyright assignment form**.

* **Deadline:** Before **29 September 2026**
* **Submit by email to:** <Schalk.els@up.ac.za>
* The form applies to original material submitted to conferences of the International Society for Terrain-Vehicle Systems (ISTVS) and is required for publication by ISTVS.

**2. Submit your final paper via EasyChair**

Please submit the final version of your paper, revised to address the reviewers' comments, via **EasyChair**.

Both file formats are required:

* **Word**
* **PDF**

**3. Update your abstract, if required**

If your abstract has changed, please update the abstract in **EasyChair**.

The abstract entered in EasyChair, rather than the version included in the final paper, will be used in the **conference programme**.

**4. Note the ISTVS no-show policy**

ISTVS has a **no-show policy**. Only papers that are **presented in person at the conference by one of the paper's authors** will be included in the final Conference Proceedings.

{% file src="/files/Y64HDjbOpoDAM9RwmCtl" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://2026.istvs.org/conference/call-for-papers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
