FEZA innovation – Home
← All products

Development around your driving school's timetable

Driving School

Driving School Software

Plan driving lessons around instructor, vehicle and learner availability. In the driving school software we will build, lesson records, documents and exam tracking will be scoped around your internal workflow.

  • Instructor and vehicle availability
  • Theory and driving attendance
  • Exam records linked to learners
Car, steering wheel and binder beside a tablet displaying a lesson schedule
  1. Discovery
  2. Scope and quote
  3. Development

An available instructor is not enough when the car or learner is unavailable

An empty instructor slot in the weekly driving timetable is only one requirement. The vehicle may be undergoing maintenance or the learner may be at work. When a lesson changes, reception contacts several people; attendance kept elsewhere means recalculating remaining lesson time. Discovering missing documents before an exam requires another check.

Consider all resources in the same decision to follow changes more clearly. The project will scope instructor, vehicle and learner availability together. Scheduled and completed lessons will have different states. Documents, payments and exam information will link to the same learner, with separate responsibility for each area.

Conditions outside the weekly timetable

  • A vehicle under maintenance can appear available in the lesson list.
  • Scheduled time may be counted as completed lesson time.

A lesson workflow planned around resources

  • Instructor, vehicle and learner availability will be considered in one plan.
  • Attendance and completed time will be verified separately from remaining lesson calculations.

From learner enrolment to driving lessons and exam preparation

Illustrate one learner's week with a blank timetable. We will discuss who checks submitted documents, how instructors mark lessons complete and who enters exam dates. Show differences between theory and driving records too. The workflow to be developed will follow these tasks and your defined lesson-time rules.

  1. 01

    Define the file and agreement

    Required learner fields, document submission status and agreed payment plans will be scoped as separate records. Access to medical certificates will be considered separately from other administration.

  2. 02

    Plan lessons with their resources

    Instructor, vehicle and learner availability will link to weekly appointments. Maintenance status and postponements will be designed around selected planning rules.

  3. 03

    Record completion and the next exam

    Instructor entries for attendance and duration can be scoped. Remaining lesson calculations will use these records; exam dates and results will be separate internal tracking areas.

From driving timetables to documents and payment tracking

We can shape the first release around planning and lesson records. Learner access, instalment reminders and detailed reports can be selected as additional needs. You will define time and absence rules, and we will discuss who records changes. Internal management will not replace official system procedures; any required file exports will be assessed separately.

  1. Driving school management for the initial release

    Driving plans and attendance
    Instructor, vehicle and learner availability, plus completion records for theory and driving lessons, can be included in the first release.
    Documents and exams
    Document submission status, exam dates and results can be scoped in separate fields within each learner's file.
  2. Extensions for your school

    Learner area and payments
    Remaining lessons, next appointments, exam and payment views, instalments and management summaries can be added according to need.
  3. Work requiring technical access

    Vehicle data and messages
    Vehicle tracking, messaging and accounting connections will be reviewed if your provider permits access. Outputs for official procedures will be scoped separately.

Theory classes and individual driving appointments need different planning

Class attendance for theory and vehicle scheduling for driving may require different structures. Explain how you record duration and attendance for each lesson type so we can identify separate checks. In the software we will build, learners will retain a shared file while resource and completion rules are scoped for each lesson type.

Resources required

Theory lesson
The teaching group, assigned instructor and classroom timetable are considered.
Driving lesson
Individual instructor, vehicle and learner availability are assessed together.

Attendance record

Theory lesson
Each pupil's attendance can be recorded separately for the same class.
Driving lesson
Appointment completion and recorded lesson duration will be scoped together.

Impact of changes

Theory lesson
Changing a shared lesson identifies the group's notification needs.
Driving lesson
The effect of a vehicle or instructor change on the learner's appointment is reviewed.

Give document checks and instructor lesson entries separate permissions

Seeing their lessons need not give instructors access to every learner document. We will choose the tasks reception, instructors and the school manager need. Together we will define how payment reports, document viewing and lesson corrections are separated within account roles.

Instructor timetable

Access to assigned lessons and learners, attendance entry and duration corrections will be scoped. Changing historical records will be considered separately from marking daily lessons.

Reception and management

Required fields for documents, exams, schedule changes and payments will be defined. Summary reporting and export boundaries will be discussed separately.

Reviewing learner data

KVKK, Turkey's personal data protection law, relevant legislation, medical certificate access, retention and action logs will be considered in scope. Your school is the data controller; clarify document requirements with your authorised adviser.

