What drifting attendance and credits look like
Picture a tutoring center coordinator closing the week. One family asks whether yesterday's no-show still counts against the pack. Another insists a cancelled session earned a make-up credit. The only shared record is a spreadsheet with columns labeled "credit" that nobody can agree means attended, excused, or already used.
That scene is an illustration, not a TwoQM client. Many professional services tutoring centers know the gap: attendance and make-up balances live in different chats while families still expect a clear answer. TwoQM builds custom software that encodes your attendance and credit rules once so sessions marked and credits earned stay on one shared student record.
This article is about session attendance and make-up credits — marking attended, no-show, or cancelled with a policy reason, and tracking make-up balances with earned and used dates. It is not booking or inquiry routing, and it is not class pack balances and freeze requests, a different member-facing pack workflow. TwoQM builds tooling. It does not give educational or legal advice. Your center, its policies, and its counsel decide how credits work.
Here is an original example, not a measured result. A Rio Grande Valley tutoring center sells session packs. Front desk marks "came" in one chat. Tutors text no-shows. A parent coordinator tracks make-ups in a personal sheet. At month end a family is told they have two make-ups left — then another staffer finds those credits were already used for a sibling session nobody logged against the balance.
When it doesn't work, attendance and credit collide, a no-show has no named policy reason, make-up notes live only in chat, and nobody can say who approved a credit adjustment. Nobody is careless. Attended, cancelled, and make-up simply never lived as separate fields on one student and session-credit record.
One shared student and session-credit record
Treat each student's attendance and credit balance as one record the front desk, tutors, and family coordinator all see. Each record holds:
Session attendance. Attended, no-show, or cancelled, with date, tutor, and a policy reason when the status is not a simple attended mark — pending review or confirmed.
Make-up credit balance. Credits earned and credits used as separate lines, each with date, related session, and remaining balance after the line.
Credit adjustment ownership. The named person who may approve an exception or manual adjustment, and the date, before the balance changes.
Family-facing summary readiness. Whether the current balance is ready to share, or still waiting on an open dispute.
Only confirmed attendance and approved credit lines feed the family-facing balance; open disputes stay visible until a person resolves them.
Keep attendance and make-up as different fields
The same record should make the split obvious. A cancelled session does not automatically create a make-up credit unless your written policy says it does. Attendance marks what happened. Credit lines record what was earned or used. If both apply in the same week, they appear as linked but separate fields, not one merged "sessions" total. That rule belongs in the system, not in memory.
Shared view for tutors, front desk, and families
Tutors should see their own session list and disputed marks without editing credit balances. Front desk confirms attendance against the roster. The family coordinator sees the same approved balance without hunting chat. When a mark fails review — wrong student, double booking, or a credit claimed twice — the line goes back to pending with a short note. The balance cannot flip to "ready to share" while required lines are still open.
Bilingual family notes when the Rio Grande Valley team needs them
Many Valley centers serve families in English and Spanish. Keep family notes and credit-summary wording as sibling fields on the same student record when both languages matter, not as separate chat texts. Staff still write and approve the wording; software only keeps both versions together.
Draft reminders a person still owns
AI can help in narrow ways a person reviews: drafting a reminder note for an upcoming make-up deadline, proposing bilingual credit-summary text from fields staff already entered, or flagging a student with pending attendance before the weekly family update. It never marks attendance alone, never adjusts credit balances alone, and never emails families alone. Ordinary business automation covers the rest: remind tutors to confirm sessions, notify the credit owner when a disputed line is still open, and block "balance ready" until the named owner confirms.
Connect the roster to the tools you already use
Scheduling may stay in your booking tool. Payments may stay in membership or invoicing. The attendance and credit record can sit on top as the status, balance, and approval layer. Connected systems can pass confirmed attendance into the roster your staff already uses. Whether those tools support the connections is confirmed during scoping. Sometimes a disciplined shared sheet, a written credit policy, and a named adjustment owner are enough. If that already works, scoping should say so before anything custom is built.
Where to start this week
Pull last month's family credit disputes. For each one, note whether the confusion was attendance, a no-show reason, a make-up earned, a make-up used, or adjustment ownership. Then list who may confirm attendance and who may approve a credit change. That list is the first draft of your attendance and credit rules.
If you want attendance and make-up credits that stay on one shared student record, TwoQM can scope the fields, approvals, and connections around tools your center already uses. Pricing explains how business apps, systems, and custom software are scoped. Nothing here is educational or legal advice.
Describe Your Attendance and Credit Rules · Explore TwoQM custom software