Events

Use Givebear Events when attendance matters. A campaign asks for a donation. An event asks someone to register, buy a ticket, answer questions, show up, and possibly check in at the door.

Event lifecycle

Most event work follows this sequence:

1. Create the draft event and enter the public basics.
2. Add photo, story, date, time, and location details.
3. Decide whether the event is free, paid, or ticketed in multiple ways.
4. Create ticket types.
5. Add registration form questions.
6. Review the public page.
7. Publish the event.
8. Share the event page or embed it on the website.
9. Monitor registrations.
10. Run check-in.
11. Reconcile attendance, payments, refunds, and follow-up.

The dashboard route structure includes dedicated event edit steps for details, photo, tickets, form, and review. Keep those concepts separate when training staff.

When not to use Events

Do not use Events for every calendar item. Use a calendar surface when people only need to see a schedule. Use Events when you need registration records, attendee answers, tickets, payment, or check-in.

What makes a good event page?

A good event page answers:

• What is happening?
• Who should attend?
• When and where is it?
• What does it cost?
• What information will registration collect?
• What happens after registration?
• Who should a staff member contact if something looks wrong?

Event team checklist

Before publishing, assign owners for:

• Public event content.
• Ticket and pricing decisions.
• Form questions.
• Refund or cancellation policy.
• Website embed or sharing.
• Check-in staffing.
• Post-event reporting and follow-up.