Congirus · Scientific event management platform
The congress secretariat in one panel
From the call for abstracts to the attendance certificate, the processes of a congress run in one system. The event’s own website is built from the same panel. The secretariat can devote more of its time to the scientific content of the event.
The starting point
In event management, much of the work is not visible from outside
What participants see of a congress is the programme. Behind it lies a considerable amount of work: collecting hundreds of submissions, assigning each to a suitable reviewer, following up on reviewer delays, preparing acceptance and rejection letters, collecting registration fees, matching bank receipts, resolving session clashes, printing badges and recording attendance at the door.
When most of this is handled through email and spreadsheets, the secretariat spends a large share of its time on follow-up rather than on scientific content, and individual items are easily overlooked.
Congirus brings this chain into one system. Which submission is at which stage, who has been waiting for how long, and which payment is outstanding are visible in a single list.
Who it is for
Intended institutions
Universities and faculties that organise congresses, symposia, conferences and workshops. Learned societies and scientific communities. Professional bodies and chambers. Research centres and the event units of public institutions.
The platform is suitable for a single event as well as for institutions that organise several events a year. The institutional account is permanent: each new congress is opened under the same account, and the archive of previous events is retained.
Scope
What the system covers
One institutional account · one audit trail.
| Module | Scope |
|---|---|
| Institution and event core | Several events under one institutional account; teams and roles per event. |
| Abstract management | Abstract and full-text collection, author details and file flow. |
| Form designer | Submission and review forms are designed from the panel. |
| Review workflow | A reviewer process configured per event; deadline tracking and reminders. |
| Programme and calendar | Programme building, clash warnings, calendar and programme-book output. |
| Registration and fees | Attendance with or without a paper, capacity-limited sessions, fee collection. |
| Documents and certificates | Attendance certificate, acceptance letter, invitation letter and badge; public verification. |
| Book production | Abstract and full-text books from accepted submissions. |
| Check-in and attendance | Attendance recorded at the room door; certificates are based on that record. |
| Event website | The event’s own site is built and published from the same panel. |
| Reporting and audit | Submission, review, payment and attendance metrics; audit record. |
Module details and current features are published on the product site: congirus.com
Operation
How it is operated and what it protects
- Cloud platform
- Congirus is operated as a cloud platform. The institution opens its own account and manages its events under it. Installation, updates, backups and monitoring are handled by us, so the institution does not need to administer servers. Subscription and plan management is available from the institution’s panel.
- Responsibility for participant data
- An event system holds the identity, contact and payment details of many people. The system obtains the participant’s consent at registration and keeps a record of it. Access is permission-based, so team members see only the areas they are authorised for. Personal data is processed under KVKK in Türkiye and the GDPR in Europe.
- International events
- Multilingual operation is supported at both system and content level. Event name, venue details and site content can be defined in several languages; participants submit in their own language and receive notifications in it.
- When to start
- A new congress can be set up within a short time. The form structure, the reviewer pool and the review rules should however be settled before the call for abstracts is published; starting a few weeks ahead of the call date is usually sufficient. Data from previous congresses can be migrated, and the archive is retained.
Tell us about your congress
A demo call follows your own event workflow. The expected number of submissions, the number of reviewers you work with and your fee structure are the starting points for showing how the system handles the work.