AI Conference Deadlines

---

🙏 We Need Your Help

This project thrives on community contributions. The world of academic conferences is always changing, and it's tough for one person to keep up.

If you notice a conference is missing, a deadline is incorrect, or you have more accurate information for an estimated date, you have the power to fix it! Your contribution will help thousands of researchers and students around the world.

How to Contribute

Contributing is simple! All the conference data is stored in human-readable .yaml files. You don't need to be a programmer to help out.

Find or Create the Conference File

All conference data is located in the conferences/ directory.

• To update an existing conference series: Find the corresponding file (e.g., for AAAI, open aaai.yaml).
• To add a new conference series: Create a new file named after the conference's common acronym (e.g., emnlp.yaml).

Add or Edit the Conference Data

Inside the file, you can either edit an existing entry or add a new one for a future year. Each conference year is a separate entry, starting with a unique key (like aaai2025:).

Here is an example entry for a single conference:

aaai2025:
  conferenceEndDate: "2025-03-04"
  conferenceStartDate: "2025-02-25"
  dataSrc: manual
  id: aaai2025
  isApproximateDeadline: false
  location: Pennsylvania Convention Center, Philadelphia, USA
  shortname: AAAI 2025
  tags:
    - DM
    - ML
    - NLP
    - CV
  timeline:
    - abstractDeadline: "2024-08-08T11:59:59Z"
      deadline: "2024-08-16T11:59:59Z"
  timezone: UTC-12 # The original timezone of the deadline, e.g., "AoE" which is UTC-12
  title: AAAI Conference on Artificial Intelligence
  website: https://aaai.org/conference/aaai/aaai-25/

Understanding the Data Fields

When adding or editing a conference, please refer to the table below. Date formats are flexible and will be automatically converted to YYYY-MM-DDTHH:MM:SSZ by the dateparser package.

Field	Description	Example
id	Required. A unique identifier in [a-z]+\d\d\d\d format (lowercase shortname + year).	aaai2025
shortname	Required. The common name or acronym for the conference.	AAAI 2025
timeline	This is where all deadlines for a conference go. It is a list where each element has to have the deadline entry and may have the abstractDeadline and note fields.
deadline	Required. This is part of the timeline list and represents a paper submission deadline. It may be one of multiple deadlines. Can be various formats, but UTC is preferred.	'2024-08-16T11:59:59Z'
timezone	(Optional) The timezone of the deadline and abstract deadline.
conferenceStartDate	Required. The first day of the conference.	'2025-02-25'
conferenceEndDate	Required. The last day of the conference.	'2025-03-04'
dataSrc	Required. The source of the information. For manual additions from a conference website, use off-website. For other manual entries, use manual.	off-website
title	(Optional) The full official title of the conference.	AAAI Conference on Artificial Intelligence
abstractDeadline	(Optional) This may be part of an entry in the timeline list. It represents abstract submission deadline for one paper deadline.	'2024-08-08T11:59:59Z'
location	(Optional) The city and country of the conference venue.	Philadelphia, USA
website	(Optional) A link to the official conference website for that year.	https://aaai.org/conference/aaai/aaai-25/
tags	(Optional) A YAML list of relevant research areas.	- ML - NLP
note	(Optional) This may be part of an entry in the timeline list. It's short text for additional details, like submission rounds.	Round 1
isApproximateDeadline	Should always be false for user contributions. The system sets this automatically for future estimated dates.	false
h5Index	Don't set this one. It will be automatically set from the rank/h5index.yaml file. You may however update that file :)
rating	Don't set this one. It will be automatically updated from the CORE conference rank once a day.
acceptanceRate	Don't set this one. Main-track acceptance rate in percent, pulled every ~30h from openaccept.org's metadata repo (CC BY-SA 4.0), together with acceptanceRateYear, acceptedPapers and submittedPapers.

✏️ Easy In-Browser Pull Request (No Git Required!)

Don't want to use the command line? No problem! You can edit files and create a Pull Request entirely through the GitHub website.

1. Navigate to the file: Go to the conferences/ directory. Click on the .yaml file you wish to change (e.g., iclr.yaml).

2. Click the Edit icon: In the top-right corner of the file view, click the pencil icon (✏️).

3. Make your changes: The file will open in a text editor right in your browser. Add or update the conference information according to the guidelines in the table above.

4. Propose your changes: Once you're done, scroll to the bottom of the page. You'll see a section called "Propose changes".

   • In the first text box, write a short, clear title for your change (e.g., Update AAAI 2026 website link).
   • Click the green "Propose changes" button.

5. Create the Pull Request: You will be taken to a new page. All you need to do here is click the green "Create pull request" button.

And that's it! 🎉 You've successfully submitted a contribution. We will be notified and can review your changes. Thank you for helping keep the list accurate for everyone!

---

How the "Deadline to watch" is chosen

The website's hero highlights a single Deadline to watch. This is not simply the next deadline on the calendar — a minor workshop due tomorrow usually matters less than a top-tier conference due in a few weeks. Instead, every confirmed upcoming deadline is scored by importance × urgency, and the highest score wins:

score = importance × exp(−days_until_deadline / 30)

importance = RATING_WEIGHT[rating] + h5Index / 120
RATING_WEIGHT = { "A*": 8, "A": 5, "B": 3, "C": 1, "D": 0.5 }   // unrated ≈ C (1)

• Importance rewards prestige. The CORE rating is the main signal; the Google Scholar h5Index is a gentle nudge on top, so strongly-cited (or unrated-but-notable) venues aren't overlooked.
• Urgency is the exp(−days / 30) term: a smooth decay that approaches 1 for an imminent deadline and shrinks as the deadline moves further out. The 30 is a "patience" constant (WATCH_TAU_DAYS in aideadlines/scripts.js) — larger values look further ahead for prestige; smaller values favor whatever is soonest.

Only confirmed deadlines are eligible. Estimated/approximate entries (isApproximateDeadline: true) are excluded, because their dates are only accurate to the month and a live ticking countdown would be misleading.

Worked example

Given four upcoming conferences, the scores work out like this:

Conference	Rating	h5	Days away	importance	exp(−days/30)	score
AAAI 2027	A*	232	29	9.93	0.38	3.78 ✅
ICTAI 2026	B	–	2	3.00	0.94	2.81
ACCV 2026	B	52	7	3.43	0.79	2.72
CHI 2027	A*	–	74	8.00	0.09	0.68

AAAI wins even though ICTAI is due far sooner: the A* rating and high h5-index outweigh ICTAI's head start. But the margin is small (3.78 vs 2.81) — if no A*/A deadline were within reach, the imminent B-rated ICTAI would take the spot. And CHI, despite being A*, scores low because it's still 74 days out.

Rule of thumb: an imminent deadline wins once it's close enough, but a clearly more important conference can "jump the queue" if it's within roughly two months.