Slate Summit Call for Proposals FAQ

The Slate Summit Call for Proposals (also known as the CFP or Summit Proposals) is a platform for submitting session proposals for Slate Summit. This includes full sessions at Slate Summit, sessions at Slate Presents, Affinity Groups, Show & Tells, and Slate Labs at Summit.

Slate Summit is where the Slate Community comes together. Attendees include admissions and enrollment leaders, Slate administrators, operations and technology teams, marketing and communications professionals, and data specialists from K-12 schools, colleges, universities, and mission-driven organizations. Beyond the educational sessions, Summit is an opportunity to connect with peers, share successes and challenges, and build relationships with others who understand the work you do every day.

Slate Summit will begin Wednesday morning, June 2, with our annual Opening Session, hosted by Technolutions Founder and CEO Alexander Clark. Sessions and affinity groups will begin following the Opening Session and will continue through Friday, June 4, concluding in the early afternoon.

View Sample Schedule

• Location: Music City Center

• Travel: Nashville International Airport (BNA) — 6 miles from Music City Center

Any Slate User who will be attending or who intends to attend Slate Summit. In addition, you must meet the following criteria:

• Employed at a current institution that uses Slate

• Employed at one of our Preferred Partners as a full-time employee

Consultants who are not employed by a Preferred Partner are not eligible to present at Slate Summit.

Yes! You can submit a proposal with up to two co-presenters. Presenters do not need to work at the same institution.

Presenters must be employed by an institution or organization that uses Slate or by a Preferred Partner. Independent consultants and organizations that are not current Slate users or Preferred Partners are not eligible to present. Proposals including these presenters will not be reviewed.

Students may present as part of a proposal from a current Slate institution or organization. The proposal must clearly indicate that a student will be presenting and should note whether the student is a minor.

Yes! First-time presenters are encouraged to submit proposals. The review process is designed to highlight a range of voices, experiences, roles, and perspectives from across the Slate Community.

Not at all. While we collect information about past Slate Summit attendance and presentation history, this information is not considered during the review process. Your chances of presenting this year are not affected by whether you’ve presented before.

Yes. However, sessions must be educational in nature rather than product demonstrations or sales pitches. In addition, Preferred Partners must submit a proposal with at least one co-presenter from a current Slate institution.

Yes, but we recommend that proposals use Configurable Joins where available. Proposals may include some Custom SQL especially in areas where Configurable Joins do not yet provide equivalent functionality. Sessions that heavily rely on Custom SQL are unlikely to be accepted.

No. You do not need to be a formal expert to submit a proposal. Strong sessions often come from presenters who have solved a problem, tried something new, learned from a challenge, or developed an approach that others in the Slate Community could adapt.

We're looking for sessions that are practical, engaging, and directly or broadly relevant to the Slate Community. We welcome sessions that balance technical depth with accessibility for a wide audience. Examples include:

• Real-world Slate solutions: How your institution or organization solved a problem, streamlined a process, or improved outcomes using Slate.

• Creative configurations and unexpected use cases: Share innovative approaches or those "We didn't know Slate could do that!" moments.

• Cross-lifecycle topics: Sessions that span Admission, Student Success or Advancement.

• Strategic and visionary topics: Ideas that explore trends, best practices, or the future of higher education and Slate.

• Training sessions: Hands-on, skill-based presentations that teach attendees how to accomplish something in Slate step by step.

… and much more!

If you have an idea, we’d love to see it.

Strong proposals clearly explain the challenge being addressed, the approach or strategy used in Slate, and what attendees will be able to learn or apply afterward. The strongest submissions are specific, practical, and relevant to a broad portion of the Slate Community. Proposals do not need to showcase perfect or finished work. We especially welcome sessions that include lessons learned, decisions made along the way, and ideas others can adapt.

Yes. Proposals can describe work that is still in progress, as long as the session can provide useful takeaways for attendees by the time it is presented. Strong in-progress proposals should clearly explain the problem being addressed, the approach being used, what has been learned so far, and what attendees can expect to gain from the session.

