Skip to main content
DiscoveraLaunch · field notes home

SearchSign in

Writing a Listing Like a Field Note

Copywriting · 9 min read ·

Plain, observed, specific descriptions beat brochure copy. Write a listing like a field note: what it does, for whom, its limits and when you looked.

Illustration: A field-notes page on sand paper with a handwritten entry: date, place, observation, caveat, and a small sketch of a trail marker, in forest-green ink

Naturalists, surveyors and archaeologists keep field notes: short, dated records of what they saw, written to be understood later by themselves or by others. A good field note is plain. It says where, when and what. It separates observation from guess. It admits what was not seen.

A product listing can be written the same way, and the result is usually better than the brochure language most listings use. This guide shows how.

What a field note is

Field notes, in the practice of fieldwork, are the notes taken by researchers in the course of observation, recorded as close to the time and place as possible. Their value comes from being concrete and honest. A note that says "interesting plants" is useless; one that says "two types of fern at the stream edge, one with forked fronds, noted on the north bank, afternoon" can be checked and built on.

Apply that discipline to a listing. Instead of "a powerful solution for modern teams", write what the product does, for whom, how you know and where it stops.

The brochure problem

Most listings fall into a familiar style: adjectives, aspirations and promises.

  • "Revolutionary platform that transforms the way you work."
  • "Seamless, intuitive and powerful."
  • "The ultimate solution for all your needs."

These sentences share three faults. They say nothing specific. They cannot be checked. And they could describe any product, so they identify none. A reader scanning a page of such listings learns nothing and trusts nobody.

Plain English, as a style of writing, favours clear, direct language and avoids jargon and padding. It is not about dumbing down. It is about being understood by the largest number of qualified readers with the least effort.

The five lines

A field-note listing has five parts. Each answers a question a visitor has.

1. What it is

One sentence naming the type of thing and its job. "A small web app that scales recipes between servings and converts units." Start with a noun, not an adjective.

2. Who it is for

One sentence about the person. "Made for home cooks and small bakeries who adjust recipes often." The reader should recognise themselves, or not.

3. How it works

Two or three short sentences about what the user does and what happens. "Paste a recipe or type ingredients; choose the number of servings; read the result and print it. Works in a browser, no account needed."

4. Limits

A short, honest note about what it does not do. "Does not handle recipes with instructions in tables; unusual units may need a manual check."

5. Last checked

A date for when the description was last reviewed, and, if relevant, the version. "Reviewed in June."

Together these five lines are a complete field note. They fit on a card, and every line is specific enough to be tested.

Observed, not claimed

The core of the style is the distinction between what you observed and what you hope.

Observed: "Used by about forty bakeries, according to our sign-up records in May." Claimed: "Loved by bakeries everywhere."

Observed: "Recipes scale accurately for ingredients measured by weight; volume measures are approximate." Claimed: "Perfectly accurate scaling."

Where you have evidence, state it with its source and date. Where you do not, leave the claim out, or label it as an aim: "We are working on support for tables."

Use the reader's words

Notice what your users call the thing. If bakers say "scaling a bake" and you say "recipe resizing", use theirs. Listings that use the audience's own vocabulary are easier to recognise and are found by the searches people actually type.

Describe the job the way a user would, not the way an engineer would. "Tells you when to feed your starter" beats "automates periodic fermentation reminders".

Keep it scannable

A visitor will skim first, then read if interested.

  • Put the most important words first. The first line should work alone.
  • Use short paragraphs, with one idea each.
  • Use labels for the five parts, if the format allows.
  • Avoid long lists of features. Pick the three that matter.
  • Use real text, not images, so that it can be read by assistive technology and search tools.

Google's guidance on helpful content emphasises people-first writing that is clear about what a page is for. A field-note listing satisfies that standard at a glance.

Help machines too

AI assistants and search tools read listings and decide what to say about you. Clear, factual sentences are far easier for them to summarise correctly than slogans. If your listing says "A small web app that scales recipes between servings and converts units, made for home cooks and small bakeries", an assistant asked for a tool to scale recipes can quote it. If it says "unleash your culinary potential", the assistant has nothing to use.

Where structured data is used, schema.org's SoftwareApplication vocabulary includes properties such as the application's category and operating system. If you or the site provide structured data, keep it consistent with the visible description.

