FlightChecker was built around a real operational problem: flight schedules stored in spreadsheets had to be manually checked against current flight information.

The goal was simple — reduce repetitive checking and make discrepancies easier to identify.

Tourism operations teams work with large flight schedules where timing changes can directly affect airport transfer planning.

Manually comparing spreadsheet records with external flight sources is repetitive, time-consuming, and makes important discrepancies harder to spot.

I designed and built FlightChecker to bring that workflow into a single application.

An operator uploads an Excel flight schedule, and the system:

Parses and normalizes the flight records

Retrieves current flight information

Matches scheduled flights with live data

Identifies delays and schedule inconsistencies

Highlights the flights that require attention

Instead of reviewing every flight manually, the operator can focus on the exceptions.

The project was shaped around the actual workflow rather than starting with a predefined software concept.

I translated the operational process into product logic, designed the validation flow, built the frontend and backend, and connected spreadsheet processing with external flight data.

This is the type of work I focus on: identifying repetitive business processes and turning them into practical digital tools.

FlightChecker demonstrates how a manual spreadsheet-based process can be transformed into a structured workflow where operational exceptions become easier to identify and review.