Yes. Sessions about newer or recently updated Slate functionality are welcome, especially when they help attendees understand practical use cases, implementation considerations, lessons learned, or best practices

Your session should highlight:

• Why the build was necessary.

• How it was built.

• How it has improved processes or enhanced your team’s workflow.

We encourage you to focus on the approach, decisions, and lessons learned throughout the build process rather than only demonstrating the final product. This allows the Slate Community to gain practical insights they can apply to their own work.

Traditionally, sessions take the form of presentations or panel discussions. We also offer Show & Tells, which are short, rapid-fire presentations that provide a space for sharing a variety of topics and ideas.

A typical session is 50 minutes including a 10 minute Q&A. We encourage proposal submitters to aim for sessions that last 35-45 minutes.

Show & Tells are short, focused presentations, typically 5–10 minutes in length, designed for ideas, projects, or solutions that do not require a full session. Think of them as a quick spotlight: an opportunity to share a specific example, workflow, insight, or best practice in a concise and engaging format.

Show & Tells are ideal for topics that are practical, focused, and best communicated through a brief burst of insight. They are not intended to be shortened versions of full sessions, but rather a way to highlight a specific idea, accomplishment, or approach that the Slate Community can learn from.

This format was inspired by the Slate Community itself! Megan Story, a community member, suggested Show & Tells as a way to showcase creative ideas and solutions from across the community.

A Slate Lab is a small-group, discussion-based Summit session where attendees work through realistic situations together. Instead of focusing on their own institution’s specific constraints, participants step into shared scenarios that help them think more broadly, compare approaches, and explore what might be possible in different contexts. These sessions are interactive, collaborative, and designed to spark practical problem-solving that attendees can bring back to their teams.

New for Summit 2027, hands-on workshops are a new session format that combines a traditional full-length session with an interactive workshop experience. When submitting a hands-on workshop proposal, presenters are proposing both components as part of the same submission.

The session and workshop should focus on the same topic while offering two complementary learning experiences. The session should focus on sharing a use case, strategy, or approach, while the workshop should provide attendees with an opportunity to actively apply those concepts through guided exercises, demonstrations, activities, or discussion.

Workshops are designed to move beyond a traditional presentation format. Rather than attendees simply watching a demonstration or listening to a case study, workshops should give participants an opportunity to engage with the material, practice skills, and apply concepts to their own work.

The session and workshop may be delivered in either order. One component will take place onsite during Summit, while the other will take place virtually before or after Summit. The Summit Content & Affinity Committee will work with presenters to determine which component is best suited for the virtual experience and which will take place onsite.

For example, presenters may share a use case during an in-person Summit session and follow up with a virtual workshop where attendees apply those concepts through hands-on activities. Alternatively, presenters may host a virtual session before Summit and lead an onsite workshop where attendees put those concepts into practice.

This format was inspired by the Slate Community! Katie Jordan, a Slate Preferred Partner, suggested this approach as a way to promote more active and engaged learning opportunities at Summit. Thank you, Katie, for helping shape the future of Summit programming!

A hands-on workshop should provide attendees with structured opportunities to participate, practice, and apply concepts related to the session topic. Examples may include guided exercises, building or configuring within Slate, working through scenarios, completing activities, collaborating with other attendees, or applying a strategy to their own processes.

A hands-on workshop should not be:

• A repeat of the presentation session.

• A longer version of a traditional lecture or presentation.

• A passive demonstration where attendees only watch the presenter complete a task.

• A Q&A session or open discussion without structured activities.

• A product overview or showcase without opportunities for attendees to apply what they learn.

The goal of a hands-on workshop is to help attendees move from understanding a concept to applying it in practice.

Yes. Hands-on workshops should include something attendees can follow along with during the session. At minimum, presenters should provide a step-by-step PowerPoint deck or similar guided structure that supports participation and active learning.

