Checklist · free
Pre-launch QA checklist for a branded app
Thirty-six checks to run on a branded event app in the final week, from login and branding through notifications and reports. Run it on two real phones and a laptop, tick each line and record the name of the person who tested it.
No sign-up needed.
Who it is for
- Corporate event managers who own go-live sign-off
- HR and L&D leads launching a programme app to employees
- Agency testers who need a repeatable final-week routine
How to use it
- Test on at least one iPhone, one Android phone and a laptop browser, with a mobile data connection and not only office Wi-Fi.
- Write the tester name beside each failed check and fix before moving on.
- Re-run the Login and Notifications sections after any late content change.
- Freeze content 48 hours before the event, and allow only fixes after that.
The contents
Login and access
- Log in with a phone number on a fresh install
- Log in with a wrong code and read the error message
- Log in on two different devices with the same account
- A member on the guest list gets in; a stranger does not
- Logout and login again keeps the correct groups
- A no-app user can reach the web link for polls
Branding and layout
- Logo, colours and splash render on iOS and Android
- App name and icon match the approved artwork
- Bottom navigation shows the right tabs in the right order
- Dark mode on a phone does not make text unreadable
- Text is readable at the largest system font size
Content
- Agenda times, rooms and speaker names match the master file
- Every speaker has a photo and a short bio
- Links to documents and maps open
- Typos checked on the home, agenda and notice screens
- Venue address and contact numbers are correct
Engagement
- A test poll can be launched and closed
- A test quiz scores correctly and shows a leaderboard
- Feedback forms submit and appear in reports
- Points update after a test scan
Notifications
- A push notice reaches both phone types
- A WhatsApp test message arrives with the right variables
- Scheduled announcements fire at the expected time
- Group-specific notices reach only that group
Scanning and entry
- A personal QR scans at the gate scanner
- A used QR is rejected on second scan
- Static activity QR codes scan in poor light
Admin and reports
- Each organiser role sees only what it should
- An export downloads with correct columns
- The team knows who has the admin login on event day
Where it has been used
Drawn from final-week routines for annual meets and a wellness programme, where a few login and notification failures caused most day-one problems.
Questions people ask
Who should test the app?
Someone who has not built it. A colleague from another department finds confusing steps that the builder no longer sees, and uses their own phone model.
How late can content change?
Aim to freeze 48 hours before. After the freeze, allow only corrections to facts, such as a room change, and send a notice so participants know something was updated.
What should I do about a failed check at the last hour?
Decide quickly between fix, work around or remove. If a feature fails and cannot be fixed, switch it off and tell the team rather than leaving a broken screen for participants.
Want this running inside your event app?
Sociana turns lists like this into live screens, requests and reminders for your guests and your desk. A 20-minute walkthrough shows how.