FotoFitEvent teams often have one attendee database but many output types. Speaker cards, badges and completion certificates should reuse approved data while remaining separate templates and jobs.
Model assets separately
| Asset | Typical fields | Important check |
|---|---|---|
| Speaker card | Name, title, company, photo, session | Portrait crop and title length |
| Attendee badge | Name, organisation, role, identifier | Print dimensions and QR purpose |
| Certificate | Name, event, date, credential ID | Spelling, issuer and verification |
Use the same stable identifiers
A stable attendee or recipient identifier makes it easier to reconcile outputs and correct one record. It should not expose unnecessary personal information when printed or embedded in a public URL.
Preflight dynamic photos
- Confirm every URL resolves to an actual image.
- Check consent and usage rights.
- Test portrait and landscape sources.
- Avoid links that expire before the job runs.
- Replace oversized originals when possible.
Do not mix approval states
Generate from an approved list. If event registrations are still changing, import a new snapshot for the next job rather than assuming a running job follows live spreadsheet edits.