FEZA innovation – Home
← All products

Platform development for your learning content

Education Technology

Online Learning Platform Software

Bring lessons, assessments and student access together within your education workflow. We will choose the scope of the online learning platform we will build around your content structure, live lesson needs and completion criteria.

  • Courses and chapter structure
  • Time-limited student access
  • Assignments reviewed by tutors
Laptop displaying a video player beside an open book, graduation cap and certificate
  1. Discovery
  2. Scope and quote
  3. Development

When video links, assignments and student lists are separate

When lesson videos sit on another channel, assignments in email and student lists in spreadsheets, tutors must investigate each student's stage again. New students receive links individually. Expired access makes it unclear which content should close; corporate participants bring different account owners into the same list.

Defining content order and access conditions together makes education management clearer. Courses, chapters and lessons will be linked to student enrolment in the project. Content availability, viewing information and assessment results will be separate records; clicking a link alone will not be presented as learning achievement.

Learning information between channels

  • Lesson access and assignment submissions are checked through separate lists.
  • Tutors assemble current student status from different sources.

Tracking through the course

  • Content order, student access and submission records will be scoped together.
  • Completion conditions will be defined separately according to your organisation's rules.

From enrolment to video lessons, tests and tutor assessment

Choose a course chapter as an example. We will discuss which content students see first, how they join live lessons and who reviews open-ended assignments. Describe completion rules together with missing submissions and reassessments. This example will help choose the boundaries of the workflow to be developed.

  1. 01

    Define courses and access

    Tutors' arrangement of chapters, videos and documents will be scoped. Enrolled courses, content release dates and student access periods will be designed through linked rules.

  2. 02

    Link live lessons and submissions

    Live session calendars and attendance records will depend on provider capabilities. Assignment submissions and lesson attendance will be defined as separate records.

  3. 03

    Complete the assessment

    Test scoring can be scoped according to your definitions. Open-ended answers and assignments will await tutor review; course completion will be designed to follow your selected conditions.

From core course content to live lessons and organisational places

Start with your teaching model. A video-and-document course may not need live session management; an assignment-led programme may prioritise tutor reviews. If a completion document is requested, its conditions and verification fields can be designed in the project. Its nature will be assessed within your own programme.

  1. Content and students at the start

    Course structure and access
    Chapter and lesson order, files, enrolment and access periods can be chosen as the first version's core.
    Tests and assignments
    Question banks, defined test scores, submission status and tutor assessment areas can be scoped together.
  2. Additions for your teaching model

    Organisations and completion
    Allocating organisational places, progress reports and completion documents based on your criteria can be added as needed.
  3. Work dependent on external infrastructure

    Live streaming and payments
    Sessions, lesson recordings and payments will be reviewed if your provider offers API access. Storage and video delivery conditions will be defined separately.

Individual course enrolment or places allocated to employees

Individual enrolment and a company purchasing employee places create different management needs. We will choose access start dates and reporting responsibilities around your teaching model. If both are required on one platform, organisational boundaries and tutor access will be scoped separately.

Participant assignment

Individual participation
Students will be linked to courses through the defined enrolment workflow.
Organisational places
An organisation's administrator can be given a workflow to allocate places to employees.

Access start

Individual participation
Periods can depend on course release or enrolment dates.
Organisational places
The effect of assignment and programme start dates on access periods will be defined.

Completion reports

Individual participation
Students' own progress and assessments will be scoped.
Organisational places
Organisation administrators will see only selected summaries for their own participants.

Separate tutor, student and organisation administrator areas

Permission to edit content should not imply access to every student's file. The platform we will build will scope tutors' courses, organisation administrators' participants and students' own areas as separate relationships. We will choose necessary personal fields in report exports according to the educational purpose.

Tutor course permissions

Lesson uploads, assessment editing and assignment reviews will be selected. Accessible course students and export boundaries will be designed separately.

Student and organisation areas

Students will be scoped for access to enrolled content. Organisation administrators' reports for their own places will be separate from platform administration access.

Personal data and child participation

KVKK, Turkey's personal data protection law, relevant legislation, retention, consent and access logs will be assessed. Where children participate, parental approval and parent views will be considered separately; your organisation operates the platform and is the data controller.

When a live lesson recording appears after student access expires

A live session and the release of its recording may happen on different dates. If course access expires during recording preparation, who can view the new video needs a separate decision. Attending the session does not mean indefinite recording access. This exception can help clarify your education policy.

Sessions, recording publication status and student access periods will be scoped separately. You will decide whether late publication extends access. Recording consent, retention and sharing needs will be assessed in scope, alongside provider recording availability and technical access. Assignment rules for another group's access will be defined explicitly.

