Setting renewal periods and expiration

Edited

Overview

The renewal period defines when a sponsorship is locked to first-rights holders versus open to the public. Chamberly evaluates these dates daily through an Inngest cron at midnight UTC and transitions availability automatically.

Before you start

  • Decide on a renewal start date (when first-rights window opens).

  • Decide on an expiration date (when unclaimed rights flip to public).

  • Confirm the chamber timezone in Settings > General.

Step-by-step

  1. Open the sponsorship under Sidebar > Sponsorships.

  2. Click the First rights tab and scroll to the Renewal window section.

  3. Set the Start date. Until this date the sponsorship sits in not_yet_available.

  4. Set the Expiration date. After this date unclaimed rights move to public.

  5. Optionally enable the Reminder email toggle to notify holders before expiration.

  6. Click Save. The schedule preview confirms when each transition will fire.

How transitions fire

  • Daily Inngest cron at 00:00 UTC evaluates every sponsorship.

  • If start date passed and availability is not_yet_available, it flips to first_rights.

  • If expiration passed and availability is first_rights, it flips to public.

  • If a holder claims their full quantity early, that line is marked claimed but the window stays open for other holders.

Tips & best practices

  • Give holders at least 14 days in the renewal window — shorter windows feel rushed.

  • Stagger renewal windows across events so your inbox isn't slammed all at once.

  • Use the reminder automation 7 days and 1 day before expiration for the highest claim rate.

FAQ

Can I extend the expiration after the window opens?
Yes. Update the date and the cron picks up the change on the next run.

What timezone are dates evaluated in?
The cron runs in UTC. Dates are stored as date-only and evaluated against UTC midnight.

Related articles

  • First-rights expiration reminder automation

  • What first rights are

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.