In Confy’s Initial Setup stage, responsibilities of Program Committee Chairs include:
– Creating all Tracks
– Appointing Track Chairs (one per Track)
– Writing the conference Scope
– Setting the Review Model (single blind or double blind)
– Defining the length of all possible Paper Types (the default setting is 10-20 pages for regular paper and 6-9 pages for short paper)
– Moving the stage to Paper Submission once all of the above have been completed

It is important to note that for every Technical or non-Technical Track you create, you should create an Invited Track version of that Track with the same title, and appoint the same Track Chair to it.

Technical Tracks are dedicated to main paper submission. Any number of Technical Tracks is allowed per conference. If there is more than on Technical Track in a conference, all Technical Tracks share the following properties:
– Deadlines
– Paper Types
– Review Model

For that reason, all Technical Tracks move through stages in Confy simultaneously. Changing the conference stage therefore affects all Technical Tracks, while non-Technical Tracks remain unaffected.

Non-Technical Tracks include:
– Workshop Tracks
– Demo Tracks
– Poster Tracks
– Invited Tracks
– Other Tracks

These Tracks are managed independently of Technical Tracks by their respective Track Chairs.

Each non-Technical Track can follow its own Deadlines, Paper Types and Review Model after consultation with the General Chairs, Program Committee Chairs, and the Conference Manager.

Workshop Track is a type of non-Technical Track typically dedicated to a Workshop. Any number of Workshop Tracks is allowed per conference.

answer

Demo Track is a type of non-Technical Track typically dedicated to Demos. Only one Demo Track is allowed per conference.

answer

Poster Track is a type of non-Technical Track typically dedicated to Posters. Only one Poster Track is allowed per conference.

answer

Invited Track is a type of non-Technical Track typically dedicated to Invited Papers. An Invited Track will only be visible to external user who receive its specific link.

Please make sure that you create a shadow track for every Track (Technical and non-Technical). A shadow track should have the same name as its parent track. When creating an Invited Track, please make sure to select the “Invited Track” type from the drop-down list in the Create Tracks interface, and that you tick an “Invited Authors Only” box underneath.

The Track Chair appointed to a shadow track should be the same as in its parent track. This way, all Track Chairs will have a convenient way of organizing Invited Sessions in their tracks to create a more compelling program, elevating the entire conference.

Papers submitted to an Invited Track are automatically in a fast track, requiring a single review. Since Invited Tracks are non-Technical Tracks, they do not need to comply with Deadlines and Properties of Technical Tracks.

In Confy, these Chairs should be invited as Track Chairs of their respective Tracks. For example, Demo Chair should be invited as the Track Chair of the Demo Track, the Chair of a Workshop should be invited as a Track Chair of that Workshop’s Track, etc.

As Track Chairs of non-Technical Tracks, they will be responsible for their track’s Initial Setup (Deadlines, Review Model, Paper Length), appointing Program Committee Members, performing Submission Verification, overseeing Paper Assignment and Review Management, making Final Decision, sending Notification, and moving all Track Stages.

Any number of Technical Tracks is allowed per conference. It is recommended to consider whether the scope of a conference is broad enough to warrant several specialized Technical Tracks, or narrow enough to warrant a single Technical Track.
Any number of Workshop Tracks is allowed per conference.
Only one Demo Track is allowed per conference.
Only one Poster Track is allowed per conference.
Only one Invited Track is allowed per conference.

*All* Tracks – Technical and non-Technical, should be created by Program Committee Chairs.
Paper Types and Review Model of all Technical tracks should be set up by Program Committee Chairs.
Track Chairs of all Tracks – Technical and non-Technical – should be appointed by Program Committee Chairs.
Deadlines, Paper Types and Review Model of non-Technical Tracks should be set up by their respective Track Chairs.
Stages of Technical Tracks are moved by Program Committee Chairs.
Stages of non-Technical Tracks are moved by their respective Track Chairs.

If there is a single Technical Track, the role of a Track Chair is typically filled by the Program Committee Chair. In this case, it is required that Program Committee Chair appoints themselves the role of a Track Chair.

Submission in Technical Tracks opens by moving conference into Paper Submission stage in Confy. This is possible only after all items in the Initial Setup have been completed by the General Chair and Program Committee Chair. Moving the conference stage is the responsibility of Program Committee Chairs.

In order to provide fair conditions to all submitting authors, creation of Late Tracks to supplement main paper submission after the submission deadline is not permitted.

answer

To ensure a quick response, please be as specific as possible in the description of the error or a bug you have encountered, including your precise flow of actions and information about your web browser.