Where spreadsheets work
A small, short-lived list with one owner and few dependencies can be practical. CSV also remains useful for migration, reconciliation, and accessible data export.
Where the model breaks
A row cannot naturally represent multiple service requirements, versioned plans, provider acknowledgements, approvals, disclosure packs, attendee confirmations, incidents, separate evidence sources, and superseding corrections.
A safer migration path
Start with the current sheet, minimize fields, map columns, preview cases, isolate errors, retain source keys, import an auditable batch, and continue using exports for authorized reporting.
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
Do I need to abandon CSV?
No. Manual entry and CSV import are core activation paths, and scoped CSV export remains useful.
What is the biggest spreadsheet risk?
It is the combination of unclear ownership, unrestricted copying, and hidden state—not one formula error.
When should a team move?
When requests have multiple services or owners, cross event cutoffs, provider handoffs, private notes, plan versions, attendee confirmation, incidents, or audit requirements.