Conference Program Planning Checklist for Digital Poster Sessions

A well-built conference program planning checklist turns a digital poster session from a collection of screens into a coordinated event program. Universities, hospitals, societies, and research teams can use it to align poster volume, presenter deadlines, venue requirements, and support before the schedule is locked.

Request an RFP

Start with the session format and scope

Before choosing equipment or setting a submission deadline, write down what the poster program needs to accomplish. Record the audience, event dates, locations, expected poster volume, and whether posters will run in one continuous block or in separate sessions. An academic research day may have one poster period, while a multi-track society meeting may need different groups displayed at different times.

Begin with a one-page program brief. Keep it short enough that busy colleagues will use it, but specific enough to prevent assumptions. Record the decision-maker for the event, the program owner, the venue contact, and the person authorized to approve final content. Give each person one clear responsibility. The venue may confirm room access and site rules, while the academic program lead resolves session assignments and title changes. A technology lead can confirm the display plan and support scope. If one person holds several roles, say so explicitly.

• Identify the program owner and the people approving the schedule.
• List each poster session, its start and end time, and any changeover window.
• Estimate poster count by session, not only as one event-wide total.
• Decide whether the program is in person, virtual, or a combination.
• Mark optional needs—such as abstract submission, electronic judging, virtual conference delivery, or gallery hosting—for separate scoping.

These choices affect the number of displays, content workflow, room plan, and staffing conversation. Optional modules should be confirmed individually rather than assumed to come with every equipment order. For a general planning sequence, see the University of Washington Tacoma conference planning checklist and timeline, which covers event goals and program details.

Build the poster count and session schedule

Use one working list that ties each accepted poster to its session and display assignment. Leave room for late changes, withdrawals, and corrections. Ask program leads when decisions will be final, and identify who can approve exceptions after that date.

For each session, track the planned number of posters, the available presentation time, and whether posters rotate between blocks. If presenters must be present at particular times, publish that expectation early. A changeover buffer can help staff confirm the next group is loaded before a session begins.

Separate confirmed entries from estimates. Early in planning, a department may report 80 likely posters, but that is not the same as 80 accepted, ready-to-display files. Track at least three values: expected submissions, accepted posters, and final display assignments. This makes it easier to explain why an equipment estimate or floor plan is provisional. Set a date when the count becomes stable enough for the venue and service team to work from, plus a later date for handling exceptional changes.

• Set a date for the expected final poster count.
• Identify the person responsible for maintaining the master list.
• Record session names exactly as they will appear in event materials.
• Agree how cancellations, duplicate entries, and schedule changes are handled.

Use a consistent poster identifier in every working document. A number such as P-014 or a stable submission ID is safer than matching only by author surname, particularly when presenters share a last name or submit more than one item. Keep the identifier beside the title, corresponding author, session, and display assignment. Avoid copying a changing spreadsheet row number into emails because sorting can alter it.

For a single block, a straightforward ordered list may be enough. For multiple sessions, create a separate view for each block and a master view that contains all assignments. Check that each poster appears once in the master schedule and in the intended session view. When a poster moves, update the source list first and then refresh derived schedules; otherwise presenters may receive conflicting versions.

Make an explicit decision about overflow. If accepted posters exceed the planned display count, identify who chooses a solution and what options are acceptable: adding capacity if feasible, moving an item to another session, or revising the program. Do not promise an option until the venue and delivery plan support it. Also establish how withdrawals are recorded so a vacant assignment is not mistaken for a missing file.

Set deadlines that leave time to prepare files

Work backward from the first session. A submission deadline is not the same as a ready-to-display deadline: files need to arrive, be checked, and be assigned to the right session. Send presenters clear instructions about accepted formats, dimensions or templates, naming conventions, and where to ask for help. Confirm the final specifications with the team responsible for the display workflow rather than relying on assumptions.

Plan at least three milestones: the submission deadline, the correction deadline, and the point when the event team freezes the display schedule. Tell presenters what happens if a file is incomplete or arrives late. If custom design assistance is of interest, distinguish that individual-presenter service from the organizer’s equipment and event-management scope.

A useful calendar works backward from the event instead of choosing an arbitrary number of weeks. First mark venue access, setup, testing, and the first session. Then allow time for the program committee to make acceptance decisions, presenters to prepare files, staff to inspect those files, and authors to correct problems. Add a final schedule freeze and a short contingency window. If one stage depends on another—for example, final session assignment depends on acceptance—show that dependency in the calendar.

Use dates and times with a stated time zone, especially when presenters submit from different regions. Spell out what “deadline” means: received by the organizer, uploaded successfully, or approved after review. If a submission portal is involved, tell authors how to verify receipt and whom to contact if the confirmation does not arrive. Keep one official source for deadline changes rather than relying on informal messages.

