Define your stages

Create a short internal vocabulary with a concrete entry condition for every stage. Concept might mean a proposed design; in preparation might mean defined work has begun; operating should point to observable delivery. These are editorial definitions, not legal determinations. Avoid mixing sales enthusiasm with operational status. A signed discussion document, a purchase order and a delivered service should not all receive the same launch label.

Apply labels consistently

Use the same stage language across the website, deck, profile and sales script. Add a date and state the next meaningful milestone. If a stage depends on another organisation, explain that dependency without implying an approval that has not been obtained. Revisit the wording when the project advances or pauses. A clear status update gives a prospective partner a realistic reason to continue the conversation and a specific question to ask next.

Put the guide to work

Add a short status legend to the internal content brief. Writers and designers should not have to invent a new label for every project. Keep the legend specific enough to distinguish meaningful stages while allowing the responsible project owner to explain unusual situations that do not fit neatly.

Imagine this

Hypothetical example

A team calls a planned integration live because development has started. Its stage definitions reveal that no customer transaction has been tested. The published wording changes to implementation underway, with the remaining validation milestone clearly described for prospective partners.

Make it practical.

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

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