Editorial Operations Platform
One board for every story, from rough idea to published performance.
Voyepi Tawano brings the Kanban board, SEO brief, writer deadlines, editor review, and publishing calendar into a single editorial workspace, so content teams stop losing track of what stage a story is actually in.
Editorial calendars often live in three or four disconnected places: a spreadsheet for deadlines, a doc for briefs, a chat thread for approvals, and a separate tool for social scheduling. Voyepi Tawano was built around a simpler premise: a story should carry its own status, brief, assignee, and deadline as it moves, without anyone re-entering the same information twice.
Kanban Board
See the status of every article at a glance
Each card represents one piece of content. Columns represent stages, not people, so a story's progress is visible regardless of who is assigned to it that week.
Cards move through columns you define: Idea, Brief in Progress, Assigned, Drafting, In Review, Scheduled, Published, and Recap. Teams that publish less frequently often collapse this into four or five columns, while high-volume newsrooms sometimes split drafting into first pass and revision.
Each card shows the assigned writer, the due date, the target word count, and a small SEO score indicator pulled from the linked brief. Clicking a card opens the full brief, comment thread, and version history without leaving the board view.
- Idea capture with tagging
- Assignment and due dates
- Status visible to the whole team
- Drag-and-drop stage changes
SEO Brief Builder
Give writers a brief instead of a blank page
The brief builder pulls in ranking pages for a target keyword and highlights subtopics competitors cover that a draft outline may be missing.
A brief starts with a working title and a primary keyword. From there, the tool surfaces the top-ranking pages for that term, breaks down their heading structure, and flags subtopics that appear across multiple competitors but are absent from the current outline. That comparison is descriptive, not prescriptive: writers decide which gaps are worth addressing.
Briefs also include a suggested word count range, internal linking candidates from your own published library, and tone notes for the assigned writer. Once approved, a brief attaches directly to its Kanban card so drafting starts with context already in place.
Because gap analysis is based on public ranking data at the time the brief is generated, teams typically refresh a brief if a story is delayed by several weeks and rankings have shifted in the meantime.
Writer Assignment & Deadlines
Assign work based on actual capacity, not guesswork
A workload view shows how many open assignments each writer is carrying before a new one is added to their queue.
Assignment Routing
Assign a story to a specific writer or open it to a pool of contributors who can claim it. Reassignment keeps the full brief and comment history intact, so nothing is lost when a story changes hands mid-cycle.
Workload View
A simple bar view of open assignments per writer helps editors avoid overloading one person while another has capacity.
Deadline Reminders
Writers and editors get a reminder as a deadline approaches, with a separate flag if a due date has already passed.
Revision Requests
Editors can request changes on a specific section of a draft rather than sending general feedback across an entire document.
Editor Review Queue
A single queue instead of a scattered inbox
Drafts marked ready for review land in one ordered queue, sorted by due date, so editors know what needs attention first.
Without a shared queue
- Drafts arrive through email, chat, and shared docs at different times.
- Editors track review status manually in a separate spreadsheet.
- It's hard to tell which draft has been waiting longest.
- Feedback gets duplicated when two editors review the same piece.
With the review queue
- Every ready draft appears in one ordered list, sorted by deadline.
- An editor claims a draft to review, so duplicate work is visible immediately.
- Inline comments attach to specific paragraphs rather than a whole document.
- Approval moves the card automatically to the scheduling stage.
Publishing Calendar & Social Scheduling
Plan the article and its social rollout together
The calendar view shows publish dates alongside the social posts tied to each article, so a launch doesn't get separated from its promotion plan.
Once a story is approved, it moves onto the calendar with a scheduled publish date and time zone. From the same card, a team can draft accompanying posts for the channels they use and set those posts to go out on a delay after the article publishes, rather than at the exact same minute.
Calendar views are available by month, week, or as a simple list, which matters for teams that publish daily versus teams that publish two or three long-form pieces a week. Rescheduling an article automatically prompts a check on any linked social posts still pending.
Post-Publish Performance
A recap that follows the story after it goes live
The performance dashboard connects back to the original brief, so a team can see whether the keyword it targeted is gaining or losing visibility over time.
After publication, each article gets a recap card summarizing traffic trend direction, engagement signals such as average time on page, and any movement in search ranking for its target keyword. Social reach for linked posts appears alongside it, giving editors a fuller picture without switching tools.
This dashboard is descriptive rather than predictive. It reports what has happened since publication; it does not forecast future results or suggest a guaranteed outcome from any particular edit.
Choosing an Approach
Spreadsheets, point tools, or one connected platform
Teams reach this decision differently depending on volume, headcount, and how many people touch a story before it publishes.
Spreadsheets and docs
Low cost to start and familiar to most teams. Works reasonably well at low volume with two or three contributors. Status tends to go stale quickly once more than a handful of people are editing the same file, and briefs live separately from tracking.
Separate point tools
A project board for status, a document for briefs, and a calendar tool for scheduling. Each piece can be strong on its own, but information has to be copied between them, which introduces the chance of a step being missed or a deadline going untracked.
A connected editorial platform
Status, brief, assignment, review, and publishing calendar share the same record for each story. This tends to suit teams publishing regularly across multiple writers, where the overhead of manual syncing between tools becomes noticeable.
A hybrid setup
Some teams keep a lightweight spreadsheet for very early ideation and move a story into a dedicated platform only once it is greenlit. This can reduce clutter in the main workflow while still keeping a wide net for early ideas.
Frequently Asked
Questions editorial teams usually ask first
When a brief is created, the tool looks at currently ranking pages for the target keyword and outlines their headings and covered subtopics. This is presented as a reference for the writer and editor to review; it is not an automatic rewrite or a guarantee of any particular ranking outcome.
Yes. Columns are configurable per workspace. Some teams use a short pipeline with four stages, while others add separate columns for legal review, fact-checking, or translation depending on their editorial process.
Reminders appear inside the platform's activity feed and can also be routed to email. A separate visual flag appears on any card whose due date has passed, so editors can see overdue work without opening every card individually.
The calendar schedules posts for connected social accounts and shows them alongside the related article's publish date. Each platform's own posting rules and character limits still apply, and connections are managed per account by an authorized team member.
It summarizes traffic trend direction, on-page engagement signals like average time on page, ranking movement for the brief's target keyword, and reach for any linked social posts. It reports historical activity rather than projecting future performance.
Workspace size depends on the plan a team selects. Smaller teams typically start with a workspace covering a handful of contributors and expand seats as headcount grows. Details are covered on the What's Included page.