The Slide Check and the Speaker Agreement

How run.events collects what speakers deliver, checks every slide deck before it reaches the room, and makes speakers sign the conditions first.

Article Image Alt

What speakers deliver

After acceptance, each session has things to deliver: a slide deck, a poster file, perhaps a recording link. In run.events, these are session materials. Each presentation type lists the materials its speakers must deliver, with a deadline for each, on its tab Materials.

Two parts of this make the difference on a congress: the slide check, which looks at every slide deck before it reaches the lectern, and the speaker agreement, which every presenter fills in before they can deliver anything.

Material types

On the presentation type's tab Materials, Add material type adds one, with these settings:

  • Name, for example Slides or Poster.
  • Speakers deliver: Upload, Link or Upload or link.
  • Presentation deck: the material type is the slide deck, and every upload is checked. One material type per presentation type can be the deck.
  • Required, or optional. Only required materials count as missing.
  • Allowed File Types and Max File Size (MB). A material that is not the deck takes at most 25 MB; the deck takes up to 500 MB.
  • Uploads open: the date from which speakers can deliver.
  • Deadline: A date, or a number of Hours before the session. Hours are counted from the session's slot on the published agenda, so a speaker on Friday afternoon has a later deadline than one on Wednesday morning. A session not yet on the published agenda has no deadline.
  • Grace date, for a deadline set as a date: a hidden second date. Speakers see only the deadline, and run.events keeps accepting uploads until the grace date.

Speakers see what they must deliver, with the due date, under Needs your attention on their speaker dashboard. The upload shows the maximum size and the allowed types before they choose a file.

What the slide check does

run.events checks every uploaded slide deck in the background. Depending on the file and the settings of the material type, the check looks at:

  • the file type and the size;
  • the slide format against the screen format of the session's room, for example 4:3 slides in a 16:9 room. A room without a screen format counts as 16:9;
  • fonts that are not embedded, when Warn about fonts that are not embedded is ticked on the material type. Common fonts that every lectern PC has, such as Calibri or Arial, are not flagged;
  • the image resolution, in PDF files only. Images in PowerPoint files are not measured.

Each check ends in one of three results: OK, OK with warnings, or rejected. A report in plain words explains it, for example "The slide format is 4:3; the room's screen is 16:9. Export the slides in the room's format." The speaker reads the same report on their deck card in the speaker dashboard, and can correct the deck and upload it again.

The deck card on a session's Materials tab, with its versions, their check results and the report

What the slide check does not do

  • It does not play videos. Neither embedded nor linked videos are checked, and nothing tests what plays on the lectern PC. Ask speakers to embed their videos, and test them in the speaker ready room.
  • It checks Keynote files, older .ppt files and video files for type and size only.
  • Font warnings never reject a deck; they only warn.

Versions, approval and the lock

Every upload is kept as a version, each with its own report. The room's podium page offers the newest version that passed the check.

On the session's tab Materials, each version offers:

  • Download and Open as PDF;
  • Re-run review, which checks the version again, for example after the room's screen format changed;
  • Approve, which lets you accept a version that the check did not pass, with a written note. An approved version counts as ready. Withdraw approval undoes it.

Lock, at the top of the deck card, stops anyone, organizers included, from replacing or deleting the deck, so that nothing changes shortly before the talk. Lock the deck this many hours before the session, on the material type, locks it automatically once the session is on the published agenda.

A deck is ready when a version has passed the check or has been approved. In the Agenda Builder, each room header shows how many decks of the day are ready, and the Issues panel warns about decks that are not ready a number of days before the session.

PDF copies for attendees

Each PowerPoint deck in .pptx format is also turned into a PDF with slide previews. With Attendees get a PDF of PowerPoint decks on the deck's material type, attendees open the PDF copy instead of the original. Speakers and organizers keep the PowerPoint file.

Consent to publish

A material type with Ask speakers for consent to publish asks the speaker, with every upload, whether the file may be published to attendees. A file whose speaker did not allow it is never shown to attendees, even when its status is published.

The speaker agreement

The speaker agreement is a form each accepted presenter fills in for their session, before they can deliver anything. It holds what your congress needs from every presenter: the conditions for speakers, a release for recording the talk, and, for accredited congresses, the disclosure of conflicts of interest. An accredited congress is one whose sessions count as continuing medical education; the accrediting body requires every speaker to disclose their financial ties, for example to a pharmaceutical company.

The speaker agreement is a Smart Form of the kind Speaker agreement form, with your own questions. A presentation type names it on its tab Forms, under Speaker agreement form.

  • Who fills it in: each accepted, informed speaker in a role that counts as a speaker, once per session, in the speaker portal on the session's tab Speaker agreement.
  • Who does not: co-authors who do not present, chairs and moderators. If your accrediting body needs disclosures from chairs too, collect them another way.
  • What it blocks: until the agreement is filled in, the speaker cannot upload materials for the session. The material reads "Fill in the speaker agreement first."

You follow who has filled it in with the filter Speaker agreement in Speaker Management, and read the answers on the session's tab Materials, under Speaker agreements.

Good to know: a recording release in the agreement is a question you write. run.events records the answer, but does not act on it. Check the answers yourself before you publish recordings.

Related articles