When live attendance and recording rights become confused

  • All live attendees may be assumed to have permanent recording access.
  • A new video may be opened to the entire historical student list.

Access defined by periods and publication status

  • Live attendance, recording publication and course access will have different statuses.
  • Your rules will define extension decisions for content published late.

Map video archives to course order and student history

Look beyond file counts when migrating content. Chapter order, earlier student access and the course origins of test results also matter. We will examine lesson names and formats in a sample list without personal data. Fields exportable from the old system will determine migration scope.

  1. 01

    Map lesson structure

    Videos, documents and attachments will be matched to chapters. Content rights and reuse of lessons across courses will be discussed.

  2. 02

    Compare student status

    Enrolment, access expiry, test results and progress fields will be examined in trial transfers. If earlier completion criteria differ, we will choose how new calculations treat them together.

  3. 03

    Assess technical connections

    Video delivery, live lesson and payment connection requirements will be investigated. File migration and provider-based streaming access will be scoped as separate development tasks.

Existing examples for describing your learning platform

Explore student, teacher and institution roles in Algoritma Akademi to make your requirements concrete. Your platform's course structure, live lesson infrastructure and access conditions will be defined separately; the existing product helps discuss scope choices.

Define online learning proposal boundaries with one chapter and access rule

Prepare sample lesson sequences, test structures and assignment review workflows. Explain whether live lessons are needed and who manages organisational places. Together, we will distinguish the first version's content core, additional teaching tools and provider-dependent work.

  • Share your rules for content release and student access expiry.
  • Distinguish completion conditions from viewing information and assessment results.
  • Describe technical access to video, live lesson and payment infrastructure.

The proposal will be prepared around your selected course model. Subscription use, content responsibilities and support scope will be discussed in writing.

How we work

We do not sell an off-the-shelf package: we design the software around your workflow, build the first version in short steps and keep running it after launch.

  1. 01

    Discovery

    We listen to how your business works, your team and the tools you use today.

  2. 02

    Scope and quote

    Modules, priorities and price are set out in a written quote.

  3. 03

    Development

    We show working versions at short intervals and move on with your feedback.

  4. 04

    Setup and migration

    We move your existing records across and help your team get started.

  5. 05

    Support

    We run the software on a subscription and keep it up to date and secure.

Frequently asked questions

Can we protect our video lessons from being copied?

Signed, time-limited video links, player settings that make downloading harder and checks that spot one account being used in several places at once can all be included in the scope. To be clear: no system can fully stop someone recording their screen. The aim is to make copying laborious and traceable.

What would we use for live lessons?

Live lessons need a video conferencing service. If your organisation has one in use, connecting it to the platform is scoped in the discovery meeting; if not, we help you choose a suitable service. Recording attendance and making recordings available to learners afterwards belong to the same scope.

Can we see whether learners actually complete the lessons?

Yes, the platform is designed to record it: which lesson was opened, how much of the video was watched and where the learner stopped. Knowing where learners drop off as a group is the most useful signal for improving the content, and the reports are built to answer exactly that question.

Can companies enrol their staff in bulk?

Corporate accounts can be included in the scope. A company holds a number of seats, assigns them to its own staff and sees completion reports in its own admin view. How seats are defined is decided with you in the discovery meeting.

Can we move our existing course content to the new platform?

Videos, documents and learner lists can be moved across. Transferring progress records or certificate history from another platform depends on what that platform can export and is scoped per project.

Can a student submit an unfinished assignment after access expires?

Content viewing periods and submission deadlines can be defined as separate rules. Your course policy will determine whether submissions close or selected assignments remain open; student-facing statuses will follow that choice.

Can a live lesson recording be opened to another course group?

Assignment to courses and groups can be treated as a separate publishing decision. Consent, retention and sharing needs will be assessed; if the provider supplies files or connections, the technical workflow will be reviewed separately.

How is the price set?

After a discovery meeting we prepare a written quote covering the scope, the modules and the setup work. The software is provided on a monthly or annual subscription.

Do we receive the source code?

In our standard model the software is provided on a subscription and the source code is not transferred. If you need a different model, it is agreed in a separate written contract.

Who is responsible for what is done with the software?

We build and operate the software. The business using it is responsible for how it is used, the data entered and the content published; the details are set out in the service agreement.

Related products

Bring your teaching model onto your own platform

Share course structures and student access rules so we can choose the scope of the platform we will build together.

  • Courses and chapter structure
  • Time-limited student access
  • Assignments reviewed by tutors