Registration Belongs to No One—And That's Exactly the Problem
Photo: Dialh, CC BY 4.0, via Wikimedia Commons
Ask a mid-sized US nonprofit or professional association who owns its registration process, and you'll get a shrug dressed up as an org chart. Marketing promotes the event. Programs design the agenda and draft the form questions. IT provisions whatever platform survived the last procurement cycle. Finance reconciles whatever revenue arrives. Everyone touches registration; no one is accountable for it.
This is not a staffing oversight. It is a structural flaw, and it quietly taxes nearly every sign-up your organization processes.
The Turf War Nobody Declared
The problem begins with reasonable people making locally rational decisions.
Program staff want rich data. They add questions—dietary needs, session preferences, demographic reporting, emergency contacts—until the form resembles an intake interview. Each addition is defensible in isolation. Together, they're an abandonment machine.
IT wants stability and security. They favor platforms that integrate cleanly with existing infrastructure, which may or may not be platforms that registrants find usable. When the system fails at 11 p.m. before an early-bird deadline, IT's job is to restore service—not to ask why the deadline architecture invited a midnight stampede in the first place.
Finance wants clean reconciliation. Payment fields, refund policies, and tax treatment get engineered around the general ledger, sometimes at direct odds with the registrant's experience—see: the three-screen checkout that exists because two departments couldn't agree on cost-center coding.
Each department optimizes its slice. Nobody optimizes the whole. And because registration sits at the intersection of all three, the failure modes are predictable: forms that leak conversions, systems that break under load, revenue that arrives late or misallocated, and—when leadership finally asks hard questions—a conference room full of fingers pointing in a circle.
The Case for a Designated Owner
We'd argue something unfashionable: registration is a core business process, not a task, and core business processes need owners. Not a committee. Not a matrixed working group. A named individual with the authority to make binding decisions across departments and a mandate measured in outcomes—completion rates, time-to-confirmation, revenue captured, complaint volume.
This role, whether titled Registration Operations Lead or something else, would look like this in practice:
A single view of the funnel. One person sees the entire journey—from promotion click to confirmed payment to post-event data—and can identify where registrants stall without convening three departments to reconstruct the story.
Authority over form design. Every question added to a registration form should have to justify itself to someone whose metric is completion, not data collection. That someone is the owner.
Veto power over platform decisions. Tool selection currently happens in IT procurement or finance budgeting, with registrant experience as an afterthought. The owner should hold a formal seat at that table.
A direct line to leadership. When sign-ups stall, executives shouldn't have to adjudicate between departments. They should call one person who can explain what's happening and what's being done.
The Objection, and the Answer
The standard objection is that no one has bandwidth for another role, and that registration is "everyone's job." But everyone's job has a well-documented fate: it becomes no one's job. Organizations routinely appoint owners for smaller-stakes processes—facilities access, expense approval—without controversy. Registration, which in many organizations represents the single largest recurring interaction with members and customers, deserves at minimum the same governance.
The alternative is the status quo: a process assembled by committee, maintained by accident, and diagnosed by blame. When your next registration window opens badly—and the data says eventually one will—the question won't be whose fault it was. It will be why nobody was ever in charge of making it work.