Presenters are not expected to create handouts, worksheets, or separate attendee materials unless they choose to. The format is flexible, and presenters may structure the workshop in the way that works best for their topic, as long as attendees have a clear path to follow.

If you have an idea, we encourage you to submit a proposal. The review process is designed to highlight a range of voices and perspectives, and your experiences and insights could be valuable to the Slate Community. Proposals don't need to be perfect. What matters most is that your idea is relevant and has the potential to benefit attendees.

In addition to full sessions, we also offer a shorter format called Show & Tells. These are 5- to 10-minute presentations that are perfect for sharing smaller ideas, projects, or tips that don't require a full session.

We encourage you to submit your idea and let the review process guide you. Your experiences and perspectives are enough, and your session could be exactly what someone else is hoping to learn.

No, there’s no limit! You’re welcome to submit as many proposals as you’d like on topics you’re interested in presenting.  Please do not submit duplicate proposals. Just keep in mind that submitting multiple proposals does not guarantee selection for presentation at Summit.

Please do not submit duplicate proposals. If your topic could work in more than one format, please choose the format that best matches your preferred experience.

No. Incomplete submissions will not be reviewed. Please ensure all required information is included before submitting your proposal.

Yes. Session proposals may be submitted on behalf of someone else at your institution. Please note that, as the submitter, you will receive all communications regarding the status of your proposal. If your proposal is accepted, you may designate a different primary contact for future communications.

Just one proposal should be submitted per presentation. The person who submits the proposal will be the primary contact and will receive most communications from the Summit Content & Affinity Group Committee.

No. You do not need to be registered to submit a proposal. However, if your proposal is accepted, you must register to attend Slate Summit in order to present.

No. We do not expect your presentation slides to be ready when you submit your proposal. The deadline for submitting presentation slides is typically in late May.

Once submitted, proposals should be considered final. If you need to make a critical correction, please contact Christopher Kwan at ckwan@technolutions.com. We cannot guarantee that edits can be accommodated after submission, especially once review has begun.

Proposals should be submitted with complete presenter information. If a presenter needs to be changed after submission, please contact Christopher Kwan at ckwan@technolutions.com and your session moderator as soon as possible. Presenter changes are not guaranteed and are considered based on eligibility, timing, and space available

Your proposal description should clearly outline what your session addresses, the Slate tools, strategy, or approach involved. We recommend highlighting what attendees will learn, and how attendees may be able to apply the idea at their own institution.

If submitting for Slate Summit, the Mobile App description should be as informative as possible so that attendees can easily at a glance understand the gist of your session.

Yes. To help us properly review your proposal, we recommend including internal links to the relevant areas of your database or process.

Each reviewer is a Technolutions employee and can access your database as needed. Please also include any test records, test users, impersonation instructions, or other context needed to review the process accurately.

Do not provide real records or sensitive data for review. Use test records or sanitized examples only.

All proposals are reviewed by the Summit Content & Affinity Group Committee. Each complete submission typically receives 5–14 individual or committee reviews to ensure a thorough and consistent evaluation.

There are many factors considered when evaluating a proposal. Some of the criteria include:

• Relevance to the broader Slate Community.

• Practical application and usefulness.

• Effective use of current Slate functionality.

• Alignment with Slate best practices.

The proposal submitter will receive email notifications throughout the review process. Once your submission is complete, you will have access to your Application Status Page, where you can follow the progress of your proposal as the committee reviews submissions.

Notifications will be sent before winter break for proposals submitted by the Early Deadline. All other proposal notifications will be sent in mid-Spring.

Yes. During review, the Summit Content & Affinity Group Committee may determine that a proposal is better suited for a different format. If a significant format change is recommended, the committee will contact the proposal submitter before finalizing the session.

Possibly. If multiple proposals cover similar topics or themes, we may combine them into a single session. If this happens, all presenters will be contacted before the schedule is finalized.

