How the session count and the client link work

The rules, in the order you meet them

1. Your details. You sign in with a passkey (your fingerprint, face or screen lock; no password, no email address) and set the name your clients see and your time zone. "Today" is always the date in your time zone, worked out by the server's clock, so a session logged at 11pm counts on the right day and a clock change never moves a date.
2. Clients. Each client has a label of up to 40 characters, and you choose adult or under 18 every time. A label never holds an email address or a phone number. For a client under 18 it is a nickname or initials only, one or two words, such as Sam or Sam J.
3. Packs. A pack is 1 to 100 sessions with a label, a start date and an expiry rule. It never holds an amount of money. A client can have up to 5 open packs at once.
4. Expiry rules. No expiry; a fixed date (the pack can be used until the end of that day); a number of days after the start (up to 730); or a number of days after the first session, which shows "Starts counting at first session" until then. A pack has expired once today is after its last day.
5. Which pack a session comes from. A session goes to an open pack: one that is not closed, has sessions left, has not expired and has started. With more than one, the pack that expires first goes first, packs with no expiry go last, and then the earlier start date, then the older pack.
6. When no pack is open. If a pack expired with sessions left, the server asks before logging the session on it, and marks it "after expiry". Otherwise it asks before logging it over the most recent pack, which then reads "11 of 10, 1 over". With no pack at all it asks you to add one first.
7. Counting. Used is the number of sessions logged on a pack and not removed; left is the size minus used. Changing a pack's size never goes below the sessions already used.
8. Undo. For 5 seconds after a tap there is an Undo button; after that, remove the session from the client's list. Removing a session never moves any other session to a different pack. A removed session is kept out of every count and deleted for good after 90 days.
9. Double taps and dropped connections. Every tap carries its own key. A double tap, a retry or a resend after a dropped connection finds the first one and never counts twice. If saving is paused or you are offline, the tap waits on your device and is sent again.
10. Badges. A client is Low when the sessions left across their open packs are at or below your mark (2 unless you change it, from 1 to 5), Used up at 0, and Expiring when the pack in use expires within your warning days (14 unless you change it). Your list puts low balances first, then expiring packs, then everyone else by name.
11. The client's link. One secret link per client, 128 bits after the # sign, which browsers never send to a server in the address. It shows your name, their current pack as sessions left, "7 of 10 used" and the expiry, the dates used and any note you chose to share. It reads the count fresh each time it opens. Replacing the link makes the old one say it was replaced, and the new one shows the date it was made. A pack the coach reopens says so, with the date. Archiving keeps it working; deleting the client stops it at once, and restoring them makes a new link.
12. The printed record. Any pack prints as a quarter-page card, 4 to an A4 or US Letter page, with a ticked box and the date for each session used. It says it is a record of sessions, not a receipt for payment.
13. Limits. Up to 10 active clients; archived clients do not count. Up to 120 sessions logged an hour, and up to 10 passkeys.

Worked example

A pack of 10 sessions starts on 2 November 2026 and expires on a fixed date, 30 November 2026. Seven sessions are logged from 2 to 8 November. The client's link reads 7 of 10 used, 3 left, expires 30 Nov 2026, and on your list they are not yet Low, because 3 is above the mark of 2.

The client also has a second pack of 10 with no expiry. The next session goes to the first pack, because it expires first: 8 of 10 used, 2 left, and the client is now Low. If nothing more is logged until 1 December, the first pack has expired with 2 left. A session that day finds the second pack open and goes there with no question asked.

Had the client only the first pack, the server would ask: "The pack expired with 2 left. Log this session on it anyway?" Saying yes logs it, marked after expiry, and the link reads 9 of 10 used.

A pack set to expire 30 days after the first session, first used on 5 November, can be used until the end of 5 December and has expired on 6 December.

What it does not do

• It does not take, track or show payments. There are no prices or amounts of money anywhere in the record.
• It does not book sessions. It counts the ones that happened.
• It does not make the count binding: the record is kept by you, the coach, and your client sees what you logged.
• It never emails your clients, and never asks them for an account.

Questions are answered in the FAQ. What is stored, and for how long, is on the privacy page. When you are ready, add your first client.

Sessionstub is not affiliated with any gym, tutoring agency, booking or payment service.