Enrollment feature inquiry/advice

Hi,

We’re currently evaluating Apricot’s new enrollment feature and I’d really appreciate some real-world feedback from teams already using it.

Right now, our main concern isn’t just functionality but how it actually performs once it’s rolled out at scale—especially during onboarding and the first few weeks of staff adoption.

A few specific things we’re trying to understand:

• How smooth has the transition been from your previous enrollment process?

• Did staff find it intuitive, or was there a noticeable learning curve?

• Any unexpected issues with data entry, tracking, or reporting after switching?

• Most importantly, what did onboarding look like for your staff—what worked well and what caused friction?

We’re a mid-sized team, so consistency and ease of training new staff is a big factor for us. Any honest experiences (good or bad) would really help us make a more informed decision for next school year.

Thanks in advance!

We use the program enrollment feature in Apricot!💥We LOVE it! I have a bar graph bulletin on everyone’s home screen which allows them to see program enrollments by person, but also by program! 

We used to have a Tier 2 program enrollment form created that teams had to fill out when enrolling a participant in their program. Now they go to their doc folder and create a program enrollment that way! I’ve gotten a lot of positive feedback from that change.

My team loves it and it seems so much easier for them as it’s less forms to fill out. On the reporting side, I find it easier because you don’t have to link that Tier 2 form to the report, you just link the program enrollment. 

The only downfall of the program enrollment feature is that the entry is very streamlined. (I’m sure for great purpose) but if you have extra questions you need asked -- you would have to have a form for that or include them on a profile form, etc. 

My dream is that if a program enrollment is open for a participant on a team - that team member becomes “on their team” and adds the participant to the team member’s caseload. It seems like we have to do a bunch of manual backend managing of caseloads, program enrollments, etc and if they all worked together -- that would be extremely handy for everyone involved.