Inkpilots

Clusters and Topic Planning

Workflow

Clusters are the planning system of Inkpilots. They turn isolated content ideas into an editorial structure that can actually be scheduled, assigned, and measured. In the current product, cluster planning is not a flat list. It is a managed tree of clusters and titles supported by planning notes, guidance, drag-and-drop organization, and duplicate-awareness tools. You can think clusters are categorization for your content, in a newpapers perspective, sport, politics, art are considered clusters. Pillars to support a main theme. This page explains how to use that planning layer as a real operating surface rather than as a simple backlog.

What this area is for

Use clusters and topic planning when your team needs to:

  • define editorial themes before work is scheduled,
  • organize topic titles under the right thematic group,
  • maintain a backlog outside the active cycle,
  • move titles between clusters and planning states,
  • add planning notes to topics before assignment,
  • detect possible overlap with existing published work,
  • turn a planned title into an assignment when it is ready.

Clusters are upstream from execution. Their job is to make later scheduling cleaner and less ambiguous.

How the planning surface is structured

The current cluster view behaves like a lightweight editorial file system. It includes:

  • a root planning tree,
  • cluster folders,
  • topic title items inside those clusters,
  • a backlog area for work that has not yet been placed in a cluster or cycle,
  • drag-and-drop movement between planning locations.

This is important because planning usually changes over time. Inkpilots supports that reality directly. Teams can reorganize topics instead of pretending the first categorization was final.

What a cluster represents

A cluster should represent a real editorial direction, not just a vague theme label.

In practice, clusters are useful when they help the team answer questions like:

  • what subject area does this work belong to,
  • where does this topic fit in the broader content program,
  • which work is related closely enough to be planned together.

The stronger the cluster definition, the easier it becomes to build schedules and create assignments without re-deciding the editorial purpose every time.

What users can do in the cluster tab

The current cluster surface supports more than naming themes. Users can:

  • create clusters,
  • update cluster details,
  • delete clusters,
  • create topic titles under a cluster,
  • delete planned titles,
  • move titles between planning locations,
  • store planning notes for a selected title,
  • rerun similarity checks,
  • create editorial assignments from ready topics.

This makes the cluster tab the place where raw ideas become structured, decision-ready work.

Similarity checks runs when you title is created under a cluster, the run ensures you are not creating same title twice. So, system does not depend on peoples memory.

Planning notes and topic detail

Inkpilots includes a detail panel and note-writing flow for selected topics. This is where the team can capture the context that makes a title meaningful before it reaches a schedule.

Use planning notes for:

  • angle definition,
  • intended audience,
  • internal constraints,
  • useful examples or references,
  • questions that must be answered before assignment.
  • insert images if already exists, or attach data

We are going to implement Google Docs and Microsoft Office file sharing to create a frictionless workflow.

This is a better use of the planning layer than rushing into article drafting too early. If the team still needs to decide what the topic means, it is still a planning problem.

Backlog

The backlog is a pool for pre-ideas. Use backlog to keep your topic ideas to fill, later drag and drop ideas when they are ready and condifent to start implementation. Select a cluster then assign it to a colleague.

Similarity alerts and overlap control

One of the most valuable parts of the planning workflow is similarity checking. The current cluster area can surface overlap signals against existing material and lets users rerun similarity checks when needed.

This should be treated as a planning safeguard, not as a cosmetic warning.

Use it to catch:

  • titles that are too close to already published content,
  • repeated angles under different names,
  • topic cannibalization before assignments are created,
  • weakly differentiated ideas that should be merged or rewritten.

Similarity checks does not includes total articles, instead we search a summary of each article to find the possible cannibalization.

The earlier duplication is caught, the cheaper it is to fix.

Guidance and planning assistance

The cluster area also includes editorial guidance snapshots and recommendation-style cards. These are there to help planners notice opportunities, overlaps, and refresh needs without manually re-auditing the whole tree.

Users should treat guidance as operational assistance, not as a substitute for editorial judgment. It helps surface where attention may be needed, but the planner still decides how the structure should evolve.

Guidence system is open to improvement and heavily dependent on the data you will create and we collect from your visitors. AI guidance can direct you even if you do not know what you are doing.

When a topic is ready to move forward

A planned title is ready for the scheduling layer when:

  • it belongs to the right cluster,
  • its purpose is clear,
  • planning notes are sufficient for assignment,
  • duplication risk has been checked,
  • the team can assign it without redefining the idea.

At that point, the next step is not more planning. The next step is assignment and timing through Schedules and Content Cycles.

Recommended planning practice

Plan in clusters, not in isolated titles

Single-title planning usually creates fragmented programs. Clusters force the team to think in themes and related work.

Keep the backlog intentional

Backlog should hold work that is not yet structured or scheduled. It should not become a permanent landfill of unclear ideas.

Use notes before assignment

If a topic needs explanation, capture that explanation in planning notes before handing it to a schedule or editor.

Resolve overlap early

Similarity warnings are most useful before assignments, drafts, and review time are invested.

Move topics deliberately

Drag-and-drop planning is powerful, but the point is not constant movement. The point is to place work where it reflects the current editorial model accurately.

Common mistakes to avoid

  • Treating clusters as decorative labels instead of real editorial groupings.
  • Sending topics into schedules before their intent is clear.
  • Ignoring planning notes and relying on memory or informal chat.
  • Leaving duplicate or near-duplicate ideas unresolved.
  • Using article drafting to solve unclear planning decisions.

How this page connects to the rest of the handbook

Use this page together with:

Related guides