> For the complete documentation index, see [llms.txt](https://docs.cortex.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.aic.io/workflow-guides/products/product-drafts.md).

# Product Drafts

**Open this area:** In the CORTEX menu, select **Intelligence cycle → Products**.

Prepare an editable report, retain exact evidence and analytical lineage, and record processing and currency before controlled release.

**Who uses this:** Author, Analyst, Reviewer.\
**Open in CORTEX:** `/products`.\
**In-app guide:** `/help?topic=products`.

**Expected result:** A saved Product revision contains deliberate authored content, limitations and traceable sources; internal exports remain drafts.

## Before you start

* Have Product and Memory enabled, write authority and a visible requirement; exporting needs separate permission.
* Choose handling that covers the requirement, evidence and any linked analysis before creation. Restricted handling also needs a current approved processing activity for the exact sources and purpose.
* Decide whether to author manually, prepare from a retained analytical revision or use a separately permitted CSV first draft.

## What to do

{% stepper %}
{% step %}

## Choose context and a starter

Product drafts show a pager only beyond one visible result page, with the exact authorised range; apply edited filters before paging a changed search.

In Setup, select a visible requirement and applied template. Choose:

* Brief
* Assessment
* Intelligence Assessment
* Intelligence and security directive (draft)
* Joint intelligence estimate / JIPOE (draft)

Apply a changed template only when you intend to replace the editable sections.

A policing template also needs an approved local profile and adoption reason.
{% endstep %}

{% step %}

## Prepare the content

Write and reorder sections, source notes and exact citations.

If using analysis, select its retained revision and inspect it; explicitly confirm replacement before **Build draft from selected analysis**.

Linking alone does not mean that the selected old revision was reviewed.
{% endstep %}

{% step %}

## State assurance and uncertainty

Record:

* Information-as-of
* Optional review-due
* Preliminary, unprocessed, curtailed or uncorroborated declarations
* Rationale
* Limitations

These are your assessed declarations; neither a template nor a citation supplies them automatically.
{% endstep %}

{% step %}

## Assess restricted reuse

Use **Processing purpose for this reuse** to inspect the exact requirement, direct and linked analytical datasets, and approved report projections.

Select a current independently approved activity permitting Analysis for that purpose.

Product authoring permissions and acquisition authority do not replace this decision.
{% endstep %}

{% step %}

## Preview and save

An internal draft needs a 3–200 character title and 1–16 sections with headings; section text can be completed later.

Sources can be skipped for an ordinary draft; restricted handling needs an approved processing activity there.

The coloured steps list missing inputs as you edit.

On Content, **Save basic internal draft** retains the minimum draft immediately. You can also preview and use **Review and Save product draft**.

An existing draft can use **Save and continue editing** after validation. Supply an amendment reason when required and reconcile a conflict before another save.

The saved product identifies empty sections; complete each before controlled release or sanitisation.

Internal exports remain marked as drafts and grant no distribution authority.
{% endstep %}

{% step %}

## Review AI and sanitisation impact

Open a generated origin from Product provenance to inspect its approval and impact history.

**Find affected Products** locates exact origins across retained revisions; follow **Find sanitised derivatives** from each original and inspect its pinned source revision.

Current Product, source and historical Analysis access remain required.

Missing origins are not inferred, and lookup never changes content or release approval.
{% endstep %}

{% step %}

## Inspect genuine internal output

On Product detail choose the exact revision, format and reason, then **Prepare and download internal draft**.

Inspect PDF, DOCX or JSON for marking, notices, sources and layout.

Refresh after export preparation before another change; use a separate release workflow for distribution.
{% endstep %}
{% endstepper %}

## Check the result

* Does the report answer the intended decision need?
* Are judgements, observations, alternatives and uncertainty clearly distinguished?
* Are the cited and analytical revisions the intended ones?
* Are processing/currency declarations accurate and complete for release?
* Have I inspected the actual exported file rather than only its preview?

## If you get stuck

<details>

<summary>What happens if finding or paging product drafts fails?</summary>

A temporary failure keeps the last confirmed drafts, filters and page visible with a warning.

Select **Find product drafts** to retry edited filters or select the same page control to retry paging.

A changed requirement or impact scope starts a fresh list; losing current access clears protected drafts and the create actions.

Browsing does not save, export or approve a Product.

</details>

<details>

<summary>Why did preparing from analysis refuse the content?</summary>

The full selected revision exceeded Product citation or text limits.

Select a suitable smaller retained revision or author a focused report manually; no analytical content is silently shortened.

</details>

<details>

<summary>Why can I no longer read an older Product revision?</summary>

Current access must cover all retained evidence, analytical and generated-source lineage.

Ask the appropriate authority to resolve access; deleting a current citation does not remove the protected historical obligation.

</details>

<details>

<summary>Why did export fail or a release reject my draft?</summary>

Check the safe error.

Unsupported visual glyphs or layout need appropriate supported content, not silent evidence alteration.

For missing assurance, record valid declarations in a new Product revision and amend/resubmit the release; old approval does not transfer.

</details>

## Responsibility and limits

* The author owns the report's assertions and limitations.
* A SUPINTREP-informed or doctrine-guided starter is drafting guidance, not a certified format or operational order.
* Internal exports retain the draft warning.
* Export preparation does not approve release, establish delivery or record receipt.

## Reference and scope

JDP 2-00 (4th ed.), 3.27–3.29, 3.49–3.59 and 7.4–7.11 inform production and draft patterns. Templates and author declarations do not confer command approval.

## Related workflows

* [Develop and independently review an assessment](/workflow-guides/analyse/analysis.md)
* [Review a model-assisted first draft from CSV](/workflow-guides/products/ai-assisted-drafts.md)
* [Review, approve and publish an exact internal release](/workflow-guides/products/release.md)
* [Record processing purposes and privacy applicability](/workflow-guides/assurance/processing-activities.md)
