"I heard they don't even teach long division anymore." A parent sent me that in September, along with a photo of a worksheet that looked like subtraction had lost an argument with a rectangle.
They do teach it. What changed is when it shows up and what comes before it, which is why a 4th grade division page can look nothing like the one you filled out at that age.
The timing moved, not the topic
In most schools, the standard long division algorithm, the one with the little house and the digits marching down, lands somewhere in late 5th or 6th grade. Some districts introduce a simple version earlier with one-digit divisors, like 84 divided by 4. Before that, kids spend a year or two dividing in ways that show their reasoning on the page.
So a division packet that comes home in 4th grade full of chunks and rectangles is not a school that gave up on long division. It is a school building toward it.
Is that annoying at 7:40 on a Tuesday? Sometimes. Especially when the directions say "use a strategy" and the page offers no example of the strategy. The logic behind it is decent, though: kids are being asked to understand what division does before they compress it into four fast steps. A child who can only chant "divide, multiply, subtract, bring down" often has no idea what any of those digits mean, and that catches up with them in the word problems and the fraction work that come later.
Partial quotients, in plain English
This is the method that makes parents blink. The name is fancier than the work.
It means: take out chunks. Say the problem is 156 divided by 12. Instead of asking how to do long division, your kid asks how many 12s they can pull out of 156 at once.
- 10 groups of 12 is 120. That leaves 36.
- 3 more groups of 12 is 36. That leaves 0.
- 10 groups plus 3 groups is 13. So 156 divided by 12 is 13.
The chunks don't have to be efficient. A kid who takes out 5 groups, then 5 more, then 3, gets to 13 the same way, just with more writing. That is the part parents tend to fight and shouldn't. Lopsided chunks still land on the right answer, and a kid who picks the chunk they can defend is doing actual thinking instead of following a recipe.
At my kitchen table I ask for the biggest friendly chunk my kid can explain out loud. Not the fastest one. The one they can say a sentence about without staring at the ceiling.
A decoder for the homework page
Division homework arrives in several costumes. Once you know what you're looking at, the folder gets less maddening.
A tall bracket with numbers stacked down the right side. Partial quotients. Those numbers are the chunks, and your child adds them at the end to get the answer.
Subtraction over and over. Same idea, slower. Your child pulls out the divisor in groups and keeps track of what's left.
A rectangle split into pieces. The area model. If the whole rectangle is 156 and one side is 12, the missing side is the answer. Kids usually split it into 120 and 36 because those are friendly pieces.
An "estimate first" box. The teacher wants a ballpark before the exact answer: 12 times 10 is 120, 12 times 20 is 240, so the answer sits between 10 and 20. If a kid writes 130, the estimate raises its hand.
My one rant: a page that introduces a method, gives twelve problems and shows zero worked examples is not productive struggle. It's a scavenger hunt. One sample problem at the top would rescue a lot of evenings.
When the old algorithm finally shows up
It still looks familiar when it arrives: divide, multiply, subtract, bring down. The chant survives. What's different is the framing. Teachers now present it as the shortcut version of the chunking kids already know, not as a set of moves handed down from somewhere.
That compression is the whole point, and also the risk. The standard algorithm is fast and it hides a lot. A kid can put every digit in the right column and still tell you the 1 in the hundreds place is "just a one" instead of 100 groups.
Remainders shift around too. In 4th grade, 157 divided by 12 might be written as 13 R1. A year later the same problem wants 13 and 1/12, and by 6th grade it may want 13.08. The form depends on the unit, and sometimes on the story: if the problem is about loading kids into vans, that remainder means somebody's parent is driving.
Why your way, too early, backfires
I understand the temptation. The dog is barking, dinner is doing that thing where it's either raw or burnt, and you can finish 936 divided by 6 in twenty seconds using the method you learned in 1997.
Sometimes showing it helps. Too early, it costs you. Your child ends up running two systems at once, and switching between them before either is solid makes a kid slower and less sure, not faster. There's also the grading problem: on a lot of pages the teacher is checking whether the strategy from this unit shows up, not just whether the answer is right. That isn't pickiness. If the lesson is partial quotients, the work has to show partial quotients.
Fair times to show your method:
- Your child can already chunk without melting down.
- They ask whether there's a faster way.
- The class has been introduced to the standard algorithm.
- They're in 6th grade and the numbers are getting long.
Even then, call it the shortcut for what they already know, not the real way. The real way is the one they can explain.
What actually helps at the table
Estimate before anyone picks up a pencil. "About how many 12s are in 156?" If your kid says maybe ten, ask what 12 times 10 is. If they land on 120, they have their first chunk and the rest is bookkeeping.
Watch for the real bottleneck, which is usually not division at all. If the multiplication facts aren't automatic yet, every chunk turns into a side quest and the whole page takes an hour. That looks like a division problem wearing a disguise. It's a fact problem, and it's worth fixing separately, in short doses, away from homework.
Use "how many groups of" language out loud. How many groups of 12 can we make? Could we take out ten? What's left? Can we take more? Kids who hear division described in groups hold onto the sharing idea underneath it much longer than kids who only hear steps.
And when the directions are genuinely unreadable, ask. One line to the teacher does it: "Are they supposed to use partial quotients on these, or is the standard algorithm fine?" That one question has saved me from confidently teaching the wrong tool more than once, and teachers would rather answer it on Tuesday than see a failed page on Friday. If the homework has become a nightly fight rather than a method question, that's a different conversation with the teacher and worth having on its own.
Then set a limit. Twelve honest minutes, timer on the stove, and a note in the folder if it's still a mess when the timer goes. Twelve minutes of real work beats forty-five minutes of pencil tapping and sighing while everyone pretends this is building character.