Build a small correction window into the process. A file may open but still contain an outdated title, an incorrect author line, or a wrong session label. Set a clear rule for which changes are allowed after the deadline and who approves them. Scientific or editorial decisions belong with the authorized program contact; the technical workflow can flag a mismatch but should not decide the research content.

Prepare and verify poster content

Choose a consistent way to collect and review files. A simple tracker can include presenter name, poster title, session, file received, file checked, correction requested, and final approval. Have an authorized program contact resolve content questions; technical staff should not be expected to make scientific or editorial decisions.

Before loading, check that files open, match the agreed format, and correspond to the correct presenter and session. Keep a controlled final version so that older drafts are not accidentally displayed. If abstract submission or reviewer coordination is needed, scope it as a separate workflow with its own owners, review dates, and communications.

Make the review repeatable. One practical sequence is to verify receipt, confirm the file is readable, compare its name or identifier with the master list, check the assigned session, and note whether a correction is needed. The reviewer should record a status and date rather than relying on memory. Useful statuses include received, needs correction, ready for approval, approved, and withdrawn. Avoid using “done” to mean both technically checked and approved by the program lead.

When a correction is requested, make the request precise. State the poster identifier, what needs attention, the deadline, and the route for sending the replacement. If the problem is a file that will not open, say so; if the issue is a mismatch between title and schedule, identify which record is authoritative. Ask presenters to submit a new final file rather than editing a local copy without a record. Keep the replaced version out of the final display folder.

Use version control that is simple enough to follow under deadline pressure. Store incoming files separately from approved files, and give approved files a stable name tied to the poster identifier. Limit access to the final folder to the people who need it. If a late change is authorized, record who approved it and when, then confirm that the updated file reached the correct display assignment. This process reduces avoidable mix-ups without asking technical staff to make editorial judgments.

Consider what presenters need to know about readability. Provide any approved template or technical specifications early, and recommend that they test the final file at a practical viewing size. A dense poster can be difficult to follow even when the file technically meets the requirements. If design guidance is offered, clarify whether it is general advice or a separate custom design service. Do not imply that every organizer order includes individual design work.

Map the room and venue requirements

Sketch the poster area before confirming the final display arrangement. Mark entrances, exits, accessible routes, registration, poster displays, audience circulation, and any adjacent sessions. Think about where people may pause to read or discuss work, and avoid planning a layout that blocks normal movement through the venue. The National Center on Health, Physical Activity and Disability conference planning guide advises keeping exhibit-hall and poster-session aisles clear for access.

Coordinate the plan with the venue contact. Confirm where equipment can be placed, how it will be delivered and removed, and what restrictions apply to setup times. A floor plan should identify each display position and connect it to a session or content assignment. Review the drawing with the people who will run the room, not just the person who created it.

Start with a blank venue plan and mark fixed features before drawing display locations. Include doors, columns, built-in furniture, registration points, nearby presentations, and any areas the venue says must remain clear. Then draw the proposed display positions and the paths people will take between them. Give the drawing a version date and label it as draft or approved. A plan without a version label can be easy to confuse with an earlier layout after room assignments change.

Walk through the plan as several users. Imagine an attendee entering during a session, a presenter stopping to discuss a poster, a staff member replacing a display assignment, and a person using a mobility aid navigating the room. Look for pinch points where people might gather across a route. If the poster area shares space with registration or refreshments, account for those queues rather than treating the room as an empty rectangle. Ask the venue to review the final drawing against its own requirements.

Connect each display position to an assignment method. This may be a numbered position, a session group, or a menu arrangement, depending on the chosen configuration. Keep the labels consistent between the floor plan, master tracker, and staff instructions. If a display can show more than one poster in different time blocks, document the sequence and the changeover moment. Avoid publishing a location until the room and assignment have been confirmed.

Confirm power, internet, and equipment needs

Ask the venue to identify electrical service near the planned display positions and explain any restrictions on cables or outlet access. Confirm who is responsible for providing and checking power arrangements. Do not assume that an outlet shown on a general venue map is available for the program.

For internet-dependent features, ask whether a wired or wireless connection is needed, who provides it, and how access will be arranged. Clarify whether the planned session needs online services during the event or whether files will be prepared for local display. The answer depends on the program configuration; it should be confirmed during planning.

• Record venue power locations and any cable-routing rules.
• Confirm the internet connection, access process, and responsible venue contact if required.
• List displays, stands, touch or kiosk options, and any other equipment under consideration.
• Ask who handles delivery, setup, testing, breakdown, and return logistics.

Translate “we have Wi-Fi” into questions that can be answered. Is the connection available in the poster room? Is it intended for event equipment, attendee use, or both? Does access require credentials or a sign-in process? Who can troubleshoot if it is unavailable? If the planned display workflow can operate from prepared local files, confirm that approach with the delivery team rather than assuming it. If an online feature is part of the plan, document its dependency and the contact responsible for access.

