# data[].attributes.body
Improved templates and communication around Channel scholarships.

# data[].attributes.body
Extremely valuable! Prepared counselors with specific details and allowed for Q+A.

# data[].attributes.body
Constant communication across teams via Slack, Asana, meetings, to communicate time sensitive info, changing requirements, etc

# data[].attributes.body
I think the relationship between both teams has continued to improve-- communication, escalations, alignment on goals, etc. Good progress this cycle.

# data[].attributes.body
everyone worked really well together and stayed in touch between channel ops meetings - didn't feel like anything major fell through the cracks!

# data[].attributes.body
Real time updates, lots of visibility, improved communication!

# data[].attributes.body
Collaboration across stakeholders greatly improved YoY. Communication and alignment, specifically.

# data[].attributes.body
visibility into who, how many, who has enrolled etc

# data[].attributes.body
More channel partners in "repeat" cycles and were experienced with having attended past Open Houses, Summit, etc

# data[].attributes.body
Frequency, attendance, partner participation, organization, and increased admissions SAC participation for answering questions (as we had more sessions)!

# data[].attributes.headline
Big impact from late launches from previous cycle

# data[].attributes.subject
Big impact from late launches from previous cycle

# data[].attributes.body
IU, USC

# data[].attributes.body
Was able to confirm open house timelines with advanced notice for annual strategy sessions to discuss live in the room with partners

# data[].attributes.body
Very organized, with great presenters and breakout rooms. A lot of support from staff and Channel partners.

# data[].attributes.body
Course Guides were incredibly helpful. Onboarding was able to redirect students/parents to those resources

# data[].attributes.body
This year they were much easier to manage, and dynamic content worked correctly, allowing for much more scalable work in the future.

# data[].attributes.body
When partners are open to it, having a channel contact for prospective students was extremely valuable as many nearly demanded it to get them over the line.

# data[].attributes.body
Tested different areas to improve immediately or to better plan for future cycles

# data[].attributes.body
Just having updates on what might be coming, updates on who was pulled and enrolled in their channel school, has been very helpful

# data[].attributes.body
continuous improvement - each cycle get better and better

# data[].attributes.body
Cutting down on redundant programs (i.e. rolling UConn and Syracuse Engineers into their flagship programs) -and- adding programs for new audiences (UConn addition of Year program)

# data[].attributes.body
Ability to customize content for partners, set up custom journeys for capacity programs, and accommodate minor dynamic content requests.

# data[].attributes.body
Being able to share the email/text journey with partners allowed them to create parallel journeys to students/families.

# data[].attributes.body
Ability to find most if not all pertinent partner program data in Salesforce!

# data[].attributes.body
Better usage of SF as the source of truth with partner programs, which better supported information sharing between Rev Ops, Enrollment, etc.

# data[].attributes.body
Reduced the number of places AMs were expected to 'report out' and log different channel program details

# data[].attributes.body
-From an AM standpoint, I preferred working with cross-functional teams with SF as the 'source of truth' for numbers and most info (although Asana is still best for project management tasks!).

# data[].attributes.body
Loved having additional information about partners/programs in Salesforce, rather than solely Asana

# data[].attributes.body
Additional comms saw a boost in attendance and day-of sign ups

# data[].attributes.body
specifically the part where we assigned specific Verto team members to various Verto breakout rooms to assist in the chat. The creation of a doc with FAQs and links to pull from and easily copy paste into the chat was a huge help, too

# data[].attributes.body
Worked really well as a source of truth this cycle

# data[].attributes.body
The articulation workbook made articulation data much more consistent. The google sheet allowed me to monitor progress and help partners who had questions.

# data[].attributes.body
Loved having additional focus on what the partner can do to improve enrollment post launch (open house emails, waitlist releases, etc)

# data[].attributes.body
Evidence of deepening trust and relationship between partners & Verto from channel open house presenters/presentations to willingness to connect with Verto students at different points throughout the cycle(advising), information alignment, etc.

# data[].attributes.body
Specifically want to highlight Meghan and Jenn for incredible communication prior to launches! Thorough articulation of what to expect and specificities of the program.

