Good batches start
with a clean list.

Prepare your Excel or Sheets file

Keep one header row and one person per row. Use columns such as Full name, Role and ID number. Remove totals, merged cells and notes above the header. Export the relevant worksheet as UTF-8 CSV; direct XLSX import is not supported by the Android preview.

A CSV does not store spreadsheet column types. Before editing the downloaded sample in a spreadsheet, import its ID number column as text. Check the resulting file so leading zeros survive.

Map, then inspect

In the Android import preview, choose the CSV, map each column to its intended field and inspect the staged records before committing. Check duplicate numbers, blank names and long values. Extra data should map to the correct custom field rather than being squeezed into the role.

The implementation currently guards imports at 5,000 rows, 10 MiB, 64 columns and eight extra fields. These are resource limits, not a promise of tested speed on every device. Committing an import is Studio-gated, and production billing is not yet configured.

Keep photos unambiguous

Use a deliberate file-naming convention when preparing a photo set. Review any missing, duplicate or ambiguous matches rather than assuming a similar file name belongs to the right person. The downloadable CSV contains no photographs.

Review the output in smaller batches

Check a few cards before exporting the whole roster. The current Android export guardrail is 500 people per job, with PDF output split into chunks of up to 100 cards. Larger rosters need separate export jobs.

Download a separate native sample sheet to understand the print sequence. Those PDFs use their own fictional fixture roster; they are not the output of the three-row CSV above.