Slate Features

What features do we use in Slate?

Slate is a relational database, which allows us to store information about a prospective student so that it can be accessed throughout their lifecycle. We can store parent/relationships with alumni, where they went to school, where we met them, test scores submitted, and more. If they submit an application, all of the the information in the database is accessible to them in the application. Slate also allows us to see more than one application per person. Learn more about the Person Record. 

Email Communications - Email communication in Slate allows us to send messages to prospective students, parents of prospective students, follow up with inquiries and applicants, as well as communicate about admission decisions. Use the Deliver tool to create and manage email outreach campaigns to prospective students, applicants, and other groups within Slate (e.g., counselors). 

Events - You can create event registration forms, communications related to events.

Interviews - Set up prospect interviews on recruitment trips, application interviews during the review process and more. You can also create communications related to interviews. 

Portals - A fully customizable access point for external users. This could be alumni, volunteers, parents, prospective students, applicants, admitted students, etc. 

Query - Queries produce a list of records that contain granular details about each record. For example, a query may return a list of applicants with columns that display the application round in which they applied, their entry term, and their admission decision.

Reports - Allows you to see aggregate data to answer questions you may have about the number of prospects, applicants, admitted students or interviews you have. 

Reader - All aspects of your reading process, from managing reader queues to reviewing applications and determining admissions decisions, can be accomplished in the Reader.

Test Environment - A recent backup copy of the production database that is a new, standalone database.  Use the Test Environment to try something that would impact a process that you would like to test before putting into production.