How do I keep reviewers away from abstracts from their own institution?

Switch on conflicts of interest from affiliations, give your reviewers their institutions, catch differently written names with Amal, and correct what is wrong.

Article Image Alt

What run.events does for you

A reviewer should not rate an abstract written by colleagues from their own institution. run.events can find these cases by comparing institutions, and keep the reviewer away from the abstract. It also always keeps a reviewer away from an abstract on which they are an author.

What it cannot find are other relationships: a reviewer who has published with the author, or supervised their thesis. Those rely on the reviewer declaring a conflict. Conflicts of Interest explains all kinds of conflicts.

Step 1: Switch on conflicts from affiliations

  1. Open Content And Speakers, then Call for Content Settings, and its tab Speakers and messages.
  2. Tick Use affiliations, if it is not ticked yet. Authors are then asked for their institutions.
  3. Tick Raise conflicts of interest from affiliations.
  4. Save.

Both are off on every event until you switch them on. Do this before the call opens, so that every abstract arrives with its authors' institutions.

Step 2: Give each reviewer their institutions

  1. Under Configure, open Content Team.
  2. Choose a reviewer.
  3. Under Affiliations, enter each institution the reviewer belongs to, in full, as the authors are likely to write it.
  4. Choose Apply.

A reviewer without affiliations is compared by the company in their profile, which is often empty or out of date. Enter the institutions yourself.

The Content Team fly-out of a reviewer, with buckets, topic preferences, review limits and affiliations

Step 3: Catch the names written in different ways

run.events ignores upper and lower case, accents, punctuation and a legal form such as GmbH at the end, but it does not expand abbreviations. So "Univ. Hospital Nordstadt" and "University Hospital Nordstadt" do not match by themselves.

  1. Under Configure, open Conflicts of interest.
  2. Choose Check with Amal. Amal, the AI assistant of run.events, compares the institution names that are written in different ways.
  3. Each match becomes a conflict of the kind Same organisation (AI check), with a sentence that explains why.

Run the check after the call has closed and before you assign the abstracts. Check with Amal works only while AI is available for your organizer.

Step 4: Review the list and correct what is wrong

Go through the list on Conflicts of interest. Each row names the reviewer, the session and the kind. In each row's menu:

  • Not the same organisation: Amal matched two institutions that are in fact different. The match is removed for every reviewer and session, and later checks remember it.
  • Override…: this one conflict does not apply, for example because the reviewer and the author work in different departments of a large hospital and do not know each other. Give a reason. Override… is offered on conflicts from institutions only.

A conflict because the reviewer is an author of the abstract cannot be set aside.

Step 5: Assign the abstracts

Now assign the abstracts. Automatic assignment skips every reviewer who is in conflict. If you assign a reviewer by hand to an abstract they are in conflict with because of their institution, run.events asks you for a note. See How do I assign abstracts to reviewers automatically, and set how many reviews each needs?.

Step 6: Ask reviewers to declare the rest

Tell your reviewers, in your instructions, to choose I have a conflict on any abstract they know too well to rate fairly. A declared conflict removes the abstract from their view, and any review they gave earlier stops counting.

Good to know: at a company's own conference, where everyone works 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