Separate Launch News From Marketing Promises

The headline said the new platform eliminates scheduling delays for every employer. What shipped was one feature: employees can request a shift swap, and a manager still approves it. The same headline went into the customer email, and the first reply asked where the platform was.

Sort every line of a launch brief into four kinds of claim before anyone drafts: the change that takes effect, the capability it gives, any outcome someone has measured, and the ambition the company holds. Lead with the change. Qualify the capability where it appears. Publish an outcome only with its study, and attribute ambition as an aim. Once the wording reaches a product page or a customer email, advertising rules apply as well: the UK code says marketing must not exaggerate a product's capability or performance↗¹, and the FTC's advertising substantiation policy↗ expects a reasonable basis before a claim goes out².

The launch brief leads with a promise to transform how teams work. The product owner has supplied a release note describing one new scheduling feature. The executive wants a confident quote, and the account manager needs a headline by lunchtime. Start by asking what a customer will be able to do after the announcement that they could not do before.

That answer provides the news. The wider commercial ambition may still belong in the story, but it needs wording and evidence appropriate to its status. Separating these parts early lets the team discuss the actual announcement without forcing every aspiration into the first paragraph.

Ask a different question of each part of the brief: what changes, what it lets people do, what it has been shown to achieve and what the company hopes for.

The change taking effect

Ask what launches, its effective date, its eligible audience and any access conditions. A feature enabled for existing subscribers in one plan is a narrower announcement than a service open to every business. Confirm the launch state with the delivery owner. A target date in an earlier deck needs confirmation before the release presents it as a committed availability date.

The capability being offered

Ask what the feature actually permits a user to do under specified conditions. A demonstration may show a shift-swap request being routed to a manager. It does not establish that requests are always approved, that managers respond faster or that staff experience less stress. Keep the description close to the demonstrated action and the confirmed product behavior.

The outcome being claimed

Ask what was measured, for whom, against what comparison and during which period. If a pilot measured fewer scheduling emails among participating teams, inspect the method and exclusions before proposing a result. An outcome observed in that setting needs its setting retained, the same care you would give a result measured in one group and quoted for another. It cannot silently become a guarantee for every organization that buys the product.

The ambition being expressed

Ask whose aim this is and whether they accept the wording. A leader may want to explain why simplifying shift requests matters to the company. Mark the proposed perspective for approval, using the person's approved voice examples and the organization's current position. Future language still deserves scrutiny if it creates a specific commitment about delivery or results.

Put each part of the proposed headline against what the team actually holds, then reword each part to the strength of its evidence.

In a fictional example, suppose the scheduling feature lets employees submit shift-swap requests and lets managers accept or decline them. It will be available to existing customers on a specified plan in two regions. The team has no cleared study of time saved. The requested headline is: New platform eliminates scheduling delays for every employer.

The words platform, eliminates and every employer each expand the claim. Absolute words like these deserve the extra care that first, leading and only call for, because each one makes a promise about scale or effect. The source describes a feature, establishes a routing capability and limits eligibility. A possible headline for review is: Company adds shift-swap requests for eligible scheduling customers. The opening paragraph can name the confirmed plan, regions and date, with a clear explanation of the request process.

This version may feel less dramatic. If the commercial team believes a stronger result is central to the news, ask what evidence would support it and whether the announcement can wait for that evidence. Replacing eliminates with helps eliminate does not by itself resolve the unsupported outcome claim.

Give the executive quote a specific contribution, the kind that makes an executive quote earn its paragraph. Ask why the company chose to bring employee requests and manager decisions into one workflow, or which customer question shaped the feature. Use only a confirmed explanation the speaker accepts. The quote should not become a second route for inserting the unsubstantiated time-saving promise, which would still be a factual promise carried inside an executive's view.

QuoteIt runs the same split on a draft. Each claim sits beside the release-note passage it came from, and a claim nothing in the uploaded material supports, such as eliminates scheduling delays, is flagged before review. Wording that gives the executive a belief or a hope stays marked as proposed until they approve it, and any fact inside it is still checked. Jasper is built for marketing teams producing campaign content; how QuoteIt compares with Jasper for PR work sets out where each fits, and the comparison of AI tools for PR professionals covers the rest.

In the UK, a release sent only to journalists generally falls outside the advertising code, while the same wording mailed to customers or run as a paid ad likely falls within it.

Launch wording rarely stays in the release. The same paragraph often becomes a product page, an email to existing customers or a sponsored post, and the rules can change with the channel. In the UK, CAP’s advice on non-broadcast advertising↗ treats a release sent to journalists or placed in a website's press section as outside the CAP Code, while a release mailed to consumers or run in full as a paid ad would likely fall within it³.

Where the Code applies, marketing must not mislead consumers by exaggerating a product's capability or performance, and must not mislead by leaving out significant limitations and qualifications¹. Those two rules line up closely with the capability and outcome questions above. In the US, the Federal Trade Commission's policy statement on advertising substantiation expects advertisers and their agencies to have a reasonable basis for advertising claims before they are disseminated². An unmeasured promise to eliminate scheduling delays would be hard to defend under either.

Ask the client at the briefing where the launch wording will appear, and treat anything headed for customer channels as marketing copy from the first draft. This is general guidance, not legal advice; check the rules that apply to your organization with counsel.

Next to the claim they limit, in every format a reader may see on its own: headline, summary, social caption and image.

Read the headline, summary and social caption separately from the release. A reader may encounter only one of them. If eligibility matters to the claim, the short version needs compatible scope even when the details live in the body. A footnote cannot help a caption that already promises availability to everyone.

Review illustrations and proposed demonstrations too. Showing a request approved instantly may imply an automatic decision when the feature requires a manager. Ask the product owner which states the demonstration represents and describe them accurately. The launch story includes what the reader sees as well as the sentences the editor checks.

A useful review note has four lines: available change and source; capability and conditions; measured outcome and study, if any; proposed ambition and speaker. Each line can become an entry in the claim review sheet from the press release checklist. Attach the public-use decision to the material you intend to disclose. Leave unsupported benefit language visible as an open editorial choice until it is supported, narrowed or removed.

Place a plain operational opening beside the brief's preferred headline. Their differences provide a concrete decision agenda: support the stronger claims, narrow them to the confirmed launch, or express future ambitions clearly as aims.