Review process

How Pregnancy Metrics reviews content and formulas

Each page finalized under this process is checked for source-to-claim fit, formula consistency, user understanding, safety boundaries, technical behavior, and production output.

This is an independent editorial and methodology review process led by Pregnancy Metrics' individual developer. It is not a physician review, clinical review, or medical certification. The individual developer retains final editorial and publication responsibility; automated tools are not final reviewers. Pregnancy Metrics does not currently claim external clinician certification, hospital approval, or professional-society endorsement.

Who is responsible for the review

Pregnancy Metrics is independently developed and maintained by an individual developer. The developer is responsible for selecting sources, checking formulas and boundaries, comparing public explanations with the running code, and making the final decision to publish or revise a page.

This process is an editorial, methodological, and technical review. It is not a clinical review performed by a physician, midwife, fertility specialist, hospital, or medical organization, and no external clinician certification is currently claimed.

Automated tools, including AI-assisted research, drafting, code-inspection, and testing tools, may be used to help organize evidence, inspect implementation, identify inconsistencies, or prepare draft wording. These tools are not treated as medical authorities, primary sources, clinicians, or final reviewers.

No medical claim, formula, threshold, assumption, or safety boundary is published solely because an AI or automated tool produced it. Relevant claims must be checked against applicable authoritative sources, and calculator explanations must be checked against the code that produces the result. The individual developer retains final editorial and publication responsibility.

What the review covers

For each page finalized under this process, four areas are checked before release.

Sources and formulas

Check that each formula, calendar offset, assumption, and boundary matches the published method and the authoritative sources listed on the relevant page.

User wording and medical limits

Check that ordinary users can understand the page and that educational estimates are not presented as diagnosis, treatment, clinical redating, or certainty about biological events.

Accessibility and technical behavior

Check keyboard access, focus behavior, error messages, responsive layouts, date handling, metadata, structured data, and regression behavior.

Preview and production acceptance

When the Preview is accessible, inspect its rendered output before release. If Preview access is unavailable, use the local static artifact and browser regression suite for the pre-release check; after the reviewed page change reaches the formal domain, verify the Production output again.

How a page is reviewed

A page finalized under this process follows these review steps from start to finish.

Step 1 — Define the page’s job

Decide which question the page answers, what it should do, what it must not do, and how it relates to the other pages on the site.

Step 2 — Check sources and formulas

Select sources for the specific claim and context rather than applying a universal ranking. Consider the claim type, jurisdiction, current authoritative guidance, directness, applicability, recency, and whether guidance has been superseded. Verify that the sources are real and correctly support the formula, threshold, assumption, and conclusion boundaries on the page. The formula must match the running code.

Step 3 — Check user understanding and safety

Ensure ordinary pregnant people, people planning pregnancy, and family members can understand the page. Estimates are not presented as facts; the site is not framed as a diagnostic, treatment, or emergency-triage service; and users are not required to understand abbreviations or internal technical vocabulary first.

Step 4 — Test the actual implementation

Run formula unit tests, content contracts, TypeScript, linting, and the production build. Check browser interaction, keyboard focus, mobile, tablet, and desktop layouts, and verify that the console, page errors, and resource requests are clean.

Step 5 — Review Preview and Production separately

An implementation report cannot substitute for inspecting the real code or rendered output. Each page change is reviewed within its stated scope. When the Preview is accessible, it is inspected before release; otherwise the local static artifact and browser regression suite provide the pre-release evidence. When a change affects shared registry, navigation, methodology, privacy, or other site-wide content, those files may be updated in the same release. After it reaches the formal domain, the Production page is verified again. Reversion follows the actual files and shared dependencies involved.

Step 6 — Record completion and future triggers

Record the page’s completed status and the real triggers that would require future review. The formula version is updated only when the formula implementation changes. A page is reopened only when a real trigger requires it.

Which sources are prioritized

Source selection is claim-specific, not a universal ranking. The review considers:

the type of claim and the definition, formula, or boundary being supported
the jurisdiction, population, and care setting addressed
current authoritative guidance and the source's directness and applicability
recency, reaffirmation, replacement, withdrawal, and supersession status

Depending on the claim, relevant source categories may include:

professional organizations and formal guidelines
government or public-health agencies
peer-reviewed primary research
systematic reviews
authoritative reference databases

