Skip to main content
Liaison

Using CAS Application Data After Loading it Locally

Using CAS Data Once You've Loaded It

There are six purposes for which institutions use CAS application data in their local systems. The following list presents these purposes in the order of an admissions funnel.

uses-for-app-data-in-local-systems.png

  1. Recruitment – Encouraging prospects to apply
  2. Application management – Encouraging applicants to complete their applications
  3. Application review – Reviewing completed applications for admission to your program
  4. Decision release – Notifying applicants of admission decisions
  5. Post-offer operations – Collecting necessary paperwork and fees from matriculating students
  6. Student record creation – Creating official digital records for matriculating students
How Your Intended Use for Data Affects Your Integration

Different uses for CAS application data in local systems have different requirements. To perform early-admissions funnel operations like application-management and application review in local systems, it is necessary to bring many different data points from CAS and to bring them frequently.

Decision release requires somewhat fewer data points (enough to create person and application records and indicate the decision), but if decisions are released on a rolling basis, the data would need to be loaded to local systems frequently.

High frequency data transfers covering many data points are hard to handle with approaches that don't involve data integration, since they require a great deal of time-consuming manual work by admissions staff.

If you want to perform application management, application review, or decision release functions in local systems, it's best to go with Batch Processing or Automated Integration.

If you’re going to review applications and release decisions in Liaison’s platforms, and you only want to perform post-offer operations (e.g., collecting matriculation deposits) or student record creation for matriculating students in local systems, then the slower, labor-intensive processes are fine. These approaches that don't involve data integration have the added benefit of requiring little initial planning and effort to implement. With a lower initial investment required, you can start accepting applications sooner.

 

  • Was this article helpful?