# When an ultrasound should change the due date

Six days apart at an eight-week scan. ACOG puts the threshold at five days that early, so the ultrasound date replaces the period-based one.

**Estimated due date 2025-10-14 — currently 9w4d, with 213 days to go.**

> This is arithmetic on the dates you supplied, not medical advice. It cannot see an ultrasound, a chart, or a person. Clinical dating is done by a qualified clinician, and an estimated due date is an estimate — most births do not happen on it. Nothing here should change what you do without talking to your own clinician.

## Estimate

| | |
| --- | --- |
| Estimated due date | **2025-10-14** |
| Method | Ultrasound measurement |
| Gestational age on 2025-03-15 | 9w4d |
| Days remaining | 213 |
| Trimester | 1 |
| Estimated conception | 2025-01-21 |

## Period date vs ultrasound

| | |
| --- | --- |
| From the last period | 2025-10-08 |
| From the ultrasound | 2025-10-14 |
| Difference | 6 days |
| ACOG threshold at up to 8w6d | more than 5 days |
| Redated | yes |

The two estimates differ by 6 days. At a scan gestational age of 8w0d (up to 8w6d), ACOG supports redating when the discrepancy exceeds 5 days — so the ultrasound date is used here.

## Milestones

| Date | Gestational age | Milestone | Note |
| --- | --- | --- | --- |
| 2025-04-14 | 13w6d | End of first trimester | Also the last point at which ultrasound dating is at its most accurate. |
| 2025-05-13 | 18w0d | Anatomy scan window opens | The detailed anatomy scan is usually done between 18 and 22 weeks. |
| 2025-06-10 | 22w0d | Anatomy scan window closes | After this the standard views become harder to obtain. |
| 2025-07-21 | 27w6d | End of second trimester | The third trimester begins the following day. |
| 2025-09-23 | 37w0d | Early term begins | ACOG classifies 37w0d to 38w6d as early term, not full term. |
| 2025-10-07 | 39w0d | Full term begins | Full term runs 39w0d to 40w6d. |
| 2025-10-14 | 40w0d | Estimated due date | A reference point, not a prediction. Most births are not on this day. |
| 2025-10-28 | 42w0d | Post-term begins | From 42w0d a pregnancy is classified post-term. |

## Read before relaying this

### Gestational age counts from the last period, not from conception (caution)

This is the most misunderstood fact in the subject. The 40-week clock starts at the first day of the last menstrual period, roughly two weeks BEFORE conception. So at 9w4d the pregnancy is about 7w4d since conception. Weeks 1 and 2 of a pregnancy are, by this convention, before there is a pregnancy.

**What to do:** When comparing against a known conception or transfer date, use that method instead — it does not go through the two-week offset.

### The due date is a reference point, not a prediction (caution)

Only a small minority of births happen on the estimated date. The useful output is the term windows — early term from 37w0d, full term from 39w0d — not the single day.

### Redated to the ultrasound (6 days apart) (caution)

The two estimates differ by 6 days. At a scan gestational age of 8w0d (up to 8w6d), ACOG supports redating when the discrepancy exceeds 5 days — so the ultrasound date is used here.

**What to do:** This follows ACOG Committee Opinion 700. Confirm with the clinician who did the scan — the guidance is a rule of thumb applied to a whole clinical picture.

### Not medical advice (info)

This is arithmetic on the dates you supplied, not medical advice. It cannot see an ultrasound, a chart, or a person. Clinical dating is done by a qualified clinician, and an estimated due date is an estimate — most births do not happen on it. Nothing here should change what you do without talking to your own clinician.

---

Canonical URL: https://due-date.gumballtools.com/dating/when-an-ultrasound-changes-the-due-date
JSON API: `GET https://due-date.gumballtools.com/api/v1/estimate?method=lmp&date=YYYY-MM-DD`
MCP endpoint: `https://due-date.gumballtools.com/api/mcp`