Documents

Every document in one list, how final it is, and what is out of date

Updated 1 Nov 2026 · 6 min read

On this page
  1. Needs attention
  2. Waiting on you
  3. The list
  4. The one document row
  5. A document's page
  6. A feature's Docs tab
  7. An initiative's Documents
  8. New from evidence
  9. Suggested edits
  10. Who can do what
  11. What stale means
  12. FAQ

Build › Documents lists every document of the product: PRDs, help articles, briefs, prototype prompts, launch plans and the rest. A document looks and acts the same here, on a feature's Docs tab and on an initiative's page. Everyone on the product reads documents; owners, admins and editors create and change them.

Needs attention

Under the title, one line of chips says what needs you, and each chip is a filter:

  • Stale N: documents with feedback that arrived since their last edit (see What stale means).
  • Drafts N and In review N: documents not yet Final.
  • Edits waiting N: documents with a suggested edit nobody has decided. This chip jumps to Waiting on you.

When nothing needs attention the line is hidden and the title says all up to date.

Waiting on you

At the top: edits Mind or a teammate suggested (Review it), and your Friday review once it is drafted (Open the review, editors). Viewers see the suggestions and can open them, but cannot decide them.

The list

  • Group by: What it's for (a feature's documents together, then documents about a problem, a competitor, the product or a chat), By type, or Newest first.
  • Status filters always show: Any status, Draft, In review, Final, Imported and Stale. Type chips (PRD, Brief…) show once the product has more than one type.
  • Initiative filter: All N in Documents on an initiative opens the list for that initiative's features. A chip says so; its x removes it.
  • Clear filters appears whenever a filter is on. A filter is never hidden, in Focus view too.
  • 50 documents a page.

The one document row

The same row appears everywhere:

  • Title, in full (it wraps between words), with The spec on a feature's PRD.
  • Type (PRD, Brief…) and where it came from: Drafted by Mind, Imported, Written by hand or Saved from a chat. A link, N suggested edits wait, shows when edits are waiting.
  • Status: Draft, In review or Final. A document from before the redesign reads Imported · Final (or Draft, or In review) until someone edits it, then just its status. Under it: Approved 6 Oct on a Final document, Stale: 3 new pieces of feedback when it is stale, Archived when it is.
  • For: the feature and its key (in I-1 for its initiatives), or the problem, competitor, product or chat the document is about. Not shown on a feature's own Docs tab.
  • Owner: who started it (Not recorded when unknown).
  • Changed: the date and by whom, or by Mind. Hover for the exact time.
  • Export (PDF, Word, Markdown) and More (Edit on the feature, Copy the link, Archive for editors, which can be undone). A deck's PowerPoint export is on its own page.

On a phone each row is a card; nothing scrolls sideways.

A document's page

Click a title. The header gives its type, its feature (full name), the initiatives it serves, the problem, competitor or product it is about, its owner, its last change and where it came from (Saved from a chat links back to the chat). Beside the name sit its status, The spec, Stale: N new pieces of feedback since {date} and N suggested edits wait.

Actions: Ask about it, Export, More (Copy for an agent, Archive) and one main button: Edit on the feature for a feature's document, Copy for an agent for one that has no feature. Below: suggested edits, the document, its approvals and discussion; at the side its sections and versions.

A feature's Docs tab

Documents N lists the feature's documents as those rows, the open one marked. The title opens it below, where it is edited, set Draft, In review or Final, regenerated, and its history read. New starts another. An archived document says Archived. The More menu there also has Duplicate, Save as a template and Delete. Final on the PRD approves the spec: stories are written from it, and Final documents go to the Build Pack.

An initiative's Documents

On an initiative's Overview, Documents N shows the latest six documents on its features, then All N in Documents (the library filtered to it). Editors get New. Archived documents are not counted. The section is hidden while the initiative has no features.

New from evidence

New from evidence (Build › Documents, editors) starts a document About a feature, a problem, the product or a competitor, from a template (the workspace's own or a shared one) or a blank document. The title is optional. Tick Have Mind write it now to have Mind draft it; the template's credits show before you create it, and the document appears in the jobs tray. From a problem, the draft starts with its own words and what people said, word for word. Mind quotes only its sources and takes out a number it can't trace. If credits run out, the started document stays. Save to Documents in Ask Mind keeps an answer as a document.

Suggested edits

Mind can suggest an edit to one section. Nothing changes until an editor accepts: then only that section changes, and the document before it is kept as a version. A suggestion made before the document changed can't be accepted; ask again. Reject leaves the document as it is.

Who can do what

Owner, admin, editor Viewer
Read documents, rows, history yes yes
Export, Copy the link, Copy for an agent yes yes
New from evidence, edit, set status, Archive yes no
Accept or reject a suggested edit yes no
Duplicate, Save as a template, Delete (Docs tab) yes no

A demo session cannot create or change anything.

What stale means

A document is stale when feedback counted on its feature has arrived since the document was last edited (or since it was created, if never edited). The row says how many pieces: Stale: 1 new piece of feedback. Editing the document resets the count. Final does not exempt a document.

A document about a problem, a competitor, the product or a chat has no feature, so it is never stale. In a product with more than 1,500 live documents, staleness is counted only for the rows on the page, and the Stale chip and filter are not offered.

FAQ

Why does an old PRD say "Imported · Final"? It was written before the redesign and nobody has edited it since. The first edit makes it a normal Final document.

A document is stale. Do I have to change it? No. Read the new feedback, edit the document if it matters, or ask Mind (Ask about it).

Where did an archived document go? Off the library and the initiative's count. It stays on its feature's Docs tab, marked Archived. Archive can be undone.

The Stale chip is missing. Either nothing is stale, or the product has more than 1,500 live documents.

Why can't I accept an edit? Only owners, admins and editors can. Or the document changed since it was suggested: ask again.

See also Feature page, Initiatives, Exports and The Build Pack.