| Metric | Value | Copy |
|---|---|---|
| {{ row.label }} | {{ row.value }} | |
| No age snapshot rows yet. | ||
| {{ header }} | Copy |
|---|---|
| {{ cell }} | |
| No milestone mapping rows yet. |
| {{ header }} | Copy |
|---|---|
| {{ cell }} | |
| No age-use notes yet. |
| {{ header }} | Copy |
|---|---|
| {{ cell }} | |
| No transition guardrails yet. |
Corrected age is a way to judge a preterm infant's or toddler's progress from the date they were expected to be born, not only from the calendar date of birth. That matters because a child who arrived several weeks early can look "late" on milestones if every check is read against chronological age alone.
This calculator turns gestational age at birth and current chronological age into a corrected-age snapshot, a prematurity offset, and a milestone timeline. It is built for the recurring follow-up question in preterm care: what does this child's age look like once the weeks born early are taken into account?
The page gives you more than one number. It also maps common corrected-age checkpoints to their chronological equivalents, shows where the child sits relative to a chosen correction window, and produces guidance text that can be copied into handoff notes, parent updates, or follow-up plans.
A practical example is a baby born at 32 weeks' gestation who is now 6 months old by the calendar. The calculator subtracts the 8-week prematurity offset, shows the corrected age in months, and lays out where 3, 6, 9, 12, 18, and 24 month corrected milestones land on the chronological calendar.
A corrected-age result is a timing lens, not a diagnosis. Public pediatric guidance commonly uses adjusted or corrected age through about 2 years, so any longer window chosen here should be treated as a local planning choice rather than a universal rule.
This calculator is most useful when the debate is about timing rather than symptoms. If a family, therapist, or clinic is asking whether a milestone should be read against chronological age or corrected age, the output gives a consistent answer and shows the milestone date shift that prematurity creates.
The default workflow is straightforward: enter gestational age at birth and the child's current chronological age, then review the summary before touching any advanced settings. If your follow-up program uses a stricter or looser transition point, you can adjust the corrected-age window, milestone buffer, and transition buffer to mirror that policy more closely.
Advanced guidance controls do two different jobs. The corrected-age window and the two buffers change how close-to-cutoff cases are framed, while the follow-up interval and catch-up priority change the wording and cadence of the guidance notes rather than the corrected-age math itself.
| Situation | What to look at first | Why it helps |
|---|---|---|
| Child is clearly under the correction cutoff | Summary badge and milestone timing rows | Shows the corrected age to use for milestone conversations and the chronological calendar equivalent for each checkpoint. |
| Child is close to the handoff point | Transition guardrails | Shows the core window, extra bridge period, and the current status so teams can avoid switching too abruptly. |
| You need shareable follow-up notes | Guidance tab and exports | Packages the result into copyable guidance, CSV, DOCX, JSON, and chart exports for charting or family communication. |
The core calculation is intentionally narrow. Gestational age at birth is limited to 22 to 40 completed weeks, chronological age is limited to 0 to 60 months, and the prematurity offset is calculated as 40 weeks minus gestational age at birth. Corrected age is then chronological age minus that offset, converted from weeks to months with the package's built-in 4.3482142857 weeks-per-month factor and never allowed to fall below zero.
The milestone table is generated from fixed corrected-age checkpoints at 3, 6, 9, 12, 18, and 24 months. For each checkpoint, the package adds the prematurity offset back to show the matching chronological age, then labels that row as corrected-age, blended-review, or chronological-only based on the selected correction window and the added milestone buffer.
The default correction window is 24 months, but the form allows 12 to 36 months. A transition buffer of 0 to 6 months can extend the blended-review period, and a milestone buffer of 0 to 8 weeks softens hard cutoffs at milestone edges so the page does not overstate delay from a date that is only barely on one side of the line.
The guidance output is generated locally from the result metrics. It emphasizes continuing corrected-age interpretation or transitioning to chronological framing, adds a catch-up priority lens, and recommends documenting corrected and chronological ages side by side. This slug does not calculate developmental scores, symptom screens, or growth percentiles; it stays focused on age correction, timing, and follow-up wording.
| Component | Current package behavior | Practical meaning |
|---|---|---|
| Gestational age at birth | Numeric input, 22 to 40 weeks | Determines how many weeks early the child was relative to 40 weeks. |
| Chronological age | Numeric input, 0 to 60 months | Acts as the calendar-age anchor for the correction. |
| Corrected-age window | Numeric input, 12 to 36 months | Sets the main period where the result recommends corrected-age framing. |
| Milestone buffer | Numeric input, 0 to 8 weeks | Adds slack around milestone timing so borderline dates are not over-read. |
| Transition buffer | Numeric input, 0 to 6 months | Creates a bridge zone after the core window. |
| Generated outputs | Summary, metrics, milestone timing, guidance, transition guardrails, chart, JSON, CSV, DOCX | Supports both quick interpretation and documentation. |
No server-side processing path is present for the calculation itself. The page computes results in the current browser session and only leaves the page when you deliberately copy or download an export.
If a result feels surprising, keep the gestational age fixed and change only one advanced timing setting at a time. That makes it much easier to see whether the shift came from policy choices or from the age inputs themselves.
The top summary tells you the main story in one pass: corrected age in months, chronological age, weeks of prematurity, and whether the child is within or beyond the current correction window. That summary is best read as a framing aid for milestone review, not as a pass or fail label.
The most useful distinction is the transition status. "Inside corrected-age window" means the page still recommends using corrected age as the main lens. "Bridge zone" means the child is near the cutoff and the page is deliberately showing both corrected and chronological framing. "Chronological-only zone" means the core correction period has passed for the selected window.
| Result area | What it shows | What not to over-read |
|---|---|---|
| Corrected age | The age after subtracting the prematurity offset from chronological age. | It does not prove normal or delayed development by itself. |
| Milestone timing | Chronological equivalents for 3, 6, 9, 12, 18, and 24 month corrected checkpoints. | These are timing guides, not individualized developmental predictions. |
| Transition guardrails | The chosen cutoff, extra bridge period, and current status. | A longer custom window is not automatically standard practice everywhere. |
| Guidance rows | Follow-up wording tied to the current result and catch-up emphasis. | The guidance is not a substitute for symptom review, examination, or local policy. |
Near 24 months, changes in classification are especially easy to overinterpret. Pediatric growth guidance already warns that transitions around age 2 can shift how a child appears on charts, which is why the bridge-zone view is best treated as a discussion aid rather than a hard switch.
A 32-week gestation means the baby arrived 8 weeks early. The calculator converts that to about 1.84 months and reports a corrected age of about 4.16 months.
That is the kind of case where the summary, milestone table, and guidance all point in the same direction: keep corrected age as the main timing lens.
At 29 weeks' gestation, the prematurity offset is 11 weeks, or about 2.53 months. A child who is 23 months old on the calendar therefore lands at about 20.47 months corrected.
With the default 24-month correction window, the result still sits inside the corrected-age period, and the 24 month corrected milestone maps to about 26.5 months chronological.
A 34-week gestation means 6 weeks early, or about 1.38 months. The corrected age is about 23.62 months, which is still close to 2 years even though the calendar age has moved past it.
With a 24-month correction window and a 2-month transition buffer, this type of case falls into the bridge zone. That is exactly the situation where documenting corrected and chronological ages side by side prevents confusing handoffs.
Chronological age is the time since birth. Corrected age subtracts the weeks the child was born early, which gives a fairer developmental timing reference during early follow-up.
Adjusted-age developmental guidance commonly runs through about 2 years, and CDC growth-chart guidance also shifts chart use at 24 months. The package therefore defaults to a 24-month correction window and lets you add a bridge period when local practice is more gradual.
Yes. The form allows a corrected-age window from 12 to 36 months plus an extra transition buffer, but that extended range should be treated as a custom policy aid rather than a universal standard.
No. This slug focuses on age correction, milestone timing, transition framing, and guidance notes. It does not ask for exam findings, developmental screening answers, weight, or length.
In the current package, the main corrected-age output is driven by gestational age, chronological age, and the timing buffers. The visible calculation and milestone timeline are not percentile-curve outputs.
No server-side calculation path is present for this page. The inputs and exports stay in the current browser session unless you deliberately copy or download them.