How editing mentorship works at Kelposandu
Structured, long-term guidance for editors working in software-based post-production environments. Each stage is designed around your current level, your tools, and your actual project work — not a generic curriculum.
From intake assessment to independent practice
Every engagement begins with an honest look at where you are technically. Gaps in workflow, tool familiarity, and decision-making habits surface quickly when working through real material — and that diagnostic work shapes everything that follows.
Technical intake
A detailed review of your current editing environment, software version, project history, and recurring friction points. No questionnaire — a working session.
Structured sessions
Regular one-on-one meetings built around your active projects. Techniques are applied in context, not taught in isolation against artificial examples.
Between-session work
Targeted exercises and assigned tasks tied to software-specific skills — timeline management, colour handling, audio sync, export configuration.
Progress calibration
Periodic reviews compare early-session recordings to current work, making skill development measurable rather than a vague impression of improvement.
Screen-share editing review
Your timeline is the working surface. The mentor identifies structural issues, redundant cuts, or pacing decisions directly within your sequence — not through abstract description.
Software-specific technique drilling
Whether the gap is in DaVinci Resolve's node graph, Premiere's multicam workflow, or Final Cut's magnetic timeline — the technique addressed matches the tool you actually use.
Decision-making discussion
Beyond technique, sessions examine editorial choices — why a cut was made, whether it serves the sequence's rhythm, and what the alternatives were. This builds judgment, not just technical fluency.
Written session notes
Each session concludes with a written summary of what was covered, what to practise before the next meeting, and any software-specific references or documentation links.
What changes over a full engagement
The table below reflects the kinds of development that typically occur across a sustained mentorship — these are directional patterns, not guarantees. Results depend on frequency, the complexity of your starting point, and how much independent practice happens between sessions.
Editing software depth comes from repeated application, not explained theory.
Most editors who struggle with advanced software features are not missing knowledge — they are missing structured repetition in a context where mistakes have consequences and someone can identify the source of the problem immediately. That is what consistent mentorship provides. Kelposandu has been running this model since 2022.
| Focus area | Early sessions | Later stages | Software context |
|---|---|---|---|
| Timeline organisation | Single-track flat edits, inconsistent naming, no markers | Layered sequences with clear track logic and colour-coded labels | Premiere / Resolve |
| Colour grading workflow | Applying LUTs without understanding correction vs. grade distinction | Primary correction before creative grade, consistent node structure | DaVinci Resolve |
| Audio handling | Reliance on camera audio, no reference levels, manual clip-by-clip adjustments | Consistent gain staging, use of audio tracks for dialogue, music, FX separation | Premiere / Avid |
| Export configuration | Single delivery format, trial-and-error codec selection | Multiple preset outputs, understanding of bitrate, container, and codec relationships | Media Encoder / Compressor |
| Editing pace and judgment | Cutting on action without considering rhythm, no reference to sequence purpose | Decisions tied to narrative intent, willingness to question assembly cuts | All platforms |