The accountancy period is nearly over. A second-year B.Com student has written the entry on the board without a mistake: purchases debited, creditor credited, narration neat. Then the teacher asks one quiet question, “Why is purchases debited and not the supplier?”, and the room goes still. The entry was right. The reason was never there.
A correct answer proves a student can copy a pattern; a correct explanation proves they own it. That gap is what the teach-back method is built to find, and commerce hides it better than most subjects because so much of the syllabus can be memorised as a format.
We work on this problem daily while building an AI tutor for commerce students, so this post stays practical. Below are teach-back method examples you can run in a B.Com or BMS class this week: what to ask, what a weak explanation sounds like, and the follow-up that exposes it. If the method is new to you, start with our guide on how the teach-back method works for students.
A teach-back session is short, and the teacher mostly listens
The method comes from healthcare, where clinicians ask patients to repeat instructions in their own words to check they were understood. In a classroom, a teach-back session means the same thing. The student explains a topic back without notes, and the listener asks “why?” and “what if?” until the explanation holds or breaks.
A good session has three parts. The student explains the idea in plain words. The listener asks one question that pushes the idea into a slightly new case. The student notes where they stumbled and goes back to just that part.
Five minutes is usually enough for one topic. The listener’s job is not to teach. It is to find the exact sentence where the explanation goes vague.
Example 1: a day book entry shows whether the rule is understood
Give the student one line from a small shop’s day book: goods bought on credit from a wholesaler for ₹12,000. Ask them to record it, then explain the entry as if to a younger cousin who has never studied accounts.
A weak explanation recites the rule: “Debit what comes in, credit the giver.” A stronger one says the shop now has more goods to sell, and it owes the wholesaler money it has not paid yet. Both sides of the business changed by the same amount.
The follow-up that separates the two is simple: “Next week the shop pays half. What changes, and what does not?” A student who memorised the rule hesitates. A student who understood it says the debt falls by ₹6,000, cash falls by ₹6,000, and the purchases figure stays where it was.
Example 2: a bank reconciliation exposes the direction of every adjustment
Bank reconciliation is where memorised formats fail fastest, because the student must know which way each item moves. Here is an illustrative case with simple numbers. It is a classroom exercise, not data from any business.
Say a café’s cash book shows a bank balance of ₹48,000 at month end. The bank statement shows ₹45,500. The student finds three differences:
- A cheque of ₹4,000 issued to a supplier has not yet been presented.
- Cheques of ₹6,000 deposited on the last day have not yet been credited.
- The bank charged ₹500 that the café has not recorded.
Start from the cash book. ₹48,000 + ₹4,000 = ₹52,000, because money the café thinks has gone is still in the bank. Then ₹52,000 − ₹6,000 = ₹46,000, because money the café thinks has arrived has not reached the bank yet. Then ₹46,000 − ₹500 = ₹45,500, which matches the statement.
Now the teach-back. Ask the student to explain only the first adjustment, in one sentence, without using the word “add”. If they say the cheque is still with the supplier, so the bank has not paid it out yet, they understand timing. If they say unpresented cheques are always added, they have a rule with no reason behind it.
A rule without a reason survives exactly one exam question. The next one, with a different starting point, breaks it.
Picture the same class a month later. A student stands at the board and explains why a cheque in transit pushes the bank figure up. The teacher’s follow-up gets an answer instead of silence. The marks may look the same. The understanding underneath them does not.
Example 3: a furniture workshop’s GST bill can test the idea without testing the rate
GST is the topic where students most often confuse a percentage with a concept. So run the teach-back without asking for the rate at all. Show a small furniture workshop’s sales bill that lists tax separately, and a purchase invoice from its timber supplier that also shows tax.
Then ask: “Who actually bears this tax, and why does the workshop care about the supplier’s invoice?” A weak answer says the workshop pays tax to the government. A strong answer explains that the workshop collects tax from its customer, has already paid tax to its supplier, and can generally set one against the other, subject to the rules that apply to its business. That is why the supplier’s invoice matters.
Any figures in this exercise should come from a rate table the student can see, not from memory. That keeps the teach-back about reasoning rather than recall. Our note on why an AI tutor should never do mental maths makes the same argument for software.
Three more prompts work because each one moves the idea to a new case
| Topic | Teach-back prompt | A weak answer sounds like | Follow-up question |
|---|---|---|---|
| Depreciation | Explain why a delivery van loses value in the books even if it still runs well. | “Because we charge depreciation every year.” | What would profit look like if we never recorded it? |
| Current ratio | A shop has more current assets than current liabilities. Is that good news? | “Yes, a higher ratio is always better.” | What if most of those assets are stock nobody is buying? |
| Break-even | Explain what the break-even point tells a tea stall owner. | The formula, recited. | If rent goes up, must the stall sell more cups or fewer? |
Each follow-up pushes the idea into a case the textbook did not show. That is the whole trick. Our case-based teaching playbook for commerce shows how to build cases like these around businesses students recognise from their own city.
Sixty students and one period is a fair objection, and it has answers
The strongest objection comes from faculty, and it deserves respect. A teach-back session is one listener and one explainer. A lecture hall has sixty students and forty-five minutes. Nobody can listen to sixty explanations before the bell.
We do not think the answer is to drop the method. Three adjustments make it workable. Pair students and give the listener a card with the follow-up question, so half the class explains while half probes. Collect written teach-backs of three or four sentences as an exit slip, and read them for the vague sentence, not the right answer. Then rotate: one topic, a different ten students each week.
Software can carry part of the load, provided it asks instead of answers. In Teach-Back, a Socratic assistant asks the follow-up questions with each student, never does graded work, and shows faculty a gap heatmap of where the class is stuck. But the method works on paper first, and it should. A tool earns its place only if it does what a good listener already does.
What to do this week
- Pick one topic from this week’s syllabus that students usually memorise as a format, such as bank reconciliation.
- Write one teach-back prompt and one follow-up question that moves the idea to a new case.
- Run it in pairs for five minutes, with the follow-up printed on the listener’s card.
- Collect a three-sentence written teach-back from everyone and mark the first vague sentence in each.
- Open next week’s class with the most common vague sentence, and browse our guides on teaching commerce for understanding for the next topic.
None of this needs a new syllabus. It needs one extra question, asked calmly, after the right answer.