# data[].attributes.headline
Working with Israel for Channel Academics

# data[].attributes.subject
Working with Israel for Channel Academics

# data[].attributes.body
Working with Israel on course registration guides and articulation follow-up was organized and went well! Thanks, Israel!

# data[].attributes.body
Increase in total Opportunities.

# data[].attributes.body
While a lot of work and time, the weekly meetings provided a critical space for key stakeholders to align, which created less "spin" on key issues that would be identified.

# data[].attributes.body
We don't control our partner timelines.

# data[].attributes.body
Staffing for a short timeline without having the inputs is challenging.

# data[].attributes.body
The plans we set with the partner and intentions we have from our fall strategy sessions to how things actually play out with their applicant pool don't always align as we'd hoped!

# data[].attributes.body
It's challenging when a partner sends less students than we had originally anticipated/they had estimated at the top of the cycle. The challenge here with the 'estimated audience size' field in SF potentially being seen as a guaranteed audience number rather than a best case scenario estimate.

# data[].attributes.headline
Fluctuating Launch Dates/Inability to Plan

# data[].attributes.subject
Fluctuating Launch Dates/Inability to Plan

# data[].attributes.body
A "normal" situation for us, but it makes staffing challenging when the launch dates change. I know we're a bit at the mercy of the partners, which is why real-time updates were so helpful.

# data[].attributes.body
I know we can't control these things

# data[].attributes.headline
Alignment on how partner program fields are used

# data[].attributes.subject
Alignment on how partner program fields are used

# data[].attributes.body
Disconnect between teams on how to use partner program fields and interpret information.

# data[].attributes.body
During the articulation process, lots of partners stated that the syllabi linked on the main list didn't have the information they needed to articulate courses effectively. I had to spend lots of time looking for onsite syllabi or trying to develop syllabi for new courses on the fly.

# data[].attributes.body
Due to very quick/rushed implementation of SFMC, we had multiple SFMC fires during the cycle

# data[].attributes.body
As the migration was such a large undertaking, timelines got delayed and butted up against channel launches. This led to lots of bumps along the way and discovering issues and bugs etc. as channel launches began and volume increased.

# data[].attributes.body
Part of our business model is that these are their students first to make their fall enrollment, and that is why we gain the opp to yield more students. So, we need to continue to understand this dynamic. Some years will be better than other years.

# data[].attributes.headline
Additional resources would be beneficial for specialized channel programs

# data[].attributes.subject
Additional resources would be beneficial for specialized channel programs

# data[].attributes.body
MANY students in specific STEM programs or Business that would benefit from more resources about how Verto would impact their trajectory, i.e. Kelley Business School

# data[].attributes.body
Channel student transcript collection this cycle is night and day compared to last cycle

# data[].attributes.body
USC/Indiana as examples with School specific limitations for enrollment weren't clear at the beginning of launch. Having additional clarity would be very helpful.

# data[].attributes.body
Prior cycle partner data and top of funnel data not in Salesforce and makes it difficult to look back and compare.

# data[].attributes.body
In some cases, there were last minute changes in requirements for launches (requiring updates to minisites, comms, or rushed turnaround of requests)

# data[].attributes.body
Dear Colleague letter/political climate had a some partners rethinking strategies post-campus strategy visits.

# data[].attributes.body
As we continue to build out marketing asks, and growth expectations (e.g. adding more programs), we are pushing partners hard and need to continue to balance critical asks to ensure we are making the most of our requests. We are pushing the line here with a number of partners. As Kelly Walter from BU tells us regularly, Verto's enrollment goals aren't BU's enrollment goals.

# data[].attributes.headline
Missing team members made it challenging

# data[].attributes.subject
Missing team members made it challenging

# data[].attributes.body
UP Team rose to the moment to meet the challenges.

# data[].attributes.body
Limited resources across multiple teams, requiring a lot of prioritization and reprioritization to focus on the most essential work and minimizing the ability to do more enhancement-focused work -- including limited tech and marketing resources.

# data[].attributes.headline
Presentation/transparency of program info for students & parents

