Glossary term

Listing status

The recorded state of one product on one directory — from draft through pending, scheduled and live to blocked or not a fit.

Definition

Listing status is the recorded answer to “where is this product on this directory right now”. A useful status distinguishes work on your side (draft, prepared but needs a human), receipt by the platform (submitted pending review, queued, scheduled), public visibility (live, already listed) and stops with a reason (blocked, deferred because paid, not a fit, unavailable).

Each status is tied to a minimum observation. A saved form is a draft; a dashboard label “Under review” is submitted pending review; a public URL without a pending label is live.

Example

One week into a launch the tracker holds five rows. PitchWall is under review, TinyLaunch has a confirmed date, SaaSHub is reachable but still marked “Pending approval”, Uneed is blocked by the one-pending-launch limit, and Product Hunt passed a logged-out check. A single “done” column would have said four or five.

With separate states the next steps are obvious: recheck PitchWall after the review window, verify TinyLaunch on its date, leave SaaSHub as submitted until the label is gone and wait for free capacity on Uneed. Only one of the five can honestly be quoted as a public listing.

Why it matters for a directory launch

A single “done” column answers five questions at once and gets most of them wrong. With distinct states you know how many listings a stranger can find, how many are waiting and where you personally still have to act — and an agent restarted tomorrow can read the same rows and continue without resubmitting.

How LaunchRepo handles it

The tracker (record.py writing submissions.json) uses eleven states with the minimum observation for each documented in the runbook. Live requires the public URL plus an explicit confirmed-public flag; scheduled requires the confirmed date. The dashboard shows the same rows grouped by what to do next. The status guide on this site walks through two real cases where “done” would have been wrong.

Go deeper

Recording outcomes: states, evidence and record.py

All eleven states with the minimum evidence each one needs, the rules the script enforces and how to resume without duplicates.

See the term in the repository

LaunchRepo is 299 directory playbooks, a product context file and a submission tracker your own agent runs. Pay €119.00 once; use it for every product you own.

See pricing