Four officers, one club
Whoever gets to the room first runs check-in — no shared password, no bottleneck.
Run it as a team. Survive exec turnover.
Invite co-officers by email, transfer ownership in one tap when new exec takes over, gate check-in to your campus domain, and kill leaked QR codes before they cost you a clean roster.
The short answer
Attendance-HQ separates club owners from officers: owners invite and remove officers, transfer ownership, and run retention purges, while officers create events, run check-in, correct roster entries, and export reports. Roster access is scoped to the club's members, campus email domains can be enforced, and every change is written to an audit log.
How it works
Three steps, every meeting.
1
Invite your exec
Add officers by the email they already sign in with. No extra seats, no cost.
2
Lock down check-in
Set allowed campus email domains and regenerate QR tokens whenever a link leaks.
3
Hand off in May
Promote next year's president to owner. You stay on as an officer.
What you get
Tuned for this exact job.
Owner vs officer
Officers run meetings; only the owner deletes the club or transfers it.
Invite by email
Add co-officers using their existing host account email.
Ownership transfer
One tap at exec turnover. Nothing gets re-created or lost.
Campus domain gate
Only your school's email domains can check in to your events.
QR leak controls
Regenerate the event token to invalidate a forwarded screenshot.
Scoped roster access
Member data is visible only to that club's owner and officers.
Audit log
Manual adds, removals, and profile corrections all leave a trail.
Retention & purge
Rolling 730-day window plus an owner-run delete-older-than tool.
Real scenarios
Built for the way you actually work.
Spring exec handoff
Outgoing president promotes the incoming one and stays on to help transition.
A QR code hits the group chat
Regenerate the token mid-meeting and remote check-ins stop instantly.
Frequently asked questions
Can multiple officers manage attendance for the same club?
Yes. The club owner invites co-officers by the email they already use to sign in. Officers can create events, run check-in, correct roster entries, and export reports. Only the owner can delete the club or transfer ownership.
How do I transfer club ownership to next year's exec?
From the club page, the current owner promotes an existing officer to owner. The former owner automatically becomes an officer, so nothing is lost during exec turnover and no data has to be re-created.
Can I restrict check-in to my campus email domain?
Yes. Set the allowed email domains for your university and anyone using a different domain is rejected at check-in — so guests, alumni, or typo'd addresses never land in your official roster.
What happens if our QR code leaks in a group chat?
Regenerate the event's QR token. The old link stops working immediately and a fresh code takes its place, so a screenshot that got forwarded can't be used to check in from a dorm room.
Who can see member data?
Roster access is scoped to the club's owner and officers. Emails are masked in the ops view, every roster change is written to an audit log, and nobody outside the club's membership can read its attendance.
Is Attendance-HQ FERPA-friendly?
Attendance-HQ is designed with FERPA in mind: minimum-necessary data collection, role-scoped roster access, encryption in transit and at rest, a rolling 730-day retention window, and an owner-run purge tool. See the Privacy page and the DPA documentation for detail.
Can I fix a member's misspelled name or email?
Yes. Officers can correct a member's name or email directly from the event roster. The correction is validated against your allowed domains and recorded in the audit log.
Explore more