For founders and product teams

Keep the product story aligned with the product itself.

Product communication draws on product behaviour, positioning, launch decisions, approved claims, support material and previous messages. When those sources drift apart, a polished draft can still misrepresent what the product does.

In Second Read Studio you can keep drafts in a project with its own editorial settings and reference files. Reviews can then consult that context, so claims and terminology stay connected to the material you supplied.

What the writing has to achieve

Announcements, release notes and product pages should say what the product does today, in the terms the team has agreed on.

Where drafts tend to go wrong

  • A feature in limited beta is described as available to every customer.
  • An old brainstorm is treated as approved positioning.
  • Terminology differs between the launch page, documentation and release notes.
  • A projection is rewritten as a measured outcome.

Different documents, different editorial questions

Product descriptions
Feature explanations that need traceable support in a specification or current reference.
Announcements and release notes
Status, availability and scope must match what has actually shipped.
Positioning and landing pages
Approved positioning should carry through without vague adjectives replacing it.

Questions a second read asks

  • Does this claim match the supplied product material?
  • When sources conflict, which one is current and authoritative?
  • Is a company projection still attributed as a projection?
  • Is terminology consistent with the rest of the project?

How Second Read approaches it

  • Project-context and brand-positioning references for drafts written on behalf of a project or company.
  • The product-verification reference, which separates what a source states from what has been observed at runtime.
  • Every suggestion is anchored to the exact passage, explains its reasoning and waits for your decision. When a passage already works, no change is a valid result.

In Studio, choose a writing type such as Release notes / product update, Landing page, Brand positioning or Mixed purpose to route the review to its focused reference.

Synthetic example · the draft

Worked example

A launch page says a feature is available to every customer. A supplied current release note says it is in a limited beta.

What a useful review does

The review flags the mismatch, names the conflicting source and leaves the status unresolved if it cannot be established.

What Second Read does not claim

  • Supplied context can reveal a mismatch with your own material; it does not make that material independently true.
  • Second Read does not automatically know a product's live state. Repository inspection is not proof of production behaviour.
  • When the current status cannot be established, the review should leave it unresolved rather than choose for you.

Read more about the method in how Second Read reviews a draft and editorial review with project context.

Related guides

Try it on your own terms

See a second read before you apply.

The interactive demo uses a sample review and needs no account. The beta is free and applications are reviewed personally.