MinistryCentral Europe
1. Purpose of This Guide
This guide defines the Course Coordinator role within MinistryCentral Europe.
It explains:
- What Course Coordinators are responsible for
- How they interact with Instructor Coordinators, Editors, and Media
- Where their authority begins and ends
- How course content moves from concept to canonical learning material
This is an operational guide, not an onboarding checklist.
2. The Role in One Sentence
Course Coordinators ensure that courses are structurally coherent, complete, and ready for editorial and platform processing.
They own course design and readiness, not instructor relationships or platform mechanics.
3. What Course Coordinators Own
Course Coordinators are responsible for:
- Course scope and learning outcomes
- Lesson sequencing and internal logic
- Alignment with curriculum standards
- Ensuring all required materials exist
- Preparing content for editorial review
- Declaring when a course is “ready for editors”
They are accountable for learning coherence and completeness.
4. What Course Coordinators Do NOT Own
Course Coordinators do not own:
- Direct instructor communication
- Pastoral follow-up or encouragement
- Intake of raw instructor material
- Canonical documentation authority
- Editorial wording or style enforcement
- Platform configuration (WordPress, LearnDash, Elementor)
- Video hosting or media pipelines
If a task touches those areas, it must be coordinated or escalated, not absorbed.
5. Relationship to the Instructor Coordinator (Critical)
Instructor Coordinator (Distinct Role)
The Instructor Coordinator serves as the primary liaison to instructors.
They own:
- Instructor communication
- Expectations setting
- Material intake (text, video, notes)
- Follow-up and encouragement
- Pastoral sensitivity and tone
Course Coordinator Relationship
Course Coordinators:
- Receive instructor materials via the Instructor Coordinator
- Do not independently chase or manage instructors
- May communicate directly only when explicitly coordinated
- Focus on structuring and preparing received material
This separation protects:
- Instructor relationships
- Course quality
- Project velocity
6. Where Course Coordinators Work
Primary Working Areas
- Notion (course planning, structure, readiness tracking)
- LearnDash (course and lesson structure only)
- Coordination meetings or documentation
Not Primary Tools
- Echo KB (read-only, canonical reference)
- Elementor
- Platform or plugin settings
- Media hosting tools
7. Course Structure Expectations
Recommended Hierarchy
- Course
- Sections (few, meaningful)
- Lessons (primary teaching unit)
- Topics (only if necessary)
- Quizzes (usually lesson-level)
Rules of Thumb
- If a lesson is very long → split it
- If many topics are required → lesson scope is unclear
- If many sections exist → course scope may be too broad
Course Coordinators enforce structure, not style.
8. Working With Content Editors
Course Coordinators:
- Deliver complete, organized, and clearly structured material
- Flag unclear or incomplete areas
- Do not rewrite instructor content without agreement
- Do not bypass editorial review
- Accept editorial feedback as part of the lifecycle
Editors own clarity, consistency, and canonical preparation.
9. Working With Media & Video Contributors
Course Coordinators:
- Ensure required videos are identified per lesson
- Confirm lesson-to-video mapping
- Do not upload videos to WordPress
- Do not embed media independently unless authorized
All media follows the Video Usage Policy and is coordinated via Media roles.
10. Lifecycle of Course Content
Course-related materials follow the same lifecycle as documentation:
- Idea / Draft
- Review
- Approved
- Canonical (published)
- Maintenance
A course is not live until its components meet canonical standards.
11. Common Pitfalls to Avoid
- ❌ Acting as Instructor Coordinator
- ❌ Acting as Content Editor
- ❌ Publishing or editing canonical material
- ❌ Allowing partial or structurally unclear courses
- ❌ Making platform changes to “move things along”
Speed never overrides coherence.
12. Escalation Guidelines
Escalate when:
- Instructor material conflicts with curriculum standards
- Course scope changes materially
- Required materials are missing or delayed
- Governance questions arise
- Platform constraints affect course design
Escalation is expected and supported.
13. Relationship to Other Documents
Course Coordinators must be familiar with:
- Content, Platform & Documentation Operations Guide
- Documentation Workflow
- Status Lifecycle & Canonical Rules
- Video Usage Policy
They are not required to read:
- Platform & Technical Governance
- Elementor Do / Don’t Guide
- CSS or performance rules
14. Summary
- Course Coordinators own course structure and readiness
- Instructor Coordinators own instructor relationships
- Editors own clarity and canonical preparation
- Platform leads own technical integrity
Clear separation enables speed, trust, and scale.