NeftalyApp Courses Partner Invest Corporate Charity Divisions

Neftaly Email: sayprobiz@gmail.com Call/WhatsApp: + 27 84 313 7407

Tag: Technical

Neftaly is a Global Solutions Provider working with Individuals, Governments, Corporate Businesses, Municipalities, International Institutions. Neftaly works across various Industries, Sectors providing wide range of solutions.

Neftaly Email: sayprobiz@gmail.com Call/WhatsApp: + 27 84 313 7407

  • NeftalyCHAR IMPLEMENTATION PLAN – 2026

    NeftalyCHAR IMPLEMENTATION PLAN – 2026

    To the Chairperson of Neftaly Kingdom Royal Committee Mr. Clifford Legodi, all Neftaly Kingdom Royal Committee Members, Neftaly Royal Chiefs and all Neftaly Human Capital.

    Kgotso a ebe le lena. 

    1. Executive Summary

    Our mission is to deliver a comprehensive suite of 15 Funded and 5 Non-Funded courses. By leveraging a specialized 3-person Human Capital team, we map technical expertise against rigorous compliance standards. This plan ensures that every learner is not only trained but also “captured” within the digital evidence ecosystem required by our funders.


    2. Course Categorization & Scope

    The curriculum is divided into two distinct streams to ensure that funded mandates are met without neglecting community-based non-funded programs.

    Stream A: Funded Programs (Priority Compliance)

    • Information Technology: Computer Training, Network Engineering, Systems Development, Technical/Systems Support.
    • Business & Management: Bookkeeping, Project Management, Entrepreneurship, Data Capturing.
    • Creative & Design: Graphic Design.
    • Social & Life Skills: Life Skills, Life Skills/S2S, Advice and Referral.

    Stream B: Non-Funded Programs (Community Impact)

    • Advice, Referral & Paralegal Services.
    • Programming & Technical Support.
    • Web Development & Computer Skills / Web Design.
    • HIV/AIDS Awareness.


    3. Human Capital Mapping (The Royal Team)

    We utilize a “Triad Model” where each member holds a specific pillar of the implementation sheet.

    I. Linda: The Academic & Quality Lead

    Role Alignment: Linda is the primary driver of the “Instruction” column on the implementation sheet.

    • Technical Execution: Conducts theoretical and practical sessions for high-complexity courses (Network Engineering, Systems Development).
    • The “Paper Trail”: She doesn’t just teach; she prepares Assessor Reports and Meeting Minutes, which are the legal backbone of funded projects.
    • Intervention: Identifies student learning challenges, ensuring our “Completion Rate” (a key funded KPI) remains high.

    II. Dube: The Operational & Compliance Specialist

    Role Alignment: Dube manages the “Data & Evidence” columns.

    • S2S Academy Management: Directly assists students with the S2S program, ensuring seamless digital learning.
    • Evidence Custodian: Handles the heavy lifting of scanning registers and uploading photo/video evidence to OneDrive.
    • Statistical Reporting: Translates daily attendance into the Training Reports required for funding drawdowns.

    III. Project Lead: Strategy & Governance

    Role Alignment: This role bridges the gap between the classroom and the Funder.

    • Policy Compliance: Ensures all activities align with Education and Training policies.
    • Quality Assurance: Audits the work of Linda (Assessments) and Dube (Statistics) to ensure zero errors in reporting.
    • Sustainable Integration: Manages the Non-Funded stream to ensure it doesn’t detract from Funded obligations.


    4. Operational Workflow (The Implementation Cycle)

    To manage 20 courses with 3 people, we follow a synchronized weekly cycle:

    1. Phase 1 (The Intake): Dube registers students and sets up profiles on the Education System.
    2. Phase 2 (The Delivery): Linda facilitates the sessions while Dube captures live evidence (photos/videos).
    3. Phase 3 (The Upload): Dube scans registers; Linda marks tasks and updates the system.
    4. Phase 4 (The Report): The Lead compiles the statistics for the final weekly “Royal” Performance Report.

    5. Detailed Weekly Schedule: The Royal Standard

    This schedule ensures 100% coverage of the 20 proposed courses.

    Staff Member: Linda (Facilitator/Assessor)

    Time BlockMonday – WednesdayThursdayFriday
    08:00 – 13:00Core Facilitation: Network Engineering / Systems Dev / Computer SkillsPractical Lab: Technical Support & Graphic Design sessionsAcademic Admin: Marking assessment tasks & feedback
    13:00 – 16:00Business Block: Bookkeeping & Project ManagementStudent Support: 1-on-1 interventions for struggling learnersDocumentation: Compiling Assessor Reports & Minutes



    Staff Member: Dube (Operations/S2S)

    Time BlockMonday – WednesdayThursdayFriday
    08:00 – 13:00S2S Academy: Active student support and profile managementEvidence Collection: Scanning registers from all sessionsReporting: Compiling the weekly Training Report
    13:00 – 16:00Registration: Onboarding new students for Funded/Non-FundedDigital Filing: Uploading photos/videos to OneDriveStats: Finalizing the weekly attendance statistics


    Staff Member: Project Lead (Strategy/Oversight

    Time BlockMonday – WednesdayThursdayFriday
    08:00 – 13:00Compliance Watch: Reviewing adherence to training policiesInternal Audit: Verifying Dube’s registers against Linda’s profilesFunder Liaison: Submitting weekly progress to stakeholders
    13:00 – 16:00Non-Funded Stream: Managing HIV/AIDS & Paralegal program flowQuality Check: Reviewing marked assessments for accuracyStrategic Review: Planning the upcoming week’s curriculum

    6. Risk Mitigation & Compliance

    • Evidence Loss: Dube’s role includes a daily OneDrive sync to ensure no data is lost.
    • Assessment Backlog: Linda has dedicated “Friday Blocks” for marking to ensure feedback is never delayed.
    • Audit Readiness: By separating the Facilitator (Linda) from the Statistician (Dube), we create a “Check and Balance” system that prevents fraudulent reporting.

    To reach these ambitious targets within the 3-month period (January – March 2026), we must implement a high-velocity throughput strategy. With the addition of Itu, we now have a “Double-Stream” delivery model, allowing us to run two specialized classes simultaneously while Dube handles the massive S2S data flow.


    1. Target Breakdown Table (Jan – Mar 2026)

    FunderProgramTotal Target3-Month (Q1) GoalMonthly Avg
    DSDComputer, Network, Bookkeeping, Systems Dev2406020
    DSDLife Skills60015050
    AccentureLife Skills / S2S2500625208
    AccentureAdvice & Referral50012542
    AccentureICT & Business Modules45011237
    ModularAdvice, Programming, Web, HIV/AIDS61015251
    ModularCertificate Logistics600600Once-off

    2. 3-Month Achievement Strategy

    To hit these numbers, we will use three specific “Engines”:

    Engine A: The S2S Mass-Processor (Led by Dube & Itu)

    • The Target: 625 S2S learners in 3 months.
    • How we reach it: We will treat the first hour of every day (09:00 – 10:00) as the “S2S Portal.”
    • Tactics: Dube handles the registration and login profiles for 15-20 new learners daily. Itu provides technical support in the lab to ensure they complete their digital modules. This ensures we hit the 208 per month requirement without interfering with afternoon technical classes.

    Engine B: The Technical Rotation (Led by Linda & Itu)

    • The Target: 20 Networking/Systems Dev and 37 Accenture ICT learners monthly.
    • How we reach it: Using the parallel teaching method.
    • Tactics: * Room 1 (Linda): Focuses on DSD high-compliance courses (Bookkeeping/Systems Dev).
      • Room 2 (Itu): Focuses on Creative/Tech (Graphic Design/Web Design/Computer Training).
      • By splitting the technical courses, we double our capacity to 40 learners per time block instead of 20.

    Engine C: The Logistics Blitz (Led by Project Lead & Dube)

    • The Target: 600 Certificates delivered.
    • How we reach it: Dedicated “Logistics Fridays.”
    • Tactics: During February, every Friday from 13:00 to 16:00 is designated for certificate sorting and courier dispatch. Dube scans the collection registers as evidence immediately to satisfy Modular Mining’s requirements.

    3. Monthly Milestone Roadmap

    Month 1: January (Foundation & Onboarding)

    • Focus: Launching the S2S platform and enrolling the first 210 Accenture learners.
    • Key Action: Start the DSD Computer Training and Life Skills blocks as per the calendar (09:00-11:00).
    • Compliance: Dube ensures all Jan registers are uploaded to OneDrive by Jan 30th.

    Month 2: February (Peak Production)

    • Focus: High-intensity technical delivery.
    • Key Action: Linda ramps up Network Engineering and Systems Development. Itu begins the Graphic Design and Web Design cohorts.
    • Certificate Blitz: Start the once-off 600 certificate delivery process for Modular Mining.

    Month 3: March (Assessment & Close-out)

    • Focus: Finalizing Portfolios of Evidence (PoE).
    • Key Action: Linda and Itu focus on marking and “Assessor Reports” to ensure all learners are graded.
    • Reporting: The Project Lead compiles the Q1 DSD Quarterly Report and the Accenture Quarterly Milestone Report for submission.

    4. How the “Core Four” Team hits the targets

    MemberContribution to the Numbers
    LindaEnsures the 172 specialized learners (Networking/Systems/Project Mgmt) are competent and graded.
    ItuManages the ICT & Creative volumes (Web, Graphics, Computers) and assists with S2S technical lab flow.
    DubeThe “Data Machine”—he is responsible for the 2,500 S2S entries and the scanning of 100% of registers.
    Project LeadThe “Closer”—audits the evidence to ensure 100% of the 4,440 targets are legally defensible for funding.

    5. Risk Mitigation

    • If attendance is low: Dube will flag “At-Risk” learners by Wednesday each week.
    • If power/internet fails: Itu will have “Offline Theory” modules ready for the Computer Training classes so that no instructional time is lost.
    • Load Balancing: If Linda is overwhelmed with marking, Itu will take over the “Advice and Referral” sessions to free up her time.

  • NeftalyP409-8-2-11-12 Neftaly Chancellor Daily Meetings Report Meeting — 15 January 2026

    NeftalyP409-8-2-11-12 Neftaly Chancellor Daily Meetings Report Meeting — 15 January 2026

    To the CEO of Neftaly, Neftaly Malatjie, Royal Committee Chairperson Clifford Legodi, Neftaly Royal Chiefs, and Human Capital


    Kgotso a ebe le lena

    1. Opening

    The Neftaly Chancellor Daily Meeting was officially opened with an opening song led by Ms Linda Tivane, followed by an opening prayer conducted by Ms Itumeleng Malete.

    1. Attendance

    The following members were present:

    Jeffery Motapina

    Linda Tivane

    Itumeleng Malete

    Phidelia Dube

    1. Daily Planning and Matters Discussed
      3.1 Linda Tivane

    Linda Tivane indicated that she would be responsible for the following tasks:

    Writing and compiling meeting minutes

    Conducting system imports

    Transferring the learners’ list to OneDrive

    Opening and organising a new folder for the 2026 academic year

    3.2 Jeffery Motapina

    Mr Jeffery Motapina informed the meeting that he planned to:

    Conduct a face-to-face induction session focusing on Information and Communication Technology (ICT)

    3.3 Itumeleng Malete
    Itumeleng Malete stated that he planned to:

    Conduct a face-to-face session on computer keyboard shortcuts

    Provide training on Microsoft PowerPoint, Word, and Excel

    Compile a complete list of students for course booking purposes

    3.4 Phidelia Dube

    Ms Phidelia Dube reported that she was:

    Working on S2S activities

    Compiling contact numbers for advice and referrals, as requested by Mr Jeffery Motapina

    1. Daily Challenges

    The following challenges were reported during the meeting:

    4.1 Linda Tivane

    Tivane reported that she was unable to complete system imports due to slow system loading and system access issues.

    4.2 Jeffery Motapina

    Motapina reported difficulties in registering some students on the Education system due to technical challenges.

    4.3 Phidelia Dube

    Dube reported that her system was not opening, which prevented her from completing assigned tasks.

    4.4 Itumeleng Malete

    Malete also reported system access challenges, which affected her productivity.

    1. Feedback Report
      5.1 Linda Tivane

    Tivane reported that she successfully:

    Created folders on OneDrive

    Uploaded all required registers

    Wrote and compiled all meeting minutes

    Added new students to the spreadsheet

    5.2 Jeffery Motapina

    Motapina reported that he successfully:

    Conducted a face-to-face ICT session

    Covered desktop usage, mouse usage, hardware, and software

    Compiled statistics for ICT activities

    5.3 Phidelia Dube

    Dube reported that she successfully:

    Completed S2S activities

    Registered two (2) students in the Education system

    Compiled statistics for S2S activities

    5.4 Itumeleng Malete

    Malete reported that she successfully:

    Conducted a face-to-face ICT session

    Covered PowerPoint and keyboard shortcuts

    Registered two (2) students in the Education system

    Compiled ICT statistics

    1. Closing and Adjournment

    The meeting concluded with a closing song led by Ms Phidelia Dube, followed by a closing prayer conducted by Ms Itumeleng Malete.

    There being no further matters to discuss, the meeting was formally adjourned.

    Prepared by:
    Linda Tivane
    Kgotso a ebe le lena

  • NeftalyP409-8-2-11-9 Neftaly Chancellor Daily Challenges Report Meeting — 15 January 2026

    NeftalyP409-8-2-11-9 Neftaly Chancellor Daily Challenges Report Meeting — 15 January 2026

    The CEO of Neftaly, Mr Neftaly Malatjie
    Royal Committee Chairperson, Mr Clifford Legodi
    Neftaly Royal Chiefs
    Human Capital Department

    Opening Greeting:
    Kgotso a ebe le lena

    1. Opening

    The meeting was officially opened with an opening song led by Ms Linda Tivane, followed by an opening prayer conducted by Mr Jeffery Motapina.

    1. Attendance

    The following members were present:

    Jeffery Motapina
    Linda Tivane
    Itumeleng Malete
    Phidelia Dube

    1. Daily Challenges Discussed

    3.1 Linda Tivane
    Linda Tivane reported that she was unable to complete the imports because the system was taking a long time to load. She further indicated that her system was not opening properly on the day of the meeting.

    3.2 Jeffery Motapina
    Jeffery Motapina reported that he was unable to register some of the students in the Education system due to technical challenges.

    3.3 Phidelia Dube
    Phidelia Dube reported that her system was not opening, which prevented her from completing her assigned tasks.

    3.4 Itumeleng Malete
    MItumeleng Malete also reported that his system was not opening, which affected her ability to work effectively.

    1. Closing

    The meeting concluded with a closing song led by Ms Phidelia Dube, followed by a closing prayer conducted by Itumeleng Malete.

    1. Adjournment

    There being no further matters to discuss, the meeting was formally adjourned.

    Prepared by:
    Linda Tivane

  • NeftalyP409-8-2-11-12 Neftaly Chancellor Daily Meetings Report Meeting Minutes — 13 January 2026

    NeftalyP409-8-2-11-12 Neftaly Chancellor Daily Meetings Report Meeting Minutes — 13 January 2026

    Daily Planning and Challenges Report
    Meeting Minutes

    Meeting Type: Daily Report Meeting
    Chairperson: Neftaly Chancellor
    Minute Taker: Linda Tivane

    1. Opening

    The meeting officially started with an opening song led by Linda Tivane.
    This was followed by an opening prayer conducted by Itumeleng Malete.

    1. Attendance

    The following members were present at the meeting:

    Jeffery Motapina

    Linda Tivane

    Itumeleng Malete

    1. Apologies

    Phidelia Dube

    1. Purpose of the Meeting

    The purpose of the meeting was to:

    Plan daily activities

    Allocate responsibilities

    Report on challenges experienced during daily tasks related to student registration, learner records, and administrative support for Neftaly.

    1. Planning: Discussions and Responsibilities

    5.1 Linda Tivane
    Linda Tivane is responsible for:

    Writing the meeting minutes

    Doing student imports

    Creating a learner list for the year 2026 using a spreadsheet

    Assisting students with opening and setting up S2S profiles

    5.2 Itumeleng Malete
    Itumeleng Malete is responsible for:

    Creating a learner list for course bookings using a Word document

    Registering students online on the education system

    5.3 Jeffery Motapina
    Jeffery Motapina is responsible for:

    Registering students

    1. Challenges Reported

    6.1 Linda Tivane

    Google Alerts were not opening.

    Reports could not be pushed because the Ideas system was not working.

    6.2 Itumeleng Malete

    Unable to push reports on the Ideas platform because the system was not working.

    1. Actions / Way Forward

    The challenges were noted by the meeting.

    Technical system issues affecting Google Alerts and the Ideas platform need to be resolved.

    Reports will be completed and submitted once the systems are working.

    1. Closing

    The meeting was closed with a closing song led by Linda Tivane.
    A closing prayer was conducted by Jeffery Motapina.

    Meeting Adjourned

  • NeftalyP409-8-2-11-9 Neftaly Chancellor Daily Challenges Report Meeting Minutes — 13 January 2026

    NeftalyP409-8-2-11-9 Neftaly Chancellor Daily Challenges Report Meeting Minutes — 13 January 2026

    Neftaly Chancellor Daily Challenges Report Meeting

    Meeting Minutes

    1. Meeting Information

    Date: 13 January 2025

    Chairperson: Neftaly Chancellor

    Minute Taker: Linda Tivane

    1. Attendance

    The following members were present at the meeting:

    Jeffery Motapina

    Linda Tivane

    Itumeleng Malete

    1. Apologies

    Phidelia Dube

    1. Purpose of the Meeting

    The purpose of the meeting was to report on daily challenges experienced during work activities and to record issues that prevented the submission of reports.

    1. Challenges Reported

    5.1 Linda Tivane

    Challenges experienced:

    Unable to complete Google Alerts because they were not opening.

    Unable to push reports because the Ideas system was not working.

    Explanation:

    Technical system issues prevented task completion.

    5.2 Itumeleng Malete

    Challenges experienced:

    Unable to push the report on the Ideas platform.

    Explanation:

    The Ideas system was not working.

    1. Actions / Way Forward

    The reported challenges were noted.

    Technical issues with Google Alerts and the Ideas platform need to be resolved.

    Once systems are working, reports will be submitted.

    1. Closing

    The meeting was closed with a closing song led by Linda Tivane.
    A closing prayer was conducted by Jeffery Motapina.

    Meeting Adjourned

  • Neftaly Logistics and Technical Setup

    Neftaly Logistics and Technical Setup

    Logistics Setup

    1. Venue Selection and Preparation:

    • Physical Events:
      • Choose a venue that accommodates the number of participants comfortably.
      • Ensure the venue has the necessary amenities like seating arrangements, restrooms, and accessibility features.
      • Check for adequate lighting, ventilation, and climate control.
      • Arrange for refreshments and catering if needed.
    • Virtual Events:
      • Select an online platform that supports the number of attendees and required features (e.g., Zoom, Microsoft Teams, WebEx).
      • Ensure the platform has capabilities for breakout rooms, screen sharing, and interactive tools.

    2. Equipment Setup:

    • Physical Events:
      • Arrange for audio-visual equipment such as microphones, speakers, projectors, and screens.
      • Set up recording devices if the event needs to be documented.
      • Ensure there are sufficient power outlets and extension cords.
      • Test all equipment beforehand to avoid any technical issues during the event.
    • Virtual Events:
      • Ensure all participants have access to a computer or mobile device with a stable internet connection.
      • Provide guidelines for participants to test their audio and video equipment before joining the session.
      • Prepare backup equipment (e.g., an extra laptop or microphone) in case of technical failures.

    3. Signage and Directions:

    • Physical Events:
      • Place clear signage to guide participants to the event location, registration desk, restrooms, and other key areas.
      • Use directional arrows and maps if the venue is large or complex.
    • Virtual Events:
      • Send detailed instructions and login information to participants in advance.
      • Provide a step-by-step guide on how to join the virtual event and use its features.

    Technical Setup

    1. Platform Configuration:

    • Virtual Events:
      • Configure the online platform settings to match the event requirements (e.g., participant permissions, breakout rooms, recording options).
      • Set up registration and login processes to ensure smooth access for participants.
      • Enable features like polls, Q&A, and chat to encourage interaction.
      • Test the platform thoroughly to ensure all features are working correctly.

    2. Internet Connectivity:

    • Physical Events:
      • Ensure the venue has a strong and reliable internet connection.
      • Set up a dedicated network for the event if possible to avoid bandwidth issues.
    • Virtual Events:
      • Advise participants to use a stable and high-speed internet connection.
      • Provide troubleshooting tips for common connectivity issues.

    3. Technical Support:

    • Physical and Virtual Events:
      • Have a technical support team on standby to assist with any issues during the event.
      • Provide a helpdesk or contact number for participants to reach out to if they encounter problems.
      • Conduct a dry run or rehearsal to identify and resolve potential technical issues.

    4. Backup Plans:

    • Physical Events:
      • Prepare for contingencies like power outages or equipment failure by having backup power sources and spare equipment.
    • Virtual Events:
      • Have alternative platforms or communication channels ready in case of technical difficulties.
      • Plan for seamless transitions if the primary platform encounters issues.

    By carefully organizing the logistics and technical setup, you can ensure that the event runs smoothly and participants have a positive and engaging experience. Whether it’s a physical or virtual event, thorough preparation and testing are key to success.

Layer 1
Login Categories