# data[].attributes.subject
Presentation/transparency of program info for students & parents

# data[].attributes.body
I learned the hard way this cycle that when info is dug down deep in FAQs, this can lead to issues (i.e. whether participating in the program guarantees admission to intended major). More on this in Areas of Improvement (it's an easy fix!).

# data[].attributes.headline
Too much micro management from the very top getting into the dirt below the weeds

# data[].attributes.subject
Too much micro management from the very top getting into the dirt below the weeds

# data[].attributes.headline
Standardized method of recording small details for channel programs

# data[].attributes.subject
Standardized method of recording small details for channel programs

# data[].attributes.body
This can be an admissions responsibility in tandem with UP, but we had amazing pre launch meetings that could benefit from a standardized way of recording all the valuable info shared within them.

# data[].attributes.body
We encountered some bugs and issues with our web technologies (form systems, website backend etc) throughout the cycle that required quick remediation

# data[].attributes.headline
Articulation issues (approval for core courses) 

# data[].attributes.subject
Articulation issues (approval for core courses) 

# data[].attributes.body
We ran into some issues with challenges for faculty approving courses for core curriculum.

# data[].attributes.headline
Late(r) changes to the partner mainlist and CRG

# data[].attributes.subject
Late(r) changes to the partner mainlist and CRG

# data[].attributes.body
Can improve closer collaboration with UP/AAHQ so this is incorporated into an earlier planning cycle.

# data[].attributes.headline
Channel users not getting pulled into comms correctly

# data[].attributes.subject
Channel users not getting pulled into comms correctly

# data[].attributes.body
Until later on in the cycle, we did not have reconciliation reports to tell us if many users were not getting pulled into comms and why. When we found this out, it was usually by accident, and we had to go back and create a catch up campaign, etc.

# data[].attributes.body
Limited enrollment slightly for OG-dependent populations of late launch schools like UAlbany/Baylor, especially for DOB issue students with Prague as only option.

# data[].attributes.headline
Partners who didn't perform in-line with previous cycles

# data[].attributes.subject
Partners who didn't perform in-line with previous cycles

# data[].attributes.body
I had partners with similar audiences to last year who just didn't perform this cycle (despite doing "all of the things" -- i.e. University of Denver). Huge contrast in deposits from last year to this cycle and no good explanation.

# data[].attributes.headline
Lack of staffing resources on the marketing team made it particularly challenging, all cycle

# data[].attributes.subject
Lack of staffing resources on the marketing team made it particularly challenging, all cycle

# data[].attributes.body
Hopefully we will notice a change here with a new team member :)

# data[].attributes.headline
Cost-Benefit Analysis - Channel Partners & Programs

# data[].attributes.subject
Cost-Benefit Analysis - Channel Partners & Programs

# data[].attributes.body
Continuing to align resources poured into so many things we do: 1) Co College and no ROI but time intensive for all involved 2) Building a Pitt program w/ no enrollment

# data[].attributes.body
We need templates for all AMs for all schools so SACs can refer back to them with consistent information.

# data[].attributes.body
Admissions-specific, but we do our best to try to balance each Pod's portfolio of partners. Fluctuating timelines and audience types/sizes lead to imbalances across pods, so sometimes some pods were slammed and others weren't, or one pod worked with schools with much higher conversion rates which sometimes impacted SAC morale, etc.

# data[].attributes.body
Tons of resources and no ROI

# data[].attributes.headline
Fall Alignment being very program specific, where updates were previously provided. 

# data[].attributes.subject
Fall Alignment being very program specific, where updates were previously provided. 

# data[].attributes.headline
Datashare expectations v. resources to support

# data[].attributes.subject
Datashare expectations v. resources to support

# data[].attributes.body
Resources don't align with the growth of this audience.

# data[].attributes.body
Aligned approach internally to present externally

# data[].attributes.body
Recognizing the channel team begins planning months prior to many teams, given the nature of our cycle. Improve expectation setting for when information from other teams will be ready for the 26-27 cycle to manage partner expectations.

# data[].attributes.body
We can't build things that create additional work for partners/students. We need to always have the "customer lens." To this end, we also need to understand how many asks/emails we are sending to partners.

