Common Music School Makeup Lesson Credit Tracking Mistakes and How to Prevent Them

Teacher absences, student cancellations, studio policies, group makeups, and credits are reconciled through messages and calendars, creating forgotten or duplicated obligations. The recurring failures are usually process-design problems rather than motivation problems. For independent music schools and multi-teacher lesson studios, these are the mistakes worth finding before buying or building software.

1. Giving a credit without linking the original lesson

This usually survives because the workflow records activity but not the decision that activity was meant to produce. Add Original lesson and teacher at the point of work and enforce this guardrail: Completion requires recorded evidence that every eligible missed lesson becomes one scheduled makeup, valid credit, policy closure, or billing adjustment with a clear expiration When the exception occurs, keep it visible instead of repairing it privately in email.

2. Applying different policy based on who answers the message

This usually survives because the workflow records activity but not the decision that activity was meant to produce. Add Cancellation party and notice time at the point of work and enforce this guardrail: Automated reminders stop after verified completion or a documented closed reason When the exception occurs, keep it visible instead of repairing it privately in email.

3. Using the same credit for two rescheduled lessons

This usually survives because the workflow records activity but not the decision that activity was meant to produce. Add Policy version and eligibility at the point of work and enforce this guardrail: Keep lesson schedule, attendance, billing, and policy system as the system of record; only necessary coordination data belongs here When the exception occurs, keep it visible instead of repairing it privately in email.

4. Leaving teacher compensation unresolved after a studio cancellation

This usually survives because the workflow records activity but not the decision that activity was meant to produce. Add Credit type, value, and expiry at the point of work and enforce this guardrail: Every open makeup lesson credit needs one owner and a next review time When the exception occurs, keep it visible instead of repairing it privately in email.

Audit five recent records

Pick five completed or abandoned examples and ask:

• Can we reconstruct student, family, and instrument without asking the original owner?
• Can we reconstruct original lesson and teacher without asking the original owner?
• Can we reconstruct cancellation party and notice time without asking the original owner?
• Can we reconstruct policy version and eligibility without asking the original owner?
• Can we reconstruct credit type, value, and expiry without asking the original owner?

If the answer is no, improve the capture point rather than adding a later reporting step. Reports cannot recover decisions that were never recorded.

Use mistakes as software requirements

Turn every frequent failure into a testable requirement. “Better visibility” is vague; “show every record with no owner or next date” can be tested. “More automation” is vague; “stop reminders after the completion condition is recorded” can be tested.

Next step

Explore the Makeup Lesson Credit Board workflow concept and record whether this is painful enough to justify a focused tool.