An editorial workflow is the sequence of stages, responsibilities, decisions, and handoffs that moves a piece of content from an initial idea to a maintained publication. A useful workflow does more than arrange tasks in order. It preserves context, makes review responsibilities visible, and creates clear places for human judgment.
The example below follows an informational article through planning, research, drafting, review, publication, and maintenance. It is not a universal template. Editorial teams can adapt the stages to fit their subject matter, publishing system, regulatory environment, and available resources.
Editorial workflow overview
At its simplest, the example workflow follows this path:
- Define the article’s purpose and intended audience.
- Collect sources and identify factual requirements.
- Create an editorial brief and working structure.
- Draft the article.
- Review its substance, scope, and organization.
- Verify factual claims and source support.
- Copyedit and review accessibility.
- Prepare the page in the publishing system.
- Publish and inspect the live page.
- Maintain the article as information and reader needs change.
This sequence is only the visible path. Each stage also needs a defined input, an expected output, and a condition for moving forward. Without those elements, a workflow may appear orderly while leaving important decisions unresolved.
Workflow composition explains how these individual parts can be assembled into a coherent process. Workflow architecture considers the larger system: how information, responsibilities, tools, and feedback move across the complete workflow.
Stage 1: Intake and purpose
The workflow begins by defining why the article should exist. A topic alone is not enough. The intake stage should establish the reader’s likely need, the intended scope, and the publication’s reason for addressing it.
Useful intake information
- A working topic or question
- The intended audience
- The primary informational purpose
- Known scope boundaries
- Relevant existing pages
- Subject-matter requirements
- Important claims that will require verification
- Possible publication or review constraints
For example, an intake request that says “write about accessible forms” provides a subject but little direction. A more useful intake record might identify the audience as small website teams, define the purpose as explaining practical form design principles, and note that the article should distinguish native HTML behavior from unnecessary ARIA use.
Better intake may require a few additional minutes at the beginning. That effort can reduce uncertainty during research, drafting, and final review. The gain appears across the workflow rather than within the intake task alone.
Output of this stage
A short, approved statement of purpose with enough context for research and planning to begin.
Stage 2: Research and source collection
Research establishes the factual ground of the article. Sources should be selected according to the nature of the claim, not merely because they are easy to find.
Primary documentation, standards, official records, technical specifications, and direct subject-matter expertise may carry more evidentiary weight than summaries. Secondary sources can still be valuable for explanation, comparison, historical context, and identifying areas that require deeper investigation.
Research tasks may include
- Locating authoritative sources
- Recording publication and revision dates
- Capturing the specific passage supporting each important claim
- Identifying disagreements or uncertainty among sources
- Separating established information from interpretation
- Noting terminology that needs a clear definition
- Finding related internal content that may help the reader
Source notes should travel with the article. If supporting information remains in a private browser session, an unshared document, or one contributor’s memory, later reviewers may have to repeat the research.
Decision point
If the available evidence cannot support the proposed article, the workflow should return to intake. The scope may need to be narrowed, reframed, or held until better information becomes available.
Output of this stage
An organized source set, research notes, and a record of important uncertainties.
Stage 3: Structure and editorial brief
The editorial brief converts the original request and collected research into a workable plan. It gives the writer direction without requiring every sentence to be predetermined.
A practical editorial brief may contain
- A working title
- A concise description of the reader’s need
- The article’s central question or purpose
- Primary entities and terminology
- Required sections
- Questions the article should answer
- Claims requiring careful attribution
- Relevant internal links
- Scope exclusions
- Review requirements
The proposed heading structure should reflect the subject’s natural relationships. Headings are not merely visual dividers. They help readers scan the page, support navigation with assistive technology, and provide meaningful boundaries for retrieval systems. URLMD’s guide to heading hierarchy explores this structural role in more detail.
Output of this stage
An approved brief and article outline that connect purpose, evidence, and structure.
Stage 4: Drafting
Drafting turns the brief into a complete explanation. The writer should answer the article’s central question early, then add context, examples, distinctions, and practical detail where they improve understanding.
A draft does not need to be polished before it can be reviewed, but it should be complete enough for a reviewer to evaluate its reasoning. Placeholder claims, missing sections, and unresolved source questions should be clearly marked rather than hidden inside apparently finished prose.
During drafting, the writer should consider
- Whether the introduction defines the subject clearly
- Whether each section has a distinct purpose
- Whether claims remain within the available evidence
- Whether technical language is defined when first needed
- Whether examples clarify rather than oversimplify
- Whether links provide useful paths to related information
- Whether the conclusion reflects the article rather than introducing a new argument
Internal links should serve the reader’s next reasonable question. They are semantic pathways through a body of knowledge, not decorations added after the article is complete.
Output of this stage
A complete working draft with sources, open questions, and uncertainties visible to reviewers.
Stage 5: Substantive review
Substantive review examines what the article says and how its explanation is built. This review usually occurs before sentence-level copyediting because major structural changes can make early polishing unnecessary.
The substantive reviewer asks
- Does the article fulfill its stated purpose?
- Is the scope appropriate?
- Are important concepts missing?
- Does the explanation follow a coherent order?
- Are distinctions and limitations represented fairly?
- Does any section repeat information without adding value?
- Could a reasonable reader misunderstand a claim?
- Does the article overstate what its sources establish?
Feedback should identify both the problem and its significance. “This section is unclear” is difficult to act on. “This paragraph shifts from website accessibility to legal compliance without explaining the relationship” gives the writer a specific structural issue to resolve.
Possible outcomes
- Approved: the draft can move to factual and copy review.
- Approved with revisions: limited changes are needed before the next stage.
- Returned for restructuring: the article needs substantial revision.
- Returned to research: claims or sections require better evidence.
Output of this stage
A substantively approved draft or a documented revision request.
Stage 6: Fact-checking and source review
Fact-checking verifies that meaningful factual claims are accurate, supported, current enough for the article’s purpose, and represented in context. It is not limited to checking names and dates.
A fact-checking pass may verify
- Definitions
- Technical behavior
- Statistics and measurements
- Dates, names, and locations
- Quoted material
- Statements about laws, standards, or policies
- Comparisons between products, methods, or systems
- Claims that use words such as “always,” “never,” “required,” or “best”
The reviewer should also confirm that citations support the claim actually being made. A credible source does not automatically support every statement placed beside it.
If evidence is incomplete, the responsible response may be to qualify the language, narrow the claim, present the uncertainty, or remove the statement. Editorial confidence should follow the evidence rather than exceed it.
Output of this stage
A fact-checked draft with resolved citations and any remaining uncertainty clearly represented.
Stage 7: Copyediting and accessibility review
Copyediting improves readability, consistency, grammar, and style without changing the article’s intended meaning. Accessibility review examines whether the content and its structure can be understood and navigated by people using different devices and assistive technologies.
Copyediting checks may include
- Sentence clarity and unnecessary complexity
- Consistent terminology
- Grammar, spelling, and punctuation
- Redundant language
- Ambiguous pronouns or references
- Descriptive link text
- Consistency between headings and their sections
Accessibility checks may include
- A logical heading hierarchy
- Semantic lists for list-based information
- Descriptive alternative text for meaningful images
- Tables with appropriate headers when tabular data is used
- Links that make sense in context
- Instructions that do not depend only on color, position, or visual appearance
- Clear language appropriate to the intended audience
Accessibility should be considered throughout the workflow, not treated as a final repair step. The dedicated review remains useful because publishing tools and page assembly can introduce issues that were not present in the original draft. The URLMD accessibility neighborhood connects related guidance on semantic structure, images, forms, keyboard navigation, and assistive technologies.
Output of this stage
An edited, accessible draft ready for page assembly.
Stage 8: Publishing preparation
Publishing preparation moves the approved content into the content management system and adds the page-level elements needed for a complete publication.
Common publishing tasks
- Assign the final page title and URL
- Apply semantic heading structure
- Add internal and external links
- Prepare images and alternative text
- Write an accurate title tag and meta description
- Assign relevant categories or other organizational metadata
- Check preview behavior on different screen sizes
- Confirm author, reviewer, and revision information where applicable
Images should be sized and compressed for their actual use rather than uploaded at an unnecessarily large resolution. The website image optimization workflow provides a focused process for image preparation.
Page markup should also be inspected before publication. A structured HTML validation workflow can help identify unclosed elements, invalid nesting, duplicate identifiers, and other markup problems.
Output of this stage
A complete page in preview or staging form, ready for final approval.
Stage 9: Publication and quality assurance
Publication is a transition, not the end of the workflow. A page can behave differently after it becomes live because of caching, templates, content delivery systems, plugins, or production-only settings.
Live-page quality assurance should confirm
- The correct page was published at the intended URL
- The title and headings appear as expected
- Internal and external links work
- Images load and include appropriate alternative text
- The page remains readable at narrow and wide viewport sizes
- Keyboard users can reach and operate interactive elements
- No draft notes or unresolved placeholders remain
- The canonical URL and indexability settings are appropriate
- The publication date and author information are correct
The person performing live QA should have a clear way to record and resolve problems. If an error could materially mislead readers, publication may need to be corrected promptly or temporarily withdrawn while the issue is reviewed.
This stage illustrates why human-in-the-loop systems remain important. Tools can detect many technical conditions, but a person must still judge whether the live page communicates responsibly and fulfills its intended purpose.
Output of this stage
A verified live page and a record of any post-publication corrections.
Stage 10: Maintenance and refinement
Published content exists within a changing information environment. Standards evolve, source pages move, links break, terminology changes, and readers reveal questions the original article did not fully address.
Maintenance should be based on the article’s subject and risk profile. A historical overview may remain accurate for years. An article about current software behavior, regulations, prices, or technical specifications may require more frequent review.
Maintenance signals may include
- A source or standard has been revised
- A linked page has moved or disappeared
- A product or interface has changed
- Readers repeatedly encounter the same ambiguity
- A correction affects related pages
- New internal content creates a useful linking opportunity
- The article no longer matches the publication’s current structure or terminology
Maintenance is also a source of workflow knowledge. Repeated corrections may reveal a weakness in research, intake, review, or publishing preparation. Workflow refinement uses these observations to improve the process rather than treating every issue as an isolated mistake.
Output of this stage
An updated article, a documented review with no changes required, or a decision to consolidate, redirect, archive, or remove the page.
Roles, handoffs, and workflow states
A workflow does not require a separate person for every role. On a small publishing team, one person may research, write, edit, publish, and perform QA. The responsibilities should still remain conceptually distinct so that one kind of review is not mistaken for another.
| Stage | Primary responsibility | Expected output |
|---|---|---|
| Intake | Editor or content owner | Approved purpose and scope |
| Research | Researcher or writer | Source set and research notes |
| Brief | Editor and writer | Article plan and structure |
| Drafting | Writer | Complete working draft |
| Substantive review | Editor or subject-matter reviewer | Approved draft or revision request |
| Fact-checking | Fact-checker, editor, or qualified reviewer | Verified claims and citations |
| Copy and accessibility review | Copyeditor or accessibility-aware editor | Clear, consistent, structured content |
| Publishing preparation | Publisher or web editor | Complete page preview |
| Live QA | Publisher or independent reviewer | Verified live page |
| Maintenance | Content owner | Review record and any necessary update |
Workflow states make progress visible. A simple state model might use:
- Proposed
- Researching
- Brief approved
- Drafting
- In substantive review
- In factual review
- In copy and accessibility review
- Ready to publish
- Published pending QA
- Published and verified
- Scheduled for review
- Archived
Each state should communicate something meaningful. A broad label such as “in progress” may conceal whether the article is being researched, revised, fact-checked, or waiting for approval.
A complete handoff preserves context
When work moves between people or tools, the handoff should include the current draft, source material, relevant decisions, unresolved questions, and the specific kind of review being requested.
A link to a document accompanied only by “please review” shifts the burden of reconstructing the assignment to the reviewer. A structured handoff reduces that uncertainty and makes the requested judgment clearer.
Automation and human judgment in an editorial workflow
Automation can reduce repetitive work, but its value depends on where it is placed and what information it preserves.
Tasks that may be suitable for automation
- Creating a standard project record from an approved intake form
- Checking for broken links
- Flagging missing image alternative text
- Running HTML validation or spelling checks
- Notifying reviewers when a workflow state changes
- Recording publication and review dates
- Scheduling periodic maintenance reminders
Tasks that continue to require accountable judgment
- Defining the article’s purpose and boundaries
- Evaluating source authority and relevance
- Deciding whether evidence supports a claim
- Recognizing misleading implications
- Balancing completeness with readability
- Approving substantive revisions
- Determining whether the page is ready for publication
- Deciding how to correct a consequential error
An automated intake form may save administrative time while removing context that editors later need. A writing tool may produce fluent prose while leaving source support unclear. A validator may confirm that markup follows a specification without determining whether the article itself is understandable.
Automation is most useful when it supports a well-understood workflow. It should preserve provenance, expose uncertainty, and leave consequential editorial decisions with responsible people. URLMD’s discussion of editorial review and responsibility examines this relationship between assistance and human accountability.
What makes an editorial workflow useful?
A useful editorial workflow does not need to be elaborate. It needs to make the work understandable.
Its stages should answer several practical questions:
- What information is needed before this work begins?
- Who is responsible for the current decision?
- What must be true before the article moves forward?
- What context should accompany the handoff?
- Where can the workflow return when a problem is found?
- How will the published page be checked and maintained?
The workflow should also permit return paths. Fact-checking may send an article back to research. Accessibility review may reveal a structural problem that requires substantive editing. Live QA may uncover a publishing issue that was not visible in preview.
These returns are not necessarily workflow failures. They are part of how a responsible editorial system detects and resolves uncertainty before it becomes durable misinformation or avoidable reader friction.
Frequently asked questions
What is the difference between an editorial workflow and an editorial calendar?
An editorial workflow defines how content moves through planning, creation, review, publication, and maintenance. An editorial calendar organizes when content is expected to be developed or published. A calendar can support the workflow, but it does not replace the stages, responsibilities, and decision points within it.
Does every article need all ten stages?
Not necessarily. The appropriate process depends on the article’s complexity, potential consequences, source requirements, and publishing environment. A short update may combine several stages. A medical, legal, financial, or safety-related article may require additional specialist review. Even when stages are combined, their underlying responsibilities should remain visible.
Should the writer also edit and publish the article?
One person can perform several roles, particularly in a small organization. When possible, a separate review can help identify assumptions the writer may no longer notice. If independent review is unavailable, separating drafting and review in time and using role-specific checklists can provide some additional perspective.
When is an editorial article finished?
An article is ready for publication when it fulfills its defined purpose, its meaningful claims are adequately supported, required reviews are complete, and the assembled page has been checked. Publication does not make it permanently finished. The article may need later review as its sources, subject, or surrounding website evolve.