Slate was tailor-made to process applications:
👩🎓 Applicant-centric: Designed with users in mind, Slate offers an intuitive, mobile-optimized interface, easy document uploads, and nudges to encourage completion.
🏠 Self-hosted: The Slate-hosted application streamlines and hyper-personalizes your application process. You can also import applications from external sources.
✨ AI-enabled: Use Slate AI to analyze application materials, perform calculations on transcripts, and more.
This video provides an overview of the features available in the Slate-hosted application. It is comprehensive: feel free to jump around using the timestamps in the accordion below.
⏯️ Timestamps
Content | Timestamp |
|---|---|
0:18 | |
Types of Applications | 0:39 |
Application Functionality | 1:03 |
2:19 | |
Slate Hosted Application: Applicant Perspective | 3:13 |
5:34 | |
6:40 | |
Custom Application Pages | 8:16 |
10:22 | |
10:42 | |
12:50 | |
16:44 | |
16:44 | |
16:53 | |
23:27 | |
Understanding Configurable Joins Webinar and Configurable Joins with Alexander Webinar | 27:11 |
References | 31:48 |
32:55 | |
33:18 | |
33:27 | |
33:47 | |
36:04 |
Building an application in Slate in three phases
There are three main phases to building the Slate application:
Phase I: Core Components: Create Slate objects that store application data.
Phase II: The Slate-Hosted Application: Build out and test the applicant experience.
Phase III: Checklists, Automations, & The Status Page: Configure the automations that keep your application humming along.
We break these phases down into the following checklists.
Phase I: Core components
In the first phase of application building, you establish the fundamental data structures on which your application will run. You’ll also prepare Slate to receive external applications, test scores, and payments.
Create periods. A period must be active in order to use the application editor.
Create rounds. Rounds should be inactive until ready to go live.
Create application-scoped fields, person-scoped fields where necessary, and prompts for prompt-based fields.
Create the materials to be collected as part of the application.
Create the forms that store metadata associated with materials.
Create a material to store application data on the student record upon submission.
Configure Slate to import external applications and test scores by adding source formats from the Source Format Library. Create custom source formats as necessary.
Configure your database to accept payments.
With these foundational elements in place, you can move on to crafting the applicant’s experience in Phase II.
Phase II: The Slate-hosted application
In the second application building phase, you create the interface that applicants use to complete your application. You’ll also test the application from the user’s perspective and set up submission requirements.
Application structure
Get an overview of the Slate-hosted Application.
Explore the Application Editor.
Consider creating a form that creates applications.
Application pages
Explore the application pages that come with your database.
Learn how to create a custom application page and a custom application widget.
For each existing application page, learn how it can be customized or replaced as necessary.
When you’ve finalized your application pages, learn how to show or hide them conditionally.
Application submission requirements
Create submission requirements as needed.
Application testing
Learn how to test the application by impersonating an applicant.
Phase III: Checklists, automations, & the status page
Lastly, you configure the application checklist, set up the rules that automate the hard stuff for you, and flesh out the applicant status portal.
Organize all checklist items into checklist groups.
Create checklist rules to assign items in checklist groups.
Add and activate application status rules from the Slate Template Library; adjust as needed.
Use Application Editor to modify the Slate delivered status page or create custom status portal using the Portal Editor (Optional).
The status page settings pertain to a Slate-delivered status page only. If using a custom status portal, edits can be made directly to the status portal using the Portal Editor.
Build payment rules where appropriate.
Consider employing identity verification.
➡️ First up: Introduction to application periods and rounds
Your first step in building your Slate application is understanding how periods and rounds shape your application structure.
📚 First article in this series: Application periods and rounds