# Conference attendance-certificate issuance register

Editable English worksheet. Make a copy for each event or session. This is an organizer-controlled release record, not a certificate generator or proof that a message was delivered. Keep recipient email addresses and other contact details in the restricted delivery system; use a stable reference here.

## 1. Define the claim and source of evidence

| Decision | Event-specific entry |
| --- | --- |
| Event / edition / session | |
| Exact certificate statement | |
| What the statement means (registration, checked-in attendance, or other documented condition) | |
| Evidence source, export date and scope | |
| Recipient groups included / excluded | |
| How group bookings and manual admissions will be reviewed | |
| Issuer name shown on certificate | |
| Wording owner and approver | |
| Batch cutoff and intended release date | |
| Restricted contact-data location and access owner | |

Do not describe a person as having completed training, earned professional credit or demonstrated skill merely because an attendance record exists. Route any such claim to the responsible program owner for separate approval.

## 2. Check the actual specimen

| Proof item | Checked by / date | Exception or change needed |
| --- | --- | --- |
| Short and long display names fit | | |
| Accents and non-Latin names display correctly | | |
| Every certificate wording variant is correct | | |
| Event title, date/session and issuer are correct | | |
| File name and recipient-to-file match are correct | | |
| Email subject, body, link or attachment are correct | | |
| Reader-facing text is available as real text where possible | | |
| Printed proof checked with printer, if applicable | | |
| Second reviewer opened final output | | |

Specimen file or batch reference: **[enter]**

Approved by: **[enter]**  Date/time: **[enter]**

Decision: **Ready / revise / hold**

## 3. Recipient and release register

Use one row per intended certificate. References such as `P-001` are examples, not personal identifiers. Store the actual names and delivery addresses only where access is appropriate for the event.

| Recipient ref | Group / session | Evidence ref + result | Display name checked? | Eligibility decision + reviewer | Proof variant | Batch / sent status | Exception ref / owner |
| --- | --- | --- | --- | --- | --- | --- | --- |
| P-001 | Main conference | CHECKIN-001 / present | Yes | Eligible / AB | Standard | Batch A / pending | — |
| P-002 | Workshop 2 | SESSION-002 / unclear | Yes | Pending / CD | Workshop | Hold | X-01 / CD |
| [add] | | | | | | | |

Decision terms: **Eligible** means the agreed evidence and wording were approved; **Pending** means a named reviewer must resolve a gap; **Excluded** means the event's stated condition was not met or the record was withdrawn. Adapt these labels to the event's process. Do not release Pending rows by default.

## 4. Batch release and delivery check

| Release field | Entry |
| --- | --- |
| Approved eligible count and exact recipient-set reference | |
| Suppressed pending / excluded count | |
| Sender or delivery supplier and approved channel | |
| Internal test recipient and result | |
| Final batch/file reference | |
| Release approver and release time | |
| Submission/sent status evidence | |
| Bounce or failed-delivery review owner | |
| Recipient correction route | |

File generation, queue submission and confirmed delivery are different states. Record only the state your sending system or supplier actually reports.

## 5. Correction and unresolved-case log

| Case ref | Recipient ref | Reported issue | Source checked / owner | Decision | Replacement ref / earlier version status | Recipient update / closed date |
| --- | --- | --- | --- | --- | --- | --- |
| X-01 | P-002 | Session evidence unclear | [record] | Hold | — | [record] |
| [add] | | | | | | |

Recheck the underlying evidence before changing an eligibility decision or display name. Mark a prior version superseded only when your issuance process can do so. Transfer unresolved cases to a named owner and keep this worksheet according to the event's access and retention rules.