Skip to main content

Sunday, 22 November 2026Week 47 editionSign in

New ProductLaunches home

Launch wireNew products, filed daily, ranked by community votes

Send a releaseGet your launch on the wire

Spec Blocks and Availability Lines

The Craft · 10 min read ·

Trade readers want facts they can scan: a compact spec block and one clear availability line. How to write both so they are accurate and quotable.

Illustration: A trade-press 'At a glance' box in grey with ruled rows Product, Maker, Platforms, Version, Availability, Pricing, Contact, in condensed print type

In a trade publication, certain things appear in a standard box at the foot of a product story: the "at a glance" facts. Platforms, versions, supported formats, requirements, availability. They are set apart because readers look for them in a different way from the story. They want to see them quickly and compare them. They sometimes want to copy them.

For a maker, that box is an opportunity and a risk. Done well, it gives an editor the facts exactly as you want them stated. Done carelessly, it contradicts your own page, goes out of date and wastes the trust you built in the story. This guide covers how to write a spec block and an availability line that are accurate, compact and quotable.

What a spec block is

A spec block is a short list of specifications, the measurable or checkable facts about a product, kept apart from the narrative. A datasheet is the classic form: a document that summarises the performance and technical characteristics of a product in a concise format. A spec block is a datasheet in miniature.

It serves three audiences.

  • Editors, who lift or adapt it.
  • Readers, who scan it to decide whether the product fits.
  • Machines, which can read structured facts and present them in search results and summaries.

What goes in

The right facts depend on the product, but a typical software block has these fields.

Product name and version. Exactly as filed, and the release you mean.

Maker. Company or team.

What it is. Category, in a phrase.

Platforms. Browsers, operating systems, devices.

Languages. Supported interface languages.

Requirements. Anything the user needs: an account, a plan with another service, a minimum system.

Integrations. Named, with how they connect.

Data. Where data is stored, export formats.

Access. Open, invitation, waitlist; free, trial, paid.

Support. Channels and hours.

Licence or terms. Where relevant.

Availability. The line described below.

Contact. For press, a name and an address.

Link. The canonical product page.

Date. When the spec was last checked.

For hardware, the fields differ: dimensions, weight, materials, power, connectivity, certifications, warranty. The principle is the same: a short list of facts that can be checked.

What to leave out

  • Adjectives. "Robust", "powerful". A spec block states, it does not praise.
  • Marketing claims without evidence.
  • Facts that change daily. Customer counts, uptime.
  • Prices as numbers that will go stale. Use a pointer.
  • Anything you cannot verify.
  • Internal jargon.

If a fact needs explaining, put it in the story and keep the block clean.

Writing each line

Short. A phrase, not a sentence.

Parallel. Same style across lines.

Exact. "Chrome, Firefox, Safari and Edge, current and previous major versions" is better than "all modern browsers", provided it is true.

Units and formats stated. "Exports to CSV and JSON."

Honest about limits. "No mobile app. Mobile browser supported."

Consistent with your website. Compare line by line.

The availability line

The availability line is the single most useful sentence in a product announcement. It answers: can I get it, where and how?

A good line has four parts.

  1. Stage. General availability, public beta, early access.
  2. Place. Where it can be obtained or used.
  3. Date. Now, or a specific date.
  4. Terms. How it is obtained, with a pointer to price.

Example: "Available now in the UK and Ireland as a public beta, with a thirty-day free trial. Pricing at the address below."

Stage

General availability, the point at which a product is released to the public in a form considered ready for general use, is different from earlier stages such as beta or early access. Use the word that matches reality. Do not call a beta "launched" without saying it is a beta.

Place

State the countries or regions. If there are restrictions, name them. "Not yet available in the EU" is more useful than silence.

Date

"Now" is only true if it is. If the date is in the future, state it, with the year if there is any risk of confusion. Avoid "soon" and "coming this spring" unless you must, and if you use them, do so honestly.

Terms

Say whether it is free, paid or both, and where to find the details. If there is a trial, state its length and whether a card is needed. If there is a waitlist, say so.

Where the product is sold to consumers at a distance, the law in the UK, for example, expects certain information to be given before an order is placed, including the price including taxes, delivery arrangements and cancellation rights. Government guidance on distance selling sets out the list. An availability line is not the place for all of that, but it should point to a page that has it.

