| Metric | Value | Copy |
|---|---|---|
| {{ row.label }} | {{ row.value }} |
| Checkpoint | Gestation | Date | Status | Planning note | Copy |
|---|---|---|---|---|---|
| {{ row.label }} | {{ row.gestationLabel }} | {{ row.dateLabel }} | {{ row.status }} | {{ row.note }} |
| Window | Gestation | Date span | Status | Planning focus | Copy |
|---|---|---|---|---|---|
| {{ row.label }} | {{ row.gestationLabel }} | {{ row.dateSpan }} | {{ row.status }} | {{ row.focus }} |
Pregnancy due dates are calendar estimates used to anchor gestational age, scan timing, leave planning, support arrangements, and later-pregnancy follow-up. Obstetric dating counts from the first day of the last menstrual period rather than from fertilization itself, which gives clinicians and families one shared timeline even when conception happened about two weeks later.
That timeline can start from different kinds of evidence. A reliable last menstrual period often works well when cycles are steady. A known conception date or an IVF embryo transfer can give a tighter starting point when those dates are documented. An ultrasound can also set gestational age, especially when periods are irregular or the menstrual date is uncertain. The main question is not which route sounds most familiar, but which dating anchor is most reliable for this pregnancy.
The expected delivery date works best as the center of a term window, not as a promise that labor will begin on one exact day. The same pregnancy can be described as preterm, early term, full term, late term, or post-term depending on how many completed weeks have passed. That is why small dating shifts matter. Moving the starting point by only a few days can move testing windows, follow-up timing, and post-dates planning.
This description is for informational planning only, not for diagnosis, treatment, or emergency decision-making. If your maternity team has already assigned an official due date, that date should guide medical care, especially when it differs from a calendar estimate.
Gestational age is measured from an LMP-equivalent day 0. That standard keeps pregnancy length comparable even when the known starting event is not a period. A conception date can be translated back by about 14 days because obstetric dating starts before fertilization. IVF transfer dating does the same thing, but it also subtracts embryo age on transfer. Ultrasound dating uses the scan date and the gestational age assigned at that scan to reconstruct the same shared timeline.
Once the anchor date is set, a due date is created by adding the chosen gestation length. The default planning length is 280 days. In LMP mode, cycle length shifts the due date by the difference from a 28-day cycle, which mirrors the common assumption that ovulation is later in longer cycles and earlier in shorter ones. A manual adjustment can then mirror a clinician-assigned date exactly.
Earlier ultrasound dating is generally more accurate than later ultrasound dating, so first-trimester scans are treated as stronger anchors than scans after about 22 weeks. The confidence badge also falls when LMP dating is paired with cycle lengths outside the common 21 to 35 day range. Those badges describe dating certainty, not pregnancy health, fetal growth, or the chance of labor starting on the due date.
The main calculation adds the planning horizon to the chosen dating anchor, then measures today's gestational age from that same anchor.
| Symbol | Meaning | Where it comes from |
|---|---|---|
Anchor |
The LMP-equivalent day 0 used for all later timing. | The selected dating method and its date inputs. |
G |
Standard gestation length. | Standard gestation, default 280 days. |
ΔCycle |
Cycle-length shift applied only in LMP mode. | Cycle length minus 28. |
ΔOffset |
Manual change added to match another assigned due date. | EDD adjustment. |
| Dating method | Anchor rule | What changes the result |
|---|---|---|
| Last menstrual period | The entered LMP date becomes the anchor. | Cycle length can move the due date earlier or later than the 28-day baseline. |
| Known conception | The anchor is the conception date minus 14 days. | The due date reflects the usual gap between obstetric age and fertilization age. |
| IVF embryo transfer | The anchor is the transfer date minus 14 days and minus embryo age. | Day-3, day-5, and day-6 transfers land on different due dates. |
| Ultrasound dating | The anchor is the scan date minus the entered gestational weeks and days. | Earlier scans are treated as stronger dating evidence than later scans. |
Several checkpoints come from fixed gestational-day boundaries. These are useful for interpreting summary badges, milestone rows, and later-term warnings.
| Checkpoint | Gestational day | Week label | How the planner uses it |
|---|---|---|---|
| First trimester complete | 97 | 13w 6d | Marks the end of the first trimester in the milestone calendar. |
| Third trimester begins | 196 | 28w 0d | Changes the current trimester label and later-care emphasis. |
| Early term begins | 259 | 37w 0d | Starts the early-term window. |
| Full term begins | 273 | 39w 0d | Marks the full-term window that contains the due date. |
| Late term begins | 287 | 41w 0d | Triggers more active post-dates planning. |
| Post-term threshold | 294 | 42w 0d | Triggers the post-term warning and the strongest follow-up language. |
The best first pass is to choose the strongest dating evidence you actually have. Use LMP when the menstrual date is clear and cycles are fairly steady. Use conception or IVF transfer when those dates are documented. Use ultrasound dating when an early scan assigned the pregnancy age or when cycle timing is uncertain enough that menstrual dating feels shaky. If your care team has already given you an official due date, the safest approach is to make the planner match that date instead of treating a different estimate as equally valid.
The summary box is the fastest trust check. Start with Estimated due date, then look at Dating confidence, Current stage, and Next checkpoint. After that, Dating Snapshot shows the anchor date behind the calculation, Pregnancy Calendar places milestone dates on the calendar, and Checkup Pace turns the same timeline into average-risk visit windows for a first pregnancy or a follow-up pregnancy.
The warnings deserve real attention. A cycle length outside 21 to 35 days, an ultrasound entered before about 7 weeks or after about 22 weeks, or custom settings that push the due date outside the usual 38 to 42 week planning center all mean you should slow down and compare the result with your dating scan report, IVF paperwork, or clinician-assigned EDD. A high confidence badge does not mean labor will start on the due date, and a lower confidence badge does not mean something is wrong with the pregnancy. It only tells you how solid the dating anchor is.
After you confirm the anchor date, use Full term begins, Late term begins, and Post-term threshold as the practical markers for later planning. Those dates are usually more useful for transport, childcare, work coverage, and post-dates monitoring than the due date alone.
Work from the dating anchor first, then use the later tabs only after the main date looks right.
Estimated due date is the center of the planning timeline. It is not a promise that labor will start on that exact day. The most important companion fields are Dating confidence, which tells you how secure the dating anchor is, and Current stage, which tells you whether the pregnancy is still preterm, early term, full term, late term, or post-term today.
Even a Very high confidence IVF date should not be overread as a prediction of the baby's actual birthday. The corrective check is simple: compare Estimated due date with the official date in your scan report or maternity record, then keep one date consistent across appointment booking, work forms, and family planning.
Pregnancy dating changes how people plan scans, follow-up, and late-term monitoring, so a few days can matter. Use the planner as a scheduling aid, not as medical advice or as a substitute for a clinician's record.
If there is bleeding, leaking fluid, severe pain, reduced fetal movement, or disagreement about the official due date, contact your maternity provider rather than relying on the calendar alone.
No. The due date is the center of the timeline, not a guaranteed birthday. Most pregnancies deliver earlier or later than that exact date.
Use the strongest evidence you have. A clear LMP is often fine when cycles are steady. Known conception, IVF transfer, or an early dating scan usually deserves more weight when those dates are documented.
The planner subtracts embryo age from the transfer date before building the gestational timeline. A day-3 transfer and a day-6 transfer therefore land on different due dates even when the transfer happened on the same calendar day.
Common reasons are a cycle length outside 21 to 35 days, a very early ultrasound, an ultrasound after about 22 weeks, or custom settings that push the due date outside the usual 38 to 42 week planning center. Those messages are asking you to verify the dating anchor, not telling you that the pregnancy is unhealthy.
The page needs a valid reference date before it can build the timeline. If the date is missing or in the future, the timeline stays hidden until you correct it.
No. It is an average-risk planning view that helps place common booking, scan, and follow-up windows on the calendar. Real prenatal care is individualized.