How to Turn an Editorial Draft Into a Publishable News Post

An editorial draft is not a rough version of the final article. It is the working file where reporting, verification, and editorial decisions stay together until the moment of publication. When a news post moves from a lean draft straight into WordPress, the editor has to go back for source names, recheck numbers, and guess the intended angle. That slows publishing and raises the chance of factual errors. The workflow below gives a small newsroom or solo editor a repeatable path from raw notes to a publishable post: a reporting note, a clear angle, a review table, and a WordPress checklist.

Start with a reporting note, not a blank page

The first block of the draft should answer three questions in plain language:

• What happened, changed, or became known?
• Who is affected, and why should they care?
• What does this post need to explain or correct?

Keep the answers short and factual. Example: “The city council approved the library budget; the vote was 5-2; opening timeline unchanged.” This note anchors the entire post. If it cannot be written from material already in hand, add a list of missing interviews, documents, or confirmations to the draft. Do not write body copy until that list is visible and each item has an owner.

A common mistake is to paste a press release into the draft and add transitions. A press release answers the sender’s questions, not the reader’s. Treat it as one source among several, then write your own reporting note from the evidence you have verified.

Keep new facts separate from background

New facts move a story forward. Background gives context. The two need different treatment in a draft. New facts should carry a source name, a date, or a document reference. Background should be short and clearly separated, because it is often reusable from previous posts and does not need the same level of re-verification each time.

Use two labeled blocks in the draft: “New information” and “Context.” The new information block should contain only claims you can support in the final post. The context block should stay at one or two lines. If the context section grows longer than the new facts, the angle is probably too broad.

This separation also simplifies updates. When a vote changes, an editor can compare the new facts against the context block and see exactly what changed without rereading the whole article.

Choose one angle before writing the first full paragraph

An editorial draft often holds several possible stories. A council meeting can produce a budget story, a tax story, a staffing story, and a transparency story. All may be true, but a single post should focus on one. Write the angle as a sentence that could appear in the first or second paragraph: “The approved budget expands library weekend hours but leaves mobile outreach unstaffed.”

Once the angle is written, every section heading and paragraph must support it. If a fact supports a different story, leave it in the reporting note for a later post. That keeps the article tight and gives the editor a standard for cutting material.

If the angle is not yet clear, do not open WordPress. Drafting inside the CMS before the angle exists tends to produce long, unfocused posts with generic headings such as “Background” or “What this means.” Instead, write three possible angles in one sentence each, then pick the one that changes what a reader should do, understand, or expect.

Use a five-row review table to track progress

A review table replaces long comment threads that repeat the same feedback. It shows where the draft stands at a glance and keeps the review process visible. The table below lists the stages most news posts need.

| Stage | Main task | Publish-ready signal |
| 1. Reporting note | List facts, sources, and missing checks | One clear angle can be extracted |
| 2. Draft structure | Write H2s that support the angle | Each section has a single point |
| 3. Body text | Fill sections with verified facts | No new claims without support |
| 4. Editorial review | Check claims, fairness, and tone | All queries answered or cut |
| 5. Publication | Format and publish in WordPress | Headline, metadata, image, and links pass |

Keep this table at the top of the draft document. When an editor moves a row from “in progress” to “done,” add a one-line note saying what changed. That record prevents the same question from being asked twice and gives a future editor a clear decision trail.

Run a WordPress publication checklist before publishing

The final review table row is the gate for the CMS. Move to WordPress only after the draft passes these checks:

• Headline copies the angle sentence, not a generic topic label.
• SEO title and meta description use the same words as the reporting note.
• Category and tags match the editorial calendar, not the draft’s working tags.
• Featured image alt text describes the image and supports the story.
• Source names and numbers in the body match the reporting note.
• Internal links point to the most relevant previous posts.
• Preview is checked on mobile; no heading or table breaks the layout.
• The review table has no row left with unanswered queries.

Each check takes less than a minute when the draft is structured. If a check fails, return the draft to the correct row of the review table instead of fixing it silently during publication.

What to do when a fact cannot be verified before deadline

Unverified facts are the main reason a publishable draft stays in the review table. Do not delete a claim automatically when it is important to the story. Instead, mark it as unverified, then choose one of three options:

• Attribute the claim to its source: “The library director said the timeline is unchanged.”
• Rephrase the claim so it describes the statement, not the underlying fact.
• Cut the claim from the post and move it to the reporting note for a follow-up.

Publish only if an editor has signed off on one of those options. A post that reaches WordPress with an unverified core claim fails the publication row, no matter how well the rest of the draft is written.

This workflow keeps the editorial draft as a usable record: the reporting note explains what was known, the review table shows what was checked, and the publication checklist makes sure the final post matches the verified facts.