Documents

QwenWorkDocuments that survive a read

The useful part is not the prose. It is the outline, the heading hierarchy and the tables staying consistent when you move a section from page two to page six.

It starts with a document type

Tell it 「weekly report」 or 「technical proposal」 and the outline changes accordingly. A weekly report gets a summary, progress, blockers and next steps; a proposal gets background, approach, schedule and cost. This is the single biggest difference between a draft you can use and one you rewrite from scratch.

What it does well

Where it fails

Numbers it did not see. If the source material contains no figures, any number in the output is invented. Dates behave the same way. The failure is not obvious because the sentence reads perfectly — which is why every generated document with figures needs a pass that checks only the figures.

A workflow that works

  1. Give it raw material, not instructions

    Paste the transcript, the emails, the previous report. 「Write about Q3」 produces generic filler; the raw notes produce something specific.

  2. Approve the outline before the prose

    Editing six headings takes a minute; editing six pages takes an afternoon.

  3. Revise paragraph by paragraph

    Ask for one section to be rewritten rather than the whole document. Whole-document rewrites lose the parts you already fixed.

  4. Check figures and names last

    Read only the numbers, dates and proper nouns. That is where the errors live.

Documents are the surface most people start with. If your work is mostly numbers, read spreadsheets first.