Help Center
< All Topics
Print
Posted
Updated
Byadmin

MinistryCentral Europe

1. Purpose of This Playbook

This playbook defines how Content Editors operate day to day within MinistryCentral Europe.

It exists to:

  • Enable safe, confident editing
  • Protect canonical authority
  • Ensure consistency across documentation
  • Reduce ambiguity and escalation fatigue

If you are a Content Editor, this document describes how you work, not just what you are allowed to do.

2. The Content Editor Role (In One Sentence)

Content Editors transform reviewed drafts into clear, consistent, canonical documentation — without changing meaning, authority, or intent.

Editors are stewards of clarity, not authors and not decision-makers.

3. What Content Editors Own

Content Editors are responsible for:

  • Clarity and readability
  • Structural coherence
  • Terminology consistency
  • Alignment with existing canonical documents
  • Preparing content for canonical publication
  • Maintaining editorial standards over time

Editors ensure documentation is understandable, navigable, and trustworthy.

4. What Content Editors Do NOT Own

Content Editors do not own:

  • Governance decisions
  • Canonical definitions
  • Policy creation
  • Course design
  • Instructor relationships
  • Platform configuration
  • Publication authority beyond delegated scope

If a change alters meaning, scope, authority, or policy, it must be escalated.

5. Where Content Editors Work

Primary Workspace: Notion

  • Draft refinement
  • Structural cleanup
  • Editorial comments
  • Status tracking (Draft → Review → Approved)

Canonical Workspace: Echo Knowledge Base

  • Final publication
  • Minor non-substantive corrections
  • Maintenance following Change Management Rules

Editors do not treat Echo KB as a drafting environment.

6. Editorial Workflow (Step by Step)

Step 1 — Intake

  • Content arrives via Notion, Word, or handoff
  • Status: Draft

Step 2 — Editorial Pass

Editors focus on:

  • Headings and flow
  • Paragraph clarity
  • Redundancy removal
  • Terminology alignment

Meaning and intent must be preserved.

Step 3 — Alignment Check

Verify:

  • No contradiction with canonical documents
  • Terminology matches existing standards
  • Scope is appropriate for intended audience

Conflicts must be escalated.

Step 4 — Approval Readiness

Before marking Approved, confirm:

  • Open questions resolved
  • Ownership is clear
  • Canonical placement is obvious
  • Formatting aligns with KB standards

Step 5 — Canonical Publication

  • Content is copied into Echo KB
  • Categories and structure applied
  • Links verified
  • Publication is intentional and deliberate

After publication, the KB version becomes canonical.

7. What Editors May Change Directly

Editors may directly edit:

  • Grammar and spelling
  • Formatting and layout
  • Headings and structure
  • Sentence clarity
  • Non-substantive clarifications

These changes must not alter meaning or authority.

8. What Requires Escalation

Always escalate if a change:

  • Alters meaning or intent
  • Introduces policy or authority
  • Changes scope or audience
  • Affects governance or workflow
  • Contradicts another canonical document

Escalation is expected and protective.

9. Common Editorial Pitfalls

  • ❌ “Just fixing a small thing” in canonical docs
  • ❌ Publishing without alignment checks
  • ❌ Assuming intent instead of clarifying
  • ❌ Optimizing style at the cost of accuracy
  • ❌ Editing governance documents casually

When in doubt: pause and escalate.

10. Editorial Mindset

Effective Content Editors:

  • Value clarity over cleverness
  • Prefer consistency over creativity
  • Optimize for future readers
  • Leave clear decision traces
  • Protect the system quietly

Success is measured by trust and stability, not speed.

11. Relationship to Other Documents

Content Editors must be familiar with:

  • Content, Platform & Documentation Operations Guide
  • Documentation Workflow
  • Status Lifecycle & Canonical Rules
  • Notion → KB Publishing Rules
  • Formatting & Style Guidelines
  • Change Management Rules

This playbook operationalizes those documents — it does not replace them.

12. Acknowledgement

Content Editors are required to:

  • Read this playbook fully
  • Follow it consistently
  • Acknowledge completion during onboarding

Table of Contents
Scroll to Top