Catch bad rows before they become certificates
The import review flags missing names, invalid emails, and rows that do not fit the mapped fields, so problems are fixed before the batch is issued.
An event spreadsheet is assembled by several people, often late at night. A blank name, a missing email, or a row shifted one column to the left is normal. Finding it after the send is not.
The import review now checks the rows before they become recipients.
What gets checked
The review looks at the mapped fields and flags rows that cannot become a usable certificate: a missing recipient name, an email that is not an address, a required Attribute with no value, or a row that does not match the expected columns. It also identifies duplicates against the existing list.
You can fix a row in the review, skip it, or correct the source file and re-import. The batch is not published from the import screen; it is prepared for review under Recipients.
A practical import checklist
Export the list with a header row. Keep one person per row. Use a single email column rather than mixing personal and college addresses. Put the values the certificate needs into named columns and map them deliberately. Check the first five rows and the last five before trusting the whole file.
The boundary
Validation catches format and completeness problems. It does not know whether someone attended, paid, or completed the programme. That check still belongs to the event team, and it is the reason review before issuing exists.
Related