Bring the schedule into focus
Import the flight programme, check it against the source and review each amendment.

THE FLILU PLATFORM
Explore 22 planned modules connecting flight schedules, crew rosters, qualifications, crew services and safety workflows.
ONE PRODUCT / CONNECTED WORKFLOWS
Flilu is being developed as a modular airline crew management system. Core workflows are designed to share context while keeping authority, confidential data and airline environments clearly separated.
EXPLORE THE SYSTEM
Select a domain or open a module to explore the defined scope. The modules describe the planned product scope. Capabilities scheduled for later phases are identified within each module.
22 modules
Manage company settings, operating bases, departments and delegated authority within each airline’s environment.
Controlled user onboarding and offboarding; role administration; airline-specific operating settings.
Bring commercial schedules into a reviewable, versioned flight programme.
Import weekly PDF schedules; compare amendments; retain source files and reviewed corrections; use Excel as an alternative input. Additional layouts, scanned-document extraction and schedule feeds are roadmap extensions.
Link crew demand to the actual aircraft and its approved configuration.
Aircraft registrations, types and variants; seating and crew minima; base and operational requirements; approved rest-facility evidence where applicable.
Check licences, ratings, medical certificate status and recent experience when assessing assignment eligibility.
Role and seat privileges; aircraft type and variant qualifications; restrictions and expiry dates; external work and supporting records. Access to detailed medical information is restricted.
Make each scheduling decision explainable against an approved rule version.
Flight time, flight duty periods, duty periods and rest calculations; acclimatisation and reference time; cumulative history; crew composition restrictions; clear statuses for missing data and unsupported cases.
Connect sectors, positioning and rest into workable duties and rotations.
Manual and assisted pairing construction; report and release times; continuity between sectors and bases; accommodation requirements and approved exceptions.
Build a roster around coverage, availability and individual eligibility.
Weekly and monthly views; fixed activities; clear conflict explanations; versioned approval and publication. Automatic generation and advanced fairness objectives are roadmap capabilities.
Distinguish available reserve crew from crew who are eligible for the required assignment.
Separate reserve and standby categories; notification and call-out history; protected rest and contact periods; coverage and utilisation.
Understand the crew consequences of delays, cancellations and replacements.
Planned and actual times; effects on subsequent rest; delayed reporting; commander’s discretion records where applicable; replacement checks and recovery coordination.
Test an alternative before changing the live roster.
Separate what-if scenarios; impact comparison; revalidation before applying changes; detection of updates to the live roster. Automated recovery with multiple planning objectives is a roadmap capability.
Give every unresolved operational issue a visible owner and next action.
Record severity, deadlines, evidence and escalation; confirm the transfer of open issues between shifts.
Connect the published duty to the journey that gets a crew member there.
Pickup and drop-off requirements; travel times and rest opportunities; supplier and driver acceptance; versioned changes; completed services and costs. Routing optimisation is a later extension.
Track assignment versions, message delivery and crew acknowledgement separately.
SMS text messages and portal notices; message templates; delivery attempts; acknowledgement of the specific assignment version; protected contact windows. Additional providers and channels are phased extensions.
Give crew a clear view of their own schedule and the changes that affect them.
Responsive web access; roster and documents; transport details; acknowledgements; requests and fitness declarations. Native mobile applications are not part of the initial scope.
Assess leave requests against crew capacity, qualifications and operational coverage.
Leave requests and approval; capacity impact; basic preferences. Duty swaps, open-duty requests, structured bidding and preferential bidding are planned for later phases.
Keep training results connected to the privileges they enable or restrict.
Training prerequisites; instructor and examiner authorisations; signed results; recent experience requirements; controlled activation and suspension of qualifications. Full resource optimisation is a later capability.
Keep arrangements visible when they affect the legality of a duty.
Required accommodation and positioning records; confirmations and linked changes. Expanded supplier booking, cancellation and settlement workflows are planned for later phases.
Give the right person the current document and preserve distribution evidence.
Controlled manuals; crew lists; duty briefings; amendment notifications and inspection evidence packs. Crew-related regulatory outputs require agreed data requirements and verified interfaces.
Connect crew operations with protected reporting and evidence-based safety actions.
Twelve safety workstreams cover governance, reporting, hazards, risk, corrective and preventive actions, performance and assurance. Planners receive authorised operational restrictions; confidential report details remain access-controlled.
See the gap between the operation you plan and the crew capacity available.
Initial views of crew supply, demand and qualification expiries; future scenarios for recruitment, attrition, promotion, fleet changes and training requirements.
Distinguish operational activity, cost estimates and pay-related calculations, with traceable inputs.
Crew coverage; planned and actual duty and block times; notification acknowledgements; transport performance; initial cost exports. Detailed pay calculations and forecasting are planned extensions.
Build a shared product without sharing one airline’s operational data with another.
Separate airline environments; access limited by role; audit trails; retention and recovery; versioned interface specifications. Third-party connections require verified access and agreed data mappings.
HOW IT FITS TOGETHER
A shared data model is intended to connect flight versions, duties, qualifications, approvals, notifications and services—without blurring who is authorised to decide.
Import the flight programme, check it against the source and review each amendment.
Match duty coverage with crew qualifications, work history, rest requirements and approved rules.
Assess the impact, test an alternative and publish a traceable change.
Keep crew notices, transport arrangements, actual times and safety actions aligned with the published plan.
A CLEARER VIEW OF CREW OPERATIONS
Explore the modules, operational workflows and implementation approach behind Flilu.