Prepare the minimum dataset
Include stable event and source references, requester contact, affected dates or sessions, request fields, communication preference, consent, submitted time, and source update time. Exclude unused columns.
Preview before writing
Map columns, classify fields, validate formats, show new and changed records, flag duplicates, isolate invalid rows, and require a deliberate import confirmation.
Make retries deterministic
Use a batch identifier and source key so the same file cannot silently create duplicates. Preserve row-level results, actor, time, source hash, errors, and reversal status.
Keep decisions human and evidence explicit
Evencue records decisions made by authorized organizers and coordinates their event-specific consequences. It does not determine legal reasonableness, medical validity, entitlement, or venue certification. Provider and onsite views receive only the information required for their task.
What teams usually ask
Can CSV be the primary setup method?
Yes. Evencue’s core activation must work through manual entry and CSV import; integrations are optional accelerators.
What happens to invalid rows?
They should be excluded from the write, reported with precise row-level errors, and safely retryable after correction.
Can an import be reversed?
A batch should be reversible when records have not progressed into conflicting work, with the reversal and any exceptions recorded in audit.