See who actually showed up, in Slate
When someone checks in at your event, Guidebook marks their Slate registration Attended, with the time they arrived.

Send app engagement back to Slate
For students who opt in, downloads, schedule adds, views, and form responses land on their event registration every hour.

Build the campus event once in Slate
Link a Slate folder to a guide. Every event becomes a session, and registrants are added automatically.

Slate profiles, in the campus app
Match each student's Slate record to their Guidebook account, so college, major, and orientation details stay current on every sync.

Campus apps by department
Admissions, orientation, student life, and more — one campus app that works across departments.

Build unlimited event apps on one license
One partnership for unlimited campus events — orientation, tours, student life, and everything in between.

Compare event app platforms
See how Guidebook stacks up against other event app and registration platforms.

Event apps for nonprofit and community programs
Give members, volunteers, and donors one branded app for conferences, fundraisers, and year-round community.

Campus integrations and an open API
Connect Guidebook with the campus systems, APIs, and tools your team already uses.

Event apps for corporate and enterprise teams
Internal meetings, offsites, and large-scale corporate events — with the branding and control enterprise teams need.

Create a branded event app with no coding
Put schedules, maps, resources, and updates in every attendee's pocket — built for campus events and programs.

Launch a branded, white-label event app
A white-label event app with your branding, your content, and your attendee experience — no coding required.

Everything in the Guidebook platform
Explore the features event teams use to engage attendees before, during, and after the event.

One app for in-person and virtual attendees
The same schedule, networking, and updates whether people are in the room or joining remotely.

Event apps built for associations
Annual meetings, chapter events, and member engagement — without rebuilding a new app every year.

A branded event website that matches the app
Promote the event, collect interest, and keep branding consistent from the first click to check-in.

Plan, run, and measure events on one platform
App, registration, badges, and websites in one workflow — so planning isn't a pile of disconnected tools.

Keep members engaged between events
One branded app for the conference and everything that happens the other 51 weeks of the year.

The conference app attendees actually use
Schedules, maps, networking, and live updates for annual meetings, summits, and multi-day conferences.

Registration that feeds your app and badges
Collect registrations, payments, and attendee data in the same platform as your event app.

Design and print event badges in one place
Custom badges, QR check-in, and on-site printing — without a separate badge vendor.

A Smaller School?
Deliver a polished, branded event experience without a large team or a big budget.

Running Family Programs?
Give families everything they need, from schedules and maps to real-time updates, all in one place.

Coordinating Move-In Day?
Share updates, manage events, and keep students informed from move-in through the academic year.

Offering Campus Tours?
Deliver branded, self-guided tour experiences with interactive maps and rich media, available 24/7.

Organising a Career Fair?
Simplify logistics for students, employers, and Career Services staff with one easy-to-use app.

Managing Alumni Events?
Plan reunions, regional events, and fundraising campaigns with an app built for alumni engagement.

Boost Student Engagement
One hub for schedules, resources, and events that keeps students connected throughout the academic year.

Planning Orientation?
Help new students feel prepared from day one with schedules, campus resources, and real-time updates in one app.

Running Admissions Events?
Manage open houses, tours, and yield events with a branded app that saves time and engages prospective students.

Get a custom Sponsorship Package Template
Stop starting from scratch. Grab free templates that helWe'll build a tailored sponsorship package with suggested pricing, tiers, and benefits..for your specific event.p you build professional sponsorship packages and close deals faster.

Plan Your Next Event Without Missing a Beat.
From venue selection to post-event wrap-up, this free checklist walks you through every step (so nothing falls through the cracks).
.avif)
Real Results From Real Events
100,000+ organizations trust Guidebook. See exactly how universities, associations, enterprises, and more put it to work.

Flexible pricing for every event size
Find the perfect plan for your needs, from intimate gatherings to large-scale conferences.

Join our event experts
Watch on-demand webinars and join live sessions with industry leaders sharing best practices for event success.
.avif)
Guidebook in Action
Book a personalized walkthrough and discover how we help event teams create better attendee experiences.

Build Your Campus Event Once in Slate

Build Your Campus Event Once in Slate
- Link one Slate folder to one guide, and every event becomes a session under a track named for the folder.
- Names, times, locations, and descriptions stay in step with Slate on every sync. Capacity and waitlist settings are copied once, then stay yours in Builder.
- Slate registrants are added to the guide with a status of Created. A change in Builder does not write back to Slate.
- Pausing stops the sync. Removing it leaves the sessions already in the guide.
The room change lands an hour before doors. You fixed it in Slate. The guide still has the old room, because the schedule was built a second time last week. This is for the person who owns the Slate folder, and for the person who would otherwise rebuild it in the app.

The Slate events and sessions connection is the part that stops the second build. Link a folder to a guide, and every event in it becomes a session, with its registrants added automatically. Edit the event in Slate, and the guide follows on the next sync.
What is the Guidebook and Slate events and sessions connection?
It's the part of the Guidebook and Slate integration that turns the events in a Slate folder into sessions in a guide's schedule. Names, times, locations, and descriptions stay in step with Slate on every sync, and anyone who registers in Slate is added to the guide automatically. The data flows one way, so Slate stays the plan of record.
Build it once
Link a folder to a guide and its events show up as sessions, grouped under a schedule track named for the folder. From there, these details stay in step with Slate on every sync:
- Name, description, and start and end times
- All-day setting, location, and address
- Schedule track
Bates College's open house is an example of the schedule this fills. Parking and a campus map sit beside the day's sessions.

New events in the folder appear as sessions. Events you delete in Slate are removed. Nothing gets edited twice.
What's copied once, and what stays yours
The mistake is assuming every field keeps updating. Names, times, locations, and descriptions do. A smaller set is copied once, the first time the session is created, and then the sync leaves it alone. Images, rank, and ratings are never copied. You set those in Builder.
| The field | What the sync does with it | Where you change it after that |
|---|---|---|
| Name, description, times, all-day, location, address, schedule track | Updated on every sync. New events are added, and deleted events are removed | In Slate. The guide follows |
| Capacity, login requirement, add-to-schedule, waitlist, registration dates | Copied once, and only when the Slate event has a capacity | In Builder. The sync will not touch them again |
| Online event URLs, recording URLs, registrant and attendee counts | Not imported | They stay in Slate |
That split is why a capacity you change in Slate next month will not move the session. The first copy already happened. If the room changes, change it in Slate. If the waitlist rules change, change them in Builder.
Registrants, handled
When someone completes registration in Slate, they land on that guide's Users list with a status of Created. If they already have a Guidebook account, that account is added. If they don't, one is created first. A change you make to that user in Builder does not change their registration in Slate.
Pausing the connection stops the sync. Removing it stops the sync and leaves the sessions already in the guide. You still can't delete an imported session, or the track and location the sync created, from Builder. Delete the event in Slate, and the next sync removes the session.

Slate leads, Builder follows
The sync runs one way, from Slate to Guidebook. One folder feeds one guide, and each guide receives events from one folder, so there's never a question of where an event lives. Build it in Slate, and the guide stays true to the plan.
Bowdoin's homecoming guide is the track view. The weekend is split into tracks, with a personal schedule beside the full list.
.png)
The folder is worth linking on the days that decide the year, which is the difference between an Open House and an Admitted Student Day. Manchester's open day is one picture of a campus day run from a single app. Map one folder to one guide, and the next room change has one home.
Frequently asked questions
Get the Mobile App Playbook
A short guide to running the whole student journey in one app. No fluff, just what works.
%20(1).avif)


.avif)

