To run attendance for a multi-day conference, model each day, key session and meal as its own activity, set a daily time window and eligibility for each, scan with one steward per lane, read the numbers every evening and export a final record of unique accepted attendance per activity.
What makes multi-day attendance different
A one-day event has one question: who came? A three-day conference has many. Who came on Day 1? Who stayed for the afternoon plenary? Who attended the workshop that carries a certificate? Who used the lunch on each day? A single “checked in” flag cannot answer them, and a paper sign-in sheet cannot be reconciled by Friday.
The other challenge is endurance. Stewards tire, signs fall off walls, and by Day 3 half the audience has lost interest in scanning. A good system makes scanning quick, boring and consistent, so it survives the third morning.
Step 1: write the list of things you will count
Before you configure anything, write down the activities that matter, in the order they happen. For a three-day conference it might be:
| Day | Activity | Why you count it |
|---|---|---|
| 1 | Registration and welcome | Entry record |
| 1 | Opening plenary | Core attendance |
| 1 | Gala dinner | Catering and eligibility |
| 2 | Morning breakout A, B, C | Session attendance, seats |
| 2 | Lunch | Catering |
| 3 | Closing and awards | Final record |
Resist the temptation to count everything. Each activity is a scan the delegate must make and a number you must read. Count what you will use.
Step 2: choose the grain
Decide how fine the record should be. A day-level activity says “attended Day 2”. A session-level activity says “attended the 11 am breakout in Hall B”. Use sub-activities where a step has parts, for example a gala with arrival and dinner. A finer grain gives more insight and more work; start with day-level plus a handful of sessions where attendance matters, such as certified workshops.
Step 3: set rules per activity
For each activity, decide when it opens, which groups are eligible, whether a ticket is needed, whether repeat scans are allowed and whether steps must be completed in order. A morning session might open thirty minutes before the start and close at its end. A gala might be for delegates and speakers but not exhibitors. A paid workshop might require a ticket.
Write the rules in a table so that the organising team reads the same thing as the person configuring the app.
Step 4: issue passes and brief delegates
Each delegate has a personal pass in the app, and the same identity resolves across entry, exhibitor scans and activity QRs. Tell delegates the first day, in the invitation and at registration, how to open it: Entry Pass on Home, or the QR in Profile. Tell them it will be needed again, and explain why: “scan once per session so that your certificate and lunch are recorded.”
India had 1.03 billion internet users in October 2025 (DataReportal, 2026), so most delegates will be able to open the app, but add a plan for those who cannot.
Step 5: staff the lanes for the day, not the week
Staffing changes each day. Day 1 has the biggest crowd at registration; Day 2 has the breakouts; Day 3 is the smallest audience with the most important record. Brief stewards each morning on what is different today and which activities are open. A steward who knows that the lunch scan is once only will not wave through a second.
Rotate stewards so that nobody scans for six hours, and keep a lookup lane on every day.
Step 6: read the numbers every evening
At the end of each day, check three things. First, the accepted attendance per activity against the expected head count. Second, the attempts against accepted, to see where scanning is slow or confused. Third, the exceptions you added manually, with notes. Share a two-line summary with the organising team: “Day 1: 412 of 480 at plenary; 38 lunch repeats flagged; two manual adds.”
If a number looks wrong, fix the cause tomorrow. A low count in one hall may mean a sign is missing, not that people are absent.
Step 7: handle the late joiner and the early leaver
Some delegates arrive on Day 2 and some leave on Day 2 afternoon. Your system should treat that as normal. A late joiner is checked into the activities they attend; an early leaver simply has no record for the later ones. Do not “fill in” attendance to make a certificate list look neat. If you need a minimum attendance for a certificate, say so on the first day and report from the data.
Step 8: export the final record
After the closing, export attendance for every activity. Keep a record of the definition you used, such as unique accepted attendance, and of the final list of exceptions. Store with the date and the owner. For certificates or CPD claims, use the export, not memory.
Your report might read: “Day 1 plenary: 412 unique accepted attendances of 480 registered (86 per cent), measured at 11:30 on 12 March.” Always include the denominator.
Common mistakes
One activity for the whole conference. You cannot read Day 2 from it.
Leaving the rules the same each day. Windows and eligibility change; update them.
Forgetting the lookup lane. Phones die, especially on Day 3.
Reporting scans as attendance. Report unique accepted attendance.
An evening review template
At the end of each day, spend ten minutes with the duty manager and one steward from each lane. Read three numbers aloud: accepted attendance for the main session, the number of manual additions and the attempts-to-accepted ratio. Then ask two questions. What slowed us down today? What will be different tomorrow? Write the answers on one line each and share them with the whole team before the first session on the next day. Over three days, the notes become a small playbook for your next conference, written in your own venue and with your own people.
How Sociana handles this
QR attendance and activities models attendance as activities with optional sub-activities, each with time windows, group eligibility, ticket requirements, repeat limits and ordering. The entry pass and personal QR gives each delegate one identity for all scans. Agenda and show flow holds the programme, in-app mobile dashboards show live counts to Owners and Managers, and reports and exports deliver attendance with scanner and time.
EEMA Connect, the official Sociana app for every occasion run by the Event and Entertainment Management Association, offers attendance and trigger notifications as organiser tools, a Member Pass on Profile and a NOW LIVE strip for sessions in progress. Read the EEMA Connect case study and the APMI case study.
Frequently asked questions
How many activities should a three-day conference have?
As many as you will read. A dozen is common: entry, main sessions, meals and a few workshops.
Can delegates check themselves in?
Where self check-in is allowed on an activity, yes, under the same rules staff scanning would apply. Decide per activity.
How do we give certificates based on attendance?
Use the unique accepted attendance export for the relevant workshop, and agree a minimum before the event.
What if a delegate forgets to scan?
Add a note and a manual record through the desk, and keep the exceptions list for the report.
Related reading
Glossary: attendance activity, sub-activity, self check-in, attendance rule. Occasion hubs: conferences, association events and conferences with room booking. See templates and checklists for an activity planner.