Joey Crowley, CAPM
Project Manager & Data Analyst
Admissions Office and Enrollment Team

Recruiting the next undergrad class often means communications, strategies and tools need to be in-line with current technology as well as generational trends and expectations.

The CRM we use to communicate with admitted students and record necessary information is critical for our yield. Yield is defined by admitted student to matriculated student. 

Within our CRM, we built a portal for applicants to University of Montana and Missoula College. We then also build a portal for admits. It's currently being combined by a company we've contracted with, however, we have a huge gap in documentation and project planning for each student type and each term. 

For instance, Spring-start & Summer-start students have not yet been planned for. 
Additionally, requirements within the portals vary depending on the type of student (international students, post-bac students, true first year on-campus, transfer students who will only take online classes...these are only a few examples.

I have a project plan for our core group, but I would like some help with planning and documentation for future use. As we rebuild and automate the portals to assist in yield, it leaves little time to clean-up decisions made, pivoting points, new information, helpful information, and project planning for the next term. 

As a current project manager, I could use some fresh eyes on how to organize, plan and document the portals. They are large projects with lots of information. They make sense to me, but I want these documents to be usable for the future. 

Output documentation is the measurable result. 
Output documentation would include updated timelines and planning documents, training aids, documentation of the previous term's portal (decisions made, pivoting points, new information, helpful information), and project planning for the next term.