CodeREADr holds the scan records, attendee credentials, and event exceptions an operations team needs at the door. Strawberry can sort those records into an exception queue, while the event operator retains every decision to admit an attendee, change a status, or message someone.
01
A scan record is easier to trust when the surrounding event context is visible.
Strawberry can help turn the CodeREADr screen you choose into an exception review that pairs visible scan information with the relevant attendee or credential context.
02
Attendance reviews should distinguish what happened from what needs a decision.
A companion can organise the selected CodeREADr activity into a concise operational brief, separating observed attendance patterns from questions for the event or access-control owner.
03
Credential checks deserve a reviewable evidence trail.
When a scan or access record needs follow-up, Strawberry can prepare the relevant CodeREADr details and related tabs as a handoff rather than quietly changing someone’s eligibility.
04
Event operations can prepare the next exception pass automatically.
At the opening of each event day, a CodeREADr pass can collect duplicate scans, failed credentials, and attendance exceptions for the responsible operator. It does not change a scan status or send an attendee message unreviewed, because either could wrongly deny access or create a false attendance record.
It can prepare CodeREADr scan exceptions, attendance summaries, and credential-review packets from the operational pages you open.
No. Attendance status, access decisions, and messages to attendees require an accountable operator’s approval.
Yes. Run a CodeREADr exception pass at each scan window to surface duplicate scans, failed credentials, and unresolved attendance cases for the event operator.
No. CodeREADr remains the event scanning system; Strawberry helps turn operational records into a reviewable queue.
CodeREADr Strawberry