# 5.7 Choose the output format: inline, artifact or structured data (/managing-ai-workers/the-four-part-brief/output-format)

---
type: Document
title: "5.7 Choose the output format: inline, artifact or structured data"
description: "How the next reader of a result decides whether it comes back in the chat, as a document someone keeps, or as data a system reads."
status: stable
order: 205.7
ksor:
  owner: team:panaversity
  audience: [ public ]
  approval:
    by: process:panaversity
    at: 2026-10-06T13:16:37Z
chapter: "05"
part: II
expert_status: required
concepts: [ "5.7" ]
last_verified: 2026-10-06
generated:
  at: 2026-10-06T13:16:37Z
  by: esl-rewrite/1.2.0+ksor.1
trust_tier: unverified
build_id: sha256:c93b28093c2f70c60faae2645a693d881b657ff94d00f7dd9f8c06427ff61c87
dirty: true
ksor_version: 0.0.60
---

**In everyday life.** You send a quick text to say you are late, a birthday card that someone keeps, and a form that the bank's system reads.

Who or what reads the result next decides its format.

- **Inline.** In the chat itself. A person reads it once, now: a quick check, an explanation, a short list. No separate file is needed.
- **Artifact.** A file or document of its own. A person keeps, edits, shares or approves it: a memo, a document, a slide deck, a spreadsheet. Name the type, the audience and where it must go.
- **Structured data.** A system or a later step reads it: a CSV file, a JSON record, a table with fixed columns. Name every field (column) and its type (date, number or text). Ask for one row per item, say how to mark a missing value, and say "no prose", meaning no paragraphs around the rows.

For the payment run, the structured-data line can read like this. "One row per open invoice, with these columns: invoice_no, vendor_name, due_date, amount, currency, action, reason, policy_section. If you cannot fill a field, leave it blank and say why in the reason column. No prose."

One task can need all three. Brightline's payment run does: a proposal CSV that a program checks, a one-page memo for Dave, and a three-line note to Maria in the chat. Each reader gets the shape it can use.

Format also organizes the content. In an artifact, start with what the reader must decide: "Approve Midwest Packaging 4519, decide on the Canadian invoice, then sign the run." Group items by what the reader will do with them, not by the order in which the worker found them. For example, put the invoices to approve together, and the ones on hold together.

Format decides what you can check. A CSV with one row per open invoice can be checked by a machine: the row count matches the invoice list, the totals add up, and every row has an action. Two pages of prose are hard to check except by reading them. When a decision depends on the result, ask for a shape you can check.

![Under the title Choose the format for its next use, a box asks: who or what uses the result next? Three arrows lead to three columns. Inline, in navy: a person needs a quick answer, so reply in the conversation, with no separate deliverable. The Brightline example is a three-line note to Maria, saying what is held and why, reviewed for accuracy and clarity. Artifact, in gold: a person will keep, edit or approve it, so create a reusable document and name its type and destination. The Brightline example is a one-page memo for Dave, decisions first, then totals, reviewed for evidence and decisions. Structured data, in red: a system or a later step needs fields, so specify the fields, their types and missing values. The Brightline example is the payment-run proposal CSV, one row per open invoice, with automated checks of rows, totals and actions. A note says these uses can overlap: a CSV can also be a saved artifact. A footer reads: one task can need all three, and Brightline's payment run does.](img/output-format.png)

*Figure 5.4. Who reads it next decides the format.*