Start a conversation

Event app contingency checklist

We created this guide to help you avoid common problems that can occur when using event apps e.g. users unable to install apps, poor internet during the event, etc.

It includes suggestions on how to plan for these issues and solutions to resolve them. Unfortunately, there are many variables with apps and events have a hard deadline so unlike other apps where we can resolve issues as they arise, event apps 'must work' or alternatives must be offered.

We suggest you take these precautions before any event:

  1. Explain to attendees the role the app will play and how much better their experience will be because of the app

    • Agenda with lots of information in it, more than you could print

    • A complete list of attendees to help make networking easy

    • Live polls so you can contribute

    • Easy quick surveys to the firm can improve the event in the future

  2. Registration staff should help attendees to access and explain how the app will be used if registration staff do not check people can access and understand the app your level of usage will be lower

  3. Do not offer alternatives to the app unless you want the app to be optional e.g. do not give people a printed agenda, therefore, they have to access the app. This stops people defaulting to using the paper agenda and not using the app.

  4. If a user cannot open the app or has other problems, suggest they use the web app, backup devices you can lend to attendees to avoid resolving technical issues with user's devices, or a paper agenda

  5. Ask presenters to reference the app. Your users are not used to an app so the more people on stage can reference the app the better:

    • You can find a copy of my slides in the app

    • Please leave me feedback via the app

    • Please give me your opinion via a live poll in the app

  6. Have a backup plan in case the wifi has issues e.g. The wifi is down so please raise your hand to answer the poll question

  7. Set expectations that you are trying an app for the first time because it is better for the environment, offers more features, etc. By using language like this you leave yourself open to feedback and improving e.g. the app needs X or I had trouble with X in the app. It also means complaints can be welcomed as feedback instead of seen as errors.

Want this as a PDF so you can tick items off? Download the attachment for ease of use and distribution to your team


  1. 99 KB
  2. View
  3. Download
Choose files or drag and drop files
Was this article helpful?
  1. Johanna Gustafsson

  2. Posted
  3. Updated