Ad-Hoc Participant CSV & Google Sheets Import for Walk-in Winners

The Walk-in Winner Dilemma

At the end of an intense college hackathon or cultural festival: The judges announce that a walk-in team from an outstation college has won 2nd Place in the AI Track. Because they registered in-person at the desk, their details exist only in a separate Google Sheet. * The organizer needs to issue them an official, verifiable digital certificate without disrupting the rest of the event roster.

---

1. Spark’s External Attendee Importer

In Spark (import_external_attendees procedure): Organizers can ingest external attendee rosters directly from RFC-4180 CSV files or Live Google Sheets:

Automatic Column Header Heuristics: Spark’s parser automatically detects and maps column variations: Name: Matches Full Name, Name, Participant, Student, Winner. Delivery Target: Matches Email, E-mail, Email Address, Mail. Institution: Matches College, University, Institution, Department. Phone: Matches Phone, Mobile, Contact, WhatsApp.

---

2. Deterministic Row Fingerprinting

When synchronizing with a live Google Sheet: If you import 200 rows, and later add 15 more winners, naive importers create 200 duplicate records. Spark computes a deterministic SHA-256 row fingerprint for each record. * Re-syncing the sheet imports only the 15 new rows while skipping existing rows, preventing duplicate emails and certificate spam.

Each imported participant receives an official ticket code (TCK-XXXXXXXX), permitting instant certificate rendering and public verification.