Write in Google Docs. Publish with Tenwrite.

Publish to WordPress or Blogger, manage updates, and track search performance.

Start free 5 free exports · No credit card required

Build an Editorial Workflow From Draft to Published Post

Abstract document, workflow, and CMS symbols representing an article moving toward publication.

An editorial workflow is the set of steps that moves an article from an assignment to a published post—and makes clear who acts next, what source they should use, and what must be true before the article moves on. For a small team, it can be as simple as one shared record and a few agreed decisions.

A practical sequence is assigned → drafting → review → approved → CMS draft → scheduled or published → update needed. These are suggested editorial labels, not necessarily statuses you will find in WordPress or Blogger. If a reviewer requests changes, the article returns to drafting before approval.

The guide below gives you a record and stage table to copy, then follows an illustrative article through approval, a failed preview check, publication, and a later correction.

What an editorial workflow does—and how it differs from a calendar

An editorial calendar tells you what you intend to publish and when. An editorial workflow tells you how each article gets there. The two can live in the same spreadsheet, but they answer different questions.

Suppose a calendar says an article is due on Thursday. That date alone does not tell the publisher whether the writer has finished, whether an editor has approved the current document, or whether a CMS draft exists. A workflow adds those answers: the article is in review, the editor owns the next action, and approval is needed before production begins.

You do not need a separate person for every stage. A solo blogger can write, review, prepare, and publish an article. The benefit is still real: the blogger knows which version is ready, what remains unchecked, and where the published post lives.

Use only the stages that help you make a decision. If two labels always lead to the same action for the same person, combine them. If a single label hides an important decision—such as whether the wording is approved or merely waiting for review—split it.

Set up one article record before work starts

Create one record per article in a shared document, spreadsheet, or task system. Its purpose is not to capture every conversation. It should let someone open the right source, understand the article’s current state, and take the next action without searching through messages.

Copy this starting record and replace the brackets. At assignment, fill in the reader question, people, next action, source, and target site. Add the CMS link when the draft exists, the live URL after publication, and update notes when needed.

Article title:
Intended reader question:
Owner:
Reviewer / approver:
Current editorial stage:
Next action:
Next-action owner:
Next-action due date:
Working-document link:
Approved source or version:
Target site:
CMS draft link:
Published URL:
Publication timing:
Update note:

The owner is responsible for keeping the article moving; the next-action owner is the person currently expected to do something. They may be the same person. Name the reviewer or approver even if that person is also the writer, so the approval decision is explicit.

For a solo publisher, the record might say “Owner: me,” “Reviewer / approver: me,” and “Next action: review the document against the reader question on Tuesday.” This is not an extra approval meeting. It is a reminder to make a deliberate review pass before preparing the post.

Keep the working-document link stable where possible. If a copy or revision becomes the approved source, identify it in the record rather than leaving two plausible versions. A source can be an approved document link plus a version identifier, date, or other clear reference your team can find again. Avoid using “final” as the only distinction between multiple files.

The destination fields serve a different purpose. The target site identifies where the article belongs; the CMS draft link locates the work in progress; the published URL identifies the reader-facing result. They are not interchangeable. If you publish across several sites, the distinction also helps prevent an update from landing on the wrong one. For a broader setup, see how to track posts across WordPress sites.

Define stages, owners, and clear exit conditions

A stage should identify the person responsible and the condition for moving forward. The following is a suggested small-team setup, not a mandatory set of CMS statuses. Copy it and change the roles or conditions to match your work.

Editorial stageResponsible personRequired informationExit conditionIf changes are needed
AssignedArticle ownerReader question, writer, reviewer, target site, due dateWriter accepts the assignment and has a usable working documentClarify the assignment before drafting
DraftingWriterBrief or reader question and working documentDraft addresses the question and is ready for reviewWriter continues drafting
ReviewReviewer; writer revisesCurrent draft and review criteriaRequested changes are resolved and the approver records a decisionReturn to drafting with specific requests
ApprovedApproverRevised source and resolved review requestsApproved source or version is identified; publisher can begin CMS preparationReturn substantive changes to review
CMS draftPublisherApproved source, target site, title, timing, images and supplied metadataSaved draft passes checks and the publishing decision is recordedFix presentation and recheck; send content changes to review
Scheduled or publishedPublisherChecked draft and approved timingScheduled state or live post is verified and its location is recordedCorrect scheduling or publication issues and verify again
Update neededUpdate ownerExisting post URL, source, requested change and reasonChange is reviewed as needed, applied to the existing post and verified liveReopen the update if the live result is wrong

Review and approval are related but different. Review produces feedback; approval is the decision that the identified source is ready for CMS preparation. The reviewer can also be the approver, but the decision should be visible—for example, “Approved by Alex; use document revision dated May 6.” A comment saying “looks good” on an earlier draft is not enough if subsequent edits changed the article.

