Schedules and Content Cycles

Workflow

Schedules are the execution layer of Inkpilots. They take work that has already been planned and place it inside a real operating window with owners, dates, and visible state changes. In the current product, scheduling is managed through content cycles, assignment states, and a kanban-style board backed by cycle analytics.

This page explains how to use that layer as an operational system rather than as a simple task list.

What this area is for

Use schedules and content cycles when your team needs to:

decide which work belongs to the current publishing window,
assign responsibility to a team member,
track movement from pending to published,
separate active cycle work from backlog work,
compare current cycle performance with the previous cycle,
carry unfinished work into a new cycle intentionally.

The scheduling layer is where planning becomes commitment.

What a content cycle means in Inkpilots

A content cycle is a named operating period. It can represent a week, a campaign, a monthly batch, or any other planning window the team uses consistently.

The current cycle system supports:

selecting the active cycle from a workspace-level cycle indicator,
creating a new cycle,
optionally defining start and end dates,
using a global backlog when work is not tied to a cycle,
moving unpublished assignments into a newly created cycle.

This last point matters. Inkpilots does not assume unfinished work disappears between periods. It gives the team a deliberate way to roll work forward when a new cycle starts.

How assignments move through the workflow

Once work is scheduled, it is tracked through explicit assignment states. The current board uses five states:

pending,
in progress,
review,
approved,
published.

These states are shown as columns in the schedule board, and assignments can be moved between them through drag-and-drop interaction.

This matters because schedules are not just about dates. They are about movement. A cycle is only useful when the team can see exactly where work is stalled, active, or complete.

What users can do in the schedules tab

The current schedules surface supports more than viewing assignments. Users can:

select the active content cycle,
create a new cycle,
filter scheduled work,
open assignment details,
drag assignments across state columns,
see assignee information,
review due dates,
open linked articles when they exist,
inspect schedule analytics for the selected cycle.

This makes the tab both an execution board and a cycle-performance surface.

How assignments are represented

Each scheduled card carries the practical information needed to manage work in motion. In the current UI that includes:

topic title,
cluster association,
assignee identity,
state,
deadline timing,
linked article access where available.

Cards also visually highlight urgency, which helps operators identify overdue or soon-due work before the cycle drifts further off track.

Why the cycle selector matters

The content cycle selector is one of the most important controls in this area because it determines which operating window the team is evaluating.

Use it to answer questions like:

are we looking at the current cycle or the backlog,
what work was intentionally moved forward,
which cycle should new assignments belong to,
what should be compared in analytics.

Without that cycle boundary, assignment reporting becomes much harder to interpret.

Analytics in the schedule layer

Inkpilots includes cycle analytics so the team can compare work completed in the current cycle with the previous one.

The current analytics surface includes:

current cycle completion totals,
previous cycle completion totals,
delta in completed work,
completion-rate comparison,
completion by member,
member-level current versus previous performance tables.

This is important because a schedule should not only show where work is. It should also show whether the current operating model is working.

Recommended operating sequence

Start with a clear planned topic from Clusters and Topic Planning.
Select or create the correct content cycle.
Assign the work to the right person.
Move the assignment through the state columns as work progresses.
Use the board to detect stalled, overdue, or overloaded work.
Use analytics to review whether the cycle pace is realistic.
Move unfinished unpublished work forward intentionally when a new cycle begins.

This sequence keeps schedules grounded in operational reality instead of becoming a static plan.

Good operating practice

Keep the active cycle honest

Do not overload the selected cycle with work the team cannot realistically move. A crowded cycle creates false confidence and poor analytics.

Update state as work actually changes

The board only stays trustworthy when the columns match real progress. If state changes lag behind reality, the schedule becomes misleading.

Carry work forward deliberately

When the cycle ends, decide what moves into the next cycle. Do not let unfinished work drift without an explicit decision.

Use analytics for staffing and cadence decisions

If completion rates repeatedly fall, the problem may be planning quality, assignment size, or team capacity. Analytics should inform those decisions directly.

Keep schedules tied to articles

Assignment work is most useful when it points clearly to an article outcome. Scheduling without a likely output path creates administrative motion without editorial value.

Common mistakes to avoid

Treating schedules as a generic task board disconnected from planning.
Creating cycles without clear operating boundaries.
Leaving assignments in outdated states.
Ignoring overdue work until the cycle is already slipping.
Reviewing cycle performance without comparing it to the previous period.
Carrying work forward informally instead of through the cycle workflow.

How this page connects to the rest of the handbook

Use this page together with:

Clusters and Topic Planning for the upstream structure of work,
Article Lifecycle and Editor for the downstream output of assignments,
Editorial Workflow for the full end-to-end system view.