Pages link to the sources that directly support their content.
Whether a source supports a specific formula, assumption, or boundary must be traceable.
Blogs, SEO articles, forums, and AI summaries are not used as a substitute for obtainable authoritative primary sources.
Being cited does not mean the source organization has approved this site.
Large sections of a source are not copied.
Sources are checked for current applicability to the page and its intended audience. The review checks for updated versions, reaffirmation, replacement, withdrawal, and superseded or superseding guidance; an accessible link alone does not prove that a source is still current.

The methodology page lists the formulas, assumptions, and official references. The calculator selection guide helps you choose the right tool for the record you have.

How wording, safety, and accessibility are checked

A due date is an estimate, not a guaranteed delivery day.
Pregnancy weeks are shown as completed weeks and additional days; they follow the record entered.
A conception result is a calendar estimate—not confirmation of fertilization, intercourse, implantation, or parentage.
IVF results use documented Day-3 or Day-5 transfer dates.
Weight-gain pages use guideline-based total ranges and current-change context; they do not create a custom weekly diagnostic classification, nutrition prescription, or diagnosis.
Pregnancy-test timing is a calendar reference, not pregnancy probability or confirmation. Positive results do not establish pregnancy location, viability, or a due date; hCG, recent-pregnancy, and timing boundaries are checked explicitly.
Ovulation and fertile-window results are calendar estimates for a supported cycle range. They cannot confirm ovulation, calculate pregnancy probability, or identify safe days for contraception; fertility-sign explanations are context only and are not diagnostic inputs.
Clinical records and early ultrasound are noted as more informative than a date-only calculator.
Pages do not provide viability, fetal-wellbeing, diagnosis, treatment, or urgent-care determinations.
No traffic-light, risk-color, or diagnostic-style labels are used to mislead users.
Important boundaries are not conveyed by color alone.
Keyboard access, focus order, ARIA behavior, error text, and mobile layouts are tested.

How technical and production quality are checked

Date formulas are tested against fixed examples and boundaries.
Leap years and cross-year dates are tested.
Browser timezone handling is checked.
TypeScript, lint, the static build, and automated browser tests must pass.
Keyboard focus and form errors are checked.
390-pixel, 768-pixel, and 1280-pixel layouts are checked.
Canonical URLs, structured data, robots rules, and the sitemap must not change accidentally.
Console warnings, page errors, and failed resource requests must be clean.
When Preview is accessible, it and Production are checked separately. If Preview access is unavailable, the local static artifact and browser regression suite are used before release; reaching the formal domain is still part of acceptance.

Calculator math lives in pure calendar functions that run in your browser. Automated tests are not a substitute for inspecting the rendered Preview when accessible, the local static artifact, and the Production output, and they are not a clinical review.

When a completed page is reviewed again

A page that is already complete is reopened only when a real change requires it:

authoritative guidance changes
a source is updated, withdrawn, replaced, or becomes unavailable
formula, threshold, supported input, or product scope changes
a production, safety, accessibility, privacy, or legal defect is confirmed
a repeated user misunderstanding reveals unclear wording
a confirmed factual or source-mapping error

The formula version changes only when the formula implementation changes. No fixed or fabricated clinical review date is displayed; a public reviewed or updated date is shown only after a real, traceable substantive review. Ordinary typography or minor wording changes are not presented as medical or formula review, and no annual clinician review is claimed unless it was actually performed. A completed page is reopened when one of the real triggers above applies.

What this review does not mean

no external clinician certification is currently claimed
no physician, hospital, medical board, ACOG, or ASRM approval
no individual patient record or ultrasound review
no guarantee that a calendar estimate matches an individual pregnancy
no diagnosis, treatment, medication, redating, or urgent-care decision
no replacement for pregnancy records or clinical care
no fabricated reviewer name, credentials, portrait, or signature
no reviewedBy, dateReviewed, or similar structured-data claim without a real reviewer and documented review

Report an error or accessibility problem

You can report a formula concern, unclear wording, broken link, incorrect page output, accessibility problem, mobile layout problem, or privacy or disclaimer inconsistency.

Contact support@pregnancymetrics.com. Reports are reviewed as website-quality reports, not as requests for medical diagnosis or emergency advice.

Learn more about the site in About, read the privacy notice and medical disclaimer, or use the calculator selection guide to find the right tool.