What makes attendance evidence defensible?
A register is not evidence because it exists. It is evidence because someone independent can test it. Here is the minimum chain a SETA auditor should be able to follow.
Most providers can produce an attendance register. Far fewer can answer the follow-up questions without leaving the room to fetch another file.
A defensible record has four properties: it is linked, contemporaneous, tamper-evident and reproducible.
1. Linked
Every attendance event should resolve to a learner, a cohort, a venue, a programme and the person who captured it. If the register is a spreadsheet assembled from three sources, the link is a person’s memory. That is not a link; it is a story.
The practical test: pick a random row in the register and ask for the learner’s consent record, the venue geofence and the device that captured the check-in. If those are in three systems with no shared identifier, the record is weakly linked.
2. Contemporaneous
An event captured at 07:58 on the day is stronger than a register completed on the 30th. The platform records the capture time, the device time, any clock drift and the sync time. A verifier can see whether the record was created near the event or reconstructed later.
Offline capture is not a weakness if the device records a monotonic batch sequence and the server stores a receipt. It is a weakness if the batch can be edited after the fact with no trace.
3. Tamper-evident
A hash column is not enough. The hash has to be part of a chain: each entry includes the previous entry’s hash, and the chain root is sealed daily. Changing one row changes every subsequent hash and breaks the seal.
The public verification endpoint is the second half of this property. It must resolve a hash against the sealed ledger. A verifier that returns “verified” for any well-formed string is worse than no verifier, because it creates false assurance.
4. Reproducible
Given the same learner, month and policy, the register should be reproducible. That means the calculation rules — public holidays, payable days, SD5 hour limits, approved leave — are recorded with the output. If a stipend is disputed, finance should be able to show the arithmetic, not just the total.
The auditor’s walk
A useful exercise is to give an auditor a learner ID and ask them to walk forwards:
- Find the enrolment and consent record.
- List the attendance events and their verification state.
- Show the workplace attestations.
- Show the stipend calculation and the lock snapshot.
- Verify the evidence pack hash against the public endpoint.
If any step requires a phone call, the chain has a gap. The gap is the thing to fix before the audit, not during it.
Where RemoteRegister fits
The platform links those steps to one learner record, chains the audit entries, seals daily Merkle roots and exposes a verification endpoint that only resolves hashes present in the sealed ledger. It does not make a weak process strong; it makes a good process testable.
If you want to test the chain, bring a real cohort and a real question to a demo. That is a more useful session than a feature tour.
This note describes product design and South African statutory context. It is not legal advice. For an assessment of your own evidence process, book a working session.