Predicting Height for More Than One Child? 5 Mistakes Parents Make
Once a family has more than one kid, height prediction stops being a one-off calculation and turns into an ongoing comparison — the older sibling was tall at this age, the younger one seems shorter, and suddenly everyone wants to know why the numbers don't match. Here are the mistakes that trip families up most often, and how to read the results correctly instead.
Mistake 1: Expecting siblings to match exactly
Say a family has two sons. Because the mid-parental formula only depends on the mother's and father's height, both boys will get the identical mid-parental estimate and the identical ±3.3 inch target range if you run the Parents' height tab for each of them. That's expected — it's not a bug, and it's not a sign that one calculation is "more accurate" than the other.
Where families get confused is when they then check the From current height tab for each son at, say, age 8, and see two different projected numbers. That's also expected: one child might be tracking near the top of the family's genetic range and the other near the bottom, or one might simply be a few months ahead developmentally. Both projections are still consistent with the same shared mid-parental range — they're just two different points inside it.
A useful habit: run the Compare tab separately for each child rather than eyeballing one child's printout against another's. It keeps each sibling's own current-height and Khamis-Roche data attached to their own result instead of getting mentally averaged together.
Mistake 2: Mixing units mid-calculation
The unit toggle at the top of the calculator (ft/in, lb vs. cm, kg) is a convenience — the formulas underneath are unit-agnostic, converting everything to a common scale before calculating. The mistake happens at data entry: a parent measures a child at, say, 127.3 cm, but after switching to the cm field types "127" as a round number, or switches back to ft/in and rounds to the nearest whole inch. Over one input that's a trivial difference; across two parents' heights and a child's current height, small roundings can stack into a target range that shifts by half an inch or so.
If you're going to compare a prediction across visits — say, checking it again in six months — it helps to stick with one unit system for that child's numbers rather than switching back and forth, just to avoid compounding rounding errors.
Mistake 3: Treating the target range as a promise
It's easy to read "5 ft 6 in to 6 ft 1 in" as two hard walls a child's adult height can't cross. In reality, the mid-parental method's range corresponds to roughly 95% confidence — a well-established but not absolute band. Genetics still account for the largest share of the variance (commonly cited as around 70–80%), but the remaining share, driven by nutrition, sleep quality, chronic illness, and the timing of puberty, is enough to occasionally push a result outside the modeled range in either direction.
This matters most for families with a specific medical concern — a child tracking well below the third percentile for age, or a noticeable deceleration in growth velocity between checkups. In those cases, the desk-calculation methods on this page are a starting conversation, not a diagnostic tool; a pediatrician or pediatric endocrinologist, potentially with a bone-age X-ray, is the appropriate next step.
Mistake 4: Relying on just one method
It's tempting to run one tab, get one number, and stop there. But the mid-parental method only "knows" the parents' height — it has no information about how this particular child is actually growing. The current-height and Khamis-Roche methods only "know" the child's own trajectory — they say nothing about genetic potential from either parent. Used together, through the Compare tab, they act as a check on each other: a wide gap between the mid-parental estimate and the Khamis-Roche projection is often worth a mention at the next pediatric visit, even if neither number alone would raise a flag.
| Situation | Best-fit method | Why |
|---|---|---|
| Newborn or toddler, no growth history yet | Mid-parental | Only needs parents' height |
| School-age child, steady growth (age 4+) | Current-height projection | Uses the child's own growth curve |
| Approaching puberty, want a BMI-adjusted view | Khamis-Roche | Adds weight as a maturity proxy |
| Any of the above, for a fuller picture | Compare tab | Runs multiple methods side by side |
Mistake 5: Recalculating on stale measurements
Kids grow in spurts, especially close to puberty, so a height and weight recorded at last year's checkup can already be meaningfully out of date. This mistake is easy to make with siblings in particular — a parent remembers the younger child's approximate height from the older sibling's last measurement and assumes it still applies. Re-measuring at (or close to) the time of calculation, ideally with the numbers from a recent pediatric visit, keeps the current-height and Khamis-Roche results meaningful rather than stale.
A practical rhythm for most families is to revisit the calculation once or twice a year, alongside a well-child visit where height and weight are already being measured accurately — rather than trying to track it more frequently than that.
Ready to run the numbers correctly for each of your kids — mid-parental, current-height, age-2 rule, and Khamis-Roche, side by side?
Try the free Child Height Predictor →