How to check your kid's math homework when you forgot the math
You do not need to remember the math. A simple routine: your kid explains first, you check the setup, then you verify the steps.
There is a moment most parents know. Your kid slides a page of fractions across the table and asks if it looks right. You look at it. You have not divided one fraction by another in years. You remember something about flipping, but not what gets flipped or why. You say "looks good" and hope.
Here is the good news. Checking homework and doing homework are different jobs. You do not need to be able to teach the math. You need a routine that finds out whether your kid understands it, plus a way to verify the answers that does not rely on your memory.
The routine has four parts. It works on math you remember and on math you have never seen.
Start by not looking at the answer
The first instinct is to grab the page and start checking. Skip that. Ask your kid to walk you through one problem out loud.
You are not testing them, and it helps to say so. Try "I forgot how this works, show me what you did." That sentence is honest, and it flips the roles in a useful way. Your kid is now the expert and you are the confused adult who needs it explained.
Listen for two things:
- Can they say why, or only what? "Then I moved the 5 over" is a what. "I subtracted 5 from both sides so the x is alone" is a why. A kid who can give the why usually understands the step.
- Where do they speed up or go vague? A rushed "and then you just do this part" is often the exact spot where the understanding runs out. Ask them to slow down there.
You do not have to know if they are right to hear this. Confidence and clarity sound different from guessing, and you have been listening to this child for years. You will notice.
Pick one or two problems for this, not the whole page. Nobody wants to explain twenty problems after dinner.
Check the setup before the answer
Most homework mistakes do not start at the end of the problem. They start at the top, in how the problem got set up. You can check a lot of that with no math knowledge at all:
- Does the problem on the page match the one in the book? Numbers get copied wrong all the time.
- Did they answer what was asked? A word problem might ask for the total, the difference, or how much is left.
- Is there a unit where there should be one? Feet, dollars, minutes.
- Is the work shown? Many teachers want the steps, and a bare answer can lose marks even when it is right.
Then ask the most useful question in all of math: does this answer make sense? If a word problem about a school bus says the bus holds 4,000 kids, something went wrong, and you do not need algebra to see it.
Two quick checks catch a lot of errors.
Estimate. Take 3/4 + 1/2. Your kid wrote 4/6. You may not remember common denominators, but you can see that 3/4 is already more than a half. Adding another half has to land above 1, and 4/6 is less than 1. So something is off, even if you cannot say what yet.
Plug it back in. If the problem was 2x + 5 = 11 and your kid says x = 3, put the 3 back where the x was. Two times 3 is 6, plus 5 is 11. It checks out. This works for most equations, and it is a habit worth handing to your kid for good.
Use a solver as your answer key
Sometimes neither of those settles it, or the math is past the point where you can estimate anything. This is where a photo-based solver earns its place.
Think of it as an answer key with reasons attached. The back of the textbook gives you an answer, if you are lucky. A solver gives you the answer and the steps that got there, so you can see where your kid's work and the correct path part ways.
The order matters here, so this is the sequence:
- Your kid finishes the work on their own first.
- You take a photo of the problem and read the steps yourself, on your phone.
- You compare. Find the first line where their work and the explanation disagree.
- Point at that line and ask them to look at it again. Do not fix it for them.
That last part is the hard one. You will want to say "you forgot to flip it." Try "something changed between this line and this one, can you find it?" The mistake they find themselves is the one they tend to remember.
Keep the phone in your hand, not theirs, at least at first. The goal is for you to be the coach and the app to be your reference book. Once the app is what does the thinking, it stops being a check, and that gets into the difference between using a solver as a tutor and as a copying machine.
The one we make is AI MathMaster. You take a photo of handwritten or printed work, or type the problem in, and it returns the answer with a step-by-step explanation. Parents helping with homework are one of the groups it was built for. Any solver that shows its steps will work for this routine, ours included. Full disclosure, it is ours, and it is free to download.
One warning. AI solvers can misread a photo, and they can be wrong while sounding sure. Before you trust the steps, check that the problem on the screen matches the problem on the page. If the app and the textbook disagree, the textbook and the teacher win.
When you both get stuck
Some nights the routine will not rescue you. Your kid is lost, the steps make no sense to either of you, and the mood at the table is getting worse. That is fine. Stop.
A note in the margin that says "we got stuck here" is useful information for a teacher. So is a kid who can walk in and say exactly which step they did not follow. A finished page that hides the confusion helps nobody, and a fight over one worksheet can cost more than the worksheet is worth.
If the same topic keeps causing trouble week after week, that is a separate problem from homework, and a human tutor may be the better tool.
The short version
Have your kid explain one or two problems first. Check the setup and ask whether the answer makes sense. Estimate, or plug the answer back in. Use a solver to find the first wrong line, then let your kid find the fix.
You do not have to remember the math. You have to stay curious at the table, and "show me how this works" is a sentence anyone can say. If you want to see how the rest of our small apps get made, the method page has it, and the apps page has the full list.