Clear expectations, easier events
How JYC registration works
JYC’s website is the official event record. OneTable, Eventbrite, ShulCloud, and similar services may securely complete registration or payment. The event page tells you which service applies and who to contact.
Provider selection
The event page—not a blanket rule—is authoritative.
JYC does not assign OneTable, Eventbrite, ShulCloud, or another service solely because an event is Shabbat, free or paid, or above a presumed attendance threshold. For every confirmed event, the registration owner records the service after the venue or host confirms payment, funding, capacity, cutoff, and security needs. An earlier roughly 30-person threshold and any assumed ShulCloud configuration are not standing JYC rules.
Check the JYC event page
Confirm the date, time, location, price, deadline, host, food/kashrut information, accessibility route, and cellphone or photography policy.
Register using the named service
Use your own name and email. Complete every required field and keep the confirmation. Registrations are not transferable; substitutions are not allowed for security reasons.
Pay only through the stated method
If payment is required, the amount appears before submission and the provider issues the receipt. JYC does not ask you to send card details by email or through the website contact form.
Cancel in both places
If plans change, cancel with the RSVP provider and email jycnewjersey@gmail.com before the event’s deadline so another person can use the place.
Refunds follow the event rule
Eligibility, deadlines, and any nonrefundable costs are stated on the event page or checkout. The payment/refund owner reconciles approved refunds through the original payment service.
Check in under your registration
The attendance owner uses the named-registration list, records aggregate attended/no-show totals, and protects attendee information. Request an accommodation privately before the event when possible.
JYC closes the loop
Within 48 hours, the reporting owner reconciles registrations, payments/refunds, attendance, referrals, regional reach, email results, and follow-up coverage. WordPress stores aggregate counts only.
Questions go to the event owner
Use the designated host on the event page for event-specific answers. Use the JYC inbox for cancellations, payment/refund questions, privacy concerns, or accommodations.
Who owns each handoff?
| Role | Before the event | After the event |
|---|---|---|
| Event owner / host | Confirms program, venue, food/kashrut, accessibility and attendee communications. | Documents issues and lessons learned. |
| Registration owner | Publishes the external RSVP link and monitors capacity, deadline and cancellations. | Exports the final registration total. |
| Payment / refund owner | Confirms price and payment method. | Reconciles paid orders, approved refunds and net revenue. |
| Attendance / reporting owner | Prepares the named check-in list and no-substitution process. | Records aggregate attendance, no-shows, referrals and regional reach within 48 hours. |
| Follow-up owner | Prepares reminders and any survey. | Records Mailchimp engagement and sends attendee follow-up. |
Private accommodation request: Tell JYC what would help you participate.
Event questions, cancellations or refund questions: jycnewjersey@gmail.com.
Event-specific controls
Capacity, partners, and follow-up stay explicit.
Capacity and waitlists
Each confirmed event records its own capacity statement, waitlist process, registration cutoff, export cadence, and responsible owner. A provider name or past attendance threshold is never treated as a standing rule.
Payments remain external
Card and bank details stay with the event’s authorized payment service. JYC custom website code does not collect, store, or transmit payment credentials.
Co-hosted listings
Before publication, partners must identify the registration authority, payment/refund authority, attendee-data controller, and day-of incident lead. Unconfirmed responsibilities remain visibly unresolved.
Post-event evidence
Named check-in, private feedback, referral source, repeat behavior, and public testimonial permission remain distinct. WordPress reporting exports use de-identified evidence fields and aggregate event totals.
