One booking
Availability, transitions, people and billing rules connect through the same action.
OSCorpus OS
A system for
the studio’s daily operation.
Product design for Corpus OS: connected scheduling, students, teachers, contracts, make-up classes and a student portal.
- Scope
- Product · Interface · Interaction
- Platform
- Web / team, tablet and student
CORPUS OS
The studio’s day,
in one clear view.
Schedules, people and rules in the same context.Explore the contexts ↘TODAY09:00
Pilates / current class
● ● ● ○3 / 4
Recurring slots✓
Attendance and make-ups↗
Student access↗
01 / THE CONTEXT
One schedule brings
different decisions together.
Pilates scheduling, students, teachers, contracts and make-up classes need shared context. The challenge is to give the team an operational view and provide teachers and students with access suited to their routine.
One class
Recurring slots, available spots and make-up classes behave differently within the schedule.
Three contexts
The team, the teacher in class and the student need distinct views of the same operation.
02 / THE EXPERIENCE
The same system.
The information needed.
The operations view organizes the day; the tablet focuses on the current class; the portal presents the student’s own routine. Try switching contexts.
CORPUS OS / A DAY AT THE STUDIO
STUDIO / EXAMPLEOPERATIONS VIEW
Today
08:00Lia
Pilates / Studio
3 / 4
Spots available09:00Caio
Pilates / Studio
4 / 4
Class full10:00Lia
Pilates / Studio
2 / 4
Spots availableMake-upOne spot, another context.
A one-off attendance does not change the student’s recurring slot.
ContractA schedule has rules.
Enrollment and plan dates determine occupancy.
IN THE CLASSROOM
09:00 · Pilates
The current class. Attendance within one tap.
0 attendees marked in the example.
STUDENT PORTAL
My routine
NEXT CLASSThursday at 09:00
Pilates · Caio
My planRecurring days and times
Personal information through a separate account.
My accountPayments and notices
Context changes with the role.
Elements reconstructed from the product with fictional data. Actions stay on this page.
03 / PROBLEM → ITERATION
Changing classes
shouldn’t be a search.
When evaluating class changes on mobile, the dropdown proved inadequate. Weekday, time, teacher and availability were mixed into one decision.
“It needs to let me select a weekday, then the class time. Use a friendlier selection interface.”
Feedback recorded during interface evaluation · October 2026
BEFORE / TWO SELECTORS
Too much information
in one list.
Current slotMon 08:00 · Lia ⌄
New slotChoose a slot ⌄
- Mon 09:00 · Caio · 4/4
- Tue 08:00 · Lia · 2/4
- Tue 09:00 · Caio · 3/4
- Wed 08:00 · Lia · 1/4
The selector required reading each combination before understanding which slots worked.
AFTER / GUIDED SELECTION
Schedule class change
One decision at a time. Availability appears with the class.
1. Which current slot will change?
2. Choose the new weekday
3. Choose the class time
4. Choose the class
Selected: Tue · 09:00 · Caio
Progressive reading
The flow structures the decision in four steps, without requiring the full schedule to be read.
Visible capacity
Teacher, occupancy and available spots sit next to each option. Full classes cannot be selected.
Routine continuity
In subsequent tests, scheduled changes gained their own editable and removable cards, allowing a change for each weekly slot.
Usage feedback and iterations documented in the project history. Elements recreated from the class-change component with fictional data. No schedule change is sent to the product.
04 / A CONNECTED SYSTEM
AI interprets.
Rules decide.
The assistant understands intent. Availability, conflicts, transitions, access and billing are checked by the system.
- 01
Request
An intent in natural language.
- 02
Ask Corpus
Identify the action and its context.
- 03
Rules
Check availability and permissions.
- 04
Action
Apply the allowed workflow and record it.
What the case demonstrates
Scheduling, roles, operational logic and interface language, using fictional data.
What depends on activation
Payments and external integrations have their own environments and configuration. They are not presented as real transactions or messages sent by this demonstration.
05 / THE DELIVERY
An operation with shared context.
Corpus OS connects the studio’s day with teachers and students. Iterations to selection, capacity and scheduled changes came from problems found when evaluating the actual routine.