Coordinating professional learning records for accountants
Accountants attend partly to keep their learning records in order, so the way attendance is captured can matter as much as the programme itself.
The short answer
Ask the professional body what a valid record looks like for its members: what is recorded per session, who issues proof and by when. Then design check-in, session capture and a reconciliation step to produce exactly that, and tell delegates beforehand what they must do on the day.
The organiser records and reconciles attendance. Whether a session counts for any scheme, and how many hours, is decided by the body or scheme that governs it, not by the organiser.
What a record usually has to answer
A record usually has to show who attended, which sessions and for how long. Some bodies also want a session title, a speaker, a date and a unique reference.
Ask the body for its required fields in writing, because the check-in design depends on them.
Capture options compared
| Method | Suits | Risk | Question to confirm |
|---|---|---|---|
| Day check-in only | Short events with one stream. | Does not show which sessions were attended. | Is day attendance enough for the body? |
| Scan at each session door | Parallel tracks, session-level records. | Queues, scanner failures, volunteers needed. | Who staffs each door and what is the fallback list? |
| Self-declaration form after the event | Low-cost option. | Weak evidence, low return. | Does the body accept it? |
| Sign-in sheets per session | Backup for scanning. | Illegible, slow to compile. | Who keeps and types them up? |
| Exit check for partial attendance | Where minimum time applies. | Delegates leave without scanning. | What counts as partial and who decides? |
Sequence from registration to certificate
- Ask the body which fields are required, which format proof takes and the deadline for issuing it.
- Collect the member or reference number at registration, with the purpose explained.
- Choose a capture method per session type and brief the venue and registration supplier.
- On the day, check in at the start, capture per session if required, and keep a manual fallback list.
- Within a set number of working days, reconcile scans against registration and mark late arrivals and early leavers.
- Send each delegate their record or proof as the body requires, and log corrections in a decision log.
Handling the awkward cases
- Late arrival: ask the body what minimum attendance applies, then record start time.
- Early departure: record whether exit capture is needed.
- Substitution of attendee: decide the rule at registration and keep a change log.
- Delegate who forgets to check in: set a correction route with a deadline.
- Duplicate or missing member numbers: reconcile before records are issued.
Data questions to ask your privacy contact
Ask your own privacy or data contact how long attendance records may be held, who may access them and whether consent text is needed on registration.
Keep the member number and attendance data out of the shared programme files.
Worked example · Fictional example
A fictional two-day accountancy conference
Fictional organisation and figures, for illustration only.
The fictional Persatuan Perakaunan Contoh runs a two-day conference with six sessions across two tracks and 280 registrations. The body asks for session-level attendance and member numbers.
The secretariat scans badges at each session door. After day one, 12 delegates are found to have arrived after the opening session started, and 9 scans are missing because of one scanner fault. Using the backup sign-in sheets, the secretariat completes the 9.
The 12 late arrivals are marked as partial and referred to the body for its rule. Reconciliation is completed within five working days, and each delegate receives a record in the format the body requires.
Use this yourself
Attendance record worksheet
Copy this table, list each session and confirm every column with the body before registration opens.
| Session | Date and time | Required fields (confirmed with body) | Capture method | Fallback | Reconciliation owner and date | Proof issued by | Proof deadline |
|---|---|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- One stream, day-level attendance is enough and the body accepts it.
- Small numbers and a secretariat that can reconcile by hand.
- Little or no variation in who attends which sessions.
Outside planning help earns its fee when
- Parallel tracks with session-level records for hundreds of delegates.
- Several bodies or schemes with different requirements.
- Reconciliation is slipping and nobody owns corrections and proof issuance.
Need help with attendance records on the day?
A conference project lead can confirm the body's required fields, choose the capture method per session, brief the registration supplier and volunteers, run the fallback lists and own reconciliation and corrections through to issuing proof. The body keeps decisions about what counts. Send your programme and expected numbers to scope the work.
Questions organisers ask
Who decides whether a session counts?
The professional body or scheme that governs it. The organiser captures and reconciles attendance and passes on what the body requires.
Is a scan at the door better than a sign-in sheet?
Scans are faster to compile, but a sheet is a useful fallback. Many events use both.
What if a delegate arrives late?
Ask the body what minimum attendance applies and record the arrival time so the question can be answered later.
How long should records be kept?
Ask your privacy contact and the body, and write the answer in the registration notice.
Related resources
- Planning concurrent audit and accountancy conference tracks
- Managing accounting software sponsors alongside independent sessions
- Planning practitioner case-study sessions with confidential examples
- Coordinating member-firm group bookings at a professional conference
- Event brief builder
- Outsourced conference project management
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.