
Overview
We designed the package workspace so the entitlement card and attendance ledger explain the same balance.
View the screen ↓
We designed the package workspace so the entitlement card and attendance ledger explain the same balance.
The account begins with 12 allocated sessions; five attendance debits and one disputed cancellation leave six remaining.
A package balance can be disputed when the customer cannot trace the deductions. Entitlement, attendance and the query need a shared record.
Two future sessions are earmarked rather than deducted, leaving four unallocated. We show the disputed debit in the ledger until a coordinator records a decision. That makes the current balance understandable without silently rewriting the history when a question is raised.
The build brings overview, session entitlement, attendance ledger, balance query BQ–018 and package terms and inclusions into one workspace.

We designed the package workspace so the entitlement card and attendance ledger explain the same balance.
View the screen ↓
The allocation and the calculation behind Jordan’s remaining sessions.
View the screen ↓
Posted debits, future visits and their effect on the session balance.
View the screen ↓
I contacted reception the morning before my appointment. Could you check the time recorded? I expected the session to stay in my balance.
View the screen ↓
The administrative rules attached to Jordan’s individual session package.
View the screen ↓Explore the interface, from the first impression to the finer details.
Choose a view to enlarge ↓Tell us what your customers or team need to do. We can help define the pages, records and interactions around that task.