Agree on what happens when feedback conflicts. A simple rule is that the approver resolves open requests before the publisher starts. If a writer disagrees with a requested change, record the decision rather than leaving the publisher to guess which wording won.

For a solo workflow, make a short note such as “Reviewed against brief; approved for CMS.” You can perform the review yourself without pretending that another person signed off. If you later change the substance, treat that approval as applying to the earlier version and review the new wording before release.

A stage name alone is not a handoff. When you change the record, also update the next action, its owner, and its due date. “Review” with no reviewer or deadline is a description of a queue, not a plan to clear it.

Move the approved document into a CMS draft

The publisher’s first job is to establish what is being published, not to start transferring whichever file was most recently opened. Before preparing a WordPress or Blogger draft, confirm:

  1. Approved source: Open the document or version named in the record. Check that the approval refers to this source, not an earlier copy.
  2. Destination: Confirm the target site and intended post title. If the team manages more than one site, identify the specific site before creating a draft.
  3. Timing: Note whether the article is intended for immediate publication or a scheduled release, including the intended date and time where relevant.
  4. Assets and details: Gather required images, captions, image descriptions, and any title or metadata supplied for the post. If something essential is missing, name the person who will provide it.
  5. Draft location: Prepare the post as an unpublished CMS draft using your chosen method. Save it, then add its draft link to the article record.

Do not assume that a transfer method will preserve every heading, image, link, or field. The record should distinguish the editorial stage from the actual state in the CMS: an article can be editorially approved while its CMS post is still a draft. Similarly, a saved draft is not proof that the content has been approved.

If the source is a Google Doc and you are deciding where the finished writing should live, this guide to choosing a Google Doc publishing destination explains the distinction between a web page, an embed, and a WordPress post.

During production, correct obvious presentation issues, such as a heading that needs the intended heading structure. But do not quietly rewrite a substantive instruction because it seems unclear in the CMS. Record the issue, return the wording to the writer or approver, and identify the newly approved source before continuing. If the fix changes the meaning or recommendation, it needs an editorial decision rather than a formatting decision.

Check the saved draft before publishing or scheduling

Open the saved draft and compare it with the approved source. Work through the article in order, rather than checking a few familiar paragraphs from memory. The goal is to establish that the saved post contains the intended content and is suitable for the planned release.

Use this checklist for WordPress or Blogger, adapting the fields to what your site actually provides:

  • Title and destination: Confirm the title and target site match the record. Make sure you are inspecting the intended post, especially if similar drafts exist.
  • Content and structure: Compare the opening, section headings, and closing text with the approved source. Check that headings use appropriate heading structure and appear in the intended order. Count list items and check their sequence.
  • Links: Open or inspect each link and compare its destination with the source. Check that the linked words make sense in context.
  • Images and captions: Where images are present, confirm that the intended image appears in the right place, its caption is correct, and the intended alternative text is entered where applicable.
  • Available metadata: Compare any supplied description or other publishing details with the fields available on the site. If a field is unavailable or the instruction is unclear, record the gap and decide how to handle it; do not assume the setting exists everywhere.
  • Preview and timing: Preview the saved post and look for missing content, awkward layout, or unreadable elements. Confirm the planned publication date and time before scheduling, including the relevant time zone if the setup displays one.

Treat a failed check as a decision, not just a note. A presentation fix—such as applying heading structure to text already approved as a heading—can be made in the draft, saved, and previewed again. A substantive change—such as replacing an instruction or removing a step—goes back for editorial approval. After the decision, update the record so the publisher knows which version to use.

The draft is ready when there are no unresolved blocking issues and the person responsible has recorded the decision to publish or schedule. A blocker might be a missing required image, an unresolved content question, or the wrong target site. A minor optional enhancement can be noted separately if the team agrees it does not prevent release.

After publishing, open the live URL and check that the intended post is visible there. After scheduling, confirm the saved post reflects the intended schedule; check the live result when the scheduled time arrives. Record the published URL once it is available.

Worked example: one article from assignment to correction

The following record is illustrative, not a customer case study or a tested publishing run. The names, dates, source and destination placeholders, and events are invented to show how the decisions fit together.

The article is called “How to Prepare a Blog Post for Publication.” Its reader wants to know what to do between finishing a document and releasing a post. Maya is the writer and article owner; Lee reviews and approves; Sam prepares the post in WordPress.

At assignment, Maya creates a working document and records the reader question, target site, reviewer, and due date. The CMS and published URL fields remain blank because neither exists yet. Maya’s next action is to produce a draft for Lee, not to create a post.

After reviewing the draft, Lee asks Maya to clarify one instruction. Maya revises it in the working document. Lee checks the revision and records approval against the identified source. Sam can now prepare the CMS draft without guessing whether an unresolved comment represents a required edit.

The following checkpoints show how the same record changes. The bracketed links are placeholders, not downloadable examples.