Do not put figures that change

Prices, counts and similar details go out of date. Do not type them into the description. Link to the live page where they are kept, and describe the model: "Free to use; optional paid features described on the pricing page." The pricing page on this site always shows current figures, so linking to it keeps your listing true without further edits.

Review on a schedule

Field notes are dated because the world changes. Put a reminder to review your listing every quarter, or when something important changes.

  • Does the first line still describe the product?
  • Is the audience still right?
  • Are the limits still accurate?
  • Is the date current?
  • Do the screenshots match the product?

Update the date when you review, even if nothing changes; it signals that someone is paying attention.

A worked example

A maker's first listing reads: "Next-generation cooking assistant that revolutionises your kitchen workflow with powerful, seamless scaling."

She rewrites it as a field note.

"What: a small web app that scales recipes between servings and converts units. Who: home cooks and small bakeries who adjust recipes often. How: paste a recipe, choose servings, read and print the result; works in a browser, no account needed. Limits: does not handle recipes in tables; unusual units may need a manual check. Reviewed: June."

She adds a screenshot of a real recipe, scaled, and a link to the pricing page for the optional features. A month later, a user writes that they chose the tool because the listing said what it could not do. An assistant asked about recipe scaling tools quotes her first line almost word for word.

Questions makers ask

Will plain language make my product look small? It will make it look clear. Many readers are tired of inflated claims and read plain ones as confidence.

Where do I put my story or personality? On your own page, in a founder note or about page. The listing is a short summary; keep the colour for places that have room for it.

What if my product does many things? Lead with the main job and mention the rest in a second sentence. A listing that lists everything says nothing.

Can I use humour? A touch can help, if it does not obscure the facts. Do not let a joke replace the first line.

How do I check that it works? Show the listing to three people who do not know the product. Ask each to say what it does, who it is for and what it does not do. If they cannot, rewrite.

A rewrite exercise

Take your current listing and mark every adjective. Delete each one and read what remains. Where the sentence collapses, you had a claim with no content; replace it with a fact or remove it. Next, mark every sentence that could describe a competitor equally well and either make it specific or cut it. Then add the missing lines: limits and date. Finally, read the result aloud as if you were describing the product to a friend over a campfire. If it sounds like you, you have written a field note.

Three listings, three field notes

To see the style in other settings, here are three more field notes in the five-line form, for imaginary products.

A habit tracker. What: a simple app that tracks daily habits with a streak count. Who: people who want a plain checklist, not a coaching programme. How: add habits, tick them off each day, see a calendar of streaks; works on phones and in a browser. Limits: no reminders by message yet; no sharing between users. Reviewed: March.

A code formatter. What: a command-line tool that formats configuration files consistently. Who: developers who maintain several repositories with shared style. How: run one command in a folder; it rewrites files in place and prints a summary. Limits: supports three file types; does not fix errors, only layout. Reviewed: April.

A seed catalogue. What: a searchable list of heritage vegetable varieties with growing notes. Who: allotment gardeners and small growers. How: search by name or sowing month; each entry gives sowing, spacing and typical harvest times. Limits: covers temperate climates only; notes are from the maker's own beds. Reviewed: May.

Each is under a hundred words, and each tells you whether it is for you.

When the facts change

If a limit is lifted or a new one appears, change the note and the date. A field note that was true last year and is not true now is worse than none. Keep a short history of your listing text somewhere private, with dates. It helps you see how the product has changed and reminds you which sentences you have already tried.

Summary

Write your listing like a field note: plain, observed, specific and dated. Say what it is, who it is for, how it works, what it does not do and when you last checked. Replace adjectives with facts, use your audience's words, keep it scannable, leave changing figures to linked pages and review it regularly. Clear, honest notes are easier for people to trust and for machines to quote correctly.

Questions and answers

What is a field note?
A brief record made by an observer in the field: what was seen, where and when, written plainly so that it can be checked and used later.
How does this style help a listing?
It replaces vague claims with specifics, which readers and AI assistants can understand, trust and quote accurately.
How long should the description be?
A clear first line, then a short paragraph, then a few labelled details. Long enough to be useful, short enough to scan.
Should I include limits?
Yes. A short, honest limit shows that you know your product and respects the reader's time.

Sources

Questions?