Notifications will be sent based on when your proposal was submitted. Proposals submitted by the Early Deadline will receive decisions before winter break, while all other submissions will receive decisions in mid-Spring. The Summit Content & Affinity Group Committee may reach out earlier if they have additional questions regarding your proposal.

For approved proposals, all listed presenters will receive a decision notification. For proposals that are denied or waitlisted, only the proposal submitter will receive the notification.

Being waitlisted means your session has strong merit, and we would like to include it at Slate Summit if space becomes available. Due to capacity and scheduling constraints, we are unable to guarantee a session slot at this time.

What happens next?

• To confirm your continued interest, you will need to complete the Slate Summit Backup Reply Form, which will be available as a Checklist Item in your Summit Application Status Portal. Completing this form keeps your session under consideration for Slate Summit.

  • If you prefer, you may also indicate through this form that you would like your session to be considered for Slate Presents.

• If your session is deferred, it means the committee has identified your proposal as a strong fit for future programming but is moving it into the following year's Slate Summit proposal pool. Deferred proposals may be considered for the next Slate Summit or a Slate Presents series.

We receive hundreds of submissions each year and, unfortunately, can only select a limited number of proposals. Due to the volume of submissions, we are unable to provide detailed feedback for declined proposals.

Accepted presenters are expected to:

• Register for Slate Summit.

• Meet all posted presenter deadlines.

• Submit required presentation materials by the specified deadline.

• Respond to communications from the Summit Content & Affinity Group Committee.

• Prepare and deliver their accepted session format.

• Notify the Summit Content & Affinity Group Committee as soon as possible if they are no longer able to present.

Presenters may also be asked to connect with a session moderator before Summit to discuss session flow, expectations, and opportunities for feedback.

No. While you can let us know if you will be arriving late or leaving early, we are not able to accommodate specific scheduling or room requests.

No. All presenters for in-person Slate Summit sessions must attend in person. If one of your presenters is unable to attend Slate Summit, we encourage you to submit your proposal instead for our virtual Slate Presents series.

The application includes options for both. Please note: All in-person Slate Summit proposals may also be considered for Slate Presents if the topic is a better fit for the virtual series or if space is unavailable at Summit.

Yes, we encourage all presenters to practice their sessions ahead of Slate Summit. Session moderators are also encouraged to connect with presenters before the event to schedule a run-through and provide additional feedback.

On-site rehearsal space may be available based on availability and will take place on the Tuesday before Slate Summit as part of your scheduled tech check. During this time, presenters can familiarize themselves with the room setup, test their presentation materials, and complete any required technical checks for their session.

Only Slate Presents sessions are recorded. For sessions at Slate Summit, your PowerPoint deck will be shared with the Slate Community after Summit.

Yes. Presenters are responsible for ensuring they have permission to share any institutional processes, examples, screenshots, data, or materials included in their session. Presentations should not include any sensitive, confidential, or student-specific information unless it has been appropriately removed, anonymized, or sanitized.

If you experience a career change after submitting your proposal, please let us know as soon as possible. This includes situations where:

• You are no longer employed by an institution or organization that uses Slate.

• You are no longer employed by the institution or organization represented in your proposal.

If you change institutions and move to another institution that uses Slate, you may still be eligible to present. However, we require the following additional information:

• An email to Christopher Kwan - ckwan@technolutions.com notifying us of your career change.

• An email from your former supervisor granting permission for you to present on that topic as an employee of your new institution.

If selected to present at Summit, your slides must also include a notice indicating that you have received permission from your former institution to present this topic.

Yes. If you need an accommodation related to presenting at Slate Summit, you will be able to note that in your proposal. You can also notify the Summit Content & Affinity Group Committee if accepted.

It depends on the format.

Traditional sessions should generally be structured as presentations or panels and are not expected to include audience participation.

Audience participation may be appropriate for Slate Labs, Affinity Groups, or hands-on workshops when it supports the goals of the format. If your proposal includes audience participation, discussion, reflection, or activities, please describe that in your submission so the committee can consider room setup, timing, and format needs.