Power planning also benefits from named ownership. Ask the venue to confirm outlet locations and any rules about cable paths, temporary coverings, or equipment placement. Assign someone to verify that the proposed locations are still available during setup. Keep a copy of the approved floor plan with the power notes, and share it with the people who will install and operate the displays. Do not infer that a general room diagram guarantees a particular outlet can be used.

Match the equipment conversation to the program configuration. List the number of planned display positions, stands, any touch or kiosk options, and any supporting devices being considered. Confirm which items are supplied by the venue, which are part of the event scope, and which remain undecided. The customer’s managed program can include 49-inch displays and stands, touchscreen or kiosk options, presenter file preparation, venue planning, and on-site technical support, but the exact configuration and responsibilities should be agreed for the event. Avoid treating every option as standard or assuming a fixed equipment model before it is confirmed.

Write down delivery and removal logistics separately from the equipment list. Confirm the venue’s loading instructions, access window, storage rules if any, and the person who can admit the team. Identify when testing can happen without disrupting other sessions. If the event schedule changes, decide who updates the equipment plan and how the technical lead receives the revision.

Assign staffing and day-of support

Name an organizer lead who can make decisions during setup and the session. Share contact details with the venue and technical team, and designate a backup for schedule or content approvals. Establish who will answer presenter questions, report a display problem, and authorize a correction.

Make the support plan specific to the schedule. Include setup access time, testing, presenter arrival if applicable, session coverage, changeovers, and teardown. If an on-site technician or help desk is part of the requested service, confirm its hours and tasks in the proposal rather than assuming coverage beyond the agreed scope.

Write a responsibility list for event day. For each task, identify the lead and a backup: room access, equipment arrival, room readiness, final file status, presenter questions, schedule changes, technical issue escalation, and teardown. A name beside a task is more useful than a broad label such as “the committee.” If an issue needs a content decision, the support person should know which organizer has authority to make it.

Plan support around actual session transitions. Record when staff can access the room, when testing must be complete, when presenters are expected, and whether there are breaks between sessions. If posters rotate, identify the person who confirms that the next group is ready and how the team will communicate a change. A schedule that includes setup and teardown but omits the interval between poster blocks can leave a critical handoff unclear.

Agree on a simple issue-reporting route. Tell presenters and organizers where to go or whom to contact if a display is blank, the wrong poster appears, or a schedule listing is incorrect. Ask the report to include the display or poster identifier and a short description. Decide who can authorize a content replacement. Keep the contact method accessible to the people who need it, and do not promise a response time unless it has been agreed as part of the event scope.

For a managed service, state which parts are included in the agreed program: for example, venue planning, file preparation, setup, on-site support, or breakdown, where applicable. Confirm the service hours and boundaries in writing. Optional abstract submission, electronic judging, virtual conference delivery, and gallery hosting require separate confirmation. Individual presenter design is also a different service path from organizer equipment planning.

Use a final readiness review

Hold a short review with program, venue, and technical contacts before the event. Walk through the plan from room access to the end of teardown, and resolve open decisions while there is still time to adjust.

• Poster count and session assignments are current.
• Submission and correction deadlines have been communicated.
• Final files have a clear approval and version-control process.
• The room plan matches the venue’s setup rules and circulation needs.
• Power, internet, equipment, and access responsibilities are assigned.
• Staff know who to contact for schedule, content, and technical issues.
• Any optional judging, abstract, virtual, or gallery services are separately confirmed.

Make the readiness review an active walk-through rather than a status meeting in which everyone says things are fine. Open the latest master count, verify the next deadlines, and ask each owner to identify any unresolved dependency. Review the approved floor plan against the current session schedule. Confirm whether the people handling setup have the same version and know where to find the final files. Record decisions and assign a due date to each remaining action.

It can help to group open items by consequence. A missing venue access confirmation may affect setup; a late title correction may affect a single display label; an unconfirmed optional judging workflow may affect the program design. Give the highest-impact decisions an owner and an escalation date. If an item cannot be resolved, write down the fallback that the organizer has actually approved rather than leaving the team to improvise.

Use a concise final checklist that can be read on event day. Include the current poster count, session times, location of the approved floor plan, final-file status, organizer lead and backup, venue contact, support route, and any scheduled changeovers. Keep sensitive or private portal material out of general event documents. The goal is to give staff the operational facts they need without creating another uncontrolled copy of the poster files.

Contact the team to discuss your program

Put the checklist into action

A checklist is most useful when each item has an owner and a due date. Keep the working version accessible to the organizer, venue contact, and relevant technical leads, and update it when the poster count or schedule changes. For an event that needs coordinated displays, preparation, venue planning, and on-site support, request a scoped proposal and confirm exactly which services are included.

With the key decisions documented early, your team can spend event week managing the program instead of resolving avoidable planning gaps. A clear count, schedule, file process, room plan, and support assignment gives everyone a practical reference from initial planning through the final session.