Ten minutes before a scheduled session, the chair looks at an empty lectern. The presenter has not arrived, the listed co-author is in the room, and attendees are settling into their seats. The chair needs an answer now: wait, approve the co-author, connect the presenter remotely, or continue without the talk.
A conference presenter no-show policy gives the team that answer before pressure takes over. It defines when a presenter becomes a no-show, who may approve a substitute or remote exception, what the chair should tell the room, and which records must change after the decision.
This guide focuses on delivery-stage absence. If an accepted contribution is withdrawn before the event, use a separate abstract withdrawal process. Routine reminders and speaker preparation belong in the speaker management workflow.
Start With the Decision the Room Will Need
A good policy begins with the moment the team must act. Imagine a 2:00 p.m. session. The presenter has not checked in by 1:45, has not answered the emergency contact number, and has not sent a co-author. At 1:55, the chair cannot keep making calls while the audience waits.
The policy should tell the team:
- When to start the contact process.
- Who makes the final session decision.
- Which alternatives are allowed.
- What the chair says to attendees.
- How the team records the outcome.
Keep that decision path short. A policy that needs three committee calls during the first five minutes of a session will fail when the room is full.
Define the Event Before You Decide the Consequence
Not every absence is the same. A presenter who reports a medical emergency two hours before the session has created a different situation from someone who stops replying after repeated reminders. The session may need the same immediate response, but the later review should not treat both cases alike.
Use clear working definitions so that staff do not improvise labels:
| Situation | Working definition | Immediate action |
|---|---|---|
| Late arrival | The presenter has made contact and expects to arrive after the scheduled start. | Decide whether the running order can change without disrupting other speakers. |
| Unconfirmed absence | The presenter is missing and the contact window is still open. | Follow the published contact route and prepare the fallback. |
| Presenter no-show | The presenter is absent after the contact window closes, with no approved substitute or delivery option in place. | Apply the session decision and record the incident for later review. |
| Approved substitute | An eligible co-author or other permitted person has received approval to deliver the contribution. | Give the chair the approved name and any disclosure the audience needs. |
| Approved remote delivery | The conference has authorized remote participation under its published rules. | Run the agreed technical check and confirm the chair’s introduction. |
State the contact window in practical terms. For example: “If the presenter has not checked in 15 minutes before the session, the chair alerts the program desk. If the team cannot reach the presenter by five minutes before the start, the program lead chooses the approved fallback.” The exact timing can vary, but everyone should know which clock they are following.
Decide Who May Substitute Before Anyone Asks
A willing person is not automatically an appropriate substitute. The replacement may need to answer questions, handle unpublished material, respect author permissions, and meet registration or disclosure requirements.
Set eligibility rules before the conference. A policy might allow a listed co-author who:
- Knows the work well enough to present it accurately.
- Has permission from the corresponding author or required author group.
- Meets the conference’s registration and disclosure rules.
- Accepts the session format, timing, recording and accessibility requirements.
- Receives approval from the named program authority.
Do not promise that every substitute request will be approved. Some conferences restrict substitutions, while others allow them only in defined circumstances. For example, the ACM CompEd policies and the NSTA presenter policies show that associations can take different approaches to attendance, substitution and cancellation. Your rules should fit your program, and authors should see them before they accept a presentation slot.
Keep a short substitute approval record
When a program lead approves a substitute, record the decision once and share it with the people who need it. A useful record includes:
- The contribution and session ID.
- The scheduled presenter and approved substitute.
- The approver and time of approval.
- The reason category, without unnecessary personal details.
- Any disclosure, registration or recording checks.
- The records that need an update after the session.
This prevents a familiar problem: the program desk approves the co-author, but the chair still has the original name and refuses entry at the lectern.
Set a Notification and Decision Timeline
The first notice should tell presenters exactly how to report a problem. Avoid a general inbox that no one watches during the event. Give them one urgent contact route and explain what information to send: contribution ID, session time, reason for the change, proposed substitute, and whether remote delivery is being requested.
Build the timeline around three stages:
- Before the event: Publish the absence and substitution rules, collect an emergency contact, and ask presenters to report likely problems early.
- Before the session: Check presenter arrival or readiness, open the contact window, and send unresolved cases to the program lead.
- At decision time: Approve one fallback, brief the chair, and stop running parallel discussions.
For a 2:00 p.m. talk, the operations note might read: “1:40 check-in missing; 1:43 call and message sent; 1:50 co-author request received; 1:53 program lead approved substitute; 1:55 chair briefed.” That small timeline becomes useful evidence if the authors later question what happened.
Treat Remote Delivery as a Governed Alternative
Remote delivery can save a session, but it should not be a last-second favor based on a presenter’s status or reputation. Apply the same published criteria to every request.
Before approving a remote option, check:
- Whether the conference format and venue connection can support it.
- Who has authority to approve the exception.
- Whether the presenter consents to the required platform and recording terms.
- Whether captions, interpretation or other accessibility arrangements will still work.
- Whether the team has enough time for a brief audio, video and slide test.
- What the session will do if the connection fails.
A presenter calling from an airport with unstable audio may create more disruption than a clear five-minute schedule change. The decision should protect the session, not simply keep every title on stage at any cost.
Write the limit into the policy. For example: “Remote delivery may be approved by the program lead when the venue setup, accessibility needs and speaker connection have been checked. The session chair cannot approve it from the room.” The ARVO presenter and moderator guidelines offer a useful example of giving presenters and moderators concrete responsibilities before the meeting.
Give the Session Chair One Clear Decision Path
The chair should not investigate the absence or negotiate exceptions in front of the audience. The chair reports the missing presenter, receives the approved room decision, and keeps the session moving.
Use a simple flow:
Presenter missing → Contact route checked → Program lead decides → Approved substitute, approved remote option, or session fallback → Records updated
The fallback may be to move to the next scheduled contribution, extend the discussion, use a planned break, or end the session early. Choose options that fit the format and publish the chair’s authority in advance. A detailed session chair checklist can cover room management; the no-show policy only needs the decision and message for this incident.
Put the room answer in one place
Give each chair a short room note rather than expecting them to search the full policy. It should list the program desk contact, the check-in deadline, the person who can approve a change, the allowed fallbacks, and the neutral announcement to use. Keep the same note at the program desk.
Suppose the chair reports a missing presenter at 9:55 a.m. The desk can open the session record, see that no substitute has been approved, and reply: “Start the next talk at its published time. Use the first ten minutes for moderated discussion.” The chair receives one instruction, the room hears one message, and the operations log captures one decision. That is far safer than separate staff members giving the chair different answers by text, email and radio.
Give the chair language that protects everyone
A short, neutral announcement is enough:
“Our next scheduled presenter is unavailable. We will continue with the approved substitute and keep the original discussion time.”
Or, when no alternative is approved:
“The next presentation will not take place. We will move to the following contribution at the published time and use the interval for discussion.”
The chair should not guess at a reason, share private details, blame the presenter, or promise a later recording unless the program team has confirmed it.
Update Each Record for Its Own Purpose
A last-minute change can affect several records, but it should not overwrite history. Preserve who was originally scheduled, add what happened, and update only the public information that attendees need.
| Record | What to record | Why it matters |
|---|---|---|
| Operational log | Contact attempts, decision time, approver and room outcome. | Supports handovers and later review. |
| Program or schedule | The attendee-facing change, if there is time and a clear benefit. | Reduces confusion without rewriting the submission history. |
| Presenter record | The scheduled presenter, actual presenter and approval status. | Keeps badges, certificates and follow-up accurate. |
| Contribution record | Presented, substituted, delivered remotely, or not delivered. | Separates the work’s status from the person’s attendance. |
| Proceedings record | Any action required by the conference’s published proceedings policy. | Avoids an improvised publication decision during the session. |
Do not assume that a missed presentation automatically removes a paper from the proceedings. Publication rules differ across conferences and publishers. State the rule in advance, apply it consistently, and send disputed cases through the named review or appeal route.
Separate Consequences From Genuine Exceptions
Consequences should support reliable programs, not punish people for circumstances outside their control. Review the facts after the event, when the team is no longer making a room-level decision.
A fair review asks:
- Did the presenter use the required notice route as soon as reasonably possible?
- Was there a medical, travel, safety, bereavement or other serious circumstance?
- Did the presenter propose an allowed substitute or delivery option?
- Did the conference respond according to its own timeline?
- Have similar cases received similar treatment?
Possible outcomes may include no action, a reminder, loss of a presenter benefit, a proceedings action already stated in the rules, or a time-limited restriction on future submissions. Use only consequences that the conference has published and has authority to apply. Give authors a way to provide evidence and request review.
Keep sensitive personal information out of general operations notes. Staff may need to know that an approved exception exists; they rarely need the medical or family details behind it.
Turn One Incident Into a Better Policy
After the event, review the incident as a process, not a story about one difficult presenter. Ask where the response slowed down.
Perhaps the emergency number appeared only in an old email. Perhaps the chair did not know who could approve a co-author. Perhaps the venue had remote equipment, but no one had assigned a technician. Each gap points to a small improvement for the next program.
Track a few useful measures:
- Number of presenter absences and late changes.
- How far in advance the team received notice.
- Time from escalation to decision.
- How many sessions used a substitute, remote option or fallback.
- How many cases required later review or appeal.
These numbers will not explain every case, but they reveal whether presenters understand the rules and whether staff can apply them quickly.
Where Dryfta Fits
A no-show policy remains a human governance decision. Event software can make the response easier by keeping the submission, authors, scheduled presenter, session and communications connected instead of scattering them across separate spreadsheets.
In Dryfta, organizers can manage abstract and author information, speaker profiles, program schedules and event communications in one event workflow. Teams should still define who may approve substitutes, when remote delivery is allowed, and how proceedings decisions are reviewed. Confirm the product setup and capabilities needed for your conference with the Dryfta team before relying on a specific workflow.
The practical goal is simple: when the chair calls, the program desk can see the right contribution, contact the right people, record the approved decision and tell the room what happens next.
Conference Presenter No-Show Policy FAQs
What counts as a conference presenter no-show?
A presenter becomes a no-show when they are absent after the conference’s stated contact window closes and no approved substitute or delivery option is in place. Define the timing and contact route in advance so staff apply the same rule.
Can a co-author present instead?
Yes, if the conference policy allows it and the named authority approves the co-author. Check subject knowledge, author permission, registration, disclosures, recording terms and any other published requirements before confirming the change.
Should a no-show paper remain in the proceedings?
Follow the proceedings policy published for that conference and publisher. Do not make a publication decision at the lectern. Record the session outcome, review the case afterward, and offer any appeal process stated in the rules.
Can a missing presenter join remotely?
Only when the conference permits it and the program lead confirms that the venue setup, connection, consent and accessibility arrangements are ready. The policy should also state what happens if the connection fails.
What should the session chair tell attendees?
Use a brief, neutral statement that explains the schedule change without sharing private information or assigning blame. The chair should announce only the fallback that the program team has approved.
Prepare the Answer Before the Room Fills
A missing presenter should not trigger a debate beside the lectern. Publish the rules, assign the decision, brief the chair and keep a clean record. When everyone knows the next step, the team can protect the session while treating the presenter fairly.