CheckpointEditorial stageNext action and ownerSourceDestination
AssignmentAssignedMaya drafts for Lee by May 4[Working document]Target: example WordPress site; draft and live URL not yet available
ApprovalApprovedSam prepares the CMS draft by May 8[Working document, approved May 6]Target: example WordPress site; draft not yet created
CMS preparationCMS draftSam fixes heading structure and previews again[Working document, approved May 6][Saved CMS draft]
PublicationPublishedSam checks the live post and records its URL[Working document, approved May 6][Published post URL]
Later correctionUpdate needed, then publishedMaya revises the changed instruction; Lee approves; Sam updates and verifies[Working document, revised and approved June 12][Same published post URL]

In the CMS draft, Sam notices that a section title is bold text rather than a heading. The wording matches the approved document, but the structure fails the check. Sam applies the intended heading structure, saves the draft, and previews it again. The section now appears in the intended place with the intended structure. Sam records that the blocking issue is resolved and proceeds with the agreed publication decision.

After publication, Sam opens the live post and records its URL. The record now connects the approved source, the editorial decision, and the actual destination. The team does not need to search the site to find which post came from the document.

Later, an instruction in the article needs to change. Maya records the reason and affected section, revises the working source, and asks Lee to approve the substantive change. Sam applies the approved revision to the existing post through the team’s chosen method, then opens the same live URL to check the affected section. The update note records the date and verification outcome. The example does not assume that editing the source automatically updates the post.

Keep the source and published post aligned after publication

An article’s workflow does not end when the post goes live. A correction can arrive from a reader, a team member, or a later review. Decide in advance where revisions should be made and how the existing published post will be updated. The working document and the live post can diverge if someone changes only one and the next publisher assumes both are current.

Use the article record to start each update:

  1. Identify the existing post. Open the recorded live URL and confirm the site, title, and affected section. Do not create a new post simply because you cannot find the original draft.
  2. Describe the change. Record why it is needed, who owns it, and whether it is an urgent factual correction or a planned review. An urgent correction should move promptly to the person who can assess and apply it; a planned review can be assigned a future date.
  3. Revise and review the source. Update the designated working source. Send substantive changes to the approver. If the live post contains later edits that are missing from the source, reconcile them before treating the source as authoritative.
  4. Apply the approved change to the existing post. Use the method your team has chosen. Check any fields or elements that method might affect rather than assuming they remain unchanged.
  5. Verify the live result. Reopen the recorded URL and read the affected section in context. Confirm the correction is visible and surrounding content still makes sense. Record the outcome; if it is not visible, revisit the saved post and repeat the check.

A compact update note might read:

Reason: Publication instruction changed
Date: June 12
Affected section: Preparing the draft
Owner: Maya; approved by Lee
Verification: Sam checked the revised instruction at the existing live URL

This note is illustrative. For a real correction, include enough detail to identify the change without turning the record into a full editorial history. If the live check fails, leave the article in “update needed” with the next action and owner rather than marking it complete.

For a small publishing trial, use Tenwrite to turn one approved Google Doc or supported local document into a WordPress or Blogger draft. Then compare the saved draft with the source using the checks above before deciding whether to publish.

Fix bottlenecks before adding software

When an article stalls, look for the decision or information missing at that stage. A new tool may make work more visible, but it will not decide which source is authoritative or who has authority to approve a change.

SymptomFirst change to try
Articles wait in reviewName one reviewer and a next-action deadline on each record. Ask the reviewer to approve or return specific requests.
Drafts go through repeated revision roundsClarify the reader question, scope, and expected outcome before writing. Compare the next review request with that brief.
Several documents look like the final versionIdentify one current working source and record the approved version and destination. Mark older copies clearly so they are not used by mistake.
Formatting problems appear just before releaseMove the saved-draft comparison and preview earlier. Record the failed element and recheck it after the fix.
Published corrections are hard to findAdd the live URL and an update note to the original article record. Assign someone to verify the changed section.

Review a few recent records periodically. Note when each entered and left a stage, and count the review rounds if that information would help. If several articles spend a long time in review, check whether the same reviewer is overloaded or whether requests arrive without a due date. If drafting requires many rounds, inspect the assignment and feedback for recurring ambiguity. There is no universal target: compare your own articles and look for a repeatable cause before changing the process.

Start with a document or sheet if it reliably shows the source, stage, next owner, and destination. Consider editorial workflow software or editorial workflow management software when recurring assignments, visibility, or routing needs cannot be handled reliably in that setup. Define the specific problem first: for example, a team may need a clearer shared queue, while another needs help preparing posts from approved documents.

If the problem is the transfer into WordPress rather than editorial approval, the separate guide to choosing publishing automation for a WordPress team can help you evaluate that narrower job. Whatever tool you choose, keep the approval decision, saved-draft check, and live verification visible in the workflow.