Event mobile app launch checklist: T-30 to T-0

A conference I observed last fall launched its app seven days before the event. The agenda was half-populated. Speaker bios were missing photos. The push-notification system hadn't been tested. The attendee directory was inaccessible because the opt-in flow pointed to a non-existent screen. They ran every one of those issues live, on stage, in the first 48 hours. Their install rate topped out at 31% — well below the 70% the vendor had promised.

The single biggest lever on event app success is launching early enough that adoption can build. Four weeks minimum. Three weeks is a scramble. Two weeks is a failure. This guide is the countdown checklist: what needs to happen at T-30, T-14, T-7, T-1, and on event day itself.

1. T-30 days: foundation

Four weeks before the event, the app should be live and essentially complete.

• [ ] App published to iOS App Store and Google Play. Approval can take 3-7 days; don't leave this for the final week.
• [ ] Agenda fully loaded. All sessions, times, rooms, speakers. Placeholders replaced with real data.
• [ ] Speaker bios uploaded with photos at 1024px minimum. No broken image links.
• [ ] Sponsor pages live. Logos, descriptions, booth locations (if known), collateral uploads.
• [ ] Venue map uploaded. Accurate, zoomable, with room labels matching the agenda.
• [ ] Integration tests complete between registration platform and app. A test registration should produce an attendee in the app within 5 minutes.
• [ ] App install link included in registration confirmation emails.
• [ ] Privacy settings defaulted correctly. Messaging opt-in, attendee directory visibility, data handling per jurisdiction.
• [ ] Admin portal access granted to ops team. Not just one person — at least three.

At T-30, the app works. Anything not working at T-30 is unlikely to work at T-0.

2. T-14 days: polish and test

Two weeks before the event, shift from foundation to polish.

• [ ] Push notification test. Send a test notification to the internal team. Confirm delivery, targeting, rate limits.
• [ ] Survey questions loaded. Post-session, end-of-day, and post-event surveys configured. Trigger timing set.
• [ ] Schedule conflicts reviewed. Sessions overlapping in ways that don't match the agenda; wrong room assignments; speaker conflicts.
• [ ] Map and venue images uploaded including breakout room details.
• [ ] Lead retrieval scanner tested with sample QR codes (if sponsors have access).
• [ ] Networking matchmaking algorithm seeded if using one. Interest tagging on attendee profiles reviewed.
• [ ] Content moderation process defined. Who handles inappropriate messages, session Q&A spam, profile flags. Named owner.
• [ ] In-app analytics verified. Install events, session saves, message counts all firing correctly.
• [ ] Marketing push prepared. Email, social post, on-site signage templates for app promotion.

3. T-7 days: adoption push

One week out, the app is done; the focus is driving installs.

• [ ] Email blast to all registrants promoting the app. Subject line references schedule-building specifically.
• [ ] Social posts queued featuring the app across channels. Include QR codes.
• [ ] Speaker request for amplification. Ask speakers to post about the app — "my session details are in the app" type messages.
• [ ] On-stage prompt scripted. Exact wording for the emcee, keynote speaker, and session chairs. Timing: first 10 minutes of opening keynote.
• [ ] QR code designs finalized for on-site signage.
• [ ] Staff training on the app. Every ops team member should have the app installed and know how to help attendees with common issues.
• [ ] Crisis playbook for app issues. What happens if the app crashes, if push fails, if the agenda import breaks. Named on-call contact with vendor.
• [ ] Capacity check with vendor. Confirm the platform can handle your peak concurrent user load.

4. T-1 day: lock and load

The day before doors open, everything is frozen.

• [ ] Final agenda check. Read through the whole agenda in the app, as an attendee would. Spot check 10 random sessions.
• [ ] Sponsor logo verification. Confirm sponsor content accuracy — wrong logos at this level are hard to recover from.
• [ ] Push to any schedule changes. Use the push notification system to communicate last-minute changes to installers.
• [ ] Map references actual room signage. Verify the map labels match physical signs in the venue.
• [ ] QR code signage ready for on-site placement.
• [ ] On-call tech support staffed. 24/7 during event days, with named vendor contact.
• [ ] Content moderation coverage. If you've enabled messaging or Q&A, ensure someone is monitoring.
• [ ] Backup plan documented. If the app fails at scale, what do attendees do? Printed mini-program? Mobile web fallback?

5. T-0 and event days: live operations

During the event, the app is operational, not launched.

• [ ] Morning stand-up includes app health. Install count, active users, open issues.
• [ ] Push notifications used sparingly. 2-4 per day maximum. Schedule changes, major prompts, emergency only.
• [ ] Content moderation live. Inappropriate messages, spam Q&A, profile issues addressed within 15 minutes.
• [ ] Session reminders pushed 5-10 minutes before each session to users who saved it.
• [ ] Live polls and Q&A monitored in each session.
• [ ] Post-session surveys trigger automatically 2-5 minutes after session end.
• [ ] Adoption metrics monitored. Install rate tracked hourly during day 1.
• [ ] Issue escalation path active. Any attendee complaint surfaces to a single owner who tracks resolution.

6. T+1 to T+30: post-event

The app continues working after doors close.

• [ ] Post-event NPS survey pushed at T+24 hours.
• [ ] Session recordings uploaded as they become available. Push notification on major releases.
• [ ] Attendee directory remains available for 30 days (or permanently if you run a community).
• [ ] Thank-you messages from organizers and sponsors.
• [ ] Data export completed within 7 days: leads, sessions attended, NPS, engagement.
• [ ] Post-mortem scheduled with vendor on adoption metrics and incidents.
• [ ] Feature request list captured from attendee feedback for next-year planning.
• [ ] App retirement decision. Archive or persist for future events.

7. Common launch mistakes

1. Launching too close to the event. Under 3 weeks lead time produces 30-40% install rates at best.
2. No on-stage prompt. The single cheapest, highest-impact adoption tactic.
3. Agenda loaded at T-7. Attendees need pre-event planning.
4. Unclear ownership. Nobody knows who fixes what when something breaks.
5. Push notification abuse. 10+ notifications on day 1 kills the channel.
6. No mobile web fallback for attendees who won't install.

A purpose-built conference app that shares one record with registration removes most of the plumbing complexity, and a CRM connection can be scoped with your vendor; the human operational steps still need to happen on time.

FAQ

What if my event is 2 weeks away and the app isn't live? Prioritize agenda, schedule, and map. Cut networking, matchmaking, and advanced features. A simple app launched on time beats a complete app launched late.

How many staff do I need for app operations during the event? One full-time app lead for events under 1,000 attendees. Two for 1,000-3,000. A dedicated content moderation team for 3,000+.

What about day-of installs? They'll happen (a spike of 15-25% of total installs typically land on day 1). Plan for QR code signage and registration desk staff who can help. Day-of installers engage at lower rates than pre-event installers.

How do I handle a vendor outage during the event? Have a documented fallback: printed schedule, emergency webpage, SMS broadcast channel. Practice the failover once before doors open.

Should I retire the app immediately after the event? Keep it active for 30 days minimum for post-event engagement (recordings, NPS, attendee directory). Archive rather than delete; restoring for next year is cheaper than rebuilding.

Related guides

• Event app feature checklist
• Event app adoption tactics
• Pre-event marketing timeline

Ready to run your next event? Create your event on WebMobi →