# data[].attributes.body
potentially not in SF, as that maybe isn't the best place to gather non numerical data. but there have been cross functional asks of UP to share our partner knowledge more broadly and deeply with cross functional team members. not sure how to best do this, but want to note that it has been asked by many and I hear it and want to see what we can do.

# data[].attributes.body
They are getting cluttered with lots of information. How can these be optimized to focus on conversation to RFI/app? Need to really look at the data and focus the site to be pre-deposit focus only.

# data[].attributes.body
Think through content, flow and best practices

# data[].attributes.body
Collaborate with Marketing to revisit old templates and create new templates for partners to send to students

# data[].attributes.headline
Deeper requirements gathering & discovery

# data[].attributes.subject
Deeper requirements gathering & discovery

# data[].attributes.body
Before starting a big project, more time should be dedicated to discovery and fleshing out requirements, in order to ensure the work is fully scoped, viable, and doable from a resourcing and timelines standpoint.

# data[].attributes.headline
Meetings with partners specific to specialized programs

# data[].attributes.subject
Meetings with partners specific to specialized programs

# data[].attributes.body
If possible, additional resources - whether that be meeting with a partner rep or just the UP AM facilitating the comms with SAC for understanding the intricacies of some of these more specialized programs. Business school, etc.

# data[].attributes.headline
More time to focus on marketing initiatives vs 'just trying to keep up'

# data[].attributes.subject
More time to focus on marketing initiatives vs 'just trying to keep up'

# data[].attributes.headline
Expectation setting with partners earlier

# data[].attributes.subject
Expectation setting with partners earlier

# data[].attributes.body
Open houses, pre-departures, WL release, and post-launch engagement - we can have these convos and set expectations earlier so less reactive.

# data[].attributes.headline
Staffing for the cycle earlier based on anticipated growth

# data[].attributes.subject
Staffing for the cycle earlier based on anticipated growth

# data[].attributes.headline
Encourage Partners to use Creg guide to full capabilities

# data[].attributes.subject
Encourage Partners to use Creg guide to full capabilities

# data[].attributes.body
The Creg guide template has been updated to give partners more areas where they can add clarifying information for their institutions and channel requirements. Many partners are leaving sections blank. Meghan and I added some information to a Creg guide because of an upset parent. I think we should look for ways to educate partners on the Creg guide template and encourage them to use all fields.

# data[].attributes.body
Consider what infrastructure needs to be put in place to better allow for increased customization in the student experience from mini-sites and comms.

# data[].attributes.body
What are we comfortable presenting for review vs feedback? (email, SMS, mini site, etc)

# data[].attributes.body
Work with Jackie and new marketing team member, as well as UP, to look at current comms flow and see what changes might be worth making.

# data[].attributes.body
I (Brad) would propose that Meghan and I put together a cheat sheet template for each university for reference after Pre-Launch meetings. AMs provide a lot of great information that is easily lost by SACs when dealing with multiple schools at the same time, but especially when there is a tiny launch and pre-launch meeting in December/January and the massive launch is 2-3 months later.

# data[].attributes.body
Dedicate more time and resources to getting minisites to ideal state and optimize those pages to serve their ideal purpose (aka - get students to submit app / convert)

# data[].attributes.body
Is there value in personalizing marketing journeys to be partner-specific versus having efficiency as the priority? Basically, what does the data suggest as what creates the highest conversion rates.

# data[].attributes.headline
Clearer presentation of most critical program info (rather than FAQs only)

# data[].attributes.subject
Clearer presentation of most critical program info (rather than FAQs only)

# data[].attributes.body
Making sure the most critical program info is clearly (and repetitively) stated in partner decision letter, minisite, FAC deck, and course reg guide (not just dug deep down in the FAQs). I ran into a situation with angry UNH family because it was not clear that entry was guaranteed to the College of Liberal Arts, and while this is stated in the FAQs, it was hard to find. I didn't blame them for being upset. This is an easy fix! We need to consider all materials and presentation through the lens of student/parent viewing this for the first time.