WORKED EDITORIAL EXAMPLE: NOT CLAUDE OR CHATGPT APP OUTPUT
These are original teaching drafts written for this guide. They demonstrate the constraints, not comparative app quality. Word counts use whitespace-separated tokens and include greeting and closing.

FIRST DRAFT (74 words; limit 120)
Hello,

I’m writing to update you on delivery. Our current plan has moved from Tuesday to Thursday, while the agreed price remains USD 2,400. The technical review is still in progress, and the cause of the delay has not been confirmed. Thursday is the current plan rather than a guaranteed delivery date.

Could you confirm a 15-minute call on Wednesday so we can discuss the update and your questions?

Thank you for your patience.

REVISED DRAFT (51 words; limit 90)
Hello,

Thank you for your patience. Our delivery plan has moved from Tuesday to Thursday; Thursday is not guaranteed. The price remains USD 2,400. The technical review continues, and the cause of the delay is still unconfirmed.

Could you confirm a 15-minute call on Wednesday to discuss the update?

Thank you.

ANNOTATIONS
Both drafts preserve Tuesday-to-Thursday timing, Thursday uncertainty, USD 2,400, the ongoing review, unknown cause and an unconfirmed 15-minute Wednesday call. Neither adds compensation or supplier blame. The revision reduces length and opens with thanks. Whether that tone suits the client is a separate editorial decision.

FAILURE EXAMPLES, ALSO EDITORIAL
“Thursday is guaranteed” changes uncertainty into a promise.
“The supplier caused the delay” invents blame.
“We have confirmed our Wednesday call” invents client agreement.
“We will offer a discount” changes the commercial terms.

Use the source exercise for an actual native-app trial. Do not label these examples as native Claude or ChatGPT results.