Video summary

Kultor Cabinet 4 Nov

Main summary

Key takeaways

Educational

Main Ideas and Concepts Covered

  • Purpose of the meeting: Introduce and explain the “Tutor Cabinet” system—a centralized dashboard—so tutors can see key student/course/admin information without manually opening multiple links.

Tutor Cabinet: Main Components

Within the Tutor Cabinet, tutors can access:

  • QC (quality check) results and associated feedback
  • Retention info (e.g., graduation/continuation status by month)
  • Attendance
  • Replacement penalty (how many times a replacement penalty occurred)
  • Project compliance / project-related items (announced/managed via the respective Le(teams))
  • CS/ISM ticket area
    • Used like a checklist/ticket submission system for test/referrals
    • Includes status updates and comments
  • Real-time/period-based views
    • Progress by month via filters (e.g., Sep/Oct/Dec)

Shift: Weekly Feedback → Monthly Feedback

  • The discussion includes a new monthly student feedback form.
  • It is described as lighter/easier than earlier formats.
  • Tutors can submit feedback once per month rather than every 2 weeks or weekly.

Monthly Student Feedback: Content Logic

Feedback includes:

  • Student identity + group/type + lesson timing + module/month
  • Attendance/involvement/completion checkboxes
    • Mapped to how often the child attended within the month
  • Task completion quality, such as:
    • Always present and actively involved + tasks completed well
    • Or cases like only participating on “game day” / refusing tasks
  • Final project submission/link
    • A recording/video link or public link is preferred so parents can view without the student login

Technical/Operational Guidance

  • Use the cabinet tools so items auto-update and auto-record as “sent.”
  • Avoid Control+P, because hyperlinks may break.
  • Download via: File → Export/Download as PDF
  • If a project link needs inclusion, copy/paste the link into the form so it appears correctly in the PDF.

Special Concerns and Clarifications (OTR / Replacements / Responsibility)

  • The meeting discusses OTR (over/other tutor sessions) and how feedback responsibility may shift depending on timing and cabinet refresh.
  • Sunday/Monday refresh timing matters, because it affects:
    • what appears in the list
    • what is considered “sent”
  • If relevant data is missing/not yet updated:
    • verify dates
    • possibly coordinate with the previous tutor

Chatbot and Reminder System (Replacing Weekly General Feedback)

  • A WhatsApp chatbot is described as expected to replace weekly general feedback.
  • If the chatbot has bugs, tutors should submit an issue report including:
    • WhatsApp group name
    • Back-office link
    • Screenshot evidence
    • Explanation in Indonesian (or preferably English)

Course Structure Update: Moving to 36 Lessons (Instead of 32)

A separate section outlines a new course flow:

  • Graduation moved to the 36th meeting
  • Meetings 32–36 are rebalanced to reduce complaints that final projects aren’t finished in time.

Proposed late-meeting flow:

  • 32: students create project content; tutor teaches project planning/related material (“project guide” concept)
  • 33: practice/teaching presentations or mechanics
    • students may feel “project fatigue”
  • 34: includes a Game Day (refresh/entertainment; reduce boredom)
  • 35: complete final project (reserved time)
  • 36: graduation + presentation, plus intro to next material

Methodology / Step-by-Step Instructions (as Presented)

A) Using “Tutor Cabinet” as a Single Access Point

  • Open Tutor Cabinet and navigate from the cabinet’s first page (“one gate system”).
  • For QC/attendance:
    • use built-in views/filters to check progress by month (e.g., September/October/December).
  • For CS/ISM tickets:
    • click into the ticket area
    • fill student name and other fields (test/referral choice, deadline)
    • ensure updates are visible through cabinet status/comments
  • Goal: reduce repeated opening of external Sentral/Info Center pages.

B) Submitting Monthly Student Feedback (PDF-Based Workflow)

  1. In the feedback tool, choose the correct context:
    • go to New monthly personal
    • select student by name (search in list)
    • confirm course type
      • e.g., choose VP English vs VP Indonesia depending on desired feedback language
  2. Select:
    • the month
    • the correct feedback module
  3. Fill checklist/rating components:
    • Attendance/participation level (top/middle/bottom style choices indicating attendance frequency)
    • Involvement/completion indicators
      • e.g., active participation vs minimal participation (“only game days” or refusing tasks)
    • Final project section:
      • add a link to the project (recording/video/project link)
      • prefer links parents can open without student login
  4. Generate the report:
    • download as PDF using: File → Download/Export PDF
    • do not use Control+P (hyperlinks may not open for parents)
  5. Send to parents:
    • copy the created PDF/report details/messages and send via WhatsApp/group as provided
  6. Ensure “sent” status is recorded:
    • after sending, paste/update the same content back into the cabinet’s feedback comments field
  7. Timing rule:
    • cabinet updates weekly with Monday reset/refresh behavior
    • if you miss the refresh window, the system may consider feedback as not sent

C) Project Link Handling and Parent Accessibility

  • Prefer a video link (e.g., YouTube) or another public link when possible.
  • Avoid making links overly public if parent access/permissions or content concerns exist.
  • If no project exists (or the child’s work is limited):
    • use the form logic for “no project” (the “done” state)
    • still submit feedback
  • If attendance affects module/lesson mapping (e.g., the child “jumps” lessons):
    • module/month may shift based on what the child is learning, not just the calendar lesson number

D) Bug/Issue Reporting for Chatbot/Reminders

  • If WhatsApp reminder/chatbot doesn’t work:
    • fill the provided issue form
    • include:
      • WhatsApp group name
      • back-office link
      • screenshot evidence
      • short explanation (English preferred)

E) Handling Missing Entries / Refresh-Related Confusion

  • If students appear missing:
    • verify the update date (the cabinet might show “last update” at a specific cutoff, e.g., end of October)
    • wait for the next update or check again after cabinet refresh
  • If OTR responsibilities are unclear:
    • coordinate with the previous tutor
    • confirm whether feedback was already sent or needs manual completion to ensure “green” sent status appears

F) 36-Lesson Course Flow (High-Level Outline)

Late-course redesign focuses on:

  • enough time to complete final projects
  • reduced boredom via Game Days

Suggested sequence:

  • 32: project teaching + project guide
  • 33: how-to learning + presentation practice
  • 34: includes Game Days (10–15 minutes refreshing activity)
  • 35: dedicated final project completion time
  • 36: presentation + graduation, plus introduction to the next material

Speakers / Sources Featured

  • Alina (referenced via training photo context; no clear speaking lines attributed)
  • Mas Kevin
  • Mas Galang
  • Mas Lukman (also referenced as “Mas Luk”)
  • Mas Fadli
  • Mas Ho
  • Sis Putri
  • Sis Yunik
  • Sis Natania / Natania
  • Sis Fadli (speaker identification in subtitles is ambiguous; may overlap with Mas Fadli)
  • Sis Dika
  • Sis Majid
  • Brother Michael (asked about student feedback / PSPP camera; subtitle text unclear but explicitly named)
  • Uncle Leo
  • Audience/friends on Google Meet/Zoom (individual names largely not captured)

Original video