The editorial decision

Define a small vocabulary for product status and use it consistently. “Available” should describe a capability confirmed for the stated audience and market. “Planned” should identify an intended future capability without implying a launch date. “Subject to eligibility” should not be used to hide the fact that a feature has not launched at all. Where access depends on a provider or programme, explain the relevant dependency in plain language.

A working method

Keep a product-status record with the owner, evidence and review date. Have editors check it before publishing feature articles, comparisons or campaign copy. Review illustrations too: a polished screen mockup can imply that a planned service is already operating unless labelled appropriately. When status changes, update the main product page and related journal articles together. Avoid using old social posts or design files as the sole evidence for current availability.

Imagine this

Hypothetical example

A journal covers a planned expansion of financial services. The article describes the intended experience and identifies partner and programme dependencies. Current features appear in a separate section, preventing the future roadmap from being mistaken for a present entitlement for every reader.

Make it practical.

Use this checklist as you read. Checks are not stored.

References & further reading

Further reading: Google people-first content guidance ↗

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.