Official, policy-derived and estimated dates

A · Official date

The manufacturer or regulator publishes a specific date for the exact model or clearly defined family. The source, scope, and check date should be visible.

B · Policy-derived date

A duration such as seven years is combined with a documented start date. The calculation and assumptions must remain visible beside the result.

Estimated or unknown

When primary evidence is incomplete, a date should be labelled estimated or left unknown. A precise-looking date is not evidence by itself.

Read the claim before reading the calendar

A date can look exact even when the underlying statement is broad. First ask what the source actually promises: a model-specific final month, a minimum number of years, a number of OS generations, or only inclusion in a current update list. A published date for an exact SKU can qualify as Grade A. A calendar value produced by adding a duration to a documented start event is Grade B and must show the arithmetic. An analyst forecast, historical pattern or retailer statement cannot silently become either. The visible grade, scope, precision and checked date let a reader reconstruct why the calendar appears and what would invalidate it.

Policy-derived means reproducible, not guaranteed

A proper derived date names the duration, the start event, the start date, the rounding rule and the resulting precision. For example, seven years from first US availability may produce an end month; it does not prove an exact final patch day in Japan or on a carrier build. The wording should be: policy-derived, N years from the named event on the named date, rounded by the stated rule, at month or day precision. If one input is missing, the calculation stops. Reproducibility makes the estimate auditable, but only the manufacturer can publish or change the actual commitment.

Why Pixel 8 and iPhone 16 need different copy

Google describes a seven-year Pixel policy tied to availability, so the Pixel 8 page can show a policy-derived end month while retaining the exact variant scope. Apple’s UK product-security statement can support a minimum UK horizon for a listed product, but it is not Apple’s final worldwide support cutoff. The iPhone page therefore uses a software-support evidence title and labels the UK calculation as a minimum. For older iPhones without a defensible future statement, the correct output is unknown plus the latest shipped-release source. Uniform-looking marketing names do not justify uniform title or metadata claims.

Precision is part of the claim

Day, month, year and range precision are not styling choices. A source saying October 2030 should not render as 1 October unless the UI clearly stores that day only as a normalized month anchor. A minimum-through statement should show range language instead of a final cutoff. When sources disagree, preserve both captures, identify the controlling evidence and explain the conflict rather than averaging dates. Updating the review timestamp alone is not a material revision. A new source, changed scope, new policy start event or corrected calculation is material and belongs in human-readable revision history.

How a reader can audit a date

Open the cited source and confirm publisher, exact product wording and jurisdiction. Match the model code on the device. Check whether the source was captured after the product launched and whether a newer statement supersedes it. Reperform the displayed arithmetic and verify the rounding rule. Then inspect limitations: carrier delivery, regional hardware, emergency updates and current patch cadence may differ. If any essential step cannot be completed, downgrade confidence or leave the end unknown. The goal is not to maximize the number of dates; it is to publish the smallest claim that the evidence can actually defend.

When the evidence should be downgraded

Downgrade or withdraw a date when the source no longer resolves, the named model is absent, the start event cannot be reproduced, the jurisdiction was overstated, or a newer first-party statement conflicts with the calculation. A manufacturer page changing layout is not itself a policy change, but it may require a new capture and parser review. Never keep a Grade A label merely because an older URL once contained a date. Preserve the prior evidence internally, explain the public material change, and leave the field unknown until the controlling claim can again be defended. Honest uncertainty protects readers from false precision.

Worked examples from the catalog

Use the model identifier and jurisdiction together; a marketed name alone is not enough. These records show how the method is applied to real evidence.

How this guide was produced

DevLifeCheck separates manufacturer commitments, regulator notices and editorial interpretation. The editor checks the linked primary sources, records the applicable model and region, and avoids turning a missing date into an estimate.

Related guidance