| Metric | Value |
|---|---|
| {{ row.label }} | {{ row.value }} |
| No metrics yet. | |
| {{ header }} |
|---|
| {{ cell }} |
| No visit ledger rows yet. |
| {{ header }} |
|---|
| {{ cell }} |
| No interval audit rows yet. |
| Priority | Recommendation | Rationale | Timeline |
|---|---|---|---|
| {{ row.priority }} | {{ row.recommendation }} | {{ row.rationale }} | {{ row.timeline }} |
| No follow-up plan rows yet. | |||
Growth percentile trend review is about trajectory, not just size at one visit. A child can stay near the same absolute height or weight range while drifting across percentile space, or can look concerning on one visit and settle again once the next measurement is added. This calculator turns serial height, weight, or BMI entries into a clearer longitudinal picture.
The tool takes age-in-months visit rows, maps each visit to a percentile and z-score using a built-in sex-specific reference profile, and summarizes what happened between the first and latest measurement. Instead of leaving you with a list of raw numbers, it surfaces net shift, downward shift from baseline, major band crossings, a short projection window, and a guidance layer for follow-up planning.
That makes it useful when the real question is not "What percentile is this child today?" but "Has the pattern stayed on the same channel, or has it started to drift?" A pediatric follow-up, school-health review, or parent education conversation often needs exactly that kind of answer. The chart and visit table make it easier to show whether movement is gradual, abrupt, upward, or downward.
The practical caution is that this package is a structured screening aid, not a full clinical growth-chart system. Its WHO-style, CDC-style, and hybrid options are internal reference modes built into the bundle, and its crossing audit uses major marks at the 3rd, 15th, 50th, 85th, and 97th percentiles. Concerning results still need accurate measurement technique, the broader history, and clinical interpretation.
The safest way to use the result is as an organized trend summary. It can sharpen follow-up questions, but it should not be treated as a diagnosis, clearance, or substitute for standardized pediatric growth assessment.
Start with one consistent metric stream. Choose Height, Weight, or BMI in Visit metric, keep the matching unit fixed, and paste one row per visit as age_months,value. The bundle sorts the visits by age, keeps the latest duplicate age if you entered the same month twice, and then rebuilds the same summary, visit table, crossing audit, guidance table, chart, and JSON export from that cleaned series.
For most first passes, leave Growth reference set on Hybrid continuity model, Risk tolerance on Balanced, and Intervention urgency on Routine. Those defaults give you a neutral starting point before you tighten or relax the alert posture.
The advanced controls decide what counts as notable. Band crossing alert sets the crossing threshold, Percentile-shift alert sets the absolute shift threshold, Projection horizon sets the short forecast window, and Directional alert focus tells the tool whether to watch downward drift, upward drift, or both.
Directional alert focus on Downward drift only and read Downward shift from baseline before anything else.Centile Crossing Audit before reacting to the summary badge alone. That tab isolates the exact drift direction, crossing count, projection window, and trend-alert state.The strongest use case is a sequence of reasonably spaced visits measured in the same way. A single visit cannot show trend, and a noisy series can create false crossings that look more meaningful than they are.
The parser accepts one visit per line and reads the first two numeric values from each row. Blank lines are ignored, non-numeric rows raise a row-specific error, and duplicate ages are collapsed so the latest row for that month wins. Height inputs are converted to centimeters when needed, weight inputs are converted to kilograms when needed, and BMI stays in kg/m^2.
Each cleaned visit is then passed through a built-in growth model for the selected sex and metric. The model starts from age-anchored medians and standard-deviation curves, applies a modest reference-mode adjustment, and converts the result into a z-score and percentile. WHO-style and CDC-style are therefore internal profile modes, not live official chart lookups.
The trend logic itself is straightforward and transparent. Net percentile shift is the latest percentile minus the first. Major band crossings counts how often the path crosses the built-in major marks at 3, 15, 50, 85, and 97. Downward shift from baseline isolates loss from the starting percentile even when the current direction rule ignores upward movement. Projected percentile extends the first-to-latest slope across the selected projection horizon, then clamps the estimate so it stays inside the visible percentile scale.
The guidance layer is not generic filler. It reads the computed trend metrics back into a rule set shaped by Risk tolerance, Guidance follow-up interval, and Intervention urgency. A routine-looking series keeps longer follow-up timing. A trend with multiple crossings, a large shift, or a triggered direction rule compresses that timing and upgrades the recommendation priority from Routine toward Watch, Priority, or Immediate.
The chart tab plots the observed percentile line across visits and overlays fixed dashed threshold lines at the 3rd and 97th percentiles. That keeps the display focused on the screening bands the bundle uses most directly. The visit-detail table then pairs each age with the entered measurement, the computed percentile, the z-score, and the interpretation band so you can see exactly which visits are driving the headline result.
| Output | How the package builds it | Why it matters |
|---|---|---|
Percentile and Z-score |
Derived per visit from the selected sex, metric, age in months, and reference mode | Turns a raw measurement into a same-age comparison point |
Net percentile shift |
Latest percentile minus first percentile | Shows the overall direction and size of movement across the series |
Major band crossings |
Total movement across 3, 15, 50, 85, and 97 percentile bands | Highlights channel changes that are easier to miss in raw point values |
Projected percentile |
Extends the first-to-latest slope across the chosen 3 to 18 month horizon | Offers a short-range "if this pace continues" scenario |
Trend alert |
Triggered when the crossing count meets the threshold or the direction-rule shift is large enough | Separates stable drift from patterns that deserve review sooner |
Because everything runs in the browser for this slug, the visit data and exports stay local to the current session unless you choose to copy or download them. That local-only behavior is useful for draft review, but it does not remove interpretation risk. Growth monitoring still depends on accurate measurements over time, cautious chart transitions, and the full clinical picture.
Sex, choose Visit metric, and set the matching unit. Height accepts centimeters or inches, weight accepts kilograms or pounds, and BMI stays in kg/m^2.Visit data rows using age_months,value. Example height rows look like 12,74.9, 24,86.1, 36,95.0, and 48,102.2.Percentile Trend Metrics first, especially First visit percentile, Latest visit percentile, Net percentile shift, Major band crossings, and Trend alert.Visit Percentiles to verify that the per-visit percentiles and z-scores match the story you think the summary is telling.Centile Crossing Audit when you need a compact triage view of drift direction, downward shift, projected percentile, and the active direction rule.Percentile Trend Guidance for follow-up framing, then open Percentile Trend Chart if you want to visualize the path and export the chart as PNG, WebP, JPEG, or CSV.JSON when you need the full input-and-output package captured in one machine-readable record.If the red error banner appears, fix the rows before interpreting anything else. A parsing error, mixed unit history, or sparse series can make the trend look more certain than it really is.
The headline number is only the beginning. A shift from the 55th to the 48th percentile may look like movement, but it is a modest drift if no major band was crossed and the alert stayed off. A fall from the 52nd to the 14th percentile tells a different story because it combines a large percentile drop with multiple band transitions and a stronger chance that the direction rule will trigger.
The built-in interpretation bands are intentionally broad: below 3rd percentile is marked severely low, 3rd to below 10th is low, 10th to below 90th is typical range, 90th to below 97th is high, and 97th or above is very high. Those bands help explain where the latest visit sits, but the more important longitudinal signal is whether the child has stayed in a similar channel or crossed several channels over time.
The projection deserves restraint. It is a straight-line extension of the observed slope, not a biologic forecast. When visits are sparse, noisy, or clustered in time, the projected percentile can be helpful as a "watch this direction" flag but should not be mistaken for a likely endpoint. That is why the guidance tab also emphasizes measurement consistency and revisit cadence.
A stable result usually looks like a small net shift, few or no major crossings, and a non-triggered direction rule. A review-worthy result usually combines a larger shift with repeated crossings or a strong downward move from baseline. In either case, interpret the trend beside the visit spacing, the measurement method, and the age context before drawing conclusions.
Enter height rows of 12,74.9, 24,86.1, 36,95.0, and 48,102.2 in centimeters with the default settings. A series like this usually stays within a similar percentile channel, produces a modest net shift, and keeps Trend alert in the stable range. The chart is useful here because it shows whether the line is gently drifting or truly crossing into a different band.
Suppose the weight rows are 12,10.4, 24,11.0, 36,11.7, and 48,12.3 in kilograms. If the early visit started near the middle percentiles and the later visits flatten relative to age expectations, the summary can show a clear negative shift, a larger Downward shift from baseline, and enough major crossings to trigger review. In that case the crossing-audit and guidance tabs become more important than the latest visit alone.
If you paste 12 months,74.9 instead of 12,74.9, the parser raises a row-specific numeric error and the result should be treated as invalid until the input is fixed. After correcting the rows, rerun the baseline and compare the new summary with the chart. The lesson is simple: trustworthy trend review starts with clean, consistently measured visit data.
Use one line per visit with age_months,value. Spaces, commas, semicolons, tabs, and pipe separators all parse, but the first two values on each kept line must be numeric.
They are internal reference modes used by this package to shift the built-in median and spread assumptions. They help the tool behave more like WHO-oriented infancy review, CDC-oriented later-childhood review, or a blended continuity mode, but they are not a direct replacement for official charting software.
Those are the major bands hard-coded for this slug. They create a practical middle-ground view of centile movement instead of counting every small percentile change as a crossing.
It is a short straight-line extension of the observed percentile slope across the chosen 3 to 18 month window. It is a planning cue, not a forecast of what must happen.
No. It is best treated as an educational and screening-style review aid. Abnormal or fast-changing results still need accurate remeasurement, the full growth history, and clinical judgment.
No server helper is shipped for this tool. The calculations and exports are produced in the browser for the current session.