Pointing to price

Typing a price into a spec block is tempting. It makes the block feel complete. It also guarantees a contradiction the day the price changes.

Better:

  • Write "Pricing: see the pricing page" with the link.
  • Keep every price in one place, and show it from there everywhere.
  • If an editor needs a figure, give it in a covering note with the date, and tell them if it changes.

New Product Launches keeps its own prices in one place, set by our team, so pages and emails always agree. Copy the habit: one source of truth.

Machine-readable facts

Search engines and assistants read facts about products. Schema.org defines a SoftwareApplication type with properties for name, application category, operating system, offers and more, and Google documents how to mark up software applications. If you add structured data to your product page, make it match the visible spec block. Hidden or contradictory data is worse than none.

Keep a master

Specs belong in one file, owned by one person.

  • A single document or spreadsheet with every field.
  • A column for the date last checked.
  • A column for the source of each fact, such as the product page or release note.
  • A version history.

Everything else is derived from it: your website, listings, press releases and media kit. When a fact changes, change the master first, then update each place.

Check at every release

A spec block that was right at launch can be wrong by the second update.

  • Review the block whenever you release a version.
  • Check platforms and requirements against the build.
  • Check integrations still work.
  • Check links.
  • Update the date.
  • Tell editors who published older specs if something material changed.

Be honest about what is unfinished

A spec block can include a line for limits: "Not yet supported: offline mode, team accounts." Editors and readers appreciate it. It prevents mismatched expectations.

Advertising rules in many places say marketing must not mislead, and objective claims need evidence. A spec line that overstates support, such as listing a platform that only half works, creates both a bad reader experience and a compliance risk.

Accessibility of the block

A spec block is often presented as a table or list.

  • Use a real table with header cells, or a definition list, so screen readers can announce labels and values.
  • Keep contrast strong.
  • Do not put important facts only in images.
  • Provide the same facts as plain text in the email.

A worked example, described

A spec block for a booking tool: Product Notely Bookings, version 2.1. Maker Acme Software, Leeds, UK. Category online appointment booking. Platforms desktop and mobile browsers. Language English. Integrations: calendar sync with common providers, via a built-in connector. Data stored in the UK; export as CSV. Access: public beta, free trial for thirty days; pricing on the pricing page. Support: email, weekdays. Not yet: group appointments, offline mode. Contact: press name and address. Link: product page. Checked on a stated date.

An availability line beneath: "Available now in the UK and Ireland as a public beta, with a thirty-day free trial."

An editor can paste this as a box. A reader can compare it. A machine can understand it.

Common mistakes

  • Marketing language in a spec block.
  • Typed prices that go stale.
  • Contradictions with the website.
  • Vague platforms.
  • "Available now" when it is not.
  • No date on the specs.
  • No mention of limits.
  • Forgetting to update after a release.

On this site

The launches page lists new products in a compact layout, the pricing page states the current prices in one place and the submit page starts an entry, whose description can record platforms and availability. The categories page helps readers browse, and the contact page takes questions.

A last check before you send

Read your spec block and availability line alongside your product page, line by line. Do the platforms match? Is the version the same? Does the availability line say the same thing as the page about access and cost? If you find a difference, decide which is right and fix the other. Then ask a colleague to try to find a fact in the block that is wrong. Fresh eyes find things yours have stopped seeing.

The short version

A spec block is a compact list of checkable facts, separate from the story; an availability line says stage, place, date and terms. Include platforms, versions, requirements, integrations, data, access, support and limits; leave out adjectives and typed prices; point to a single pricing page; keep a master file with sources and dates; check at every release; and match structured data to the visible page. Facts that can be scanned, copied and trusted get used.

Questions and answers

What is a spec block?
A compact list of the product's key facts, such as platforms, versions, formats, requirements and limits, set apart from the narrative.
What is an availability line?
A single line that says where, when and how a product can be obtained, and in what stage.
Why separate specs from the story?
Because editors and readers want to scan facts quickly and copy them without picking through prose.
Should the spec block include price?
Better to point to a pricing page, so the figure is always current, than to type a number that may change.
How do I keep specs accurate?
Keep them in one master file, check them at each release and date them.

Sources

Related guides

Help centre