Free to read · no account needed

16 min · writing

Draft and revise writing with ChatGPT

Goal: move from blank page to an editable draft in three passes—without sounding like generic AI.

Best for: blogs, launch notes, internal posts, newsletters. Human voice still wins; ChatGPT accelerates structure.

Generate once, then revise on purpose. Mixing “write it” and “perfect it” in one breath is how mushy drafts happen.

Why beginners skip this

Skipping the hard part of “Draft and revise writing with ChatGPT” feels fine until a live thread pays the bill. Hold: Draft once, revise against a checklist—ChatGPT is a loop, not a one-shot novelist—prove it on a real artifact, or skip the badge Mid-week cost shows up as rework, not as a missing bookmark.

Pass 1 — Outline only

Goal: Propose an outline for a 800-word post.
Audience: [who] · Promise: [what they can do after reading]
Format: H2 titles only, 5–7 sections, one-line intent under each.
Boundaries: No full paragraphs yet. No hype words (revolutionize, unlock, game-changer).
Topic notes:
---
[bullets]
---

Edit the outline yourself. Kill weak sections before drafting.

Example

Filled prompt

Goal: Propose an outline for an 800-word post.
Audience: indie founders · Promise: ship a weekly AI workflow without drowning in tools
Format: H2 titles only, 5–7 sections, one-line intent under each.
Boundaries: No full paragraphs yet. No hype words.
Topic notes:
---
- I waste mornings hopping between ChatGPT tabs
- Want one “default path” per task type
- Readers already tried random prompts
---

What good output looks like

  • 5–7 H2s only; no full essay yet
  • No “revolutionize / unlock / game-changer”
  • You delete 1–2 weak sections before Pass 2
  • Pass/fail dated (Asia/Shanghai) sits next to the artifact

Pass 2 — Draft one section at a time

Goal: Draft section “[H2 title]” only (~120 words).
Voice: concrete, calm, like a practitioner writing docs—not a landing page.
Include: one example or mini-checklist.
Boundaries: Stay inside the outline. No intro/outro for the whole article.

Why section-by-section? You catch tone early and avoid a mushy middle.

Example

Filled prompt

Goal: Draft section “Pick one default tool per task” only (~120 words).
Voice: concrete, calm, like a practitioner writing docs.
Include: one mini-checklist.
Boundaries: Stay inside the outline. No intro/outro for the whole article.

What good output looks like

  • ~120 words for that H2 only
  • Includes a short checklist (3–4 items)
  • Tone sounds like docs, not a landing page

Pass 3 — Revise for voice

Paste your stitched draft:

Goal: Revise for clarity. Keep my meaning.
Do: shorten sentences, replace vague adjectives with specifics, keep contractions if present.
Do not: add new claims, metaphors, or emoji.
Return: full revised text only.

Then you add one personal sentence the model cannot invent (a number from your week, a failure, a preference).

Example

Filled prompt

Goal: Revise for clarity. Keep my meaning.
Do: shorten sentences, replace vague adjectives with specifics, keep contractions if present.
Do not: add new claims, metaphors, or emoji.
Return: full revised text only.

What good output looks like

  • Shorter sentences; specifics instead of “powerful / seamless”
  • No new claims added
  • You append one real personal line before publish

Prompt pack — subject lines / CTAs

Give 8 subject-line options for this post.
Constraints: ≤55 characters, no clickbait, no ALL CAPS, no “you won’t believe”.
Mark my top 2 with * after I reply with criteria: [curiosity / clarity / urgency].

Separate the turns

Draft without judging; critique without rewriting; revise against a checklist. Mixed turns hide failures.

Example

Filled prompt

Blank FAQ: "What is MCP in plain words?"
Outline→draft→revise: ≤100 words, no protocol jargon, draft-only tip.
Context: real workstream this week (Asia/Shanghai). Name actual files/people.
Constraints: no invented metrics/owners/prices; label Unknowns; stop before send/delete/pay.
Done check: I can mark pass/fail in one minute on the output.

What good output looks like

  • Uses only facts you typed for “move from blank page to an editable draft in three” — no invented owners
  • Format matches your asked shape (bullets/table/length) on first try
  • Unknowns marked [?]; nothing filled to sound confident
  • You can mark pass/fail in ≤60s for chatgpt-draft-and-revise drill #1

Red flag

Sending the first draft; revision invents new facts unchecked; treating draft as final—run the three-check list.

Save this card

Card: Draft once, revise against a checklist—ChatGPT is a loop, not a one-shot novelist—prove it on a real artifact, or skip the badge. Keep this beside the tool; read before you start.

1. What I shipped: ___ 2. What I refused: ___ 3. What I will never-do again: ___ (date: Asia/Shanghai)

  • [ ] Tools/writes paused
  • [ ] Refuse-line dated
  • [ ] Artifact path saved
  • [ ] Next link chosen (or stop)

Before you start

Open ChatGPT on the account you keep. Pick the live thread or Project for “move from blank page to an editable draft.” Have the messy input in front of you—not a blank box. Guide: chatgpt-draft-and-revise. If you only have a blank practice box, stop and fetch the real job first.

  • Goal in one line: ___
  • Allowed tools: ___
  • Forbidden: ___
  • Human approve needed for: ___

How to use this week

This week in ChatGPT: move one blank page to an editable draft, then one critique→revise pass. Keep both drafts dated on a live artifact—not a blank demo. Write one refuse-line and date the note (Asia/Shanghai). If you only skimmed chatgpt-draft-and-revise, put 25 minutes on the calendar and redo once.

Calendar block (chatgpt-draft-and-revise, optional): 25 minutes once this week—open the guide, run Practice once, date the refuse-line, then stop. No binge-reading counts as practice.

Pitfalls

  • One-shot “write the whole article” → bland middle; use three passes
  • Leaving AI clichés → maintain a ban-list in Boundaries
  • Publishing without fact check → dates, product names, quotes are on you

Common pitfalls

PitfallFix
Vague everyday ask with no formatRewrite Goal · Format · Boundaries before send
Treating first draft as finalOne revise pass against your checklist
New chat for a recurring jobMove it into a Project/GPT with standing Done

Practice now

Live card: one ChatGPT project/GPT/canvas action for “Draft and revise writing with ChatGPT” with refuse written first (Asia/Shanghai).

Today: produce an ugly first draft, then revise with a three-check list (facts / tone / length). Keep both versions dated Asia/Shanghai.

Today card (copy) — chatgpt-draft-and-revise: 1. Artifact I will produce: ___ 2. Pass/fail check: ___ 3. Refuse-line if tempted to skip verify/send: ___ (date: Asia/Shanghai) 4. One never-do from this guide: ___

  • [ ] Artifact path written
  • [ ] Refuse example would say "yes"
  • [ ] Dated Asia/Shanghai

One sentence takeaway

Draft once, revise against a checklist—ChatGPT is a loop, not a one-shot novelist—prove it on a real artifact, or skip the badge

  • You can point to a dated refuse-line
  • You have one artifact path from tonight
  • You can teach the red flag in one sentence

Next

Clear everyday prompts · Writing path · Outline before prose · Canvas and iterative docs · Email from correct to polished

Pair with today: open the first Next link (chatgpt-clear-everyday-prompts) only after you dated a refuse-line for this guide (Asia/Shanghai).

← Back to home · Learn · Tools · Compare · Start