When someone needs a .docx — a lawyer who will redline it, a client whose whole process runs on Word — the AI can write one.

"Write this up as a Word file for the contract review."
"Turn the treatment into a .docx with headings and a summary table."

It writes in blocks: headings, paragraphs, bulleted and numbered lists, tables and pictures. Tables get explicit column widths, because a Word table without them collapses in every reader except Word itself.

Three ways to get a Word file, and which to pick

• Ask for a Word file when the .docx is the deliverable — it goes to someone who will edit it in Word.
• Export a document when you have already written it in Storyflow. The document's own Export button and asking the AI to export it produce the same file.
• Write a document when you will keep working on it. This is the common case, and the AI will steer you here if you ask for a Word file when you meant a living page.

The distinction matters: a document is the living thing on your board, a Word file is the fixed thing someone sends. Confusing the two is the usual way this goes wrong.

Pictures

The AI generates or finds a picture and places it in the file at a width you can ask for. As with PDFs, only pictures made or sourced inside Storyflow can be embedded.

Use Cases

• Send a contract draft to a lawyer who works in tracked changes
• Produce a proposal in the format a client's procurement process demands
• Hand a writer a .docx they can mark up offline and send back