No app. No account. No password.

Every project has a public sign-up page. Share the link however you already reach people — email, a WhatsApp group, a QR code on a poster, a button on your own website. There is no sign-in wall in front of it.

The page shows your organisation's logo and name, the project, and the events on offer:

• →Which days each event can run on, and between what times.
• →How full it already is, as a fill bar — and a clear Full badge once it is.
• →Tick as many events as you want in one go.

Only a name is required. Email is optional, though someone who leaves it out will not receive their schedule or any updates. Sign-ups are protected against abuse, and two people cannot both grab the last seat at the same instant.

Full doesn't have to mean turned away

Switch on waiting lists and a full event can still be picked: the person joins its queue, in the order people arrived, and sees where they stand. When a place opens — you remove someone, or raise the capacity — the first in line is enrolled and emailed, without you lifting a finger. They can take themselves off a waiting list at any time.

First come, first served rewards whoever opened the email first. For clubs, electives and workshops there is a fairer way: switch on ranked choices, and the same sign-up page asks people to put the events they would like in order instead of grabbing a place.

• →You set two numbers: how many events each person can rank, and how many of those they are given. Rank three and get one; rank six and get three.
• →They tap events in the order they want them, and can reorder before sending.
• →Nothing is ever shown as Full, because signing up early no longer decides anything.

When you auto-schedule, the places are shared out: as many people as possible get one, and nobody is pushed down their list so that someone else can have a first choice. The result tells you how many people got their 1st, 2nd and 3rd choice. How it shares them out.

Every attendee and every instructor get their own private timetable link, showing only the sessions they are actually in. No login, no password to forget, nothing to install.

The important part is what does not happen to that link. It is created with the person and never changes for as long as they exist. It survives every new timetable, every change you publish, every time you rename an event or move a session or swap a room. The link you sent in September is still the right link in April, and it now shows April's schedule.

Instructors get one too

The same kind of link, showing the sessions they are teaching along with head counts, so they walk in knowing how many people to expect. Instructors do not need accounts either.

A personal page always shows the published schedule and never your working draft. You can auto-schedule eleven times on a Tuesday afternoon, compare the results, and change your mind twice — nobody outside sees a thing until you publish. Nothing about the link needs to be taken down or put back up in between.

The personal page shows a week with dates on it, and people can page forward to any other. A workshop that happens once appears in the week of its date and nowhere else.

When a date is different, the page says so before anyone has to go looking. A Coming up list at the top names the one-off sessions ahead, any day you have closed that takes out one of their sessions, and any session of theirs you have cancelled or moved — with your note, if you left one. On the week itself a closed or cancelled session is crossed out, and a moved one is shown where it now is.

You decide each time whether a change is also emailed. The page and the calendar feed update either way.

Two different things, and the difference matters.

Download to calendar

A one-time .ics file. Their calendar gets the events as they stand today, and it will not know about anything that changes later.

Subscribe to the feed

One click for Google, Outlook or Apple Calendar, or a link for anything else. It repeats every week, and it updates itself whenever you publish a change. Move a class on Thursday and it moves in their phone. Close a date or cancel one session and that date drops out. Their own calendar can remind them before each session.

The feed always returns a valid calendar, even when someone currently has no sessions — so a subscription never breaks and never has to be re-added. It carries the room and location, and the instructor in the event notes.

The feed is one-way: it publishes your schedule into their calendar. It does not read their calendar back, and there is no two-way Google or Outlook sync.

Both the personal page and the full project schedule print properly and save as a PDF, with your logo, your organisation name, the project and its dates on the header. Half the world still wants a list on a clipboard and a timetable on a noticeboard. When it is time to record who came, instructors can take the register on their phone instead.

Chasing forty people for their availability is worse than the scheduling. Turn on self-service and each attendee sets when they are free each week from the personal link they already have — no login, no account, no extra tool.

They can also star the times they would prefer. A plain time is a rule that is never broken; a star is a wish that is granted where possible, and given up rather than leave someone without a place. People understand the difference immediately, and you get much better data than a spreadsheet ever collects.

It is a per-project switch, off by default. Instructor availability stays admin-only on purpose.

A short list, because knowing the boundary is more useful than discovering it later. This is a scheduling tool, not a booking platform.

• →They cannot pick their own slot or swap sessions. The whole point is that the timetable is worked out for everybody at once, so it stays clash-free.
• →They cannot cancel their own sign-up unless you let them. By default they ask you, and you remove it. Switch on giving up a place and their page has a button for it, and the place goes to whoever is next on the waiting list. Leaving a waiting list they can always do themselves.
• →They cannot pay anything. There is no attendee billing, no memberships and no packages.
• →They cannot log in. There is no attendee account, by design — the link is the identity.
• →There is no mobile app to install, and no SMS or push notifications.

When you do remove someone who had an email, they are told rather than left to wonder, and they cannot immediately re-add themselves through the public link. You can lift that block whenever you want.

A confirmation when they sign up, carrying their permanent link — or a note that they are on a waiting list, and another the moment a place opens for them. Their schedule when you publish. An update when their week actually changes — and only then. A note when one of their sessions is cancelled or moved, or a date is closed, if you choose to send one. Every one of those carries your logo, and every one has a working unsubscribe.

The detail is on branding and emails.