1. Float / Sensory Tank Studio
  2. Features
  3. Session delivery
Feature · Session delivery

Session delivery

Link check-in and attendance to the confirmed booking and member plan.

OverviewOpen Sessions
Float / Sensory Tank Studio · Session delivery

Open Sessions

Sessions

New
Session nameStarts atEnds atCapacityServiceInstructor
Session 65406 Oct08 Oct240SRV-8039
Session 79307 Oct12 Oct960SRV-8206
Session 63423 Oct26 Oct160SRV-4876
Session 47309 Oct18 Oct140SRV-8920
Session 74607 Oct11 Oct760SRV-9142
6 of 6 records
Session 654Sessions · SSS-57490
Open
Starts at06 Oct
Ends at08 Oct
Capacity240
ServiceSRV-8039
TankFT-3696
Example screen with sample data

What you can do

Record what happened when the member arrived

A confirmed booking is the starting point for delivery. The Float Instructor checks the member and the scheduled session, then records an attendance entry against that exact booking. The entry identifies the check-in time and the person who recorded it. The booking status can then reflect an attended visit. The member’s plan enrollment holds the resulting consumed and remaining sessions, so the studio can answer both an attendance question and a balance question from connected records.

The distinction between a confirmed reservation and an attended session matters. A payment may be pending while the booking is confirmed. A member can miss a session after a place was reserved. Keep these states separate so reports do not call a reserved place a delivered visit or a receipt a check-in.

How the work is organized

  • Eligibility. Start from the confirmed booking, its member and the open session it references.
  • Check-in. Record the visit time and staff actor on the attendance record.
  • Consumption. Update the linked enrollment’s session balance only for the delivered booking.

What to agree during setup

Agree who may check in a member and when a late arrival becomes a no-show. The instructor’s person record should point to the authenticated user, allowing staff actions to be attributed. Decide how a mistaken check-in is investigated and corrected while retaining the booking and attendance trail. A repeated action should be checked against the original booking and operation key before any second attendance is recorded.

Before opening the first operating day, rehearse one valid check-in, one booking that remains requested and one member enrollment that is no longer active. Compare the enrollment balance before and after the valid case. The manager should be able to see the change alongside the booking status, rather than relying on a verbal handoff.

Check the handoff on an actual case

The instructor opens the evening session and finds a confirmed booking. The member’s enrollment is active and has remaining sessions. At arrival, the instructor records attendance against the booking. The attendance record holds the check-in time and recorder; the booking moves to attended; the linked enrollment shows one more session consumed. A later question about the visit can be answered by following the booking number into its attendance entry.

If the member does not arrive, the team records a no-show outcome under its agreed policy. No attendance entry should be invented to clear the queue. If the instructor sees a requested booking instead of a confirmed one, it goes back to the manager for a booking decision before delivery. This keeps delivery evidence tied to an actual reserved place.

What your team sees

  • Open Sessions — Find the session and instructor assignment before check-in.
  • Booking Work Queue — Identify confirmed bookings expected for that session.

What it keeps track of

Data model
Attendance
Booking check-in evidence and attendance records.
Bookings
Member requests and confirmed reservations for sessions.
Sessions
Scheduled service sessions with instructor and capacity.
Members
Studio members and lifecycle status.
Member plans
Membership plan enrollments held by members.
People
Studio staff and authenticated operational actors.

Who uses it

Permissions
Float Instructor
Records the visit, Booking Coordinator resolves identity questions, and Studio Manager handles exceptions to the booking decision.

Set up Float / Sensory Tank Studio your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started