What a conflict of interest is
A conflict of interest is a reason why a reviewer must not rate an abstract. The reviewer may be one of its authors, or work at the same institution as the authors, or know them in a way that makes a fair rating impossible. Scientific societies have rules on this, and the people who submit expect them to be followed.
run.events finds most of these cases by itself, lets reviewers declare the others, and keeps the reviewer away from the abstract while the conflict stands.
The kinds of conflict
run.events knows four kinds:
- One of the session's people: the reviewer is an author of the abstract. run.events always finds this, on every event, and nobody can set it aside.
- Same affiliation: the reviewer and an author of the abstract work at the same institution. This kind arises only when the event has switched on Use affiliations and Raise conflicts of interest from affiliations (see ORCID iDs and Affiliations).
- Same organisation (AI check): Amal, the AI assistant of run.events, found that the reviewer's institution and an author's institution are the same, although they are written in different ways.
- Declared: the reviewer declared the conflict themselves, with I have a conflict.
What a conflict does
While a conflict stands:
- the abstract disappears from that reviewer's view, and they cannot rate it;
- a review the reviewer gave earlier stops counting towards the score;
- automatic assignment skips that reviewer for that abstract;
- assigning that reviewer by hand asks you for a note explaining why.
How institutions are compared
For Same affiliation, run.events compares each reviewer's institutions with the institutions of the people of each abstract. It takes the reviewer's institutions from the card Content Team, where you fill in Affiliations for each reviewer. A reviewer without affiliations there is compared by the company in their profile. On the authors' side, it takes the affiliations given on the session and the company in each person's profile.
Before comparing, run.events tidies the names: it ignores upper and lower case, accents, punctuation and a legal form at the end, such as GmbH or Ltd. It does not expand abbreviations. "University Hospital Nordstadt" and "university hospital nordstadt" match; "Univ. Hospital Nordstadt" and "University Hospital Nordstadt" do not. That is what the check with Amal is for.
Where you see all conflicts
Under Configure on the Content And Speakers page, the card Conflicts of interest lists every conflict, with the reviewer, the session and the kind. The Review dashboard counts them by kind.
Check with Amal asks Amal to compare institution names that are written in different ways. Each match it finds becomes a conflict of the kind Same organisation (AI check), with one sentence that says why, shown on the row as "Amal: …". Run the check once the reviewers' affiliations are entered and most abstracts are in, and again before you assign the abstracts.
Correcting a conflict that is wrong
Each row's menu offers the corrections that fit its kind:
| Kind | Correction | What it does |
|---|---|---|
| Same organisation (AI check) | Not the same organisation | Tells run.events that Amal matched two different institutions. The match is removed for every reviewer and every session, and later checks remember it. |
| Same affiliation, or Same organisation (AI check) | Override… | Sets aside this one conflict, for this one reviewer and this one session, with a reason. For example: the reviewer and the author work in different departments of a large hospital and do not know each other. |
| Declared | Remove declaration | Removes a conflict the reviewer declared by mistake. |
| Overridden | Remove override | Brings back a conflict you set aside. |
| One of the session's people | none | A reviewer can never rate their own abstract. |
Only content admins can correct conflicts: anyone with the organizer role Admin, or the event role Event Manager or Content Owner.
What run.events cannot know
run.events sees only what is written in the event: the people of each abstract and their institutions. It does not know that a reviewer published a paper with an author last year, supervised the author's thesis, or competes with the author's group. These cases rely on the reviewer. Ask your reviewers, in your instructions, to use I have a conflict whenever they are in doubt.
Good to know: at a company's own conference, where all speakers and reviewers work for the same company, Raise conflicts of interest from affiliations would put every reviewer in conflict with every colleague's submission. Leave it off there.
Related articles