When a driving lesson is postponed close to the learner's exam

A vehicle unavailable for maintenance may require a new lesson time. The learner's exam date remains separately recorded in the same file. Counting the postponed lesson as completed misstates remaining time; changing only the calendar can hide checks needed for an approaching exam. We will agree what reception and instructors should verify.

In the software we will build, maintenance records, postponed lessons and exam appointments will be linked with separate states. Showing outstanding lessons under your time rules will be scoped. Exam assessment and official bookings remain within your authorised team's process. Finding a free calendar slot will not mean automatic exam registration. Previous results and new plans for learners retaking an exam will also be distinguished.

When postponement is disconnected from exam preparation

  • Cancelled lessons may remain in completed-time totals.
  • New lesson needs for a learner approaching an exam may be missed.

Preparation planned with separate states

  • Completion, postponement and maintenance will be considered separately.
  • Remaining lesson calculations and exam information will be tied to authorised staff review.

Separate scheduled and completed lesson time in old driving timetables

Prepare a weekly schedule and attendance sample without personal data. We will check whether listed times represent appointments or completed lessons. If learner lists, instalments and exam histories are in different sources, their matching fields will be assessed separately.

  1. 01

    Map lesson states

    Codes for planned, cancelled and completed lessons will be identified. We will select how duration units, instructor identities and vehicle identities map to the new structure.

  2. 02

    Check the learner's balance

    Remaining lessons and outstanding instalments will be compared in a sample import. We will also review whether document-status fields establish that a document actually exists.

  3. 03

    Investigate vehicle data access

    If your tracking provider offers API access, available fields will be assessed. Inferring lesson duration from vehicle movements and instructor-approved completion records will be scoped as separate issues.

Prepare to discuss driving school teaching and administration

Explore lesson and exam relationships in our learning product and custom development on our service page. Vehicles, lesson-time rules and learner documents will be scoped separately for your project. These examples help you describe your requirements.

Discuss a proposal with a weekly vehicle schedule and attendance sample

Share blank instructor and vehicle lists, lesson states and document-check fields. Explain how you obtain learner availability and who communicates changes. We will define the development scope by choosing the planning core first, then learner views and external connections.

  • Show duration rules for theory and driving lessons.
  • Identify the person responsible for vehicle maintenance and postponed lessons.
  • Explain when you check exams, documents and instalments.

The proposal will follow the agreed internal school workflow. Subscription use, support and provider connections 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

Will notifications to the authorities be made from this software?

No. Official notifications are made through the authorities' own systems and should stay there. The software we build covers the school's internal management: learner tracking, the lesson plan, attendance, payments and reporting. Whether the data needed for the official system can be exported as a file is examined per project; some manual entry between the two systems may remain.

How will the software know the mandatory lesson hours?

Hour and absence rules are defined with you at setup. The software then shows each learner's outstanding hours against those rules and warns before a learner is entered for a test. When regulations change, the rules need updating too; a settings screen that lets you change them yourself can be included in the scope.

Can lesson hours come in automatically from our vehicle trackers?

Some vehicle tracking providers allow data sharing. We look at the system you use in the discovery meeting and tell you plainly whether a connection is possible. If it is not, instructors mark the start and end of each lesson on their phone, and the record is kept with the time.

Will learners be able to see their own information?

A learner view can be included in the scope, showing remaining lesson hours, the next driving lesson, the test date and payment status on the learner's phone. These are the questions learners most often call the office about, and being able to check them themselves makes things easier on both sides.

Can instructor pass rates be reported fairly?

A raw pass rate on its own is not a fair measure, because learners who struggle may not be spread evenly across instructors. We therefore recommend showing such a report alongside the lesson hours each learner received and their number of test attempts. The report is a starting point for a conversation, not a performance grade.

Can the same driving appointment be kept when the vehicle changes?

We can scope changing the vehicle assignment separately while retaining learner and instructor links. The design will check the new vehicle's availability and maintenance status; your school will determine who approves the change.

Will a postponed lesson affect the remaining time shown before an exam?

We recommend keeping scheduled and completed time separate. We can scope postponed lessons not counting as used time, with the remainder displayed according to your rules. Exam assessment stays within your authorised team's process.

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

Let's review your driving timetable and its resources

Share your instructor, vehicle and learner arrangements so we can define the initial software scope.

  • Instructor and vehicle availability
  • Theory and driving attendance
  • Exam records linked to learners