Branding and communication
It should look like it came from you.
Everything an attendee sees is a page or an email from your organisation, not from a scheduling vendor they have never heard of. And when things change, the right people hear about it — which usually means far fewer people than everyone.
Your logo, everywhere it matters
Upload two versions and the right one is used in each place: a wide lockup for headers, and a square mark for tight spaces. Provide only one and it stands in for the other; provide neither and you get a clean initial tile rather than a broken image.
- →The public enrolment page — the first thing a new attendee ever sees.
- →Every personal schedule page, for attendees and instructors alike.
- →Printed schedules and saved PDFs, on the header alongside your organisation name and the project dates.
- →The header of every schedule email that goes to an attendee or an instructor.
- →The app itself, so your own team sees your mark rather than ours.
Each project can also carry its own colour, which is useful once you are running several at once.
What is not included
Full white-labelling is not. There is no custom domain and no vanity subdomain: public pages live on our domain and carry a small "powered by" line. If a completely unattributed experience is a hard requirement, this is the wrong tool and it is better to know that now.
Logos are accepted as PNG, JPEG or GIF, up to 1 MB. SVG is refused — an SVG is a document that can carry script, and it would run on the same origin as your attendees' pages. Replacing a logo takes effect immediately rather than waiting on a cache.
The emails your people get
| When | Who | |
|---|---|---|
| Enrolment confirmation | Someone signs up through the public link | Confirms what they enrolled in, and carries their permanent personal link. |
| Your schedule is ready | You publish a schedule | Goes to every attendee with an email and at least one placement. |
| Your teaching schedule is ready | You publish a schedule | Goes to every instructor teaching at least one session, and leads with how many. |
| Your schedule has changed | You republish and choose to notify | Names what moved: which session, from when, to when. |
| Your teaching schedule has changed | You republish and choose to notify | The instructor version of the same. |
| You have been removed | You delete an attendee from a project | So the link going quiet is not a mystery. |
People with no sessions in a published schedule are deliberately skipped rather than sent an empty timetable. The instructor wording is genuinely different from the attendee wording, not the same email with a word swapped.
Tell only the people it affects
This is the part that saves the most goodwill. When you republish, you are not limited to mailing the entire project again — you can send to only the people whose week actually differs between the old schedule and the new one.
The difference is computed on the server from the two runs, so it is the real difference, not a guess. Someone whose sessions did not move hears nothing. Someone whose class moved is told which class, from when, to when. Someone who lost their place is told that plainly, in its own line, rather than being left to compare two timetables and work it out.
Or aim it wherever you need
- Everyone
- The whole project — attendees, instructors, or both.
- One group
- Just the Beginners, just Year 9, just the Saturday crowd.
- One person
- For when a single conversation went sideways.
- Only those affected
- Recomputed from the difference between two runs.
Unsubscribes handled properly
Every schedule email carries a real unsubscribe, including the one-click header that Gmail and Outlook now expect. Opting out is recorded against the email address and the kind of message, not against a row in a table — so someone who is both an attendee on one project and an instructor on another opts out once and it holds everywhere.
- →Clicking the link shows a confirmation page rather than unsubscribing on the spot, so a corporate link scanner cannot silently opt someone out.
- →Resubscribing is offered on the same page, for the people who clicked it by accident.
- →A hard bounce or a spam complaint suppresses that address automatically, without you doing anything.
- →Account and billing messages are never suppressed. Nobody should miss a password reset because they opted out of timetables.
Your own attendee-facing mail deliberately does not carry your logo when it is an account or billing message from us — those are ours, and dressing them up as yours would be misleading.
You can see what was sent
Every attempted send is logged with its outcome — delivered, failed, skipped, suppressed, bounced. When somebody says they never got their schedule, that is a question with an answer rather than a shrug. Opt-outs are listed too, and you can resubscribe someone who asks to come back.
What we do not send
- →No SMS and no push notifications. Email only.
- →No automatic reminders before a session. Emails are triggered by enrolment and by publishing, not by the clock.
- →No marketing email to your attendees. Their addresses are yours; we do not use them.
For how the published schedule itself is produced, see the scheduling engine, and for what your attendees see when they follow the link, see the attendee experience.
See it on your own timetable.
14 days, no card. Everything on this page works on the trial and on every paid plan — the tiers differ only by how many attendees and events you can hold.
Keep reading
- How it worksThe full loop, from an empty project to a published week.
- The scheduling engineConstraints, weights, pinning, and what happens when it cannot fit everyone.
- What you enterEvery field, and which ones are actually required.
- The attendee experienceEnrolment links, permanent personal timetables, calendar feeds.