A CTO joins, and the hard questions get answers

In mid-August, Trevor joined as CTO, and the first thing he conducted was a full product review. A week later, open questions had real answers:

• Distinct opportunity types. With regard to posting opportunities, the team recognized that there is a material difference between a "need" and an "event," and that one posting type could not capture both. When creating a post, users will be able to differentiate between a Need (for example: internal serving, external volunteering, individual assistance) and an Event (for example: a community worship night). This allows for clear organization and ensures posts reach their desired audience.
• Attendees, not just volunteers. Initially, the team had planned to capture only volunteer vacancies and filled positions. After revisiting the feature and discussing it with multiple pastors, we found that it would be valuable for organizers to identify attendees as well. Churches now have the ability to track expected attendance in real time, and to let the number of volunteers and resources needed scale alongside RSVPs.
• Safeguarding stays human. Screening is a deliberate per-role choice by an organization. Each ministry and church can set custom age requirements, employ integrated verification tools, and require administrator approval. We'll provide you with the tools, while you decide when to use them.

Decisions like these appear small, but are difficult to retrofit. This is why we share our thought process openly as it occurs, inviting your feedback along the way.