Layover Companion & Document Wallet
Pickup countdowns and wake-up protection in real local time, offline maps and destination briefs, and an encrypted crew document wallet with expiry reminders — all working with no connection.
The hours between duties, handled.
Pickup is the only alarm that really matters.
A layover has one hard constraint and a lot of soft ones. The hard one is pickup — and it is exactly the thing a time-zone change, a hotel clock and a phone with no signal conspire to get wrong. The countdown and wake-up protection run on the device, in the local time of where you actually are, and do not depend on a connection to fire.
- Pickup countdown and wake-up protection, in current local time
- Offline maps and the destination brief for where you landed
- Weather, currency and practical destination information
- Recommendations sized to the layover you actually have
- Trip photos, filed against the trip
The wallet, readable with no signal.
Passports, visas, crew IDs, licences, certificates and manuals live in an on-device wallet with expiry reminders. The point of holding them locally is the border queue, the hotel desk and the ramp check — the three places where “let me just load that” is not an option.
Document wallet
Every crew document in one place, encrypted on the device and readable offline.
Expiry reminders
Visas, medicals, licences and certificates, surfaced before they lapse rather than after.
Smart documents
Search inside documents, and cross-check them against the roster ahead — the destinations you are actually going to.
Airline knowledge base
Manuals and operational documents from the airline, in the same wallet as your own.
Document checks are informational and are based on the documents and dates you provide. The product does not encode immigration or visa law and does not tell you whether you may legally enter a country.
Photograph it once, and stop thinking about it.
A receipt is captured, read by OCR, converted at the right rate, validated against policy and queued. If there is no connection it queues anyway and submits itself when there is one — which is the only workflow that survives contact with an actual trip. Submission and approval are tracked through to the outcome.